Custom stack to Google Ads Conversions
Forward every Custom stack event to Google Ads Conversions server-side, resolved to a person against a 750M+ device graph — with restored click IDs, deduplicated conversions and delivery you can audit.
Connection
Connect Custom stack to Google Ads Conversions with Upstack Data
Custom stack
Not on the list? Send events to Upstack from any stack over webhook or direct post, with the same schema and the same resolution.
Custom stack integrationGoogle Ads Conversions
Send identity-resolved conversions to Google Ads with more matched parameters, so Enhanced Conversions actually match.
Google Ads Conversions integrationWhat changes
What changes when Custom stack feeds Google Ads Conversions.
Enhanced Conversions that match
Email, phone, address and external ID hashed and attached to every event, so more conversions come back attributed.
Restored gclid
Click IDs recovered from the graph when the browser drops them, so paid search keeps its attribution.
Any stack, any framework
Headless, custom checkout, native app or a platform we haven’t listed — if it can make an HTTP request, it can send to Upstack.
The same event schema
Custom events are resolved, filtered and forwarded exactly like a Shopify order.
What actually moves
What Custom stack carries, and what Google Ads Conversions needs.
Custom stack and Google Ads Conversions describe a customer with different vocabularies. This is the mapping Upstack applies on the way through — the left column is what Custom stack can put on an event, the right is what Google Ads Conversions can actually use.
Custom stack sends
- event_name
- whatever you choose to call it
- user identifiers
- any of email, phone, external ID
- value / currency
- if the event carries revenue
- custom properties
- any attribute in your own schema
Google Ads Conversions receives
- hashed email / phone / address
- Enhanced Conversions matching
- gclid / wbraid
- keep paid search attribution
- conversion value
- value-based bidding
- order_id
- de-duplicate against tag conversions
Delivery you can audit
How you know it is working.
Ad platforms accept almost anything and tell you very little. These controls exist so you can see what was sent and what was accepted, rather than inferring it from a reporting gap.
Per-event inspection
Every conversion is inspectable from the moment it fires to the moment the platform confirms it.Deduplication
Browser and server copies of the same purchase collapse on event ID, so nothing is counted twice.Bot and fraud filtering
Automated traffic never reaches the model, because what you keep out of the training set matters as much as what goes in.
Where to check in Google Ads Conversions
Google AdsGoalsConversionsDiagnostics. Enhanced Conversions reports the share of conversions with usable hashed data attached.
Related connectors
Other places Custom stack can send to.
- Custom stackMeta Conversions API
- Custom stackTikTok Events API
- Custom stackPinterest
- Custom stackSnapchat
- Custom stackReddit
- Custom stackMicrosoft Ads
- Custom stackX
- Custom stackAppLovin
Other sources that feed Google Ads Conversions.
- ShopifyGoogle Ads Conversions
- WooCommerceGoogle Ads Conversions
- BigCommerceGoogle Ads Conversions
- Checkout ChampGoogle Ads Conversions
- RechargeGoogle Ads Conversions
- FunnelishGoogle Ads Conversions
- Lasso CommerceGoogle Ads Conversions
- Phoenix TechnologiesGoogle Ads Conversions
- SkioGoogle Ads Conversions
- Loop SubscriptionsGoogle Ads Conversions
- StripeGoogle Ads Conversions
- Everything Google Ads Conversions can take12 sources feed Google Ads Conversions, and the setup is the same for each one.Google Ads Conversions integration
- How resolution worksEvery event matched against a 750M+ device graph before it is forwarded.Upstack Signal
- What it costsThree plans that scale with your order volume. Every connector is on every plan.See pricing
Get Custom stack talking to Google Ads Conversions.
A 15-minute walkthrough of this connector on your own account.