gbraid and wbraid are URL parameters Google Ads uses to measure iOS traffic in a way that complies with Apple’s App Tracking Transparency policies. Google’s API documentation defines wbraid as the parameter present when someone clicks an ad in an iOS app and is sent to your website, and gbraid as the one present when someone clicks an ad on the web and is sent to your iOS app (Google Ads API).
Why gbraid and wbraid exist
Apple’s ATT policies took effect on April 26, 2021. Since then, Google says it no longer sends the gclid for iOS 14 traffic coming from ads on a handful of Google apps, while traffic from other Google sources keeps its GCLIDs. To keep measuring that traffic, Google introduced wbraid in March 2021 and gbraid in May 2021 (Google Ads Help).
Meta advertisers went through their own version of the same change; the tracking after iOS guide covers that side.
gbraid vs wbraid
| wbraid | gbraid | |
|---|---|---|
| Where the click happens | an ad inside an iOS app | an ad on the web |
| Where it lands | your website | your iOS app |
| Conversions it’s for | web conversions | app conversions |
| Introduced | March 2021 | May 2021 |
The “conversions it’s for” row comes straight from the field descriptions in Google’s ClickConversion reference: gbraid is the URL parameter for clicks associated with app conversions, wbraid the one for clicks associated with web conversions. On those definitions, an advertiser with a website and no app is in wbraid territory: the click starts in an iOS app and ends on a web landing page.
When they show up instead of gclid
- Auto-tagging has to be on. Google’s help page says gbraid is added to landing page URLs for iOS 14.5+ clicks when auto-tagging is enabled, and that it applies to Search, Shopping, Display and Performance Max campaigns.
- Your site has to accept them. Google warns that some advertisers need to allow arbitrary URL parameters on their website to keep measurement continuous. A server, CDN or plugin that strips unknown parameters loses them before your landing page can read them.
- They can arrive next to a gclid. The API accepts any combination on the same conversion and uses them in order of precedence: gclid, then wbraid, then gbraid.
What you lose without a gclid
When Google falls back to wbraid or gbraid because no gclid was set, the import does less. Google ignores the user_identifiers on the conversion, which rules out enhanced conversions for that record, and it doesn’t support custom conversion variables or cart data (same API guide).
The practical rule: capture all three parameters the way you capture gclid, keep each one exactly as it arrived, and upload whichever ones the click carried.
DropCPL generates its own click ID for every Meta ad click, on your landing page’s domain. Leads are joined to that ID, and the fbclid is kept next to it for the Conversions API. Start free →
What it means for your own click ID
The braid parameters show how a platform identifier can change under you because of a policy you don’t control. For part of the iOS traffic, the parameter many setups were built around simply stopped arriving. A click ID your own server generates on your own domain doesn’t depend on any platform’s policy, and the platform values become fields you store next to it.
DropCPL works with Meta only and doesn’t connect to Google Ads. On Meta traffic it logs its own click_id with the ad_id, campaign_id and fbclid, in a first-party cookie set server-side when the landing page is served.