RecipeMeta Ads
Check the Meta catalogue behind dynamic ads
Catalogue products read for availability, price sanity and coverage, before dynamic performance is judged.
IntentWhether the catalogue serves what the ads assume.
- 2
- Steps
- 2
- Tools
- 1
- Rules
- 1
- Failure modes
When to use it
Use it when
- Weekly on catalogue-driven accounts.
- After feed pushes.
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 catalogue products with statuses.
Cross top sellers against what actually serves.
Decision rules
The observable condition, what it lets you conclude, and what takes the conclusion back.
When
Top sellers are missing or rejected in the catalogue
Conclude
Feed fix outranks any campaign change: route to shopping-feed-health.
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.
- Catalogue counts differ from feed counts during processing windows: date the read.
What the answer contains
- 01Readout
- The figures, with windows and accounts named.
- 02Flags
- What deserves a deeper skill or a human decision.