Skip to content
Meta Business PartnerGlossary term

Per-User Marketing Limit

The Per-User Marketing Limit is a Meta-enforced cap on how many marketing-category template messages your business can deliver to a single WhatsApp user within a rolling time window. It is one of the least-visible but most decisive controls on the WhatsApp Business Platform: it doesn't reject your template, and it doesn't bounce your API call — it silently declines to deliver additional marketing messages to a person Meta judges is already being messaged too often. Because it operates per recipient rather than at the account level, two campaigns can look identical in your dashboard yet reach very different numbers of people. Understanding how this frequency cap works is essential for planning broadcast cadence, protecting delivery rates, and forecasting spend on a platform where you pay per delivered marketing message.

Marketing-category template messages only
Applies to
Per recipient, shared across all businesses
Scope
Undelivered = not billed (per delivered message)
Billing effect
Utility & authentication templates
Not affected
Meta, dynamically per user engagement
Set by

In one line

Meta caps how many marketing template messages one WhatsApp user can receive from all businesses in a rolling window. Exceed a user's remaining headroom and your marketing message is simply not delivered — so you are not billed for it, but the person never sees it. Space out campaigns and prioritise utility templates inside the service window to stay under the limit.

What the Per-User Marketing Limit actually is

The Per-User Marketing Limit is a frequency guardrail Meta applies to marketing-category template messages on a per-recipient basis. Every WhatsApp user has a finite, rolling allowance for how many marketing messages they can receive — an allowance shared across every business that messages them, not just yours. When a person is already near their ceiling because several brands have messaged them recently, Meta will decline to deliver further marketing templates to that individual, even though the same broadcast lands normally for everyone with headroom to spare. Crucially, this is distinct from your account's messaging tier (the 250 / 2,000 / 10,000 / 100,000 / unlimited unique-customer limits) and distinct from throughput (messages per second). Those govern how many people you can reach and how fast; the Per-User Marketing Limit governs how often any one person hears from marketers at all.

  • Applies only to the marketing category — utility and authentication templates are not counted against it
  • Enforced per recipient, and the allowance is shared across all businesses messaging that user
  • Separate from your messaging tier and from throughput limits
  • Meta does not publish the exact number, and it adjusts dynamically based on user signals

How it works in practice

When you send a marketing broadcast through the WhatsApp Business API, each message is evaluated against the recipient's remaining marketing headroom at the moment of delivery. If the user has room, the message is delivered and you are billed for one delivered marketing message. If the user has already hit their cap, the message is not delivered — and because WhatsApp bills per delivered message, you are not charged for the undelivered one. The practical consequence is a quiet gap between messages sent and messages that actually arrive. Meta tunes the ceiling using engagement signals: users who read, reply to, and interact with marketing messages tend to have more headroom, while users who ignore, mute, or block marketing tend to have less. This is why list hygiene and relevance matter far more than raw volume — an engaged audience effectively unlocks a higher practical limit.

  • A near-capped user's marketing message is declined at delivery, not at template submission
  • Undelivered marketing messages are not billed, since billing is per delivered message
  • Engaged, opted-in recipients tend to retain more marketing headroom over time
  • The 24-hour service window is unaffected — it is a free reply window, not a marketing allowance

Why it matters for Indian businesses

For teams running high-volume WhatsApp campaigns to Indian audiences — festival promotions, flash sales, abandoned-cart nudges — the Per-User Marketing Limit is the difference between a campaign that reaches its list and one that quietly under-delivers. If you blast the same segment with three marketing broadcasts in a single week, later sends will hit users who have exhausted their headroom, and your effective reach shrinks even though your API reported every message as accepted. It also reshapes cost forecasting: because you only pay for delivered marketing messages, a poorly paced campaign wastes effort rather than budget, but it also wastes the opportunity to actually reach those customers. The smart response is to lean on utility templates (order updates, appointment reminders, shipping notifications) for time-sensitive communication, since these fall in a different category and are not throttled by the marketing cap, and reserve marketing templates for genuinely promotional, well-spaced sends.

  • Frequent re-sends to the same segment produce diminishing real reach
  • Route transactional, expected messages through utility templates to sidestep the marketing cap
  • Segment and rotate audiences so no single user is over-messaged
  • Measure delivered vs. sent, not just sent, when judging campaign performance

