GCLID vs GBRAID vs WBRAID: What Marketers Need to Capture

GCLID, GBRAID, and WBRAID are Google Ads identifiers for different ad journeys. GCLID is the standard Google click identifier. GBRAID connects an ad click on the web to a conversion in an iOS app. WBRAID connects an ad click in an iOS app to a conversion on a web page.

The marketer’s job is not to predict which identifier Google will use. It is to preserve every identifier that arrives, connect it to the later lead or purchase, and send the supported data back to Google Ads.

GCLID vs GBRAID vs WBRAID at a glance

These definitions come from Google’s current offline conversion upload documentation, not from expansions of the acronyms. Google does not tell marketers to decode GBRAID or WBRAID into invented names.

What is GCLID?

GCLID means Google Click Identifier. When Google Ads auto-tagging is enabled, Google can append a gclid parameter to the landing-page URL.

For example:

https://example.com/pricing?gclid=abc123

The identifier lets Google Ads associate activity reported by your measurement setup with the ad interaction. It does not, by itself, give a marketer the visitor’s name, email address, browsing history, or every page they viewed.

If the person becomes a lead and later closes in a CRM, you can retain the GCLID with that lead. An eligible offline conversion import can then send the conversion action, time, value, and identifier to Google Ads.

Google’s GCLID documentation explains the identifier and the cases where Google may create it. Avoid using GCLID as your own order ID: Google notes that the same GCLID can be reused in some repeat-click situations.

Why do GBRAID and WBRAID exist?

Some iOS journeys cannot use GCLID in the usual way. Google uses privacy-preserving BRAID parameters so advertisers can measure eligible app-to-web and web-to-app activity without treating the parameter as a person-level identifier.

That changes two implementation assumptions:

1. A landing URL from Google Ads will not always contain gclid.
2. GBRAID and WBRAID must not be used as unique CRM keys or deduplication keys.

Google can also supply more than one supported identifier for a journey. Its implementation guidance says to include GCLID whenever possible and notes that GCLID and GBRAID can sometimes be sent together. Create separate fields for gclid, gbraid, and wbraid; do not squeeze them into one generic “click ID” field.

What must the website and CRM capture?

A reliable setup follows the identifier from the first landing page to the final business event.

1. Let Google Ads parameters reach the landing page

Keep auto-tagging enabled where your Google Ads setup requires it. Make sure redirects, URL cleaners, consent tooling, and landing-page builders do not remove unrecognized query parameters.

Test the final URL after every redirect. Seeing the parameter only on the first URL is not enough if the browser lands on a clean URL before your tracker runs.

2. Preserve the value exactly

Parameter names are lowercase: gclid, gbraid, and wbraid. Store values without changing their capitalization, trimming characters, or decoding and rebuilding them.

3. Keep separate CRM fields

A useful record contains:

• the identifiers that were present;
• your own lead or order ID;
• the conversion action and timestamp;
• value and currency when relevant;
• the consent information required by your setup;
• eligible first-party customer data when using enhanced conversions for leads.

Your own lead or order ID is the stable business key. The Google-supplied identifier is attribution data attached to that record.

4. Join the later outcome

For lead generation, the meaningful event may be a qualified lead, sales-accepted lead, opportunity, or closed deal. For ecommerce, it may be a paid order, repeat purchase, or cancellation-adjusted revenue event.

Do not upload an early form fill under the same conversion action as a closed deal and expect bidding to understand the difference. Define separate conversion actions when the business outcomes are different.

5. Validate the import in Google Ads

Check the offline data diagnostics after data is sent. A successful API request does not prove that Google accepted, matched, and processed the conversion.

Conversions keyed by GBRAID or WBRAID can take up to 72 hours to process. That documented processing time is not a rule saying every conversion must be uploaded within 72 hours.

Which identifier should a marketer use?

Use the identifier Google supplies for that journey. Do not force a hierarchy in your form or CRM.

Google currently recommends enhanced conversions for leads as an upgraded path for many lead-generation setups. That method uses eligible, normalized, hashed first-party customer data in addition to the other fields Google supports. It does not remove the need to retain accurate conversion actions, timestamps, consent, and business IDs.

Where CustomerLabs fits

CustomerLabs documentation confirms that its client-side tracking can capture Google click context such as GCLID. Its identity-resolution layer can retain external identifiers and connect them with CRM or offline events on a resolved profile.

A practical CustomerLabs flow is:

Google ad click
  -> website captures available click context
  -> form, order, or CRM record keeps the identifier
  -> later qualified lead or purchase is joined to that record
  -> mapped conversion is sent to Google Ads
  -> marketer checks Google Ads diagnostics

Before promising GBRAID or WBRAID coverage for a particular implementation, verify that those fields survive the actual source, form, CRM, and Google Ads destination mapping. Product capability and a completed account configuration are not the same proof.

Read the step-by-step GBRAID and WBRAID offline conversion implementation guide to audit that path. If your team needs the full capture-to-CRM workflow, see offline conversion activation with CustomerLabs.

Common mistakes that lose Google Ads attribution

• Stripping parameters during redirects. The tracker never sees the value on the final page.
• Using one “click ID” field. A new value overwrites a different identifier instead of coexisting with it.
• Changing capitalization. BRAID values must be preserved case-sensitively.
• Using a BRAID as a unique key. Google describes BRAIDs as privacy-preserving and non-unique.
• Uploading only the top-of-funnel event. Google never learns which clicks led to qualified revenue.
• Treating an accepted request as a matched conversion. Diagnostics, conversion action status, and processed volume still need review.
• Calling 72 hours an upload deadline. It is a possible processing duration for BRAID-keyed conversions.

The simple marketer checklist

Ask your website, CRM, and analytics owners for evidence of each step:

• Can a test landing preserve gclid, gbraid, and wbraid through every redirect?
• Are the three values stored in separate, case-sensitive fields?
• Can the team show the identifier on the final lead or order record?
• Is a qualified lead or purchase mapped to the correct Google Ads conversion action?
• Is a unique business order or lead ID used for deduplication?
• Do Google Ads offline data diagnostics show accepted and processed events?

If any answer is “we think so,” the setup is not verified yet.

Need help tracing one real ad click through your website, CRM, and Google Ads account? Book a demo and ask for an offline conversion tracking review.

Official Google sources used for this update

• About Google Ads auto-tagging
• About the Google Click Identifier
• Manage offline conversions with Google Ads APIs
• Set up offline conversion imports using GBRAID