A monthly Meta report can change even when the underlying business did not, because its attribution settings, date basis or selected columns changed. Save the report definition with the results. That lets the next reviewer compare the same measure and spot a real operational change.
Decision framework
| Step | Practical check |
|---|---|
| Capture configuration | Record account, campaigns, dates, timezone, attribution setting and report columns. |
| Define business measure | State whether the outcome is paid orders, qualified leads or another verified event. |
| Export evidence | Save the platform report and the matching store or CRM extract with extraction dates. |
| Explain differences | Show unmatched, duplicated and refunded outcomes rather than forcing totals to agree. |
How to make the decision
Add a settings box above each monthly table. Include the event name, attribution window, comparison period and any known tracking change. Next to platform results, show a separate business-result column that can be independently checked. When a setting changes, annotate the break in the series and avoid a simple month-on-month percentage that hides it.
Worked example
Illustrative lead generation account: the September deck shows 84 leads and the October deck shows 76. A reviewer discovers that October used a different date basis and a shorter view window. The team reruns both periods under the same available setting, then separately reports 29 and 31 CRM-qualified leads. The decision is based on the qualified trend, with the platform definition disclosed.
What can change the answer
Historical reports may not be perfectly reproducible if access, settings or data retention changed. Preserve the original export and label any restatement.
Review checklist
- Could a second analyst recreate the platform table?
- Are attribution and date definitions written beside the numbers?
- Are verified enquiries or orders presented separately?
Common question
Why not use platform ROAS alone?
It can guide account review, but business profitability and cross-channel attribution need separate cost and order records.
Next useful step
For the difference between impression credit and business evidence, read: Investigating View-Through Credit Without Dismissing or Overclaiming It. For help applying this to a UAE business, see Megvi’s Meta Ads service. Bring the source records and the decision you need to make.
The Flower Center case shows why measurement and account changes need a clear sequence: review the public case. Its results are not assumed for this example.
Source checked 25 October 2026: Meta Blueprint: introduction to campaign objectives. Check the current interface and policy before editing an account or profile.
Worked examples are illustrative unless a public source is explicitly named; they are not claimed Megvi client outcomes.