Enhanced conversions can improve the match between an ad interaction and an order. Whether that order value is suitable for bidding requires separate checks of the amount, currency, deduplication and refunds. An enabled status does not establish profitable sales.
14 parts · 4 checkpoints · 3 free / 11 member parts →
Key point Identify the money first
This lesson is for merchants who can already see purchase events and are considering value-based bidding. The example is a Shopify shop selling leak-proof commuter tumblers. You will prepare a check record and decide whether to repair tracking, reconcile revenue or keep observing. You can enter independently with one order you are authorized to inspect.
Start with these questions
Matching and order amounts answer different questions
The feature uses processed first-party customer information to associate an existing conversion with an advertising interaction. It does not choose between a pre-discount subtotal, collected payment, tax-inclusive revenue or revenue after refunds. Nor does it turn an arbitrary amount into profit.
Hashing keeps a field from appearing as directly readable text. It does not remove obligations around user choice, data-use policies or access. Do not paste emails, phone numbers, addresses, real order details or hashes into this page. Record field names, problem types and non-sensitive conclusions only.
Compare the amount for one order first
In your controlled worksheet, line up the order identifier, collected amount, advertising value and currency. Add discount, tax, shipping and refund status. When amounts differ, identify the field responsible for the gap. Do not change the collected amount simply to make it match the ad report. ROAS is conversion value divided by ad spend; target ROAS is the ratio you aim to achieve.
Keep the time range, market and conversion action consistent. Ad-attributed results are not all shop orders, and an interaction date can differ from the order date. Establish which records belong in the comparison before calling a gap an implementation error.
What follows an enabled status?
Self-check not answered
A record supports checks, not a return claim
A small sample can verify delivery and reveal conflicting definitions. A few matching amounts cannot rule out delayed refunds, changing traffic or chance. A responsible reviewer must separately assess mature data, current account eligibility and stopping conditions before any test.
Series start
Trace the source of value
The choices and copied text here are local learning records. They do not connect to an ad account, read customer records or approve a bid change.
Free account to read · Parts 4-14 · 11 parts
Order-value evidence and test boundaries
This part includes
- Reconcile amounts, currencies, dedupe and refunds in four order groups
- Practice repairs and save a value review with a complete handoff
- Separate manual reconciliation, tool scenarios and account test conditions
1 checklist
An account is free; sign in to read this part.
Checking your membership…
No checkpoint finished in this lesson yet. Start with “Go to the exercise”.
Self-check not answered
Common questions
Matching and value
- Can I use tROAS as soon as diagnostics look normal?
- A diagnostic status alone is insufficient. Trace the amount, its unit and what remains after deductions, then have the owner assess data maturity and account suitability. Diagnostics concern part of implementation, not a return audit.
- Is this a new purchase event?
- No. It supplements matching within existing measurement rather than replacing purchase tracking. Hashing cannot correct an amount, its unit or user authorization.
The next check
Return to tracking or metrics for an unresolved gap. With a trusted definition, prepare one test you can review.
UTM Link Builder