GBRAID and WBRAID are URL parameters that Google Ads adds to ad clicks on iPhones and iPads, where Apple’s privacy rules limit the GCLID. WBRAID is present when someone clicks an ad in an iOS app and lands on your website. GBRAID is present when someone clicks an ad on the web and is taken to your iOS app. Neither identifies a person: Google uses them to count conversions in aggregate.

If some of your Google Ads visitors arrive with wbraid= or gbraid= in the address where you expected gclid=, nothing is broken. Google is using a different click ID for that visit. This guide explains what each one is, why Google introduced them, how they compare with the GCLID, and what they change for conversion imports and call tracking.

What is GBRAID?

GBRAID is a URL parameter, written gbraid= in the address. Google’s help page calls it a privacy-preserving identifier used to measure ad performance. It measures conversions “in a non-unique fashion”, much like a campaign ID, without linking them to individual users or events.

Google’s developer documentation is more specific about when it applies: a GBRAID is present when someone clicks an ad on the web and is directed to your iOS app. Google adds it to landing page addresses for clicks on iOS 14.5 and later, as long as auto-tagging is on. That is why you can find a GBRAID on a website visit too, sometimes next to a GCLID.

What is WBRAID?

WBRAID is the companion parameter, written wbraid=. It is present when someone clicks an ad in an iOS app and is directed to your web page.

For this traffic, Google no longer sends the GCLID for ads shown in “a handful of Google apps” on iOS. The WBRAID takes its place, so website and offline conversions can still be attributed to your campaigns, with help from Google’s conversion modeling. The Google tag stores it in a first-party cookie on your domain.

Why Google introduced them

With iOS 14.5, released in April 2021, Apple began enforcing App Tracking Transparency (ATT). An app must now ask permission before it tracks a person across other companies’ apps and websites, and many people decline.

A GCLID identifies an individual ad click, so passing it from an app to a website can tie activity in one to activity in the other. GBRAID and WBRAID avoid that. Each stands for a group of clicks, not one, so Google can still count conversions for a campaign without following a single user.

What this means in practice:

  • Only iOS traffic is affected. Android and desktop clicks still carry a GCLID. Google says most advertisers see no change.
  • Reporting is less exact. Conversions matched on a WBRAID or GBRAID are reported in aggregate, and some are modeled.
  • The value is not unique. Do not use a GBRAID or WBRAID as a record ID in your CRM, or to remove duplicates.
  • Case matters. Google says the value is case sensitive, so store it exactly as it arrives.

GCLID vs GBRAID vs WBRAID

GCLID WBRAID GBRAID
What it is The standard Google Ads click ID An aggregate identifier for iOS An aggregate identifier for iOS
When it is present Ad clicks, when auto-tagging is on A click on an ad in an iOS app that leads to your website A click on an ad on the web that leads to your iOS app
What it measures Website, call and offline conversions Website and offline conversions App conversions
Identifies one click Yes No No
Accepted on offline conversion imports Yes Yes Yes
Enhanced conversion data on imports Used Ignored when there is no GCLID Ignored when there is no GCLID
Order Google uses if several are sent First Second Third

The last row matters when you send conversions back. Google’s guidance is to include every click identifier you captured. If more than one is present, Google Ads uses the GCLID first, then the WBRAID, then the GBRAID.

What changes for conversion tracking and offline imports

Website conversions tracked by the Google tag need little from you. Keep the Google tag or Google Tag Manager installed on every page, keep auto-tagging on, and the tag reads all three parameters. Google notes that a small share of sites must allow arbitrary URL parameters, so check that redirects and security rules do not strip gbraid and wbraid.

Offline conversion imports need more care, because your own systems have to carry the value from the click to the sale:

  1. Capture all three parameters. A form with one hidden field for the GCLID loses every lead that arrived with a WBRAID.
  2. Give each its own field. One shared “click ID” field means one value overwrites another.
  3. Send back every identifier you have. Google accepts any combination on the same conversion and applies its own order.
  4. Count every conversion. Google Ads does not accept GBRAID or WBRAID conversions for an action set to count one conversion per click, so set the action’s count to “Every”.
  5. Expect less from enhanced conversions. With a WBRAID or GBRAID and no GCLID, Google ignores the hashed email or phone number sent with the conversion, and does not support custom conversion variables.

