RecipeMeta Ads
Read the Meta ad activity log properly
The activity history filtered to the scope, the Meta half of every anomaly investigation.
IntentWho changed what on the account, aligned against delivery moves.
- 2
- Steps
- 2
- Tools
- 1
- Rules
- 1
- Failure modes
When to use it
Use it when
- Before blaming the auction.
- Agency handovers.
Do not use it when
- No specific contraindication beyond the preconditions below.
What it needs first
Required
Preconditions
- The account is ticked in the dashboard, confirmed via list_accounts.
Inputs
window- Analysis window.Default: last 30 days.
Procedure
In order. Every tool named is one the gateway ships, and links to its reference.
Pull activity for the window and scope.
Align edits against delivery and result moves.
Decision rules
The observable condition, what it lets you conclude, and what takes the conclusion back.
When
Edits land within 48h before a delivery drop
Conclude
Learning reset is the default suspect: expect 3-7 days of instability from the edit.
Evidence every conclusion must carry
- Every figure carries its account, metric and window.
- Anything below a readable sample size is reported as unjudged, not as zero.
Where the agent stops
- The readout changes nothing. Any change it motivates goes through Safe Writes: preview, human confirmation, then apply.
How it goes wrong quietly
The cases where the analysis is wrong and still looks right. Read them before trusting a number.
- System actors (rules, partners) interleave with humans: attribute before accusing.
What the answer contains
- 01Readout
- The figures, with windows and accounts named.
- 02Flags
- What deserves a deeper skill or a human decision.