Commerce measurement reconciliation
Match orders, analytics events, and attributed channel results at transaction level before comparing totals.
Run this reconciliation when commerce, analytics, and advertising totals disagree and the team needs to know which transactions account for the gap.
Inputs
- Order-ledger export
- Analytics purchase events
- Channel reports
- Date range, timezone, and currency rules
- Tax, refund, cancellation, and order-state policy
- Consent and tracking setup
Output
- Transaction-level match table
- Missing, duplicate, late, and transformed events
- Notes on attribution differences
- Reconciliation rules
- Fixes grouped by owner
Steps
- Normalize the date range, timezone, currency, and included order states.
- Use the commerce ledger for booked orders.
- Match transaction IDs across systems.
- Distinguish collection loss from normal attribution differences.
- Check consent, browser, server, and checkout event coverage.
- Record attribution windows and modeled conversions.
- Assign fixes and rerun the same reconciliation.
Checks
- Transaction IDs
- Currency, tax, shipping, refunds, and cancellations
- Event order and deduplication
- Consent and browser coverage
- Attribution windows and identity rules
Limits
Related pages
Keep working on this issue
Primary reference · Reference
Google Analytics ecommerce measurement
The recommended GA4 ecommerce events, item model, currency handling, purchase identifiers, promotions, and refunds.
Primary reference · Reference
Shopify Web Pixels API
Shopify's controlled browser APIs and customer-event subscriptions for analytics and marketing measurement in sandboxed pixels.
Open-source project · Stable
Snowplow JavaScript Tracker
A browser event-tracking SDK for structured first-party behavioral data and custom ecommerce measurement designs.
Open-source project · Stable
OpenTelemetry JavaScript
Vendor-neutral instrumentation for traces, metrics, and logs across commerce applications and supporting services.