Postback Binom → Google Ads
A Binom to Google Ads postback sends conversions from your PWA offer — leads, deposits — back into the ad account through the offline conversion import mechanism, since Google Ads can't see events that happen outside its own tag. Without that link, Smart Bidding optimizes on clicks alone rather than the campaign's real outcome. Here's how to set up the GCLID flow through Binom with deduplication, so data never doubles up.
Why Google Ads relies specifically on offline conversions
Google Ads has no server-side events channel on the level of Facebook CAPI or the TikTok Events API — instead, it uses offline conversion imports keyed on GCLID (the ad click identifier). That's the only official way to report a conversion that happened off-site from the Google tag — a deposit on a PWA offer some time after install, for example. Without offline conversions, Google Ads' automated bidding only sees clicks and can't optimize toward the traffic's real value.
Capturing GCLID in Binom
Google Ads automatically appends GCLID to the ad's click-through link — the tracker's (Binom's) job is to capture that parameter as a sub-ID on the user's first visit to the PWA and store it with the rest of the click data. In Google Ads itself, set up a conversion action of type Import → Clicks ahead of time — that's what accepts the offline uploads keyed on GCLID.
Setting up the postback and export in Binom
In Binom, the outgoing postback is configured in the campaign settings: on a confirmed conversion status, it builds a record with the GCLID, the conversion action name, the time, and the value. From there, delivery into Google Ads runs either through the offline conversion upload API wired to the tracker — the preferred option for a steady flow — or manually through the interface, which only really works for one-off checks. APEX supports a ready S2S postback setup with Binom, covering automatic GCLID conversion delivery without manual exports.
Statuses, deduplication, verification
Every meaningful status in Binom (lead, sale) should map to its own conversion action in Google Ads — merging them into one entity loses the ability to optimize for leads and deposits separately. Guard against double-counting by passing a unique Order ID with every conversion — Google Ads discards a repeat upload carrying an already-known transaction identifier. Stats on imported offline conversions and any upload errors show up under the Conversions section of the Google Ads account.
FAQ
- Why doesn't Google Ads have a real-time postback like Facebook CAPI?
- Google Ads has historically been built around offline conversion imports keyed on GCLID rather than a real-time events API — data usually shows up in the account with a delay of a few hours even with automated API uploads.
- What if GCLID isn't being passed into Binom?
- Check that the final PWA URL accepts the gclid parameter and that Binom has an explicit sub-ID configured to store it — skip that step and the parameter is lost on the very first click-through, leaving nothing to upload as an offline conversion.
- How do you avoid uploading the same conversion twice into Google Ads?
- Pass a unique Order ID with every conversion at upload time — Google Ads checks the identifier and automatically ignores a repeat record carrying the same value.
Cloaking, anti-bot, push, split tests and your own domains — in one service.
Get started free