Fizzi Media
Back to all articles
What Works in Online Advertising Right Now

Missing WBRAID and GBRAID Form Fields Break Google Ads iOS Bidding

Published November 15, 2026 · Last reviewed November 15, 2026

Abstract diagram of data streams splitting into three distinct tracking identifiers across web and mobile protocols

High-volume paid search accounts frequently suffer from an invisible attribution leak: lead volume looks healthy in Google Ads, but downstream CRM revenue attribution systematically vanishes for mobile users. When marketing teams evaluate pipeline by device, desktop leads show reliable offline conversion uploads while iOS mobile leads appear entirely organic or unattributed. The breakdown does not originate in the ad auction or CRM reporting dashboards. The breakdown happens directly on the landing page, where legacy JavaScript snippets inspect the incoming URL for a single tracking parameter, record nothing when that parameter is absent, and pass empty values down the sales funnel.

The short answer

Client-side form scripts that only extract the GCLID query parameter drop attribution for iOS users subject to Apple privacy policies. Google Ads substitutes WBRAID for web-to-web clicks and GBRAID for app-to-web clicks to preserve aggregate measurement. If intake forms fail to store WBRAID and GBRAID in hidden fields and forward them to CRM pipelines, offline conversion imports fail. Google Smart Bidding registers zero downstream value from iOS traffic and systematically reduces bids on mobile inventory.

Why Google Ads splits click attribution across three distinct parameters

For more than a decade, Google Ads relied almost exclusively on the Google Click Identifier (gclid) appended via Google Ads auto-tagging. When a prospect clicked a search or display ad, Google appended ?gclid=12345 to the destination URL. Landing page forms parsed this parameter, saved it to a hidden field, and passed it to the CRM. When a lead turned into a qualified pipeline opportunity or closed revenue, an automated webhook pushed the gclid back to Google Ads via offline conversion tracking.

That single-parameter architecture broke when Apple implemented privacy controls under the App Tracking Transparency framework. To comply with cross-app tracking restrictions while continuing to deliver measurement, Google introduced two privacy-preserving parameters described in Google Ads measurement documentation:

Parameter Source Interaction Primary Environment Privacy Mechanism
gclid Web-to-web without ATT restriction Desktop, Android, unrestricted browsers Deterministic click ID linking single user to conversion
wbraid Web-to-web under privacy constraints Safari, iOS web clicks subject to measurement controls De-identified aggregate identifier using cryptographic techniques
gbraid App-to-web under ATT restrictions Google Maps, YouTube app, Gmail app clicks on iOS App-level aggregate click identifier preventing cross-site linkage

When an iOS user clicks a search ad inside the YouTube app or Gmail app, Google cannot generate a standard gclid without explicit cross-app tracking opt-in. Instead, Google appends gbraid. When a user navigates from certain Safari contexts where cross-site measurement is constrained, Google appends wbraid. If your front-end scripts only look for gclid, both parameters are ignored completely.

The failure mechanism in legacy client-side form parsers

Most lead generation landing pages rely on custom JavaScript or standard tag management templates to capture URL parameters. These scripts store values in browser cookies, local storage, or session storage, then populate hidden input fields on form submission. Similar tracking failures occur when handling complex multi-step intake flows, as detailed in our guide on multi-step qualification form tracking state.

When a script searches only for gclid, here is the sequence of failure:

  1. An executive searches for your service on an iPhone inside the Google app or Safari and clicks your search ad.
  2. Google Ads generates the landing page URL with ?wbraid=AbC123XyZ or ?gbraid=DeF456WvU.
  3. The landing page form script runs, searches window.location.search for gclid, finds null, and writes an empty string to the hidden form input.
  4. The lead submits the form. The CRM creates a contact record containing standard UTM tags but blank Google click identifier fields.
  5. Three weeks later, sales closes a forty-thousand-dollar contract. The CRM triggers an offline conversion upload to the Google Ads API.
  6. The upload payload contains no gclid, no wbraid, and no gbraid. The Google Ads API rejects the conversion record as unmatchable.

Because the conversion upload fails, Google Ads records zero revenue against that ad click. Automated bidding strategies receive no positive reinforcement for that target query on iOS devices.

How to patch form capture scripts and CRM schemas

Repairing this pipeline requires adjustments across three systems: the client-side capture script, the form markup, and the backend CRM or database schema.

First, modify your front-end query parser to capture all three parameters. The script should read gclid, wbraid, and gbraid from the URL, persist them in first-party cookies or session storage, and populate matching hidden fields.

function captureGoogleClickIdentifiers() {
  const params = new URLSearchParams(window.location.search);
  const identifiers = ['gclid', 'wbraid', 'gbraid'];
  
  identifiers.forEach(function(param) {
    const value = params.get(param);
    if (value) {
      // Store in session storage to persist across multi-page navigation
      sessionStorage.setItem('gz_' + param, value);
    }
  });

  // Populate hidden input fields if present on the current page
  identifiers.forEach(function(param) {
    const storedValue = sessionStorage.getItem('gz_' + param);
    const input = document.querySelector('input[name="' + param + '"]');
    if (input && storedValue) {
      input.value = storedValue;
    }
  });
}

