What WBRAID and GBRAID are
Both are parameters Google Ads can append to a landing page URL in place of the standard click identifier. They exist because Apple’s privacy changes made it impossible to pass a single, individual click reference across every app and browser boundary on iOS. Rather than losing that traffic from reporting entirely, Google introduced parameters that identify a group of similar clicks instead of one person’s click.
Google’s documentation assigns gbraid to journeys that begin in an app and continue on the web, and wbraid to journeys that begin on the web and continue into an app. In practice you will mostly meet them as an unfamiliar parameter in a landing page URL where you expected the usual one, and as a column in a conversion upload template.
Why they matter
They keep iOS conversions in the account instead of vanishing. Traffic on iPhones is not a rounding error in most markets, and in Nepal a large share of higher-value enquiries — property, education abroad, private healthcare — comes from devices where these parameters matter. Without them, a campaign could look weak simply because the platform that produced its best customers could not report back.
They also change how you read the numbers. Because the reference identifies a group rather than an individual, part of the reporting built on them is modelled rather than directly observed. That is a genuine trade-off, not a flaw to be fixed: Google is trading precision for privacy, and the figures should be read as a reliable direction rather than a per-person record.
Where they go wrong
The commonest failure is a system built to expect only the standard identifier. A CRM with one hidden field named for the old parameter will store nothing when a visitor arrives carrying a different one, and the business quietly loses its best-attributed iOS leads. The same happens in redirect rules, allow-lists of permitted query parameters, and analytics filters written years ago.
The second problem is expecting them to behave identically to the usual identifier in every workflow. Support for these parameters in offline uploads and other advanced features has been added over time and has its own conditions, so check what your current setup and Google’s current documentation actually allow before promising a client a full offline loop on iOS traffic.
What to do about them
Capture all three parameters, not one. Add hidden fields for each to your enquiry forms, store them against the record, and make sure your redirect rules and security filters pass them through untouched. If you already store the standard click identifier, this is a small change to the same code.
Then test on an actual iPhone rather than a desktop browser pretending to be one. Click a live ad from an app such as Gmail or Instagram, complete an enquiry, and confirm the record arrives with a parameter stored. If nothing is stored, the fault is almost always in the form or a redirect rather than in Google. A periodic tracking review catches this kind of drift before a quarter of reporting is built on it.
