Skip to content

Shopify and WooCommerce stores

One order. Counted once. At the right value.

Ecommerce tracking looks simple until a store has three apps firing purchase events, values that include tax on one platform and not another, and refunds no one sends back. We make every purchase count once, at a value the client agrees with, in Google Ads, Meta and GA4, and recover what browsers lose with server-side tracking.

WHO IT'S FOR

  • Shopify and WooCommerce stores spending on Google Ads, Performance Max and Meta
  • Brands with product catalogs feeding Shopping and Meta catalog ads
  • Stores where Shopify, GA4 and the ad platforms all report different revenue

Why it's different

The rules that change the setup.

  • 01

    Duplicate purchases inflate everything

    Theme code, apps and the platform's own integration often all fire a purchase. Google needs a transaction_id and Meta needs a matching event_id across Pixel and Conversions API, or one order counts twice.

  • 02

    Shopify changed how checkout tracking works

    Shopify runs checkout tracking through customer events and web pixels, which run in a sandbox, and has been retiring old scripts on the thank-you and order status pages. Setups built the old way can silently stop.

  • 03

    Value needs one definition

    With or without tax, shipping and discounts? Each choice is fine, but the store, GA4 and every ad platform need the same one, or ROAS comparisons mean nothing.

  • 04

    Browsers lose purchases

    Safari limits how long browser-set cookies last, and ad blockers stop many tags. Server-side tracking and Conversions API recover part of that loss.

The data map

What goes out, and what never does.

What ad platforms receive

  • Add to cart, begin checkout and purchase, each counted once
  • Order value and currency on the agreed definition, with transaction_id and event_id
  • Product IDs that match the catalog for Shopping and Meta catalog ads
  • Hashed email and phone where the store's privacy policy and consent allow it

What we never send

  • Full addresses, payment details or order notes
  • Customer names or emails in plain text, in any parameter
  • Personal data from customer accounts or order status pages in URLs
  • Events fired before consent where the store's consent rules require waiting

How we set it up

Step by step, in the client's own accounts.

Pricing

Purchase tracking, Meta Conversions API and deduplication are in Essentials, $390 per store. Server-side tracking is in Server-side & Privacy, from $1,490. Monitoring from $99 a month catches app and theme changes that break tracking.

See full pricing
  1. 01Audit every purchase eventWe list every app, theme snippet and integration that fires a purchase today, and compare one test order across Shopify or WooCommerce, GA4, Google Ads and Meta.
  2. 02One source per eventDuplicate apps and leftover snippets removed, so each event has one owner, built on Shopify customer events or WooCommerce hooks.
  3. 03Fix deduplicationtransaction_id on every Google purchase, and the same event_id sent by Pixel and Conversions API so Meta keeps one.
  4. 04Agree the value definitionWith or without tax and shipping, before or after discounts. One choice, written down, used everywhere.
  5. 05Match the catalogProduct IDs in view_item, add_to_cart and purchase events matched to the Merchant Center and Meta catalog IDs.
  6. 06Add server-sideServer-side GTM or the platform's server integration, with Consent Mode v2, to recover purchases browsers drop.
  7. 07Test and reconcileReal test orders, then a store-versus-platform reconciliation after go-live, logged for the client.

Outcomes

The funnel bidding learns from

Standard ecommerce stages. Values come from the store's own orders, on the definition you agree with the client.

  1. Stage 1

    Add to cart

    Product ID and value, matched to the catalog.

  2. Stage 2

    Begin checkout

    The step where Shopify's checkout tracking rules matter most.

  3. Stage 3

    Purchase

    Counted once, with transaction_id, event_id and the agreed value.

  4. Stage 4

    Refund

    Sent back to GA4, and to Google Ads as an adjustment where the client wants it.

  5. Stage 5

    Repeat purchase

    An example optional signal: new versus returning customers, for clients who bid differently on each.

Platforms covered

Works with the client's existing stack.

  • Shopify
  • WooCommerce
  • Google Ads
  • Google Merchant Center
  • Meta
  • Meta Commerce Manager
  • GA4
  • Server-side GTM
  • Consent Mode v2
  • Klaviyo

Something else? Tell us which tools the client uses and we'll confirm before you pay.

What we do and don't claim

We don't promise more sales or a higher ROAS. We make each purchase count once at the agreed value, so the numbers bidding learns from are right. Shopify and the ad platforms change their tracking systems often, and we confirm the current approach for each store.

Ecommerce tracking: questions

5 questions

Different attribution, different value definitions, consent, browsers blocking tags and duplicate events. Some gap is normal. We remove the gaps caused by setup errors and document the ones that remain.

Often the apps are a good base. Problems usually come from extra apps or old snippets firing the same events. We check what fires, keep one source per event, and fill the gaps the apps leave.

Either can work. Many agencies prefer product revenue without tax and shipping, because that's what the client earns from. What matters is that every platform uses the same definition.

Not always. Clean browser tracking with Conversions API and deduplication fixes most problems. Server-side tends to pay off for stores with high spend or many Safari and mobile visitors.

Google Ads supports conversion adjustments, which can retract or restate a purchase. We set it up where the client wants refunds reflected, usually with a regular upload from the store.

Got a ecommerce client whose numbers don't add up?

Send us one account. We review it for free and send a short video of what's working and what isn't.