- US device IDs in the graph
- 750M+
- Match rate on events
- 90%+
- Identity window, per customer
- Lifetime
- Most brands are live
- <20 min
How it flows
How a Funnelish event reaches Google Ads Conversions. Tracked on the funnel page, resolved to a person, then sent.
01 Capture
Captured from Funnelish
Add the Upstack Pixel to your Funnelish funnels to track what shoppers do there. When Funnelish creates the order in Shopify, Upstack records it like any other Shopify order.
See the Funnelish integration →
FunnelishWhat it sends page / eventsfrom the Upstack Pixel in each funnel’s headfbclid / gclid / ttclidclick IDs kept on the way to checkoutorder_idthe Shopify order Funnelish createsorder sourceshows as Funnelish in Upstack reports
02 Understand
Resolved to one person before it leaves
Every Funnelish event is matched against a 750M+ device graph, so a phone browse and a desktop checkout resolve to one customer rather than two strangers.
How resolution works →
Resolved before it is sent - IdentityMatched against a 750M+ device graph, so a phone browse and a desktop checkout resolve to one customer.
customer_typeNew or returning, resolved before send.- DeduplicationThe browser tag and server-side conversions report to separate conversion actions, so keep one purchase action Primary and each order counts once.
- Bot and fraud filteringAutomated traffic never reaches the model, because what you keep out of the training set matters as much as what goes in.
03 Activate
Delivered to Google Ads Conversions
Send identity-resolved conversions to Google Ads with more matched parameters, so Enhanced Conversions actually match.
See the Google Ads Conversions integration →
Google Ads ConversionsWhat it receives hashed email / phone / addressEnhanced Conversions matchinggclid / wbraidkeep paid search attributionconversion valuevalue-based biddingorder_idthe order behind each conversion
The catch
Funnel pages sit outside your Shopify theme, so the Upstack app embed doesn't run on them, and click IDs such as fbclid, gclid and ttclid are easily dropped on the way to checkout.
Add the Upstack Pixel to each funnel and keep the click IDs on the links to checkout. The order itself reaches Upstack when Funnelish creates it in Shopify, counted once per Shopify order ID.
Where to check in Google Ads ConversionsDelivery you can audit
Google Ads › Goals › Conversions › Diagnostics
Enhanced Conversions reports the share of conversions with usable hashed data attached.
What changes
What changes when Funnelish feeds Google Ads Conversions. Two gains on the Google Ads Conversions side, two on the Funnelish side.
Google Ads Conversions
Enhanced Conversions that match
Email, phone, name and address hashed and attached whenever Upstack has them, so more conversions come back attributed.
Google Ads Conversions
Restored gclid
Click IDs recovered from the graph when the browser drops them, so paid search keeps its attribution.
Funnelish
Funnel pages tracked
The pixel loads in the head of every funnel page, so visits and the events you configure are recorded on pages your theme never touches.
Funnelish
One setup, every destination
Connect Funnelish once and forward to every ad platform and email tool you run.
Setup
Live in under 20 minutes.
You need admin access to the Google Ads account, with permission to create or edit conversion actions.
Upstack dashboardExample
Google Ads Conversions Destination Healthy
Read the full Google Ads Conversions setup guide → -
01
Add the Upstack Pixel to each funnel
In Funnelish, add the Upstack Pixel snippet to each funnel as a tracking code placed with Append To Page Head. If the funnel links to Shopify, add the script that keeps click IDs and UTMs on the link.
-
02
Add the Google Ads destination
Under Destinations, add Google Ads with the Conversion ID (AW- followed by 9 to 10 digits) and the 11 character Conversion Label from the Tag Setup of your Purchase - UpstackData goal. For server-side delivery, click Connect Google Ads, sign in with Google and link your events to conversion actions.
-
03
Check your primary purchase goal
Upstack marks the destination Healthy, and Goals, Conversions, Summary in Google Ads shows Purchase - Upstack (Server-side) as your only Primary purchase action. Place a test order and check that the conversion appears in Google Ads within 24 to 48 hours.
FAQ
Questions about Funnelish and Google Ads Conversions.
Why does Upstack create a new conversion goal instead of using my existing one?
Pointing Upstack at your existing goal would mix its server-side conversions with whatever already fires into that goal (gtag, Shopify’s native tag, GTM), which makes deduplication and quality comparison impossible. A dedicated Upstack goal keeps the data clean.
Why doesn’t Upstack support Enhanced Conversions directly?
Upstack already sends the hashed match keys Enhanced Conversions uses (email, phone, name, address) on every server-side event, so configuring Enhanced Conversions for web on the Upstack goal would not add data. The account-level setup is separate and still recommended: Google will not accept customer data over the API until the account has agreed to the customer data terms and turned on enhanced conversions for leads.
Which customer parameters are sent to Google Ads Conversions?
Server-side conversions carry the gclid, gbraid or wbraid click ID plus email, phone, first and last name, city, state, zip and country, hashed with SHA-256. Google accepts the customer data only once enhanced conversions are switched on at the account level.
How do I check that Funnelish events are reaching Google Ads Conversions?
Upstack marks the destination Healthy, and Goals, Conversions, Summary in Google Ads shows Purchase - Upstack (Server-side) as your only Primary purchase action. Place a test order and check that the conversion appears in Google Ads within 24 to 48 hours.
How long does it take to connect Funnelish to Google Ads Conversions?
Most brands are live in under 20 minutes. Once Funnelish events reach Upstack, every destination receives the same resolved events, Google Ads Conversions included.