LinkedIn Lead Gen Forms Connector for Dynamics 365

Key Features

Real-time (or scheduled) lead capture via the LinkedIn Lead Sync API, driven by a Business Central Job Queue entry you can pause, reschedule, or run on demand

AL table and page extensions that map every LinkedIn form question — including custom/hidden fields — to your Dynamics 365 lead and contact fields

Configurable dedup rules matching on email and company domain before record creation, so existing leads/contacts are updated rather than duplicated

Campaign attribution: LinkedIn campaign name, creative, ad account, and ad_id stored on each lead for closed-loop reporting

Auto-assignment and routing logic (round-robin, by territory, or by form) writing the owner/salesperson directly on the new record

OAuth2 credentials and refresh tokens stored in BC Isolated Storage — never in plain config or source

Idempotent ingestion using LinkedIn's lead ID so re-polling never creates a second copy of the same submission

Error capture and retry: failed pulls are logged to a setup-visible activity log instead of silently dropping leads

Dedicated permission set scoping who can configure the connector and view raw LinkedIn payloads

Multi-form and multi-campaign support — one tenant can ingest from several LinkedIn Lead Gen Forms with per-form mapping

Optional Dataverse / Power Platform path when your CRM front end is Dynamics 365 CE rather than BC, kept in sync via the BC OData/REST API

Sandbox-first deployment: validated in your test environment before per-tenant publish to production

Built to order, done for you

No DIY setup — a working app, built, installed and supported by ECOSIRE.

You order

Start with a one-time build price. We scope it with you at kickoff.

We build & install

ECOSIRE builds, configures and installs it on your Dynamics 365 Business Central.

Go live + support

You go live in about 2–4 weeks, with a post-launch support window.

About this Product

Your LinkedIn ads are generating leads — but they sit in LinkedIn Campaign Manager until someone exports a CSV days later, by which point the prospect has gone cold. This connector closes that gap by wiring the LinkedIn Lead Sync API directly into your Dynamics 365 / Business Central tenant.

ECOSIRE builds this as a per-tenant AL extension (not a generic AppSource download). We register a LinkedIn developer app against your Lead Gen Forms, store the OAuth credentials securely using BC's Isolated Storage, and stand up a Job Queue entry that polls the LinkedIn Lead Sync API on the cadence you choose — or receives near-real-time pushes where your LinkedIn ad account supports webhooks. Each submission is parsed, field-mapped, and written into your lead/contact tables via table extensions and codeunit business logic.

Because it's built to order, the field mapping matches your schema — LinkedIn question keys to BC fields including custom fields you've already added. Dedup runs against email and company domain before any record is created, so you don't pollute your CRM with duplicates. Campaign name, creative, and ad_id are captured for attribution, and a configurable assignment rule routes each lead to the right salesperson or team.

What you get is honest and scoped: a real engineer registers the LinkedIn integration, writes and tests the AL extension, deploys it to your sandbox first, then publishes per-tenant to production with the right permission sets. After go-live we keep it running — LinkedIn API versions change, and we handle that under support. No vague "connect anything" promises, just one job done properly: every LinkedIn lead in Dynamics 365, fast.

What you get

A per-tenant AL extension (.app) built for your Business Central version, deployed to sandbox then published to production

LinkedIn developer app registration and OAuth2 connection configured against your Lead Gen Forms and ad account

A field-mapping configuration matching LinkedIn form questions to your specific lead/contact schema, including custom fields

A configured Job Queue entry plus dedup, attribution, and auto-assignment rules set to your business logic

A dedicated permission set and setup page for ongoing administration of the connector

Source code, deployment notes, and a short admin runbook covering reconnection and mapping changes

Who this is for

B2B Demand-Gen Marketer

Runs LinkedIn lead-gen campaigns and is tired of exporting CSVs. Wants leads in Dynamics 365 within minutes, tagged with the campaign that produced them so they can prove ROI.

Sales Operations Manager

Owns CRM data quality and rep assignment. Needs dedup and routing rules enforced automatically so reps follow up fast and the pipeline stays clean.

Dynamics 365 / BC Administrator

Responsible for the tenant. Prefers a scoped, per-tenant AL extension with proper permission sets and Isolated Storage over a hand-rolled integration nobody can maintain.

How LinkedIn Lead Gen Forms Connector for Dynamics 365 Compares

Criterion	ECOSIRE	Custom Build	Competitor
Real-time LinkedIn Lead Sync API ingestion into BC	Included	Partial support	Partial support
Field mapping to your custom lead/contact fields	Included	Included	Partial support
Dedup against existing email/company domain	Included	Partial support	Partial support
Campaign + ad_id attribution stored on the lead	Included	Partial support	Partial support
Auto-assignment / routing rules	Included	Partial support	Partial support
Installed and supported on your tenant by an engineer	Included	Not included	Not included
Ongoing maintenance for LinkedIn API version changes	Included	Not included	Partial support
Credentials secured in BC Isolated Storage with permission sets	Included	Partial support	Partial support

Frequently Asked Questions about LinkedIn Lead Gen Forms Connector for Dynamics 365

How long does delivery take, and what does the build process look like?

Typical delivery is 2–4 weeks from kickoff, depending on how many forms and how complex your field mapping and routing rules are. We start with a short scoping call to confirm your BC version, lead/contact schema, and LinkedIn ad account. We then register the LinkedIn app, build and unit-test the AL extension, deploy to your sandbox for you to validate against live test submissions, and only then publish per-tenant to production.

What happens with ongoing support and updates after go-live?

LinkedIn periodically versions its Lead Sync API and OAuth scopes, and Business Central has regular major releases. Under our support arrangement we monitor those changes and update the extension so ingestion keeps working — including token reconnection if credentials expire. You can also request mapping or routing changes as your campaigns evolve. Support terms are agreed at purchase; we don't leave you with an extension that silently stops pulling leads.

Is this a Microsoft AppSource app I can install myself?

No — and we're explicit about that. This is a build-to-order per-tenant extension. ECOSIRE registers the LinkedIn integration, writes the AL code to match your schema, and installs it on your environment. That's why the mapping and routing fit your tenant exactly rather than forcing a generic, one-size-fits-all layout.

Does this work if our CRM is Dynamics 365 Customer Engagement (CE) rather than Business Central?

Yes. The core connector targets Business Central, but where your front end is Dynamics 365 CE / Dataverse we build a path that lands leads in Dataverse via the BC OData/REST API and Power Platform integration. We confirm the exact topology during scoping so the leads end up wherever your sales team actually works.

How do you stop duplicate leads from entering our CRM?

Every ingestion run is idempotent on LinkedIn's own lead ID, so re-polling the same submission never creates a second record. On top of that, configurable dedup rules match incoming leads against existing email and company domain — when a match is found we update the existing record and log the touch instead of creating a duplicate.

How are the LinkedIn API credentials kept secure?

OAuth2 client credentials and refresh tokens are stored in Business Central Isolated Storage, scoped to the extension — never in plain setup fields or in source control. Access to the configuration and to raw LinkedIn payloads is gated behind a dedicated permission set, so only authorized administrators can view or change the connection.