Your dashboard still loads. The definition underneath it changed. Find the failed field, material variance or missing owner before comparing performance.
Use this resource when
Download the working file.
This is the complete editable template—not a PDF preview. Add your own account data, owners and decisions.
Inventory the sources and freshness
Record the old and new extract times, comparison period, owners and a user-set variance tolerance. Official guidance and operator rules remain visibly separated.
Map every critical field
Connect old field to new field, definition, source and owner. One-to-many mappings, transforms and definition changes stay explicit instead of being forced into false equivalence.
Reconcile like-for-like totals
Compare product count, eligible offers, clicks, cost, conversions, conversion value and merchant-side profit where available. Variance uses the old total as denominator and the tolerance remains editable.
Let critical failures override passing totals
PASS requires mapped fields, reconciled totals and sign-off. REVIEW records expected discontinuities. BLOCK overrides cosmetic success when a critical field is missing, refresh is broken or a material issue remains open.
Assign ownership and rollback
Every issue has evidence, severity, owner, action, due date, sign-off and rollback note so the QA kit completes an operating job rather than stopping at a checklist.
Apply this resource
Is the failure in reporting, the product feed or measurement?
A failed continuity check does not automatically mean the product feed is wrong. Classify the broken layer before briefing a provider; this workbook remains a reporting QA tool.
Prepare a useful handover
- Reporting definition changed: assign the export or dashboard owner to reconcile the mapping.
- Product data or eligibility is the issue: capture affected product IDs, markets, feed source and the Merchant Center issue.
- Purchase collection is the issue: capture missing, duplicate or wrong-value events separately from feed diagnostics.
Continue with the resource: Connect product priorities to stock and contribution.
Practical questions
Questions that change the decision
Should old and new reports always match exactly?
No. Reconcile like-for-like fields within a tolerance you set, and document expected definition discontinuities instead of forcing equality.
Can totals pass while the final decision is BLOCK?
Yes. A missing critical field, broken refresh or unresolved material issue overrides otherwise passing totals.
Is this a full Merchant Center audit?
No. It is a focused continuity kit for reporting definitions, field mappings, totals, ownership and rollback across a change.
Sources and platform documentation
Platform features change. These links point to the primary documentation used for the implementation details above.