Common mistakes and how to avoid them

The most frequent error is treating an accepted API response as proof of delivery. The Business API can return success while Meta later declines delivery for capped users, so a dashboard that only counts sends flatters your results. A second mistake is mislabelling promotional content as utility to dodge the cap — Meta actively reviews template categories, and misuse risks re-categorisation, template rejection, and quality-rating damage. A third is over-broadcasting to a narrow VIP segment, which burns through those users' headroom fastest of all. Finally, teams often ignore per-recipient frequency in favour of account-level metrics; the fix is to track how many marketing messages each contact has received recently and cap it on your side. On InfiQ, you can plan cadence, watch delivered-message counts against sends, and pay transparent ₹ pricing (ex-GST) only for messages that actually land — so it is clear when the per-user limit, rather than your budget, is the real constraint.

  • Don't equate an accepted API call with a delivered message — track delivery status
  • Don't disguise marketing templates as utility to evade the cap
  • Don't repeatedly hammer the same small segment — rotate and rest audiences
  • Do enforce your own per-contact frequency cap on top of Meta's

See InfiQ pricing

Talk to InfiQ

See how this works on InfiQ

Tell us your use-case — we’ll show it running in a sandbox, usually within a working day.

Step 1 of 2
WhatsApp

Protected by invisible spam checks · replies within 1 working day

Frequently asked questions

Is the Per-User Marketing Limit the same as my messaging tier?+
No. Your messaging tier (250 / 2,000 / 10,000 / 100,000 / unlimited) caps how many unique customers your account can start conversations with in a rolling 24 hours. The Per-User Marketing Limit is a separate, per-recipient frequency cap on marketing-category messages, and its allowance is shared across every business that messages that user.
Do utility and authentication messages count against the marketing limit?+
No. The Per-User Marketing Limit applies only to the marketing template category. Utility templates (order updates, reminders, alerts) and authentication templates (OTPs) are billed and governed separately and are not throttled by this cap, which is why routing transactional messages through utility templates is a good practice.
Will I be charged if a marketing message is blocked by the limit?+
No. Since Meta moved to per-delivered-message billing on 1 July 2025, you pay only for marketing messages that are actually delivered. If a user has hit their marketing cap and the message is not delivered, it is not billed — though you also lose the chance to reach that customer.
What exact number is the limit?+
Meta does not publish a fixed number, and it is not a single static value. The allowance is dynamic and personalised — it rises for users who engage with marketing messages and falls for those who ignore, mute, or block them. Because it is shared across all businesses messaging a user, you cannot calculate a precise per-brand figure.
How do I know if my campaign hit the Per-User Marketing Limit?+
Watch the gap between messages sent and messages delivered. If a broadcast to an engaged, valid list shows delivered counts noticeably below sent counts — and those recipients received marketing from you recently — per-user frequency capping is the likely cause. Delivery-status tracking, available in the InfiQ dashboard, makes this visible.
How can I reduce the impact of the marketing limit?+
Space marketing broadcasts further apart, segment and rotate your audience so no individual is over-messaged, keep opt-in lists clean and relevant to preserve engagement (which raises effective headroom), and shift time-sensitive, expected communication to utility templates that fall outside the marketing cap.
Does the 24-hour window have anything to do with this limit?+
No. The 24-hour service window is a free window that opens when a user messages you first, during which you can reply without a template. It is not a billing unit and not a marketing allowance. The Per-User Marketing Limit governs proactive marketing template messages and applies regardless of any open service window.
Can InfiQ help me manage marketing frequency?+
Yes. InfiQ, an official Meta Business Partner, gives you delivery-status visibility, campaign planning, and full BSUID ownership so you can pace marketing sends, enforce your own per-contact frequency caps, and see clearly when the per-user limit rather than budget is limiting reach.