Track SEO leads and customers in Microsoft Dynamics CRM
Organic search can bring plenty of visits while leaving the commercial result unclear. By storing arrival details on every form submission and passing them into Microsoft Dynamics CRM, you can connect new leads, customers and revenue to the pages and channels that produced them.
Why visit data is not enough
Analytics tools show organic visits easily, but visits alone do not reveal whether those visitors became enquiries, customers or revenue. The missing link is usually stored on the lead record itself. When arrival data travels with the form submission into the CRM, later reporting can answer commercial questions instead of stopping at traffic.
Four-step setup and launch checklist
- Install the attribution snippet on the website so arrival information can be detected and stored in the browser, in a similar way to analytics measurement.
- Add six hidden fields to each lead-capture form: Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page and Landing Page Group.
- Let the snippet classify the visit into a channel such as Organic Search, Paid Search or Paid Social and retain the details until a form is completed.
- On submission, the form tool sends the visible answers together with the hidden arrival fields.
- Pass the combined record into Microsoft Dynamics CRM through the form builder's integration or an integration tool such as Zapier.
Checklist before launch: snippet present on every page with a lead form, all six hidden fields created, field names matched between form and CRM, and a test submission verified end to end.
How to read the six fields
Channel gives the broad arrival route. Drilldown 1 identifies the source, such as the search engine. Drilldown 2 records its domain, for example a country-specific Google domain. Drilldown 3 records the keyword when it is available. Landing Page shows the exact first page, while Landing Page Group rolls pages into sections such as /blog, /templates or /services. Together these fields separate three decisions: which channel to invest in, which search source and keyword to support, and which content section to expand.
Three reports to build first
Use built-in Dynamics reporting for routine monthly views, or send the fields to Tableau, Looker Studio or Microsoft Power BI for richer dashboards. A practical sequence is: first compare leads by channel to judge organic search against paid and social routes; then compare customers by landing page group to find the site sections that create customers; finally compare revenue by landing page to decide which individual articles or service pages deserve more work. That order moves from volume, to customer quality, to commercial value.
Worked example: template landing pages
A useful test case is a set of downloadable templates published as search landing pages. Traffic figures alone cannot show whether template visitors request demos. With arrival fields on the demo form, the CRM can count leads by template page, follow them to customer status and attach revenue. If a template section produces leads at very low cost, expanding that section becomes an evidence-based decision rather than a guess. Verify any named company outcome and quote with the owner before publishing them.
Getting started
Start with one high-intent form, confirm the hidden fields arrive correctly in Dynamics, then add the three reports in order. Keep field definitions stable so monthly comparisons remain meaningful, and review keyword availability regularly because drilldown data can vary by search engine and query type.
| Field | What it tells you | Decision it supports |
|---|---|---|
| Channel | Broad arrival route, such as Organic Search | Compare channels and shift budget |
| Channel Drilldown 1 | Search engine or source | Prioritise the strongest source |
| Channel Drilldown 2 | Source domain | Separate country or property variants |
| Channel Drilldown 3 | Keyword, when available | Support proven search terms |
| Landing Page | Exact first page visited | Improve or expand individual pages |
| Landing Page Group | Site section containing the page | Plan content by section |
Field definitions follow the captured setup; keyword availability can vary.
| Report | Primary measure | Use it to decide |
|---|---|---|
| Leads by Channel | Monthly leads by arrival channel | Whether organic search is growing and how it compares with paid routes |
| Customers from Organic Search by Landing Page Group | New customers by site section | Which sections to create more of |
| Revenue from Organic Search by Landing Page | Customers and revenue by exact page | Which individual pages deserve further investment |
Report definitions follow the captured examples.
Frequently asked questions
What do I need to set up before SEO data reaches Microsoft Dynamics CRM?
Add a small site snippet, create six hidden form fields for channel, three drilldowns, landing page and landing page group, then map those fields through your form-to-CRM integration so each submission carries its arrival details into Microsoft Dynamics CRM.
What does each captured field mean?
Channel tells you the broad route, such as Organic Search. The drilldowns add the search engine, its domain and, when available, the keyword. Landing page and landing page group show which page and section first brought the visitor in.
Which reports should I build first?
Start with leads by channel to compare organic search with paid and social routes, then customers by landing page group to see which site sections create customers, and finally revenue by landing page to prioritise individual pages.
Can I report inside Dynamics or use another analytics tool?
Use the CRM's built-in reporting for standard breakdowns, or connect the same fields to Tableau, Looker Studio or Microsoft Power BI when you need more advanced charts and dashboards.