Track affiliate leads and customers in Microsoft Dynamics CRM
Affiliate referrals often disappear between the click and the CRM record. This guide shows a practical UTM and hidden-field workflow that preserves the referring affiliate through form submission, so Dynamics can report leads, customers, and revenue by affiliate.
Why affiliate attribution needs a CRM trail
Affiliate activity can drive visits without leaving a clear trail in the CRM. A UTM-based workflow closes that gap: the link identifies the partner, the browser retains those parameters during the visit, hidden fields transfer them at submission, and the CRM receives them with the lead. The result is a record-level link between a person and the affiliate who referred them.
Step 1: Build affiliate links with three UTM layers
Give each affiliate a link that encodes three decisions. Set the medium to Affiliates so the channel is unambiguous. Set the source to the partner category, such as Bloggers, Podcasters, or YouTubers. Set the campaign to the individual affiliate's name. That separation matters later: medium rolls up to channel, source rolls up to partner type, and campaign identifies the person. Affiliate platforms may append these parameters automatically, or a UTM builder can generate them consistently.
Step 2: Add hidden fields to website forms
Add hidden fields to the forms people submit, including Contact Us and Request a Quote forms. The fields are Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page, and Landing Page Group. Most form builders support hidden fields, but the exact steps vary by tool, so follow the instructions for the builder in use.
Step 3: Carry the values through submission into Dynamics
When a visitor arrives through an affiliate link, the attribution tool stores the UTM parameters in the browser, allowing the visitor to browse and return later without losing them. On form submission, it writes the parsed affiliate details into the hidden fields. The form tool then captures those values together with the visitor's own details, and the existing form-to-Dynamics route — a direct integration or an intermediary such as Zapier or Make — delivers the full record to the CRM.
What the CRM record contains
What lands in Dynamics depends on what the UTMs encode. With the recommended pattern, an affiliate visit produces Channel = Affiliates, Channel Drilldown 1 = Bloggers, and Channel Drilldown 2 = John Smith. Non-affiliate visits are captured too: an organic Google search, for example, can produce Channel = Organic Search with drilldowns for the search engine, its domain, and the keyword when available. That breadth lets one CRM view compare every channel on the same basis.
Three reports to run in Dynamics
Run three views. First, Leads by Channel, to judge affiliate volume against Paid Search, SEO, and other sources before shifting budget. Second, Customers by Affiliate Type, to see whether bloggers, podcasters, YouTubers, or influencers convert best and recruit more of the winners. Third, Revenue by Affiliate, to rank individual partners by customers and revenue, invest in top performers, and reduce effort on weak ones. The same fields also support lead-to-customer conversion and average deal size comparisons.
Pre-launch checklist
Before scaling, check the chain end to end: every affiliate link carries all three UTM values; values use one spelling and casing convention; hidden fields exist on every conversion form; a test submission arrives in Dynamics with Channel and drilldowns populated; and reports group correctly by channel, type, and affiliate. Fix gaps at the link or form stage, because missing UTMs cannot be reconstructed later in the CRM.
| UTM parameter | Example value | CRM field it feeds |
|---|---|---|
| utm_medium | Affiliates | Channel |
| utm_source | Bloggers | Channel Drilldown 1 |
| utm_campaign | John-Smith | Channel Drilldown 2 |
Recommended pattern; values can be customised to the data you want to collect.
| Report | Question it answers | Decision it supports |
|---|---|---|
| Leads by Channel | How does affiliate volume compare with other channels? | Where to allocate resources |
| Customers by Affiliate Type | Which partner categories produce customers? | Which affiliate types to recruit |
| Revenue by Affiliate | Which individuals produce customers and revenue? | Where to invest more or less effort |
Example reports; exact metrics depend on fields captured in Dynamics.
Frequently asked questions
What UTM values should affiliate links use?
Use consistent UTM values on every affiliate link: medium for the affiliate channel, source for the affiliate type, and campaign for the individual affiliate. When those values are carried through the form into Dynamics, each lead can be grouped by channel, type, and person.
Which hidden fields are needed on the form?
Add hidden fields for Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page, and Landing Page Group. The attribution tool populates them from the visit, and the form tool sends them with the submission.
How does the data reach Microsoft Dynamics CRM?
Send the submission through the route already used for Dynamics — a direct form-to-CRM integration or an intermediary such as Zapier or Make. The hidden-field values travel alongside name, email, and other submitted details.
Which reports are most useful once affiliate data is in Dynamics?
Compare leads across all channels, customers by affiliate type, and customers and revenue by individual affiliate. Together these show whether affiliates beat other channels, which partner categories work, and who deserves more recruitment effort.