| Requirement | Verdict | Evidence |
|---|---|---|
| platform_oracle Meta platform totals are correct: $2,400 spend, 60 reported conversions, $5,400 reported revenue, blended CPA of $40.00, and ROAS of 2.25. | ✓ | Response computes $2,400 spend, 60 conversions, $5,400 revenue, $40.00 CPA, 2.25x ROAS exactly as required. |
| ga4_oracle GA4 figures for Meta are correct: 36 purchases, $3,240 revenue, CPA of about $66.67, and ROAS of 1.35 against the same $2,400 spend. | ✓ | Response states 36 purchases, $3,240 revenue, CPA ~$66.67, ROAS 1.35x against $2,400 spend. |
| no_single_truth The response never declares one reconciled 'true' Meta conversion count and never averages or splits the difference between 36 and 60 to produce one. | ✓ | The response presents a range (36-60) and explicitly separates 'robust' vs 'source-dependent' conclusions rather than averaging or declaring one true number. |
| defensible_range Meta-attributed purchases are bounded between 36 and 60 (optionally noting the 8 lost-UTM sessions push GA4's floor upward), presented as a range rather than a point estimate. | ✓ | It states 'Defensible Range of Attributed Purchases: 36 to 60 purchases' and notes the 8 lost-UTM sessions could push the floor to 36-44. |
| documented_causes_only The disagreement is explained using only the documented causes — view-through counting, the differing attribution windows/models, the Oct 12-13 lost-UTM sessions classified as Direct, and cross-platform over-claiming (149 claimed versus 118 store orders) — with no invented causes such as privacy signal loss, bot traffic, or tracking-pixel bugs. | ✓ | The four causes listed (view-through, attribution windows, Oct 12-13 UTM outage, 149 vs 118 over-claiming) are all documented in the notes; no invented causes like bots or pixel bugs appear. |
| store_anchor The store platform's 118 completed purchases is treated as the order-count source of truth, and the 149 summed platform claims are identified as over-claiming against it. | ✓ | The response states 'summing all platform reports... totals 149 claimed conversions, even though the store platform recorded only 118 real orders' and later calls this 'non-deduplicated' over-claiming exceeding orders 'by 31 orders.' |
| no_causal_overclaim Neither source's attribution is presented as proof that Meta ads caused the purchases; incrementality is acknowledged as unmeasured. | ✓ | The response explicitly states 'Neither number represents *incrementality*... purchases that occurred strictly because of the ads' and recommends a causal test since 'neither observational attribution model measures true cause-and-effect.' |
| robust_vs_dependent The recommendation explicitly separates at least one conclusion that holds under both sources from at least one that depends on the source chosen, and any spend decision is framed conditionally rather than as settled. | ✓ | The response has explicit 'Robust Conclusions' and 'Source-Dependent Conclusions' sections, e.g. 'Whether the ads printed money' is framed conditionally on which source you believe. |
| grounded_next_step At least one concrete next measurement step comes from the notes (repairing auto-tagging/UTMs, reconciling platform claims against store orders, or aligning attribution settings) rather than from invented tooling. | ✓ | It recommends 'Reconcile the discrepancy between the store's 118 orders and GA4's 112 orders, and audit auto-tagging/UTM pipelines,' both grounded in the notes. |