Meta Account Health Score Dropped Below 1: How Indian D2C Brands Recover Without a Reset
- info wittelsbach
- 5 days ago
- 4 min read
You open Account Quality and the number stares back: 0.7. Two weeks ago it was 4.5. Spend is being throttled, the algorithm has gone cold, and your ROAS halved overnight. The temptation is to start a fresh ad account and copy everything across.
Don't. A reset costs Indian D2C brands 6-8 weeks of learning, pixel maturity, and Business Verification trust. Below-1 scores are recoverable in 14 days if you stop the bleeding and rebuild the right signals.
First: Confirm It's Actually a Health Score Problem
Meta's 'Account Quality' score combines four signals into one number. Knowing which one tanked tells you what to fix.
Customer feedback score — post-purchase survey responses (1-5). Below 2 throttles delivery hard.
Policy strike velocity — disapprovals per 100 ads in the last 30 days.
Pixel signal quality — match rate, event volume, deduplication.
Business verification status — partial verification quietly caps spend at ₹25-50K/day.
Pull each one individually in Account Quality. A 0.7 with poor customer feedback is fixable in 7-10 days. A 0.7 from policy strikes is a 21+ day recovery.
The Root Causes Specific to Indian D2C
Six patterns drive most below-1 scores in the Indian market.
COD delivery failures. Buyers who refused delivery rate the brand 1-2. RTO above 25% slowly poisons your score.
Slow shipping vs ad claim. 'Get it tomorrow' creative + 5-day actual delivery = feedback score collapse.
Product quality vs visual. Heavily filtered creatives that don't match the actual product land hard.
Pixel double-firing after a Shopify theme update — every purchase logged 2-3 times skews the signal.
Repeat soft strikes — small disapprovals (claims language, before/after, sensational copy) stack.
Lookalike based on a polluted seed — a refund-heavy customer list dragging quality down.
The 14-Day Recovery Playbook
Run these in order. Do not skip steps to rush the score back up — Meta penalizes oscillation.
Days 1-3: Stop the Bleeding
Pause every ad with a disapproval in the last 60 days. Don't edit — pause.
Audit landing pages for outcome claims, before/after imagery, and aggressive countdowns. Remove.
Email the last 200 customers with a service-recovery message before they can post feedback.
Complete Business Verification if it's still 'In Progress' — submit GST + entity PAN.
Days 4-9: Rebuild Signal
Reinstall pixel cleanly. Pair with [Conversions API](https://www.wittelsbach.ai/post/conversion-api-capi-for-meta-ads-complete-india-d2c-setup-guide) for redundant signal Meta trusts more.
Launch one CBO campaign with two ad sets, three ads each, against your strongest 1% lookalike. Budget ₹2,000-5,000/day.
Avoid Advantage+ Shopping during recovery — its targeting volatility makes the score noisier.
Tighten shipping promises in creative: 'ships in 24 hours' beats 'delivered tomorrow' from a feedback-score lens.
Days 10-14: Restore Score
Add one creative refresh per ad set per week. See our guide on [detecting ad fatigue](https://www.wittelsbach.ai/post/how-to-detect-ad-fatigue-and-stop-it-before-it-costs-you).
Monitor Account Quality daily. A healthy recovery shows steady climb, not a spike.
If feedback score is the weak signal, run a customer outreach campaign asking happy customers to rate.
Scale spend only after the score crosses 2.0 and stays for 72 hours.
Why a Reset Is the Wrong Answer for Most Brands
A new ad account inherits zero pixel data, restarts the learning phase, loses Business Verification trust, and triggers Meta's 'new advertiser' delivery caps (₹500-2,500/day for the first 7 days). The 14-day recovery wins on every dimension if your underlying business is fundamentally compliant.
Reset is the right call only when: (a) you have 3+ permanent disablements on the BM, (b) the entity itself was flagged for fraud, or (c) your category violates Meta policy at the product level (e.g. CBD, unregulated supplements).
How Wittelsbach AI Monitors Account Health Continuously
Bach AI tracks all four Account Quality signals daily, alerts on velocity changes 48-72 hours before the score visibly drops, and maps each warning to the specific creative, audience, or landing-page change that's responsible. Run a free Meta Ads audit at [app.wittelsbach.ai](https://app.wittelsbach.ai).
Frequently Asked Questions
Can my Meta account be banned if the health score stays below 1?
Yes, but not immediately. Meta typically gives 30-45 days of warning throttling before issuing an account-level disablement. The pattern is: throttled delivery, then capped daily spend, then restricted features, then disablement. If your score has been below 1 for two weeks, you have time to recover — but not unlimited time. Start the playbook the day you notice the drop.
How often does Meta update the account health score?
Customer feedback rolls every 30 days on a moving window. Policy strikes refresh daily. Pixel signal quality updates within 24 hours of pixel events firing. Business verification status changes the moment a verification step is approved. So your score can move daily — but the customer feedback component, which is usually the heaviest weight, takes the longest to repair.
Does pausing all my ads help recover the health score faster?
Counterintuitively, no. A paused account stops generating new pixel signal, which Meta interprets as further degradation. The right approach is to pause the specific ads with disapprovals or low post-purchase feedback, then keep clean campaigns running to feed positive signal back into the score. Empty accounts atrophy.
Will Meta tell me which customers gave low feedback scores?
No — feedback is anonymous to advertisers. What you can see is the trend line and the verbatim category buckets (shipping, product quality, customer service, return experience). Use those buckets to triangulate. If 'shipping' is the dominant complaint, fix delivery times and adjust ad copy. If 'product quality,' audit your creative-to-product match and your QC pipeline.
Can I run ads on a different BM while one is recovering?
Technically yes, but Meta cross-references entity, payment method, login device, and directors. If two BMs share any of those and one is degraded, the second BM's score will start tracking the first within 14-21 days. The cleaner play is fixing the original BM. The exception: a genuinely different entity (different Pvt Ltd, different directors, different bank) can run in parallel without cross-contamination.




Comments