document.addEventListener('DOMContentLoaded', captureGoogleClickIdentifiers);

Second, add explicit hidden fields to your intake forms alongside your existing UTM parameters:

<form id="lead-capture" action="/api/lead" method="POST">
  <input type="text" name="email" placeholder="work@company.com" required />
  <input type="hidden" name="gclid" id="gclid" value="" />
  <input type="hidden" name="wbraid" id="wbraid" value="" />
  <input type="hidden" name="gbraid" id="gbraid" value="" />
  <button type="submit">Request Consultation</button>
</form>

Third, add custom properties in your CRM to store wbraid and gbraid alongside your existing gclid field. For teams managing lead intake through embedded components, review our breakdown on Safari partitioned iframe storage issues in lead forms to ensure cookies do not get blocked by browser storage partitioning.

Finally, update your conversion upload pipeline to use the proper Google Ads API endpoints. According to the Google Ads API click conversion upload documentation, conversion upload requests accept wbraid or gbraid when gclid is not present:

{
  "conversions": [
    {
      "conversionAction": "customers/1234567890/conversionActions/987654321",
      "conversionDateTime": "2026-11-15 14:30:00-05:00",
      "wbraid": "AbC123XyZ_ExampleValue",
      "conversionValue": 12500.0,
      "currencyCode": "USD"
    }
  ],
  "partialFailure": true
}

Google Ads matches the conversion using the aggregate identifier while preserving privacy requirements.

What this means if you're running spend

When an ad account spends thirty thousand to two hundred thousand dollars per month on Google Ads, missing wbraid and gbraid fields creates an optimization distortion inside Smart Bidding algorithms. Target CPA and Target ROAS strategies allocate capital based on conversion frequency and conversion value returned per auction context.

When client-side scripts drop iOS parameters, the downstream data flow distorts bid allocation through a clear sequence:

[iOS User Clicks Ad with wbraid/gbraid]
                     │
                     ▼
[Form Script Ignores Parameter -> Blank CRM Field]
                     │
                     ▼
[Deal Closes -> Offline Upload Rejected by Google Ads]
                     │
                     ▼
[Smart Bidding Calculates 0% ROAS on iOS Segment]
                     │
                     ▼
[Google Ads Reduces Bids on iOS Devices Automatically]
                     │
                     ▼
[Account Spend Shifts Heavily to Android and Desktop]

Because the ad network never receives offline conversion feedback for iOS leads, the bidding algorithm concludes that iOS clicks produce poor pipeline value. Over sixty to ninety days, the algorithm suppresses bids on iOS traffic and reallocates budget entirely toward desktop and Android inventory. In many high-ticket B2B and affluent consumer verticals, iOS users represent sixty to eighty percent of total executive decision-makers. The account ends up over-bidding on lower-value inventory simply because those devices pass standard gclid strings that the legacy CRM pipeline can read.

Furthermore, delayed or incomplete offline imports disrupt algorithmic pacing, as explored in our analysis of delayed offline conversion imports destabilizing Target ROAS. Implementing proper capture for all three parameters restores full visibility to the bidding engine without requiring changes to campaign structure or target bid levels.

To ensure your offline uploads match successfully, review the setup requirements in Google Ads offline conversion documentation.

FAQ

Can a single lead record have both a GCLID and a WBRAID?

No, Google Ads assigns either a gclid, a wbraid, or a gbraid to a single click, never a combination of them. Your forms should provide separate fields for all three, but any given submission will contain at most one of these identifiers.

Does Google Tag Manager automatically capture WBRAID and GBRAID?

Google Tag Manager does not automatically populate custom CRM fields with these values unless your tags or form variables are configured to look for them. If your GTM setup uses a custom JavaScript variable that reads only gclid from the URL, you must update the variable to parse wbraid and gbraid as well.

Are WBRAID and GBRAID supported in manual offline conversion spreadsheet uploads?

Yes, Google Ads spreadsheet upload templates include dedicated columns for WBRAID and GBRAID. If you upload conversion spreadsheets through the Google Ads user interface, ensure your template uses the updated schema columns rather than attempting to place iOS identifiers into the Google Click ID column.

How do WBRAID and GBRAID differ from Enhanced Conversions?

WBRAID and GBRAID are click identifiers that track ad interactions under privacy constraints, whereas Enhanced Conversions uses hashed first-party customer data like email addresses and phone numbers to match conversions. Running both methods simultaneously provides the highest conversion match rates in Google Ads.

How much of this applies to your operation?

If your marketing pipeline depends on offline lead qualification, the integrity of your attribution model relies entirely on the parameters captured during initial form submission. At five to thirty million in annual revenue, losing conversion feedback on mobile traffic directly misguides your paid media allocation. We audit tracking architecture, CRM schemas, and conversion upload mechanics as part of our paid traffic management service. If you want our team to audit your attribution setup and rebuild your conversion pipelines, submit an application through our qualification form.

Last reviewed November 15, 2026. Sources linked inline.

Speak directly with Jason, our Managing Director. No sales reps.

More from the blog