Capture the GCLID in Microsoft Dynamics 365 for Google Ads offline conversions
If Google Ads brings in leads but you cannot tell which campaigns produce paying customers, the missing link is usually the click identifier. Storing that identifier with each lead in Dynamics 365 lets you send the result back to Google Ads and judge campaigns on downstream outcomes, not just clicks and form fills.
Why the click ID matters
A GCLID is the unique identifier Google Ads attaches to a click. Without it, a lead in Dynamics 365 is just a name and email. With it, that same record can be matched back to the exact ad click that produced it.
The practical chain has four links:
- Capture the identifier when the visitor first arrives from an ad
- Keep it available across pages and return visits
- Write it into the form submission
- Store it on the Dynamics 365 lead and later return it to Google Ads
If any link is missing, offline conversion reporting will be incomplete even if the final Google Ads step is configured correctly.
This guide describes a practical workflow for implementing that chain: install a capture snippet, let it persist the GCLID in the browser, and have it write the value into a hidden form field.
Four-step capture checklist
Use this sequence as a setup checklist:
- Install the capture snippet on the website, either directly in site settings or through Google Tag Manager
- Add a hidden field named for the GCLID to every lead form
- Confirm the capture tool can read the identifier from the landing URL and persist it in the browser
- Submit a test form and check that the hidden field value appears with the name, email, and phone data
- Extend the existing form-to-CRM mapping so the hidden field is also sent to Dynamics 365. If you use a form builder such as Gravity Forms, Jotform, Typeform, or Tally Forms, use the form tool's built-in integration if it has one, or a connector such as Zapier, Make, or Power Automate
- Create the offline conversion action in Google Ads before building the return flow
- Choose the pipeline stage that will count as a conversion and build the trigger around it
- Map the stored identifier from Dynamics 365 to the Google Ads offline conversion field
- Test end to end before increasing spend
The hidden field is the hinge. The capture tool fills it automatically, the form tool carries it forward, and the CRM receives it without the visitor having to enter anything extra.
Failure to avoid: URL-only capture
A common failure is relying only on the URL visible at the moment of submission. Many form tools can read URL parameters, but only from the page where the form sits.
Consider a visitor who clicks an ad, lands on the homepage, browses several pages, and only later opens the contact form. By then the identifier is no longer in the address bar, so a form-only capture misses it. The same gap appears when someone leaves and returns days or weeks later through a different page.
Browser-side persistence solves that distinction: the identifier is saved on first arrival and reused at submission, regardless of the path taken in between. That is the difference between capturing a click that happened to still be in the URL and capturing the click that actually started the journey.
Worked example: paid and organic leads in one record
For a personal injury law firm, a paid search click might arrive with campaign and keyword tagging already in place. When that visitor later submits a case review form, the CRM record should show more than the GCLID:
- Channel: Paid Search
- Channel Drilldown 1: Google
- Channel Drilldown 2: the personal injury campaign name
- Channel Drilldown 3: the keyword that triggered the ad
- Channel Drilldown 4: the specific ad clicked
For an organic visitor who found the firm through a regular search, the same record would instead show Organic Search, Google as the source, the search engine domain, and the search term when available. Keeping paid and organic attribution in the same lead record makes it easier to compare channels inside Dynamics 365 rather than in separate reports.
Returning the GCLID as an offline conversion
First create the destination in Google Ads: open Goals, go to Conversions, start a new conversion, choose Offline Conversion, and select the option to add a data source later.
Next, decide which event counts. Sending only won deals can starve smart bidding of volume; strategies such as Maximise Conversions, Maximise Conversion Value, and Target CPA generally need roughly 50 conversions a month to perform well. If closed deals are rarer than that, an earlier stage such as Opportunity creation in Dynamics 365 usually gives Google enough signal to optimise against.
Then build the return flow in Zapier: set the trigger to the chosen Dynamics 365 event, for example Opportunity creation, choose Google Ads as the action, select Send Offline Conversion, and map the GCLID from Dynamics 365 to the GCLID field in Google Ads. Verify that conversions appear in Google Ads before scaling budget on the strength of the new data.