If you have ever looked at a Gravity Forms entry (or a CRM record) and thought, “This lead is clearly from Google Ads, so why is Google Ads showing fewer conversions,” you’re not the first.
A big part of the confusion comes down to click identifiers. Google uses URL parameters to help attribute conversions back to ad interactions. Historically, that parameter was GCLID. Now, you may also see GBRAID and WBRAID, especially in the iOS privacy era. Google Analytics, Google Ads, and your forms can all be “right” in their own way and still not match.
Let’s break down what each ID means and then dig into the most common reasons your lead counts and conversion numbers don’t line up.
What a “Click ID” Actually Is
A click ID is an identifier Google appends to your landing page URL when someone clicks your ad. That identifier helps Google connect the visit to campaign metadata (campaign, ad group, creative, etc.) and attribute conversions back to that interaction.
In classic web tracking, GCLID is often unique per click. In iOS-related measurement, you may also see GBRAID or WBRAID, which are privacy-preserving parameters and may not be unique in the same way. That’s one reason perfect one-to-one matching is harder than it used to be.
Google’s own definition for GCLID is simple: it’s a URL parameter passed with ad clicks that identifies the click and associated attributes for tracking and attribution.
The key point: if the click ID never makes it into the conversion flow, attribution gets shaky. That’s where most “my leads don’t match my conversions” headaches begin.
GCLID: The Classic Google Click Identifier
GCLID stands for Google Click Identifier. It’s the “original” Google Ads click parameter most marketers know.
You will typically see it when:
- Auto-tagging is enabled in Google Ads.
- The click happens in contexts where Google can use it without running into platform privacy constraints.
- Your landing page preserves the parameter through redirects and form submission.
GCLID is still widely used, but it’s not guaranteed in every environment anymore. In particular, iOS privacy changes are a major reason you might see something else.
Why Gbraid and Wbraid Exist
Google’s own help documentation notes that GCLID may not be used without user consent in certain iOS 14+ scenarios due to privacy changes, and that Google introduced two new URL parameters to help measure results while complying with platform policies.
Those two parameters are:
1. GBRAID: Web to App Contexts (Commonly iOS-Related)
GBRAID is used in certain iOS measurement scenarios, most commonly when an ad click happens on the web and the journey continues into an iOS app. In these situations, Google may use GBRAID (instead of relying on GCLID) to support measurement while complying with iOS privacy constraints.
In plain terms: if your conversion path includes an app handoff, you may see GBRAID in the click URL. For purely web form submissions, WBRAID is often the one you’ll see more frequently.
2. WBRAID: App to Web Contexts (Commonly iOS-Related)
WBRAID is used in certain iOS measurement scenarios, most commonly when an ad click happens inside an iOS app and sends the user to your website. This is common with traffic that originates inside apps like YouTube, Gmail, or the Google app on iPhone.
If you’re seeing iPhone-heavy traffic and you notice WBRAID instead of GCLID, this is often why.
What These IDs Mean for Your Forms and CRM
At a practical level, your site needs to capture whatever identifier exists at click time and retain it until the moment of conversion.
Some WordPress and form tracking approaches explicitly capture these IDs at submission time and store them with the lead.
Even if you never use a plugin, that description is a helpful mental model: capture the ID, store it with the lead, and you can debug attribution later.
Why Your Leads Don’t Match Your Conversions
Here are the most common mismatch causes, with concrete ways to diagnose each one.
1) Consent and iOS Privacy Changes
This is the big one. If GCLID is not used without user consent in certain iOS 14+ scenarios, then some clicks that “feel like Google Ads” will not behave like classic GCLID clicks.
What it looks like:
- Your sales team talks to real leads who clicked ads.
- Google Ads shows fewer conversions than expected.
- You see GBRAID or WBRAID sometimes, and other times you see nothing.
What to do:
- Segment by device and browser. If gaps are heavier on iOS Safari or iOS in general, this is a strong indicator.
- Make sure your consent mode and tagging setup are correct, but understand that privacy constraints still change how identifiers appear.
2) The Click ID Gets Lost Before the Form Submits
Even if Google appends the ID, your site can accidentally drop it.
Common culprits:
- Redirect chains (especially if you redirect HTTP to HTTPS, non-www to www, or route through tracking links).
- Cross-domain jumps (landing page on one domain, form hosted elsewhere).
- Page builders or scripts that reload the page and wipe parameters.
- “Clean URL” scripts that strip query strings.
What to do:
- Click your own ad using Google’s ad preview tool when possible, then watch the final landing page URL. Confirm the parameter survives all redirects.
- Submit the form and confirm your lead record still has the ID captured.
3) You’re Counting Different Things in Different Places
A form submission is a lead. A Google Ads conversion is whatever conversion action you defined in Google Ads.
Those aren’t automatically the same event.
Examples:
- Your form submits, but your Google Ads conversion tag fires only on a thank-you page that some users never reach (tab closes, redirect fails, single-page app behavior).
- Your tag fires twice for one user (double counting), then you “fix” it and numbers swing the other direction.
- You track calls, chats, and form leads together in one report, but only some are set up as conversions in Ads.
What to do:
- Write down the exact definition of a conversion in Google Ads and compare it to what your team calls a “lead.”
- Confirm where the tag fires and whether that aligns with real lead creation.
4) Attribution Windows and Reporting Lag
Even when everything is set up correctly, Google Ads isn’t always instant. There’s normal processing time, and there are also attribution windows.
What it looks like:
- Your form entries show “today,” but Ads conversions backfill later.
- Yesterday looks “wrong” until it stabilizes.
What to do:
- Compare longer time ranges (7 to 14 days) instead of same-day snapshots.
- Be cautious about making optimization decisions on very fresh data.
5) Offline Conversion Imports and Enhanced Conversions Complexity
If you upload conversions back into Google Ads (from a CRM, for example), click identifiers become even more critical.
Google’s documentation for managing online click conversions references sending click identifiers like GCLID as part of conversion upload workflows.
What it looks like:
- Leads exist, but uploads fail or match rates are low.
- Some conversions match, others do not, and it feels random.
What to do:
- Ensure you’re consistently storing the click identifier at lead creation.
- Make sure timestamps, time zones, and conversion action names align exactly with what Google expects.
6) You’re Looking for Perfect One-to-One Matching That Doesn’t Exist Anymore
This is the uncomfortable truth: in a privacy-forward world, you should aim for diagnosable, explainable gaps, not a fantasy of perfect alignment.
Between consent, device restrictions, cross-environment behavior, and modeling, it’s normal for:
- Your form system to show more “Google Ads leads” than Ads shows conversions.
- Google Ads to attribute some conversions that you can’t perfectly trace back to a stored click ID, depending on your setup and reporting view.
The goal is not perfection. The goal is confidence that your data is directionally reliable and that you can investigate anomalies without guessing.
A Simple Troubleshooting Checklist
Use this when leads and conversions diverge:
- Check the URL
Confirm the landing page URL includes GCLID, GBRAID, or WBRAID after the click. - Check Redirects and Parameter Loss
Make sure the parameter survives to the final landing page and stays through submission. - Check What You Store with the Lead
Capture and store the identifier you have (GCLID, GBRAID, or WBRAID), not just “Google Ads: Yes.” (If you use a Gravity Forms approach, the idea is to have the ID visible on the entry so debugging is possible.) - Check Your Conversion Definition
Confirm the Google Ads conversion action matches the real-world event you care about. - Check Device Breakdowns
If mismatch is concentrated on iOS, consent and iOS 14+ measurement changes are likely in play.
Turn Click IDs Into Clarity, Not Confusion
GCLID, GBRAID, and WBRAID aren’t just jargon. They’re the breadcrumbs that make Google Ads measurement possible, and the reason your “lead list” and your “conversion list” can drift apart.
Once you understand which ID shows up in which environment—and you get disciplined about preserving and storing it—you stop arguing with your reports and start using them.