Find the right page
| What you are seeing | Start with | Then, if it is not that |
|---|---|---|
| Test Events or the dataset overview shows nothing, or far fewer events than visits | Pixel events not showing | Low event match quality once events arrive |
| Browser events arrive but server events are missing, or the server count fell to nothing | Conversions API events not showing | Pixel events not showing if browser events are missing too |
| People who just bought keep seeing retargeting or catalog ads for the same item | Retargeting ads reaching recent buyers | Advantage+ audience reaching existing customers if the ads come from prospecting |
| Ads Manager reports more purchases than the shop took | Duplicate conversions from the Conversions API | Pixel events not showing if a tag fires in the wrong place |
| Nobody can say how far Meta's results should differ from the shop's orders or the CRM's leads | Reconciling Meta results with your orders | Duplicate conversions from the Conversions API if the gap turns out to be double counting |
| Events Manager warns that match quality is poor | Low event match quality | Custom audience too small if retargeting pools are also thin |
| A retargeting or customer-list audience is too small to use | Custom audience too small | Advantage+ audience reaching existing customers if the list was meant as an exclusion |
| Prospecting spend keeps landing on people who already bought | Advantage+ audience reaching existing customers | Custom audience too small for the exclusion list itself |
| Catalog items never appear in catalog ads | Catalog products not showing | Pixel events not showing when product events are missing |
| Impressions are fine but few people click | Low click-through rate | Clicks but no conversions once clicks improve |
| Plenty of clicks, no sales recorded | Clicks but no conversions | Pixel events not showing if the shop did record orders |
| A day's spend is above the daily budget | Spending more than the daily budget | All budget going to one ad if the issue is distribution |
| One ad or ad set takes nearly all the spend | All budget going to one ad | Spending more than the daily budget if totals look wrong too |
| An approved ad set has never spent its budget since launch | Meta ads not spending budget | All budget going to one ad if sibling ad sets take the money |
| Lead forms bring plenty of submissions that sales cannot book | Lead ads bringing low-quality leads | Clicks but no conversions for website lead forms |
How these pages work
Every page has the same spine. It opens by asking whether the symptom is genuine: a date range that includes today's incomplete data, an attribution window that differs between two reports, or a browser extension blocking your own test can all look like a fault. It then sets out a diagnosis table with the symptom as you see it, the check that confirms or rules out each cause, the cause, and the fix. Each cause then gets a short section with the fix, a way to verify it, and the habit that stops it returning, followed by an illustrative walk-through and a few common mistakes.
The pages do not re-teach the platform. How the pixel and the Conversions APIServer-side event sharing with Meta. fit together lives in the measurement section; budgets, objectives and the learning phase live in campaign structure; audience types and exclusions live in targeting; and formats, hooks and testing live in the creative section. Each troubleshooting page links to the relevant guide at the point where a cause is confirmed.
Sudden performance drops live elsewhere
These pages deal with problems that are present from the start or tied to one feature: events that never arrive, an audience that never grows, a budget that behaves differently from expectations. When an account that was working falls away over a few days, with rising CPMCost per 1,000 impressions., climbing FrequencyAverage times a person saw an ad. or a conversion count that collapsed after a site release, the guide to troubleshooting performance drops is the better starting point. It separates measurement breaks, learning resets, auction shifts, fatigue, account health and site changes, and the pages in this section link to it rather than repeating it.
When to audit the account instead
A troubleshooting page answers one question quickly. If several of the symptoms above appear together, or nobody has reviewed the account's tracking, structure and audiences for a long time, chasing them one by one wastes effort because the causes overlap. The Meta Ads account audit reviews every layer in a fixed order and records what it finds, and the Meta Ads account audit checklist gives the same review as a list to work through. Return to the individual pages once the audit has named the problem worth fixing first.
