Track YouTube Ads leads and customers in Microsoft Dynamics CRM
Website analytics can show that a YouTube ad produced a visit, but it does not by itself show whether that visit became a lead, a customer, or revenue. This guide explains how to carry campaign attribution through a form into Microsoft Dynamics CRM so those later outcomes can be reported by channel, campaign, and ad.
Why visit data is not enough
A visit count alone cannot tell you which campaigns create pipeline. If a visitor from a YouTube ad later submits a form, the CRM record needs to retain where that visitor came from. Without that link, leads and customers in Dynamics CRM cannot be grouped back to the ad, campaign, or channel that produced them, so budget decisions rely on incomplete evidence.
Step 1: Tag each ad with UTM parameters
Start by tagging every YouTube ad destination URL consistently. Use the table below as a naming convention: keep the medium and source stable across campaigns, and use the campaign and term values to identify the specific campaign and ad. Consistency matters more than clever naming, because these values become the drilldown fields in the CRM.
Step 2: Install the snippet and add hidden fields
Install the attribution snippet on the website using the instructions for your platform, then add hidden fields to each relevant form. The fields to create are Channel and Channel Drilldown 1 through Channel Drilldown 4. Most form builders support hidden fields, but the exact steps vary by builder, so use the guidance for the builder you actually use and test a submission end to end before relying on the data.
Step 3: Let attribution persist until form submission
When a visitor arrives, the snippet categorises the visit into a channel such as Paid Social, Paid Search, or Organic Search and stores the attribution in a browser cookie. If the visitor browses the site or leaves and returns before submitting, the stored values remain available. On form submission, the values are written into the hidden fields. Inconsistent UTM naming, such as different capitalisation of the same source, is normalised so the lead is grouped under the correct channel.
Step 4: Send the values into Dynamics CRM
The form tool captures the hidden-field values with the submission and sends them to Microsoft Dynamics 365. From there, the fields on the lead record support reporting. A worked example: a visitor arriving from a tagged YouTube ad might be recorded as Paid Social, with drilldowns identifying YouTube, the campaign name, and the ad name. That single record then lets you count the lead under YouTube Ads and, if it converts, follow the customer and revenue back to the same campaign and ad.
Three reports to build first
Use three starting reports. First, leads by channel for a high-level monthly view of where leads originate. Second, customers by campaign to see which campaigns produce buyers rather than only enquiries. Third, revenue by ad to compare revenue against cost and judge return per ad. Together these move reporting from visits to pipeline, customers, and money.
Pre-launch checklist
Before launch, check that every YouTube ad URL carries the same parameter structure, that hidden fields exist on every form you intend to measure, and that a test submission from a tagged URL creates a Dynamics record with the expected channel and drilldowns. Also test a return visit after browsing, and review capitalisation and naming in UTM values so grouping stays clean. If any check fails, fix the tagging or form setup before drawing conclusions from the reports.
| UTM parameter | Recommended value for YouTube Ads | Purpose |
|---|---|---|
| UTM Medium | paidsocial | Identifies the medium as paid social |
| UTM Source | youtube | Identifies YouTube as the source |
| UTM Campaign | Name of your campaign | Groups results by campaign |
| UTM Term | Name of your ad | Groups results by ad |
Recommended convention from the guide; adapt names consistently across all ads.
| Hidden field | Example value for a YouTube Ads visitor | What it identifies |
|---|---|---|
| Channel | Paid Social | Broad channel |
| Channel Drilldown 1 | YouTube | Platform |
| Channel Drilldown 2 | Brand Campaign | Campaign |
| Channel Drilldown 3 | Red Ad | Ad |
Illustrative example based on the tagged values in the guide.
| Report | Group by | Decision it supports |
|---|---|---|
| Leads by channel | Channel and month | Where to focus effort for more leads |
| Customers by campaign | Campaign and month | Which campaigns to fund or pause |
| Revenue by ad | Ad | Return on each ad against its cost |
Starting reports; exact fields depend on your Dynamics CRM setup.
Frequently asked questions
What is the basic setup for tracking YouTube Ads in Dynamics CRM?
Add consistent UTM parameters to the destination URL behind each YouTube ad, place a site snippet that stores the visit source in a browser cookie, add hidden attribution fields to your forms, and send submitted form data to Dynamics 365. The hidden fields carry channel and drilldown values into the CRM record for reporting.
Will attribution still be captured if someone browses before submitting a form?
Yes. The cookie retains the parameters while the visitor browses or returns later, so the values can still be written into the form when they eventually submit it.
What happens if UTM values are inconsistent across campaigns?
Inconsistent capitalisation or naming, such as youtube versus YouTube in a source value, can be normalised so those leads are grouped under the same channel instead of being split across reports.
Which reports become possible after the fields are in Dynamics CRM?
Once channel and drilldown fields are present on leads, you can group by channel for overall lead volume, by campaign for customers, and by ad for revenue, then compare those outcomes with spend to judge return.