Google today published a short explainer video walking through the mechanics of the Google Click Identifier, the string of characters that Google Ads attaches to a destination URL whenever someone clicks a paid ad. The video, titled "GCLID Explained: What is a GCLID?" and posted to the Google Ads YouTube channel, runs one minute and fifty-six seconds and pairs its walkthrough with a link to Google's existing Help Center article on setting up offline conversion imports using the identifier.

Neither the video nor the linked documentation announces a product change. Both describe a mechanism that has existed inside Google Ads for years and that continues to sit underneath a substantial share of the platform's conversion measurement. What the video does is condense several technical steps - how the parameter is generated, what data it carries, how auto-tagging is switched on, and how the resulting identifier eventually connects a click to a sale that might happen days later - into a single short piece aimed at advertisers who have not previously had reason to look closely at the mechanism.

What a GCLID actually is

According to the video, a GCLID functions as a kind of digital handshake between an ad click and a website. When someone clicks a Google Ads campaign, Google automatically appends a unique string of numbers and letters to the landing page URL. That string carries no visible meaning to a human reader, but it encodes several pieces of information behind the scenes, including which campaign served the ad, which keyword or targeting criteria triggered it, and which device the person used to click.

That encoding is what makes the parameter useful beyond simple click counting. Advertisers frequently want to know not just that a click happened, but what happened afterward - whether the person who clicked went on to fill out a form, make a purchase, or call a business days or weeks later. Because the GCLID persists through that gap, it becomes the connective thread between an initial ad interaction and whatever conversion eventually follows, however long the delay.

The video frames this as solving a specific frustration. Presenting an early example, it notes that identifying which specific ads drive business results is essential, yet tracking a customer's journey from a search click to an offline sale can be a complex and often frustrating process for advertisers who have not built out the right measurement infrastructure. The GCLID, in Google's framing, exists to close that gap.

Auto-tagging as the prerequisite

Before any of this works, an advertiser has to turn on a setting called auto-tagging inside their Google Ads account. The video describes this as a short administrative step: opening the account settings through the admin icon, navigating to account settings, opening the auto-tagging section, and checking a box confirming that the URL a person clicks through from an ad should be tagged. Saving that change is what activates GCLID generation going forward.

This detail matters because it is easy to overlook. An account that has never enabled auto-tagging will not generate GCLIDs at all, and any conversion tracking or offline import workflow that depends on the parameter will simply have nothing to work with. The setting itself carries no cost and does not change how ads are served or billed - it only determines whether the tracking string gets attached to the URL.

How the identifier moves through a conversion cycle

Once auto-tagging is active and a click generates a GCLID, the parameter's job is to travel with that visit through whatever happens next. The video describes two broad paths this can take.

The first is the more familiar one: a person clicks an ad, lands on a website, and converts on that same site, whether by completing a purchase or submitting a lead form. In that scenario, the GCLID typically gets captured automatically by Google's own measurement tools and matched against the original click without much manual work from the advertiser.

The second path is the one the video spends more time on, since it addresses the harder measurement problem: conversions that do not happen on the website at all. A lead might click an ad, browse a site, and then convert days later through a phone call or an in-person visit to a physical location. Nothing about that later action would normally be visible to Google Ads, because it does not generate any digital event that the platform can observe directly. The GCLID is what allows an advertiser to close that loop manually, by capturing the identifier at the moment of the original click, storing it alongside whatever record the business keeps of that prospect, and later uploading that stored identifier back into Google Ads once the offline outcome is known.

The technical steps behind offline import

The Google Ads Help Center documentation attached to the video lays out what this offline import process involves in practice, and the steps are more involved than the video's brief summary suggests.

An advertiser first needs to modify every lead submission form on their website to include a hidden form field that will hold the GCLID value. The documentation provides a sample line of HTML for this: a hidden input field with the name "gclid_field," inserted between the opening and closing tags of an existing form. Once that field exists, a script needs to run on every page of the site - not just landing pages - to read the GCLID out of the URL and store it, either through a cookie or through the browser's local storage, so that it survives as the visitor continues to browse. According to the documentation, the suggested script stores the value with a 90-day expiry window, after which it is treated as invalid for import purposes.

