GCLID storage and processing

Hi,

I have some doubts regarding how HS is handling the GCLID when using Google Ads…
- Where does HS extract the GCLID from in the moment a lead is created? (e.g. from the page URL or a certain cookie etc.)
- Does HS store the GCLID at the client’s end e.g. in a cookie or the browser storage so that it is available also in subsequent sessions.
- If so then which HS script is actually storing the GCLID and how is the relevant cookie for the GCLID named?
Any additional information or detailled documentation that explains the GCLID handling would be also welcome.
Thanks!
Georg

Hey @GeorgO, happy Friday!

HubSpot typically extracts the GCLID from the URL parameters when a lead is created, provided the GCLID is included in the URL (e.g., through Google Ads campaigns).

Regarding the storage of the GCLID, HubSpot uses cookies to track users across sessions. For specific details on how HubSpot handles tracking, including cookie storage and GCLID processing, I recommend referring to the following HubSpot documentation:

- HubSpot Tracking Code Overview: This guide explains how HubSpot’s tracking code works.

- Google Ads Integration with HubSpot: Details how HubSpot integrates with Google Ads, including GCLID tracking.

- Cookies and Tracking in HubSpot: A comprehensive overview of cookies used by HubSpot for tracking purposes.

I hope this helps!

Pam

Hi Pam,
Thanks. I did not find the information on the pages that you linked to. Is the GCLID stored in a cookie or do you store it somewhere else?
Kind regards

Georg