Home/Services/Ecommerce Tracking/Purchase Tracking

PURCHASE TRACKING

Purchase Tracking That Counts Each Order Once

The purchase event is the conversion your ad budgets depend on. We make sure it fires exactly once per order, carries the correct value, currency and transaction ID, and reaches GA4, Google Ads and Meta in a form each platform can deduplicate and trust.

SERVICE SNAPSHOT
Best for

Stores whose ad platform conversions do not match orders in the store backend

What you get

Free 30-minute tracking audit • No obligation

THE PROBLEM

Purchase Data You Cannot Fully Trust

When conversion counts drift away from backend orders, bidding learns from the wrong numbers and reporting turns into debate. The causes are usually specific and fixable.

Duplicate Purchases

Page refreshes, back button visits and overlapping apps can each send a purchase, inflating conversions and revenue.

Missing Purchases

Off-site payments, slow redirects, blockers and consent choices mean some orders never reach the confirmation page tag.

Inconsistent Revenue Values

One platform receives gross totals with tax and shipping, another receives subtotals, so ROAS figures cannot be compared.

WHAT WE IMPLEMENT

What We Implement for Purchase Tracking

We treat the purchase as a defined record: one order, one ID, one agreed value. Every platform receives that same record, with deduplication built in at each layer.

01

Revenue Definition

A written rule for value: with or without tax, shipping and discounts, applied the same way everywhere.

02

Transaction ID Deduplication

transaction_id in GA4, order ID in Google Ads and a shared event_id in Meta to prevent double counting.

03

Fire-Once Safeguards

A flag in order meta, session storage or the pixel so reloads of the confirmation page do not resend the event.

04

Google Ads Conversion With Cart Data

Purchase conversion with value, currency, items and enhanced conversions for better matching.

05

Meta Purchase Event

Pixel Purchase with value, currency and content_ids, paired with a Conversions API event where needed.

06

Server-Side Backup Event

An order webhook or status hook that sends purchases when the browser never reaches the thank-you page.

HOW IT WORKS

How a Purchase Travels From Order to Platform

The order is created in your store, its data is captured once, sent with a shared ID to each platform, and later matched back to the order list.

01
Order Placed

Payment confirmed in the store

02
Order Data Captured

ID, value, currency and items

03
Browser and Server

Same order ID on both paths

04
Platform Dedup

Duplicates dropped by shared ID

05
Ads and Analytics

One conversion per order

06
Reconciliation

Tracked orders vs backend orders

WHAT'S INCLUDED

What's Included in Purchase Tracking

Clear deliverables, documented and validated before handover.

Purchase Path Audit

A trace of how purchases are sent today, including every app, pixel and tag that fires on order completion.

Revenue and Value Rules

A short document stating how order value, tax, shipping, discounts and currency are handled for each platform.

Conversion Action Setup

Google Ads and Meta purchase conversions configured with the right counting, value and attribution settings.

Test Order Evidence

Test orders with screenshots of each platform receiving one purchase with the expected value and ID.

Reconciliation Check

A comparison of tracked purchases against backend orders for a sample period, with gaps explained.

Purchase Tracking Runbook

Steps to check purchase tracking health after checkout, gateway or app changes.

IMPLEMENTATION PROCESS

From Audit to Validated Data

How a Purchase Tracking project runs, step by step.

01

Audit

Audit every purchase tag and compare recent conversions with backend order IDs

02

Strategy

Agree the revenue definition and the deduplication method for each platform

03

Implementation

Implement purchase events with fire-once logic and optional server-side backup

04

Testing

Place test orders across gateways, currencies and discount codes, then reload pages

05

Validation

Reconcile tracked purchases with store orders and document any remaining gaps

PLATFORMS

Platforms and Tools We Work With

The tools involved in a typical Purchase Tracking implementation.

Google Analytics 4

purchase event

Google Ads

Purchase conversion

Meta Pixel and CAPI

Purchase deduplication

Google Tag Manager

Tag orchestration

Shopify or WooCommerce

Order records

FAQ

Purchase Tracking FAQ

Straight answers before you book. Still have a question? Talk to us directly.

Will tracked purchases ever match our orders exactly?

Usually not. Consent choices, ad blockers and attribution rules mean platforms will not see every order. The goal is to remove the fixable gaps, like duplicates and missed gateways, and to understand the gaps that remain.

There is no single right answer. Many stores send product revenue after discounts and exclude tax and shipping, because that reflects what ads influence. What matters most is choosing one rule and applying it consistently. We help you decide.

Each purchase carries the same order ID or event ID on both paths. Meta uses event_id and event_name to drop the duplicate. GA4 uses transaction_id. Google Ads uses the order ID on the conversion.

Yes. GA4 accepts a refund event with the original transaction ID. For Google Ads, conversion adjustments can retract or restate a purchase value. We set these up where your store data makes them practical.

Not always. If the browser purchase is clean and gateways return shoppers reliably, it may be enough. Server-side events help when payments complete off-site or when browser signal loss is significant for your store.

Recurring charges happen without a browser session, so they are handled server-side or through offline imports. We first agree which orders should count as ad conversions and which belong only in analytics.

READY TO FIX YOUR DATA?

Stop Guessing. Start Measuring.

Get a professional review of your tracking setup and discover where your marketing data may be leaking.

Free 30-minute review • No obligation

Scroll to Top