The working sequence.
6 sectionsFollow the document’s sequence, or jump to the step you need.
- 01Step 1: How Many Conversions Per Month?
- 02Step 2: What's Your Purchase Cycle?
- 03Step 3: The Reconciliation Check
- 04Step 4: Configuration Review
Choose the evidence for the question.
Outcome volume affects uncertainty; it does not automatically select an attribution model. Reconcile definitions before interpreting a difference.
| Question | Evidence to inspect | What it cannot establish alone |
|---|---|---|
Are purchases recorded correctly? | Matched orders, values, refunds, currency and event dates. | How much credit each channel deserves. |
Why do model views differ? | Covered touchpoints, model, windows and observed conversion delay. | Which model is causal truth. |
Should allocation change? | Acquisition costs, margins, coverage and uncertainty. | That a conversion-count threshold certifies the decision. |
Did the channel add sales? | A suitable powered test with predefined outcome and assignment. | That a before/after pause is a controlled experiment. |
Read the full source: Step 1: How Many Conversions Per Month? · Step 2: What's Your Purchase Cycle? · Step 3: The Reconciliation Check
Jump to a section
Put this guide to work
Select and reconcile measurement views using volume, purchase cycle and the question being answered.
Your task: Trace your attribution decision. Record the source, date range and reviewer beside the result. Leave anything you have not checked marked Not checked.
Related work: The E-Commerce Attribution Playbook · Incrementality Test Design Checklist
Step 1: How Many Conversions Per Month?
Record monthly purchases, conversion lag and tracking coverage. Volume guides how much evidence you can interpret; it does not by itself choose a model or establish causal accuracy. Google Ads DDA eligibility has no minimum interaction/conversion volume. A300-conversion cutoff is not a provider rule.
Path A: Under 50 conversions/month
Use simple reports and inspect journeys where possible. Compare available last-click and data-driven views without assuming either identifies incremental sales. Verify purchase events and values first; sparse outcomes make budget comparisons uncertain.
Path B: 50–299 conversions/month
Compare model views alongside acquisition costs and margins. Investigate definitions, windows and missing events before reallocating budget. Agreement between models is not independent validation.
Path C: 300–999 conversions/month
More outcomes may support finer analysis. Review model differences, conversion delays and matched-order values. Select settings for the decision and current interface; this count does not make DDA causal truth.
Path D: 1,000+ conversions/month
Consider a powered randomized or carefully designed geographic holdout for material allocation questions. Predefine assignment, outcome, duration, minimum detectable effect and contamination checks. A two-week channel pause compared with previous weeks is before/after observation, not controlled incrementality evidence.
For every path, use order records to verify total sales with documented refunds, taxes and dates. Order totals do not independently assign channel credit. Select native or imported conversions deliberately; avoid multiple primary actions for the same purchase.
Step 2: What's Your Purchase Cycle?
Choose supported windows and evaluation periods from observed conversion delays. The cycle/price/window examples below are planning scenarios, not universal settings; prices do not determine buying cycles.
Quick Purchase (Same day to 3 days)
Products under $50, impulse buys, consumables, replenishment.
- Attribution window: 7-day click, 1-day view
- Campaign evaluation: After 7 days minimum
- Warning: A longer window changes eligible credit; it does not prove causation
Considered Purchase (4-14 days)
Products $50-200, first-time purchases, products requiring research.
- Attribution window: 14-day click, 1-day view
- Campaign evaluation: After 14 days minimum, 21 preferred
High-Ticket Purchase (15-30+ days)
Products $200+, luxury goods, high-consideration items.
- Attribution window: 30-day click, 7-day view
- Campaign evaluation: After 30 days minimum
How to Find Your Purchase Cycle
- GA4: Monetization > Purchase journey > Time to purchase
- Google Ads: Conversions > Conversion action > Days to conversion
- Your average is just that - average. Add 50% buffer for your evaluation window.
Step 3: The Reconciliation Check
Use a cadence suited to spend and latency. Reconciliation alone does not establish financial savings.
Pull These Five Numbers
| Source | Where to Find It | What It Represents |
|---|---|---|
| Shopify revenue | Shopify Admin > Analytics > Finances | Ground truth |
| GA4 revenue | Reports > Monetization > Overview | Baseline attribution |
| Google Ads revenue | Campaigns > Conversions value column | Google's self-reported credit |
| Meta Ads revenue | Ads Manager > Purchase conversion value | Meta's self-reported credit |
| Platform total | Google + Meta + other platforms summed | Combined platform claims |
Read the Gaps
Align currency, timezone, event date versus ad-interaction date, refunds, taxes, consent coverage, attribution model and windows. GA4 total purchases, Ads-attributed purchases and store sales cover different populations. Investigate unexplained changes against a stable baseline; no universal percentage certifies healthy or broken tracking.
| Check | Evidence to record | Decision |
|---|---|---|
| Matched order sample | Unique IDs, values, currency, event timestamps | Correct missing, duplicate or wrong events |
| Model comparison | Model, covered channels, window, observed difference | Explain credit before moving budget |
| Coverage change | Consent, tags, imports, release dates | Investigate discontinuities |
| Incrementality question | Powered design and confidence interval | Use only within tested scope |
Step 4: Configuration Review
- Record reporting identity, consent setup and available model/window choices; choose deliberately rather than automatically maximizing windows.
- Verify purchase values against permitted tests and matched order records.
- Choose primary conversions without duplicate purchase counting.
- Review counting against the outcome: Google recommends Every for sales and One where one lead per interaction is intended. Deduplicate repeat purchase events with transaction IDs; One is not purchase deduplication.
- Review enhanced conversions, customer-data handling and server/browser deduplication where implemented and permitted.
- Record actual view-through versus click-through credit; do not assume a fixed share.
- Verify current labels/settings in official documentation before changing them.
What This Decision Tree Doesn't Cover
This tree organizes measurement questions and configuration review; it does not certify a model as true.
What it doesn't cover:
- Building the full reconciliation dashboard with automated data pulls
- Server-side tracking implementation step by step
- Conversion delay analysis with your specific product data
- The complete troubleshooting flowchart for every common attribution problem
- How to run incrementality studies and interpret results
For the complete team-operated workflow, review the Google Ads AI Agentic System. The product page lists the current deliverables, price, license terms and setup responsibilities.
Use observed measurement gaps to brief the next implementation or experiment.
Choose who handles the next step.
Use the reference yourself, book a focused paid working session, or have Tegra handle the ongoing channel work.
Search, Shopping, Performance Max and Demand Gen campaigns, plus the research, product feeds, static and video creative, and landing, offer and pre-sale pages behind them.
Explore managed Google Ads → · See paid working sessions →