Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.upstackdata.com/llms.txt

Use this file to discover all available pages before exploring further.

Data direction: This is a destination — Upstack sends event and conversion data out to this platform via server-side APIs.

​
What it does

Google Ads relies on conversion signal to power Smart Bidding, Performance Max, and any campaign that optimizes toward purchases. Upstack Signal forwards every Shopify purchase to your Google Ads account server-side, attached to a dedicated Upstack conversion goal that Google’s bidder can optimize against. Server-side delivery means conversions reach Google even when the browser-side gtag is blocked by ad blockers, ITP, or cookie restrictions. Each event carries the original click identifier (gclid or gbraid/wbraid) plus hashed customer data, so Google can match the conversion back to the ad interaction that drove it. The result is more complete conversion data inside Google Ads, sharper Smart Bidding decisions, and reporting that reflects the conversions your campaigns actually produced.

​
How it works

Google Ads uses a primary/secondary conversion goal architecture. Primary goals drive bidding — Smart Bidding optimizes toward whatever is marked primary. Secondary goals are observation-only: they appear in reports but do not influence the bidder. Upstack creates its own purchase goal in your account so you can compare it side-by-side with your existing goal before promoting it to primary. Upstack hashes customer data — email, phone, first_name, last_name, city, state, zip, country — with SHA-256 before sending it to Google’s API. Google uses these match keys the same way Enhanced Conversions does, so you get equivalent match-rate uplift without enabling Enhanced Conversions on the destination itself.

​
Primary vs secondary conversion rollout

When Upstack creates a conversion action in your Google Ads account, don’t immediately make it your primary goal. Start it as a secondary conversion (reporting only) and run it alongside your existing setup for 7–14 days. Compare purchase counts during this window — Upstack should track equal or higher volume due to enhanced identity matching. Once validated, promote the Upstack conversion to primary and demote the old one. This protects your Smart Bidding from disruption during the transition and gives the bidder a clean signal to retrain against.
Smaller accounts may need longer than 14 days to accumulate enough conversions for Smart Bidding to retrain confidently. Wait until the Upstack goal has logged conversions across a full bidding window before promoting it.

​
Setup guides

Onboarding guide

End-to-end walkthrough for connecting Google Ads to Upstack Data.

Configure destination

Configure the Google Ads destination inside Upstack Data.

Find conversion ID and label

Locate the conversion ID and label values Upstack needs.

Create purchase goal

Create the dedicated Upstack purchase conversion goal in Google Ads.

Enable primary goal

Promote the Upstack goal to primary so Smart Bidding optimizes against it.

Connect Google Ads account (source)

Connect Google Ads as a campaign data source for attribution reporting.

​
FAQ

Primary goals drive Smart Bidding — Google optimizes toward them. Secondary goals are observation-only and appear in reports but do not influence the bidder. New Upstack goals start as secondary so you can compare their volume and quality against your existing goal before switching them to primary.
Pointing Upstack at your existing goal would mix Upstack’s server-side conversions with whatever source is already firing into it (gtag, Shopify’s native tag, GTM), which makes deduplication and quality comparison impossible. A dedicated Upstack goal keeps the data clean and lets you A/B the two goals before promoting Upstack to primary.
Run both goals in parallel for at least one full conversion window. Keep your existing goal as primary and Upstack as secondary, confirm the volume and value reconcile, then follow the “Enable primary goal” guide to swap them. After the swap, demote your old goal to secondary so it stops influencing Smart Bidding.
Upstack already sends the same hashed match keys Enhanced Conversions uses (email, phone, name, address) on every server-side event, so Google’s match-rate logic applies automatically. Enabling Enhanced Conversions on top of the Upstack goal would not add data, and on the wrong goal it can cause duplicate or conflicting match logic.
Once the Upstack goal has logged conversions across a full bidding window (typically 7–14 days) and the volume and value reconcile within a few percent of your existing goal, it is safe to promote Upstack to primary. Smaller accounts may need longer to accumulate enough signal for Smart Bidding to retrain.

Conversion API forwarding

How Upstack Signal forwards events to ad platforms via server-to-server APIs.

Attribution and reporting

How Upstack attributes conversions back to the campaigns that drove them.

Events not reaching destination

End-to-end diagnostic guide when events aren’t arriving at any destination.