When the visitor eventually reaches a form and submits it, the stored GCLID gets written into the hidden field and travels along with the rest of the submitted data into whatever system the business uses to manage leads, whether a customer relationship management platform or a simpler internal tracking spreadsheet. From there, the responsibility shifts to the business itself: someone needs to modify that backend system so that when a lead's status eventually changes - closed, qualified, purchased - the stored GCLID can be matched against the corresponding record and uploaded back into Google Ads as a completed offline conversion.

The documentation also specifies a timing constraint that governs how far back an import can reach. For data sources including Google Cloud Storage, Amazon S3, HTTP, SFTP, and Google Sheets, Google Ads Data Manager imports conversions from as far back as 90 days in every run. Salesforce and HubSpot integrations behave differently: the first successful run imports the last 14 days of data, and every subsequent run imports whatever changed between the previous run and the current one. BigQuery, Amazon Redshift, Snowflake, MySQL, and PostgreSQL connections import the last 14 days of data in every run, regardless of how many previous runs have already occurred.

Creating the conversion action

Before any of that data flows anywhere, the documentation specifies that an advertiser has to create what Google calls an offline conversion action inside the Ads account itself. This happens through the Goals menu, selecting the option to create a new conversion action, then choosing "Conversions offline" as the category, and then either connecting a new data source immediately or choosing to skip that step and connect one later. Available connection options include a direct connection, a third-party integration through Zapier, or a partner integration.

The documentation walks through selecting a conversion category - a label such as "lead" or "purchase" that groups similar conversions together for reporting purposes - and then defining exactly which data fields the import will carry. Some of those fields map automatically based on the data source chosen; others need to be added manually depending on what the business tracks. Once the conversion action is created, the documentation specifies a waiting period: advertisers are advised to wait four to six hours before uploading any conversions tied to that new action, and uploads submitted during that initial window might take up to two days before appearing in reports.

For businesses managing multiple Google Ads accounts under a shared manager account, the documentation describes an additional structural requirement. All uploads have to route through the manager account, and any attempt to upload a conversion for an account that is not linked to that manager will return an error stating the upload is not authorized. Businesses using cross-account conversion measurement need to create their offline conversion actions at the manager level, while those not using that feature need to create separate conversion actions inside each individual account - and if the same conversion type, such as "lead qualified," is tracked across multiple accounts, the documentation stresses that the name needs to match exactly, including capitalization, in every account.

Third-party integration paths

The documentation also points toward integration options beyond a direct manual upload. Businesses using Salesforce can link their Salesforce and Google Ads accounts to track when a Google Ads campaign contributes to a milestone inside their sales funnel. Those using Zapier can configure an offline conversion import workflow through Zapier's platform. Those using HubSpot can set up tracking through HubSpot's own Google Ads optimization events tool.

For any business that has not yet adopted offline conversion import in any form, the documentation recommends a different starting point altogether: enhanced conversions for leads, described as an upgraded version of the older offline conversion import approach. Rather than relying solely on the GCLID, enhanced conversions for leads incorporates user-provided data such as email addresses, supplementing whatever GCLID data is already being imported to improve matching accuracy and the quality of signal available to Google's bidding systems. The provided customer data is hashed and matched both against data collected on the business's own website - a lead form submission, for instance - and against signed-in Google users who previously engaged with the ad. Businesses already using standard offline conversion imports can upgrade to this enhanced version to layer in that additional user-provided data on top of the GCLID they already import.

The technical script Google provides

For advertisers implementing the tracking manually rather than through Google Tag Manager, the documentation includes a JavaScript snippet intended to be placed on every page of a website, immediately before the closing body tag. The script checks the URL for a GCLID parameter, and if one is present, stores it using the browser's local storage alongside a calculated expiry date set 90 days into the future. It also checks a second parameter called "gclsrc," verifying that its value does not conflict with a valid GCLID before proceeding.

When a form field matching one of the specified hidden field identifiers exists on the page, and a valid, unexpired GCLID is found in storage, the script populates that field with the stored value automatically. The documentation notes that advertisers modifying this script only need to update one line - the list of form field identifiers the script should look for - to match whatever field names they used when adding the hidden inputs to their own forms.

For advertisers who already use Google Tag Manager, the documentation offers an alternative path that avoids editing site code directly. It involves creating a new Custom HTML tag inside the relevant Tag Manager container, pasting the same JavaScript into that tag, and setting the firing rule to trigger on all pages before publishing the container.

