Google has published a new help document covering how to set up offline conversions using the GBRAID URL parameter. On the surface, that reads like routine documentation maintenance. But if you run lead generation campaigns where the real value sits downstream of the form submission - in a CRM, a sales call, a qualified opportunity - this is worth understanding properly.
GBRAID (&gbraid=xyz) is a privacy-preserving identifier Google introduced to handle ad measurement in environments where cookies and device-level identifiers are restricted. The parameter gets appended to your landing page URL when someone clicks an ad, and it carries enough signal to associate a later conversion event back to the original click - without relying on third-party cookies or cross-site tracking.
Why the Distinction Between GCLID and GBRAID Matters
Most PPC teams are comfortable with GCLID - Google's standard click identifier used in offline conversion imports. You capture the GCLID at the point of form submission, pass it through your CRM, and send it back to Google when the lead converts into something meaningful. That workflow is well established.
GBRAID is different. It applies specifically to clicks that come through privacy-restricted environments - notably iOS traffic following Apple's App Tracking Transparency framework, and other contexts where standard cookie-based tracking is limited. If your campaigns are reaching mobile audiences and you are only capturing GCLID, you are likely missing attribution for a meaningful slice of iOS-originated clicks. Those clicks still happen. The conversion signal just never makes it back to Google.
The practical implication is that your offline conversion import process needs to handle both parameters. A setup that only passes GCLID is already incomplete for campaigns reaching iOS users at scale. That gap feeds directly into Smart Bidding, which cannot optimise towards conversions it cannot see.
What This Means for Smart Bidding and Campaign Performance
Smart Bidding strategies - Target CPA, Target ROAS, Maximise Conversions - are only as effective as the conversion data they receive. This is particularly acute for Performance Max campaigns, which rely heavily on conversion signals to allocate budget across channels and asset groups. When conversion signals are incomplete, the algorithm works with a partial picture. It may under-invest in placements or audience segments that are actually producing qualified leads.
For lead gen advertisers specifically, where the valuable conversion is rarely the form fill itself but the qualified call, the booked appointment, or the closed deal, offline conversion imports are already the right approach. Adding GBRAID support to that import process is not an optional enhancement - it closes a real attribution gap that affects bidding accuracy.
The scale of that gap varies by industry and audience. Campaigns targeting younger demographics, app-adjacent audiences, or running significant volume on mobile inventory will see a higher proportion of GBRAID-tagged clicks. Ignoring it in those contexts is not a minor measurement imprecision - it is a structural problem in how the campaign is being optimised.
Setting Up Your Tracking to Capture GBRAID
The basic requirement is that your landing pages and forms capture the GBRAID parameter alongside GCLID. Most implementations store GCLID in a hidden form field using JavaScript that reads the URL query string on page load. The same logic needs to handle GBRAID - typically stored in a separate hidden field and passed through to your CRM or lead management system alongside the rest of the form data.
In Google Tag Manager, this typically means updating your click ID capture variables to include GBRAID as well as GCLID. If you are using a first-party data layer or a server-side tracking setup, you need to ensure GBRAID is being passed through the full chain - from the landing page, through to the data layer, into your CRM field, and ultimately back to Google via the offline conversion import.
One point worth checking in your CRM: some platforms have field-length restrictions or validation rules that may cause issues with the GBRAID string. Test the capture end-to-end before assuming it is working. A parameter that gets stored as null or truncated is as useless as not capturing it at all.
The Broader Context: Consent and Privacy-Preserving Measurement
GBRAID sits within a wider set of privacy-preserving measurement approaches Google has developed as third-party cookies face ongoing pressure. Consent Mode, Enhanced Conversions, and server-side tagging all address different parts of the same problem - how do you maintain meaningful attribution when the user-level tracking that advertisers relied on for years is no longer universally available?
GBRAID's role in that set is specifically about click-level attribution for restricted environments. It does not replace Consent Mode, which handles modelled conversions for users who decline tracking. These are complementary mechanisms, not alternatives. A robust measurement setup uses both where applicable - and passes both GCLID and GBRAID through the offline conversion import pipeline.
The publication of this help document from Google suggests the company is actively trying to reduce the implementation barrier here. Whether that indicates growing adoption, more advertiser confusion, or simply documentation housekeeping is hard to say. What is clear is that the guidance now exists formally, which removes one of the common reasons teams leave GBRAID capture unimplemented.
Practical Steps for Lead Gen Teams
Start with an audit. Check whether your current landing page scripts are capturing GBRAID in addition to GCLID. Look at a sample of recent form submissions in your CRM and see whether GBRAID values are being stored. If the field is consistently empty, the capture is broken - or more likely, never set up.
Next, look at your offline conversion import process. If you are sending conversions back to Google via the API or via spreadsheet upload, confirm that your import template includes a column for GBRAID where applicable. Google's offline conversion import accepts both identifiers, and you should be using whichever one is available for a given lead.
Finally, consider this as part of a regular attribution health check rather than a one-off fix. The gap between what your CRM records and what Google Ads sees in conversions is a useful diagnostic. If there is a consistent shortfall - qualified leads in the CRM that never appear as conversions in the account - GBRAID capture is one of the first places to investigate, particularly if your campaigns carry meaningful iOS traffic volume.