A custom-built, per-tenant AL extension that pulls LinkedIn Lead Gen Form submissions into Dynamics 365 in real time — mapped, deduped, attributed, and auto-routed to the right rep. Built, installed, and supported by ECOSIRE on your environment. One-time license from $199.00 USD for Dynamics 365 BC (build-to-order) — includes 12 months of updates and support.

A custom-built, per-tenant AL extension that pulls LinkedIn Lead Gen Form submissions into Dynamics 365 in real time — mapped, deduped, attributed, and auto-routed to the right rep. Built, installed, and supported by ECOSIRE on your environment.
现在无需付款。此操作会向我们的团队发送报价请求——我们会通过邮件跟进价格和后续步骤。
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.
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
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.
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.
Owns CRM data quality and rep assignment. Needs dedup and routing rules enforced automatically so reps follow up fast and the pipeline stays clean.
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.
在 ecosire.com 上购买许可证并从您的帐户仪表板下载 LinkedIn Lead Gen Forms Connector for Dynamics 365 模块 ZIP。
将 ZIP 解压到服务器上的 Odoo 自定义插件文件夹中(或通过“应用程序”>“从 Odoo.sh / runbot 上的文件安装”上传)。
激活开发者模式,打开应用程序,单击更新应用程序列表,搜索 LinkedIn Lead Gen Forms Connector for Dynamics 365,然后按安装。
打开新菜单,粘贴您的 ECOSIRE 许可证密钥,连接任何外部凭据(Shopify、Amazon、Stripe 等),然后保存。
运行内置连接测试,同步前 10 条记录,并安排定期 cron。如果出现任何问题,请联系支持人员。
| 标准 | 伊科西尔 | 定制建造 | 竞争对手 | 奥杜本机 |
|---|---|---|---|---|
| Real-time LinkedIn Lead Sync API ingestion into BC | ||||
| Field mapping to your custom lead/contact fields | ||||
| Dedup against existing email/company domain | ||||
| Campaign + ad_id attribution stored on the lead | ||||
| Auto-assignment / routing rules | ||||
| Installed and supported on your tenant by an engineer | ||||
| Ongoing maintenance for LinkedIn API version changes | ||||
| Credentials secured in BC Isolated Storage with permission sets |
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.
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.
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.
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.
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.
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.
A custom-built, per-tenant AL extension that pulls LinkedIn Lead Gen Form submissions into Dynamics 365 in real time — mapped, deduped, attributed, and auto-routed to the right rep. Built, installed, and supported by ECOSIRE on your environment.