Track AI leads and customers in Microsoft Dynamics
When a new lead appears in Microsoft Dynamics, the usual question is where they came from. Paid search, organic search and social are familiar answers. AI assistants are now a real source too, and most analytics stacks stop at the click rather than following the person through to a closed customer. This guide shows a repeatable way to attach AI referral data to each Dynamics lead and then report on the outcomes.
Why AI source data belongs on the lead record
AI visibility tools can tell you how often a brand is mentioned in AI answers. Web analytics can tell you how many people clicked through. Neither closes the loop to leads and paying customers. Putting the referral source on the Dynamics lead record does close it, because the same record later carries the opportunity and customer outcome.
The practical benefit is comparison. Once AI referral sits alongside organic search, paid search and paid social as a channel value, you can compare volume, close rate and revenue on equal terms. That is more useful than a separate AI dashboard that never touches pipeline data.
Four setup steps
The workflow has four stages: place the tracking code and hidden fields, let the tool write referral values into those fields, capture the values with the form submission, then pass the submission into Dynamics.
- Add the tracking snippet to the website and create four hidden fields on each lead capture form: Channel, Channel Drilldown 1, Channel Drilldown 2 and Channel Drilldown 3. Most form builders either offer a hidden field type or let you add a standard text field and hide it in the settings.
- On each visit, the tool reads technical signals similar to those a web analytics platform uses, classifies the visitor into a channel such as AI Referral, Organic Search, Paid Search or Paid Social, and stores that classification in the browser.
- When the visitor submits a form, the stored values are written into the hidden fields and captured alongside the name, email and other entered details. The tool works with a broad range of form builders, scheduling tools and chat products, including Gravity Forms, Contact Form 7, Wix Forms, Webflow Forms, Typeform, Jotform and Calendly.
- The form tool then creates the lead in Dynamics. Depending on the builder, this can use a built-in Microsoft Dynamics integration, or an automation service such as Zapier or Power Automate. The AI referral values arrive on the lead record next to the contact details, ready for reporting.
What each captured field holds
The four hidden fields form a hierarchy rather than four unrelated labels. Channel is the broad category. The drilldowns narrow it. A separate pair of values records the landing page.
AI referrals do not carry a third level of detail, so Channel Drilldown 3 shows None for them. That is expected, not a tracking failure. The landing page pair answers a different question from the channel pair: the channel tells you which tool sent the visitor, while the landing page tells you which page the tool was recommending.
A worked example
Suppose an architecture firm markets commercial fitout services. A prospective client asks ChatGPT to recommend an architect for a new office fitout, clicks a link in the answer and submits an enquiry form.
The lead record would show Channel as AI Referral, Channel Drilldown 1 as ChatGPT, Channel Drilldown 2 as chatgpt.com and Channel Drilldown 3 as None. The landing page values would show the commercial fitouts page and the /services group.
Read together, those values answer two separate questions. The channel data says the enquiry originated from an AI assistant. The landing page data says the commercial fitouts page was the one being recommended. If that page keeps producing AI-sourced customers, it is a candidate for further investment; if AI referrals cluster on a different page, that page deserves the attention instead.
Four reports worth building
Once the data is on the lead record, the reporting layer can be Dynamics' built-in reports and dashboards, or an external tool such as Power BI, Looker Studio or Tableau. Each of the four reports below answers a different question, and each becomes actionable at a different point, so build them in this order.
The close-rate report is often the most revealing, because lead volume alone can mislead. A channel can look strong on volume while converting poorly. Comparing close rates puts AI referrals next to organic and paid search on the same footing, which is the comparison that should influence where the next marketing budget goes.
To see why AI referrals might convert differently, consider an illustrative scenario: 35% of AI Referral leads turning into customers, against 10% from Organic Search and 7% from Paid Search. Those figures are an example of the pattern to look for, not measured results. The plausible reason is that someone who arrives after asking an AI tool for a recommendation has usually done more research and is better informed about the product or service than someone who clicked a paid search ad. Treat that as a hypothesis your own close-rate report can confirm or reject.
Revenue by landing page turns the analysis into a content decision. If most AI-sourced revenue comes from a small set of pages, those pages show what AI tools are recommending and what buyers respond to. That is a clearer signal than pageviews alone.
Setup checklist
- Tracking snippet installed on every page that hosts a lead capture form.
- Four hidden fields present on each form: Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3.
- A test submission checked to confirm the hidden fields arrive populated, not blank.
- A route into Dynamics chosen: native integration or an automation service.
- Field mapping confirmed so the hidden values land in the intended Dynamics fields.
- At least the Leads by Channel report built before drawing conclusions.
- A note that Channel Drilldown 3 will read None for AI referrals, so it is not mistaken for missing data.
| Field | What it holds | Example value |
|---|---|---|
| Channel | Broad source category | AI Referral |
| Channel Drilldown 1 | The specific AI tool that referred the visitor | ChatGPT |
| Channel Drilldown 2 | The domain the visitor came from | chatgpt.com |
| Channel Drilldown 3 | A further level of detail, where one exists | None for AI referrals |
| Landing Page | First page the visitor landed on | hollowayarchitects.com/services/commercial-fitouts |
| Landing Page Group | Grouped path for that page | /services |
| Report | Question it answers | When it becomes actionable |
|---|---|---|
| Leads by Channel | How many leads arrive each month from each channel? | As soon as you have a month of submissions; it tells you whether AI is a meaningful source at all |
| Customers by AI tool | Which AI tool produces paying customers? | Once deals start closing; if nearly all AI-sourced customers come from one tool, that is the tool to watch closely and optimise for |
| Close rate by channel | What share of leads from each channel become customers? | Once each channel has enough leads to compare rates; it separates quality from volume |
| Revenue from AI by landing page | Which pages produce AI-sourced customers and revenue? | Once revenue is attached to closed deals; it turns the analysis into a content decision |
Frequently asked questions
Why does Channel Drilldown 3 show None for AI referrals?
AI referrals do not have a further level of detail beyond the tool and the referring domain, so the third drilldown is empty by design. A None value there is expected and does not indicate a tracking problem.
Should I use the native Dynamics integration or an automation service?
It depends on the form builder. If the builder has a built-in Microsoft Dynamics integration, that is the shorter path. If it does not, an automation service such as Zapier or Power Automate can create the lead each time a form is submitted, carrying the captured referral values with it.
What information is captured for each lead?
Two groups of values. The channel group records how the visitor arrived, split into the broad channel and up to three drilldown levels. The landing page group records the first page the visitor landed on and a grouped path for that page. Both travel with the form submission into Dynamics.
What should I do if nearly all AI-sourced customers come from one tool?
That is a signal to watch that tool closely and optimise for it. The Customers by AI tool report shows the split, so you can direct effort toward the assistant that actually produces paying customers rather than the one that merely mentions you most often.