How to Use Meta's Diagnostics Tab to Catch Hidden Account Issues Before They Hurt Spend

Your campaigns are running. ROAS looks fine. You assume the account is healthy. Then a hidden issue compounds for three weeks — broken Pixel parameter, fatigued creative not flagged, audience overlap silently inflating CPM. By the time you notice, you've burned ₹4-6 lakh of inefficient spend.

Meta's Diagnostics tab catches these issues early. It's the most underused report in Ads Manager. Indian D2C founders who read it weekly protect their spend. Founders who don't pay a recurring tax to inattention.

First: Confirm Where Diagnostics Lives

Two different Diagnostics surfaces, both useful:

• Events Manager → Diagnostics: Pixel and CAPI health issues

• Ads Manager → Account Overview → Diagnostics: campaign delivery, ad approval, audience health issues

Both refresh continuously. Some warnings auto-resolve when conditions change. Some persist until you take action. Both should be read weekly.

The Five Most Important Diagnostic Categories

1. Ad Approval and Policy Issues

Meta flags ads with policy violations. Sometimes the ad runs anyway with limited reach; sometimes it's outright rejected. Common Indian D2C flags:

• Health claims: 'cures', 'treats', 'medical-grade' for beauty/supplements

• Before/after images without disclaimers

• Personal attributes: copy that implies the viewer has a problem (acne, weight, financial issue)

• Restricted content: alcohol, gambling, supplements without category enrollment

2. Pixel and CAPI Quality Issues

Event Match Quality drops, parameter coverage gaps, dedup failures. See our [Pixel data quality drop debug guide](https://www.wittelsbach.ai/post/debug-sudden-pixel-data-quality-drop-4-steps-without-developer-d2c).

3. Limited Delivery Warnings

Campaign is technically active but Meta isn't spending the budget. Causes:

• Audience too narrow: under 100K people on a ₹2,000+/day budget

• Bid too low to win competitive auctions

• Ad approval pending: technical delivery delayed

• Creative fatigue across all ads in the set: Meta has nothing fresh to show

4. Audience Overlap Warnings

Multiple ad sets targeting overlapping audiences — see our [audience overlap article](https://www.wittelsbach.ai/post/audience-overlap-the-silent-roas-killer-in-meta-ads). Diagnostics shows the % overlap between specific ad sets, helping you consolidate.

5. Domain Verification and AEM Issues

Verified domain has fewer than 8 AEM events configured. New domain not verified despite running ads. AEM priorities misaligned with optimization events.

The Weekly Diagnostics Review Workflow

Monday Morning: 15-Minute Sweep

1. Open Ads Manager → Account Overview → Diagnostics tab

2. Sort issues by severity (Critical → High → Medium)

3. Address every Critical issue immediately

4. Note High issues with planned fixes for the week

5. Ignore Medium issues unless they touch high-spend campaigns

6. Cross-check Events Manager → Diagnostics for Pixel/CAPI alerts

Wednesday Mid-Week: 5-Minute Check

Quick re-scan for new alerts. Mid-week is when most policy flags fire as Meta's review system processes weekend campaign launches.

Friday End-of-Week: 10-Minute Audit

Verify Monday's Critical fixes have resolved. Plan next week's High-severity work. Document recurring issues for systemic fixes.

Why Most Indian D2C Founders Skip Diagnostics

Three reasons. First, it's a passive surface — you have to remember to check it. Second, the warnings can feel non-urgent ('Limited Delivery' doesn't stop spend, it just reduces it). Third, many warnings persist for days even after the underlying issue resolves.

The cost of skipping it compounds. A single Limited Delivery warning that goes unaddressed for 2 weeks can cost ₹1-3 lakh in efficient spend that simply didn't happen. An ad approval issue across a category can delay a product launch by 7-14 days.

Common Mistakes Reading Diagnostics

1. Treating all warnings as equal urgency. Critical = act today. Medium = address this month.

2. Dismissing warnings without investigation. The 'Dismiss' button suppresses the warning, not the underlying issue.

3. Not cross-referencing with performance data. A Limited Delivery warning combined with a campaign at 1.5x ROAS is more urgent than the same warning on a 4x ROAS campaign.

4. Forgetting to recheck after applying fixes. Some warnings take 24-72 hours to clear after the issue is resolved.

How Wittelsbach AI Replaces Manual Diagnostics Checks

Bach AI continuously monitors every Diagnostic surface and bundles them with performance context. You don't get raw warnings — you get prioritized recommendations: 'Campaign X has Limited Delivery AND running at 1.8x ROAS — pause and refresh creative' instead of 'Limited Delivery detected'. Saves the manual sweep entirely. Bach AI is live at [app.wittelsbach.ai](https://app.wittelsbach.ai). Two clicks to connect Meta.

Frequently Asked Questions

How quickly does Diagnostics surface new issues?

Pixel/CAPI issues appear within 1-6 hours of the underlying problem starting. Campaign-level issues (Limited Delivery, approval flags) appear within 1-24 hours. Policy reviews can take 24-72 hours. For real-time issue detection, you need automated monitoring — manual Diagnostics checks always lag by hours to days.

Can I customize what Diagnostics shows me?

Limited. You can filter by severity and dismiss individual warnings, but you can't suppress entire categories. This is intentional — Meta wants founders to see all issues. Use the filter to focus your weekly review but don't permanently dismiss categories you find noisy.

Does Diagnostics show issues for archived campaigns?

No, only active and recently-paused campaigns. Once a campaign has been paused for 30+ days, its issues drop out of Diagnostics. This is mostly fine for D2C — archived campaign issues are usually irrelevant. Exception: if you have a recurring pause-and-relaunch cycle for seasonal campaigns, archived issues can resurface on relaunch.

What's the difference between Limited Delivery and 'Learning Limited'?

Different problems. Limited Delivery means Meta isn't spending your budget — usually narrow audience or low bid. Learning Limited means Meta is spending but can't optimize properly because the optimization event fires too rarely (under 50/week per ad set). Limited Delivery is a delivery issue. Learning Limited is an optimization issue. Both appear in Diagnostics.

Should I act on every warning?

No. Some warnings are informational (e.g., 'Consider enabling Advantage+ creative'). Some are signal-only without a clear fix (e.g., 'Audience saturating'). Focus on warnings tied to active issues with measurable spend impact. The 80/20 rule applies — the top 20% of warnings cause 80% of the leakage.