gclid
Google Click Identifier
How it works
When someone clicks your Google ad, they land on something like example.com/offer?gclid=Cj0KCQiA.... The Google tag stores the value in a first-party cookie (_gcl_aw), so a conversion on a later page can still be matched to the click.
For some clicks on iOS devices, Google uses the parameters gbraid or wbraid instead of the gclid. They are meant for aggregated, more privacy-friendly measurement and play the same role when you import conversions.
Why it matters
The gclid connects a click to everything that happens afterwards. In lead generation the value is often created weeks later, in sales. If you stored the gclid with the lead, you can report the deal to Google Ads as an offline conversion, and the bidding strategy learns which clicks turn into customers. TSO reads gclid, gbraid and wbraid from the URL and sends the person's latest Google click to Google Ads with every conversion.
Example
A contractor gets an inquiry from a search ad. The gclid is stored along with the name and email. Three weeks later the inquiry becomes a €6,500 job. Thanks to the gclid, exactly this job goes back to Google Ads and counts for the campaign and keyword that brought the click. Without the gclid, Google would only see the form submission.
Common mistakes
- Auto-tagging switched off: without auto-tagging enabled in the account, Google adds no gclid. UTM parameters don't replace it.
- Redirects dropping the parameter: if the landing page redirects and leaves out the query string, the gclid is gone. Test the path once with a real click.
- The gclid stays in the browser: if it doesn't travel with the lead into the CRM or your tracking, a later deal can't be matched to a click.
- Reporting too late: Google only accepts imported conversions up to 90 days after the click. With long sales cycles, send intermediate stages such as "meeting booked" earlier.