Per-User Marketing Message Limits
Meta's frequency cap on how many marketing template messages a single WhatsApp user can receive from all businesses combined within a set period.
Last updated: 2026-06-10
Definition
Per-user marketing message limits are Meta's ecosystem-level frequency cap: a ceiling on the number of Marketing-category template messages any individual WhatsApp user can receive — aggregated across every business messaging them — within a given time window. When a user has hit their cap, additional marketing sends to them fail with an ecosystem-health error (Cloud API code 131049) instead of being delivered or queued; utility, authentication, and service messages are unaffected. Meta introduced the cap to protect user experience after marketing volume surged, rolling it out market by market (the US first, then expansions including India) and tuning the threshold dynamically — users who engage more can receive more. Businesses cannot see or buy around another sender's share of the cap.
How it applies in India
India — WhatsApp's largest market and its heaviest marketing-message market — is squarely in scope for per-user caps, which Meta applies alongside template pacing to curb broadcast fatigue. The practical consequence for Indian brands: a contact bombarded by ten other D2C brands may be uncontactable for your campaign through no fault of yours. Defences are engagement-based segmentation (engaged users have looser effective caps), send-time optimisation, and moving transactional content to Utility so it never competes for marketing headroom. WatEase exposes per-send failure reasons so capped sends are distinguishable from blocks.
Frequently asked questions
How many marketing messages can a user receive?
Meta does not publish a fixed number — the cap is dynamic, varies by market, and flexes with how much the individual user engages with business messages. Meta revises the mechanics periodically; treat it as "highly engaged users receive more, fatigued users receive fewer" rather than a fixed quota.
How do I know a message failed because of the per-user limit?
The send fails immediately with an ecosystem-health error — on the Cloud API, error code 131049 ("message failed to send to maintain healthy ecosystem engagement"). It is not a block, a quality penalty, or an opt-out; the same user can be reachable again once their window resets.
Does the cap apply to utility or OTP messages?
No. Per-user limits apply only to Marketing-category templates. Utility, Authentication, and free-form service replies are unaffected — another reason to keep transactional flows correctly categorised as Utility.
Related terms
- Marketing ConversationA WhatsApp message category covering promotional content — offers, product launches, re-engagement — billed at the highest rate of Meta's template categories.
- Template PacingA Meta safeguard that delivers a new or edited marketing template to a small slice of its audience first, holding the rest until early feedback confirms users aren't blocking or reporting it.
- Quality RatingA traffic-light score (Green / Yellow / Red) Meta assigns to each WhatsApp Business phone number based on customer block and report rates.
- WhatsApp BroadcastSending one message to many WhatsApp contacts at once — capped at 256 recipients on the Business App, and effectively unlimited (tier-permitting) via approved templates on the Business API.
- Opt-inExplicit, recorded permission from a customer to receive WhatsApp messages from a business — required by Meta's Commerce Policy before any business-initiated conversation.
Try WatEase free
Run your WhatsApp commerce on the platform built for India — Cloud API, GST invoices, UPI checkout, opt-in tracking, and a Free Forever plan.
Start Free Today