Shopify conversion tracking: reconcile orders, refunds and ad delivery
Verify Shopify order capture, campaign identity, transaction revenue and destination delivery without counting the same purchase more than once.
By Mika Garcia · Published
In this article
Separate the order, the money and the ad conversion
Shopify conversion tracking spans several outcomes that should not share one undifferentiated total. A checkout can begin without payment. An order can be created before it is paid. A payment can later be partially refunded. An advertising platform can accept an event without assigning campaign credit.
Choose the business question first. Counting paid orders answers a different question from summing collected money or measuring campaign-attributed revenue. Keep each definition attached to the report, especially when comparing Shopify with an advertising platform.
Begin with one known order and trace its records. It is much easier to explain a disagreement when you can point to a specific amount and status than when you only have two aggregate dashboards.
Verify the storefront and source connection together
DATALYR’s Shopify guide requires the permanent myshopify.com domain, the App Embed and the checkout Web Pixel as part of the documented setup. Follow the current installation instructions rather than adding a separate, improvised webhook.
Inventory existing purchase senders before enabling destination delivery. A Shopify app, a theme pixel, a tag manager and another server integration may already report the same sale. Write down the owner for each destination and conversion action.
After configuration, check the expected storefront activity and a known order. A source connection that receives money records does not by itself prove that the original visitor or campaign was linked.
Reconcile a sale and a partial refund
Consider an illustrative $150 captured payment followed by a $30 refund. The signed cash ledger totals $120. The original order can still be one paid order even though its net collected amount changed. A checkout-start event should not add another order or another $150.
DATALYR’s Shopify documentation distinguishes purchase events used to count paid orders from signed transaction rows used for revenue. Keep that distinction when tracing the example. Summing both representations as money would double-count the same sale.
For a clean comparison, write down whether amounts include shipping and tax, which currency is used, and whether the refund is grouped by refund date or attributed back to the original order cohort. Two policies can legitimately place the adjustment in different periods.
One order, a changing cash balance
1. Capture
+$150
One illustrative paid order.
2. Partial refund
−$30
Adjustment tied to that order.
3. Signed total
$120
Do not add checkout or purchase snapshots again.
Inspect attribution separately from receipt
A purchase may be recorded without an eligible campaign association. Check the visitor reference and the captured landing context on the known order. DATALYR documents Shopify identity handoff through storefront cart attributes and related fallback behavior; use the guide to inspect the record.
Consent choices can limit the available handoff. Do not interpret an unattributed order as proof that the payment integration is broken, and do not change collection choices simply to make every order appear attributed.
Use an explicit unattributed bucket in the reconciliation. Assigned and unassigned amounts should explain the revenue basis being compared. A dashboard with fewer blanks is not necessarily a more accurate one.
Prove delivery without assuming platform agreement
After verifying the source, inspect the conversion rule and destination. Confirm the intended business event, amount, currency and destination asset. If multiple senders remain enabled, document how the platform deduplicates that exact setup.
Keep three outcomes separate: the source event arrived, the destination accepted a request, and the destination credited an advertising interaction. Attribution windows, eligibility and reporting dates can affect the final result even when transport succeeded.
Three checks, three meanings
Source receipt
Order or transaction exists
Evidence the business record arrived.
Destination response
Request accepted
Evidence about delivery.
Campaign report
Credit assigned
A later attribution outcome.
Use a repeatable verification record
Keep the order identifier, captured amount, refund amount, currency, visitor reference, event timestamps and destination response together. Record what should happen for each case before running a test. Include an order with no attributable journey so the fallback is understood.
Use the documented test-mode behavior carefully. A test event visible in an event log may be intentionally excluded from business revenue. Do not require a bogus payment to produce the same financial records as a settled charge.
Recheck after changing themes, checkout apps, consent configuration or delivery tools. For subscription or supplement businesses, add separate first-order and repeat-purchase views rather than treating every renewal as a newly acquired customer.