Google Ads conversion tracking for crypto exchanges and platforms
Crypto advertising requires platform certification in most major markets, and even where permitted the funnel has an unusually brutal middle: a signup must pass identity verification, then actually fund, then actually trade. What Google Ads adds on top of that is a mechanical requirement: gclid, gbraid and wbraid have to reach the record that holds the money, because Google Ads can only credit a conversion it can tie back to a click it recognizes. This page covers both halves — what a conversion is in crypto exchanges and platforms, and what Google Ads specifically needs to accept it.
Free30 minutesNo obligation
Specific to Google Ads × Crypto exchanges
Google Ads for crypto exchanges: certify, then import first trades
On Google Ads, a crypto exchange should import the first trade as an offline conversion keyed on the gclid, gbraid or wbraid stored on the account at registration, sent from the exchange's account system with an expected fee value. Registration, verification and funding go in as secondary actions, and only in countries where Google has certified you.
Google treats exchanges and wallets as a certified category. In the US and most other markets it accepts their ads only after the advertiser holds Google's cryptocurrency certification for that country, which in turn depends on local registration. Keep the certified list next to the campaign location settings, because an ad group that drifts into an uncertified country is a policy strike against the account, not a wasted click. Confirm the current requirements per market in Google's financial services policy.
Create separate conversion actions for registration, verification passed, funded and first trade, make only first trade primary, and set all four to count one per click so a user who re-registers after a failed identity check is not counted twice. Put an expected fee value on the first trade rather than the deposit amount; bidding on deposit size teaches Smart Bidding to chase large balances that sit idle. Most first trades land well inside the 90-day import window, so timing is rarely what limits this build.
What does limit it is app-first onboarding. A Search click lands on a web page that pushes the install, verification happens in the app, and the gclid never reaches the account record. Either capture registration on the web before the handoff or carry the click through your mobile measurement setup, or the import will match almost nothing. Never put identity document details, wallet addresses or balances in any upload column.
Google Ads · Crypto exchanges · what breaks
Why Google Ads under-reports for crypto exchanges and platforms
- 01
KYC verification losing a large share
And the rate differs sharply by channel.
- 02
Funded accounts that never trade
A deposit is not activity.
- 03
Certification required per market
Where you may advertise is a compliance question.
- 04
Gclid, gbraid and wbraid never reaches the record
Three parameters, not one. gclid is the long-standing identifier; gbraid and wbraid arrive on iOS traffic where privacy constraints prevent the usual one. Capture code that names only gclid loses a growing share, silently, and the loss is invisible until you audit how many records carry an identifier.
Google Ads · Crypto exchanges · the fix
What working looks like — Google Ads · Crypto exchanges
Funded and trading accounts as the conversion
Not signups, not verifications.
Stage drop-off reported by source
Because it is the whole story.
Only certified markets targeted
With the rest named as unavailable.
Google Ads · Crypto exchanges · architecture
How Google Ads and crypto exchanges and platforms actually connect
- 1
The conversion in crypto exchanges and platforms
The money event is a funded account that has traded. Everything before it is a stage in a funnel that loses most of its volume.
- 2
Google Ads needs a click to match
A click identifier inside the 90-day window, a conversion action name that matches one configured in the account, a conversion timestamp for when the outcome happened, and a value. Read the match rate after uploading — a file can upload perfectly and match nothing.
- 3
The identifier: gclid, gbraid and wbraid
Three parameters, not one. gclid is the long-standing identifier; gbraid and wbraid arrive on iOS traffic where privacy constraints prevent the usual one. Capture code that names only gclid loses a growing share, silently, and the loss is invisible until you audit how many records carry an identifier.
- 4
Where it gets sent from
The account system — funded accounts that have traded, by date.
- 5
Deduplication and window
There's no shared event ID mechanism like Meta's. What matters instead is the counting setting on each conversion action — 'one' for lead-type conversions so a repeat submitter doesn't count three times, 'every' for ecommerce where a second purchase is a second sale. This is the single most common misconfiguration we find in Google Ads accounts. Google's offline import window is 90 days from the click. Anything older can't be matched, and rows outside it fail as unmatched without much explanation. Measure your median click-to-outcome time against that before designing anything.
Google Ads · Crypto exchanges · events
The conversion map for crypto exchanges and platforms
Five events with heavy losses at every step.
| Event | What it means here |
|---|---|
| Signup | Cheap, abundant, weakly predictive. |
| Identity verification submitted | Real intent, real friction. |
| Verification passed | A significant filter. |
| Account funded | Money committed. |
| First trade | The money event — revenue is fee-based. |
Google Ads · Crypto exchanges · diagnose
Diagnostic order — Google Ads · Crypto exchanges
- 01
Count records carrying gclid, gbraid and wbraid
- 02
Optimising on signups
Verification drop-off differs by source enough to invert campaign rankings.
- 03
Funded accounts assumed to trade
Deposits sit idle more often than expected.
- 04
Market volatility swamping campaign effects
A price move moves signups more than any budget change.
- 05
Read the match rate on the upload, not the success message
A conversion action that stops receiving hits is flagged as inactive 30 days later — by which point a month of budget has already run against a missing signal. Check the last-received date on every action monthly; it takes two minutes and it's the cheapest monitoring available.
Google Ads · Crypto exchanges · prove
How it gets proven — Google Ads · Crypto exchanges
Source of truth
The account system — funded accounts that have traded, by date
- Trading accounts reconciled per record against what each platform reports.
- Stage drop-off measured by source.
- Failed verifications reversed.
- Certification verified per market before spend.
- The match rate on the upload, not the success message read directly, not inferred from an upload succeeding.
Google Ads · Crypto exchanges · free audit
What we check in the free audit
- Count records carrying gclid, gbraid and wbraid
- Optimising on signups
- Funded accounts assumed to trade
- Market volatility swamping campaign effects
- Read the match rate on the upload, not the success message
Checked against
The account system — funded accounts that have traded, by date
Free30 minutesNo obligation
Google Ads · Crypto exchanges · when not to buy
When you don't need this — Google Ads · Crypto exchanges
- If Google Ads already reports conversions that reconcile against the account system within a few percent, this is working and there is nothing to buy.
- Measure identifier coverage yourself first — pull your last hundred records and count how many carry gclid, gbraid and wbraid.
- If you're running Performance Max exclusively and haven't separated your conversion actions, the import will work and the reporting won't tell you much. Worth sorting the account structure first.
Google Ads · Crypto exchanges · what we deliver
What gets built — Google Ads · Crypto exchanges
Click identifier captured on certified channels
Market by market.
Carried into the account record
At registration, before verification.
First trade fires the conversion
After funding.
Failed verifications and closures reversed
A large share never clear.
Dispatch via Google's offline conversion import
Uploaded against the click identifier, either through the Google Ads API or as a file. The upload is the easy part; what limits it is how many of your records carry an identifier at all. Verify the current column format against Google's own template — it has changed before.
Written guarantee
95%+ tracking accuracy
Measured against The account system — funded accounts that have traded, by date. Miss it and we keep working at no cost.
From $400 · See packages
FAQ
Google Ads · Crypto exchanges questions, answered
Usually yes, with the hashed email and phone collected at registration, which helps when the gclid is lost between web and app. Check Google's customer data policies for your account and keep everything from identity verification out of the payload.
Google grants crypto certification per country, so an approval in the US says nothing about Canada or an EU market. Check certification status for every targeted location before launch, not after the disapproval.
Because a signup that fails verification is worth nothing, and the failure rate varies enough by source to reverse which campaigns look good. Volume is not a substitute for signal.
As a stage. Revenue here is fee-based, so an account that funds and never trades produces nothing. The trade is the event.
Check the market first. Price movements move crypto signups more than any campaign change does, and mistaking one for the other leads to scaling into a peak.
Three parameters, not one. gclid is the long-standing identifier; gbraid and wbraid arrive on iOS traffic where privacy constraints prevent the usual one. Capture code that names only gclid loses a growing share, silently, and the loss is invisible until you audit how many records carry an identifier.
Uploaded against the click identifier, either through the Google Ads API or as a file. The upload is the easy part; what limits it is how many of your records carry an identifier at all. Verify the current column format against Google's own template — it has changed before.
By reading the match rate on the upload, not the success message and reconciling against The account system — funded accounts that have traded, by date. An upload that succeeds is not an upload that matched.
More on Google Ads · Crypto exchanges
- Crypto exchangesConversion tracking for crypto platforms, measured in funded, trading accounts
- Google Ads · Crypto and tradingGoogle Ads conversion tracking for crypto and trading platforms
- Meta · Crypto exchangesMeta Ads conversion tracking for crypto exchanges and platforms
RELATED GUIDES
More for crypto exchanges: other angles on the same outcome
- Crypto exchangesConversion tracking for crypto platforms, measured in funded, trading accounts
- Google Ads · CannabisGoogle Ads conversion tracking for cannabis businesses
- Google Ads · FirearmsGoogle Ads conversion tracking for firearms retailers
- Google Ads · Checkout → purchaseHow to track checkout to purchase for Google Ads
- Google Ads × Ecommerce OrdersHow to reconcile Google Ads against your store's order table
- Google Ads · Alcohol and wineGoogle Ads conversion tracking for alcohol and DTC wine brands
- Google Ads · MarketplacesGoogle Ads conversion tracking for marketplace sellers
- Google Ads · Crypto and tradingGoogle Ads conversion tracking for crypto and trading platforms
Free · 30 min
Get Google Ads reporting what crypto exchanges and platforms actually earn
Free30 minutesNo obligation