Throughout both the manual and Tag Manager approaches, the documentation includes a recurring caution: advertisers implementing any of this need to make sure they are observing local regulations regarding cookie consent, since the mechanism described relies on storing identifying information in the visitor's browser.

Why this matters for the marketing community

The GCLID sits underneath a considerable share of Google Ads measurement infrastructure, and its role has become more, not less, significant as browser-level tracking restrictions have expanded. PPC Land reported that Safari strips the GCLID parameter from ad URLs in an estimated 20 percent of sessions under the browser's default privacy configuration, a gap that grows further for users who have manually enabled Safari's stricter "All Browsing" tracking protection setting. That stripping problem is not new on iOS specifically; PPC Land documented in 2021 that the GCLID stopped working across several Google apps on iOS following Apple's rollout of App Tracking Transparency, an episode that first pushed advertisers toward alternative identifiers such as GBRAID and WBRAID for app-based attribution.

The auto-tagging mechanism the video describes as a short manual toggle has also been shifting toward becoming a default rather than an opt-in choice on at least one Google product. PPC Land reported that YouTube auto-tagging became enabled by default for Display & Video 360 advertisers, with existing advertisers needing to actively opt out if they did not want the setting applied to their accounts. That direction of travel signals how central the GCLID has become to Google's own measurement architecture, even for advertisers who never deliberately sought it out.

The offline conversion workflow the Help Center documentation describes is also positioned at a point of technical transition. PPC Land reported that the Google Ads API will stop accepting new adopters of offline conversion imports, including enhanced conversions for leads, starting June 15, 2026, with Google directing new integrations toward its newer Data Manager API instead. Developers who had already adopted offline conversion imports before that date are not immediately cut off, but the restriction narrows the path for anyone building a new integration from scratch going forward. PPC Land's technical analysis of the Data Manager API noted that the newer system enforces a single unified schema across Google Ads, Google Marketing Platform, and Google Analytics, replacing the fragmented, product-specific field requirements that characterized the older approach the Help Center article still documents in detail.

None of that broader infrastructure shift changes what the GCLID itself does or how the manual script-based workflow described in the documentation functions today. But it does mean that advertisers building a new offline conversion pipeline from the ground up now have a choice to make between the path the Help Center article lays out and the newer API-based route Google is steering new developers toward. For advertisers who already rely on the GCLID as their primary or sole attribution signal - a situation the documentation itself acknowledges is common - understanding exactly what data the identifier carries, how long it remains valid, and where the tracking can silently break down remains a foundational piece of campaign measurement literacy, regardless of which upload mechanism eventually delivers that data back into Google Ads.

Timeline

  • July 14, 2021: The GCLID parameter stops being appended for traffic originating from several Google apps on iOS, following Apple's rollout of App Tracking Transparency
  • September 2024: Auto-tagging, the setting that generates GCLIDs, becomes enabled by default for new Display & Video 360 advertisers
  • March 2022: Enhanced conversions for leads launches as an upgraded alternative to standard offline conversion import
  • April 21, 2026: A LinkedIn post documents Safari stripping the GCLID parameter in an estimated 20 percent of sessions under the browser's default privacy settings
  • May 15, 2026: Google publishes a developer blog post announcing that the Google Ads API will stop accepting new offline conversion import adopters from June 15, 2026
  • July 16, 2026: Google publishes "GCLID Explained: What is a GCLID?" on the Google Ads YouTube channel, alongside its existing Help Center documentation on offline conversion setup

Summary

Who: Google Ads, through its official YouTube channel and existing Help Center documentation, addressing advertisers who use or are considering offline conversion tracking based on the Google Click Identifier.

What: A short video explaining how the GCLID parameter functions, how auto-tagging activates it, and how it connects ad clicks to conversions that happen later or offline, paired with existing step-by-step Help Center documentation covering the technical implementation of offline conversion imports.

When: The video was published on July 16, 2026. The underlying Help Center documentation it links to describes a workflow that has existed in largely its current form for an extended period and was not newly changed alongside the video.

Where: The video appears on the Google Ads YouTube channel. The offline conversion import workflow it describes operates across an advertiser's Google Ads account, their website's code, and their internal lead tracking or customer relationship management system.

Why: The GCLID remains one of the primary mechanisms connecting Google Ads spending to real-world outcomes that do not happen on a website, a measurement gap that has grown more difficult to close as browser-level tracking restrictions have expanded and as Google shifts new API-based integrations toward newer infrastructure.