The import itself is the same as for a GCLID. Our guides to Google Ads offline conversions and offline conversion tracking cover each step.

What GBRAID and WBRAID mean for call tracking

A phone call is an offline conversion, so the same rule applies: the call can only be sent back to Google Ads if the click ID was saved before the visitor dialed. A call tracking script that reads only the GCLID leaves iPhone calls without a click ID, and Google Ads cannot match them to a campaign.

The path is the same for all three parameters:

In Nimbata, the dynamic number insertion script saves the GCLID, GBRAID or WBRAID from each visitor’s landing page, next to the UTMs. When a call or a form meets the conditions in your workflow, the Google Ads integration uploads it as an offline click conversion with that click ID, the call’s start time and, if you choose, its value.

Here is an example of a call that arrives with a WBRAID:

Which call conversions can be sent back

  • Calls and forms with any of the three click IDs go to Google Ads as offline click conversions. You choose which ones count: first-time callers, calls over a minute, a tag, or an answer Nimbata AI found on the call.
  • Conversion actions created from Nimbata count “Every” by default, because Google Ads refuses GBRAID and WBRAID clicks for actions that count one.
  • Calls with no click ID, such as calls to a call asset, can still be matched if you turn on enhanced conversions. Nimbata sends the caller’s phone number, hashed, and Google Ads matches the call on it.
  • Outbound calls and texts are not sent to Google Ads.

Nimbata uploads a call once it is 12 hours old, and Google Ads then processes the import, so allow half a day or more before it shows in your reports.

What to do now

A short checklist:

  1. Keep auto-tagging on in Google Ads.
  2. Open your landing page with ?wbraid=test123 on the end and check the value survives every redirect.
  3. Add separate fields for gclid, gbraid and wbraid to your forms and your CRM.
  4. Check that your call tracking script captures all three.
  5. Set imported conversion actions to count “Every”.
  6. Judge iOS campaigns on trends, not on exact conversion counts, because part of the number is modeled.

FAQ on GBRAID and WBRAID

What is GBRAID?

GBRAID is a URL parameter (gbraid=) that Google Ads adds to ad clicks on iOS 14.5 and later when auto-tagging is on. Google describes it as a privacy-preserving identifier that measures conversions without linking them to individual users. It is used to measure conversions when someone clicks an ad on the web and is taken to an iOS app.

What is WBRAID?

WBRAID is a URL parameter (wbraid=) that is present when someone clicks an ad inside an iOS app and is taken to your website. Google uses it, together with conversion modeling, to attribute website and offline conversions to your campaigns when it does not send a GCLID.

What is gclid in URL?

It is the Google Click Identifier, a parameter Google Ads adds to your landing page address when auto-tagging is on. It identifies the ad click, so a later form, sale or phone call can be matched to the campaign, ad group and keyword behind it. Our GCLID guide covers how to capture it.

Do GBRAID and WBRAID replace the GCLID?

No. The GCLID is still the standard click ID for most ad clicks. GBRAID and WBRAID cover iOS journeys between apps and the web, where Apple’s App Tracking Transparency rules apply. If more than one is present on a conversion, Google Ads uses the GCLID first, then the WBRAID, then the GBRAID.

Can I import offline conversions with GBRAID or WBRAID?

Yes. Google Ads accepts a GCLID, a GBRAID, a WBRAID or any combination on an imported click conversion. When a conversion has a WBRAID or GBRAID but no GCLID, Google ignores the hashed customer data of enhanced conversions and does not support custom conversion variables for it.

Does Nimbata capture GBRAID and WBRAID?

Yes. Nimbata’s dynamic number insertion script saves the GCLID, GBRAID or WBRAID from each visitor’s landing page and sends it to Google Ads with the call or form as an offline click conversion. The Google Ads integration is on the Pro, Marketing and Agency plans; see our pricing page or talk to one of our specialists.

What is the difference between GCLID and UTM parameters?

A GCLID is created by Google Ads for each ad click and only Google can read what it stands for. UTM parameters are labels you write yourself (source, medium, campaign) and they work for any channel. Most advertisers use both: click IDs to send conversions back to Google Ads, UTMs for their own reports.