Affiliate tracking in Microsoft Dynamics 365: a workflow guide
Affiliate programs generate commissions from a separate platform, but the sales team usually lives in the CRM.
When those two systems are not connected, someone has to bridge the gap by hand. This guide describes a real workflow used by an expat insurance provider to pass affiliate identifiers into Microsoft Dynamics 365, and the reporting questions that become answerable once the data is there.
The setup: affiliate commissions in one system, leads in another
William Russell sells health, life, and income protection insurance to individuals and families living abroad. A major acquisition channel is affiliate marketing: bloggers, influencers, and companies serving expat audiences promote the insurance products and earn a commission when a referred visitor becomes a paying customer.
Each affiliate received a unique tracking link from the affiliate marketing platform. When a visitor clicked that link and later bought a policy, the platform recognized the affiliate and paid the commission. That part worked. The gap was downstream: the affiliate platform was not connected to the company's CRM, Microsoft Dynamics 365. A sales agent therefore spent about 1.5 hours every day finding affiliate referrals in the affiliate platform and manually linking them to the matching records in the CRM.
Build or buy: the decision the team faced
The management team recognized that 1.5 hours a day adds up over weeks and months, and that the time would be better spent converting leads and closing deals. The initial plan was to build a custom system that pushed affiliate data into Dynamics. Before committing to that build, the team found an attribution layer that captured UTM parameters and passed them into Microsoft Dynamics 365, making each lead's referring affiliate visible inside the CRM.
Use this checklist when weighing a custom integration against a UTM-based attribution layer:
- Does the affiliate platform already issue per-affiliate tracking links that can carry UTM parameters?
- Can the CRM accept the UTM values as fields on the lead record?
- Will the CRM's own workflow tools be enough to link a lead to the correct affiliate once the identifier is present?
- Is the reporting need limited to source attribution, or does it also require commission calculation inside the CRM?
- How much engineering time would a custom connector consume compared with configuring UTM capture?
In this case, the team dropped the home-grown build and put UTM parameters behind each affiliate link instead.
Field and control map: what moves where
The workflow has three layers, and it helps to be clear about which layer owns which job.
- Affiliate platform: stores the affiliate identity, issues the unique tracking link, and pays commissions when a referred visitor becomes a customer.
- UTM parameters on the affiliate link: carry the affiliate identifier (and any campaign context) through the click into the website visit.
- Attribution layer: captures those UTM values and writes them into Microsoft Dynamics 365 so the lead record shows which affiliate referred it.
- Microsoft Dynamics 365: holds the lead and customer records; its built-in workflow tools automate linking each lead to the correct affiliate.
A useful distinction: the affiliate platform remains responsible for commission payment. The CRM is responsible for showing the source of each lead and customer. Confusing the two is the most common reason teams try to rebuild commission logic inside the CRM when all they actually need is attribution data on the lead.
Worked example: what 1.5 hours a day actually costs
The captured figure is 1.5 hours per day of manual tagging. That arithmetic is simple but worth making explicit:
- Per week (five working days): 7.5 hours.
- Per four-week month: 30 hours.
- Per year (roughly 250 working days): 375 hours.
That is close to ten standard working weeks of one person's time spent on a task that produces no customer conversation. Once the UTM values arrive in Dynamics automatically and the CRM workflow links leads to affiliates, that block of time is released for lead conversion and deal closing.
Reporting questions that become answerable
Because the attribution layer captures source information on leads from every channel, not only affiliates, the marketing team can compare the affiliate program against other initiatives such as Google Ads and SEO. The questions the team can now answer include:
- How many leads and customers come from the affiliate program compared with other marketing efforts?
- How much revenue has the affiliate program generated?
- Which affiliates send the most customers?
With those answers, the team has a clearer view of what is working and what is not, and can make informed decisions about where to invest in customer acquisition.
The outcome
By sending the referring affiliate for each lead directly into the CRM, the team eliminated the 1.5 hours of daily manual tagging. The same data also gave the marketing team a cross-channel view of performance, so affiliate results could be judged alongside paid search and organic search rather than in isolation.
{{OWNER_CUSTOMER_OUTCOME_STATEMENT}}
Frequently asked questions
Does the affiliate platform still pay commissions after this change?
Yes. The affiliate marketing platform continues to recognize the affiliate from the tracking link and pay the commission. The change is that the same affiliate identifier now also reaches Microsoft Dynamics 365, so the CRM can show which affiliate referred each lead without manual tagging.
Do the UTM parameters replace the affiliate tracking link?
No. The per-affiliate tracking link issued by the affiliate platform remains in place. UTM parameters are added behind each affiliate link so the attribution layer can capture the affiliate identifier and pass it into the CRM.
Can this workflow report on non-affiliate channels too?
Yes. Because the attribution layer captures source information on all leads, the team can compare affiliate results with Google Ads, SEO, and other initiatives in the same CRM.