Skip to main content
Upstack Data

Phoenix Technologies to Google Ads Conversions

Forward every Phoenix Technologies 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.

What changes

What changes when Phoenix Technologies 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.

Every event, server-side

Storefront and checkout events are captured from Phoenix Technologies on the server, independent of the browser.

One setup, every destination

Connect Phoenix Technologies once and forward to every ad platform, email tool and warehouse you run.

What actually moves

What Phoenix Technologies carries, and what Google Ads Conversions needs.

Phoenix Technologies 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 Phoenix Technologies can put on an event, the right is what Google Ads Conversions can actually use.

Phoenix Technologies sends

order_id
Phoenix order reference
email / phone
contact from the order record
line_items
initial purchase and any upsells
total / rebill_amount
first charge separated from recurring
transaction_state
approved, declined or rebill
customer_type
new or returning, resolved before send

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.

Get Phoenix Technologies talking to Google Ads Conversions.

A 15-minute walkthrough of this connector on your own account.