SignalSight Conversion Lead streams lead-stage updates from Microsoft Dynamics 365 to Meta in real time. When a lead moves through your pipeline — qualified, junk, won, or lost — those events flow back to Meta so campaigns optimize toward meaningful outcomes instead of raw form submissions.
Before you start
You need a Dynamics 365 account, a SignalSight account, and a Meta CRM Pixel set up in Events Manager. For Pixel ID and access token steps, see Meta (Facebook) CAPI Setup. New users can start with Account Creation.
Get Started
Open the Tracker Creation Wizard under Signal → Trackers and click Create Tracker. You can also add a Dynamics 365 source to an existing tracker from the tracker detail page.
Create a Tracker
Step 1 — Dynamics 365 Source
- Select Microsoft Dynamics 365 from the source list and enter a name for the source.
- Enter your CRM URL (see How to Get CRM URL below).
- Click Login to sign in to your Dynamics 365 account and grant access — the popup closes automatically and takes you to the mapping step. Alternatively, click Connect after entering the URL if your setup supports direct connection.
Configure the Event Name Prefix and field mappings. Leave the prefix empty to send events like Qualified Lead or Junk. With the CRMLeads prefix, events follow the format CRMLeads-Junk. Ensure leadgen ID fields are mapped correctly — this is required for Conversion Leads.
Click Save and Next to continue.
How to Get CRM URL
Log in to Dynamics 365 and copy the root of your instance URL from the browser address bar — for example, https://orgname.crm4.dynamics.com. Paste it into the CRM URL field when creating the source.
Step 2 — Meta CAPI Destination
Create a Meta Conversions API destination. Enter your CRM Pixel ID and access token manually, or use Connect Facebook CAPI to sign in and select the Pixel from your account.
Note
The Pixel must be a CRM Pixel — not your website Pixel. In Events Manager, click Connect Data Sources, select CRM, then Connect. Create a new dedicated Pixel (recommended) so CRM events stay separate from your web Pixel.
Step 3 — Name and Complete
Name your tracker, review the source and destination summary, and click Complete to finish the wizard.
Manage Your Source
Open your tracker at any time to update field mapping or review sent event history. Use Edit Mapping on the Dynamics 365 source to adjust mappings and the CRMLeads event name prefix. The testing feature shows sample lead data if a lead was generated within the last 7 days.
Note
Changing mapping on campaigns that have already finished learning may restart Meta's learning phase. Update mappings carefully once ads are live.
What Happens Next
Once CRM events start flowing, complete the funnel setup in Meta Events Manager. The three guides below cover everything after tracker creation:
- Validation Phase — Meta's 7-day validation window and how to resolve errors.
- Define Your Sales Funnel — map CRM events to funnel stages and set your optimization target.
- Run Conversion Leads Campaigns — campaign objective, ad set, and Conversion Leads optimization settings.
Frequently Asked Questions
Where do I find my Dynamics 365 CRM URL?
Log in to Dynamics 365 and copy the base URL from your browser's address bar — everything up to .dynamics.com (e.g. https://orgname.crm4.dynamics.com), without the path after it.
Should I use Login or Connect?
Use Login to authenticate with your Microsoft account via the popup — this is the recommended path for most setups. Connect is available when you've already entered a valid CRM URL and direct connection is supported.
What is the Event Name Prefix?
It prepends a label to every event sent to Meta. With the CRMLeads prefix, a Junk stage becomes CRMLeads-Junk. You can leave the prefix empty or customize it during setup or later via Edit Mapping.
Can I add Dynamics 365 to an existing tracker?
Yes. Open the tracker detail page and add a Microsoft Dynamics 365 source alongside your existing sources and destinations.