Skip to main content
Back to blog

Meta's Per-User Marketing Template Frequency Cap, Explained

Meta caps how many marketing template messages one WhatsApp user will receive from one business in a rolling window — per-recipient, not per-account. This explainer covers the cap mechanics, what stays uncapped, and the tenant-owned controls that surface cap risk before Meta applies it.

Orbit Editorial Team

Quick answer: Meta enforces a per-user marketing template frequency cap on WhatsApp: one business can deliver only a limited number of marketing template messages to one recipient inside a rolling window, and once that recipient's ceiling is hit, further marketing sends to them fail at delivery instead of landing. The cap is measured per (business, user) pair on marketing-category templates only — it rolled out unevenly across markets, starting in India and Brazil in 2025 and widening through 2026, and Meta does not publish the threshold, so it cannot be reverse-engineered into a quota. Utility and authentication templates, inbound service-window replies, and free entry-point conversations are outside the cap. On the platform side, the posture that keeps your sends under the ceiling is tenant-owned: frequency caps per contact, quiet-hours send windows, and template discipline — all controls you set, none of which claim compliance with a limit Meta does not disclose.

What Meta changed

Before the cap, a marketing send's failure modes were quality-driven: blocks and reports lowered the number's rating, and a bad template got paused. The per-user cap adds a second, quieter failure mode — a recipient who simply received too much marketing, from you, inside the window.

The mechanics, as far as Meta has documented them:

  • Per (business, user) pair. The counter is the recipient's marketing intake from your business specifically, not their total marketing intake or your account's volume. A heavy sender and a light sender both hit the same recipient at the same point — the recipient's ceiling, not the sender's.
  • Rolling window, threshold unpublished. Meta measures intake over a rolling window (the public signal has consistently pointed at roughly daily granularity, but Meta does not publish the exact window or count) and enforces dynamically — a recipient who chronically ignores marketing gets a lower ceiling than one who opens it. There is no number to plan against, and any vendor quoting one is guessing.
  • Marketing templates only. The counter increments on marketing-category template sends. What Meta counts as marketing is its own classification — the same classification that prices the send — so a nominally utility template with promotional copy counts here too.
  • A delivery failure, not a pause. Once the recipient's ceiling is reached, subsequent marketing sends to that recipient return a per-recipient limit failure instead of delivering. Nothing is wrong with your number or your template; that one recipient is simply closed to you until their window resets. Reads, replies, and engagement reset the recipient's standing faster than silence does.
  • Markets and phases. The cap began in high-complaint markets — India and Brazil were the first enforcement cohort in 2025 — and widened through 2026 with per-market timing Meta announces market by market. A number registered for a market where the cap is not yet live is not exempt from the posture below; the same sends still feed the quality gates.

This is the third of Meta's recent WhatsApp Business Platform policy shifts the series has covered. The per-message repricing made every marketing send individually billable, and the quality-rating and template-pause wave gated senders and templates on recipient feedback. The per-user cap sits on top of both: a send can be correctly priced, from a green-rated number, with an unpaused template, and still fail to deliver to the recipients who have had enough.

What did not change

The cap's boundaries matter as much as its mechanics, because the uncapped lanes are where re-engagement should move:

  • Utility and authentication templates are uncapped per recipient. Order updates, appointment reminders, and one-time passcodes do not count toward the marketing ceiling. This is not a loophole to exploit — a utility template carrying promotional weight gets re-classified as marketing, and then it counts, bills, and gates all at once. It is a reason to keep the categories honest.
  • Inbound service windows are untouched. A customer who messages you opens a 24-hour service window, and your replies inside it are neither capped nor charged — the free lane stays free.
  • Free entry points stay free. Conversations a customer starts from a Click-to-WhatsApp ad or a Facebook Page call-to-action open a free entry-point window, as the pricing-shift explainer details. Volitional inbound traffic remains the cheapest and unthrottled lane.
  • The quality gates run independently. The quality-rating wave covers per-number ratings and per-template pauses; the per-user cap is a separate counter. A recipient-level delivery failure is not a rating event — but the campaign pattern that triggers it (high marketing volume to disengaged recipients) is also the pattern that degrades the number.

Where the tenant-owned controls sit

Meta owns the threshold; what reaches a recipient, and how often, is your posture. On Orbit each of those inputs is a tenant-configured control:

  • Frequency caps per contact. Orbit's frequency-caps module lets you ceiling how many outbound marketing sends one contact receives over a window — per channel, with per-contact status visible on the contact profile. Set it below the volume your engaged recipients tolerate, and the cap risk surfaces as your own suppressed sends long before Meta starts failing deliveries. Each contact exposes its current cap usage against the limit you configured, so an operator can see a recipient approaching the ceiling instead of learning it from a failed delivery.
  • Quiet-hours send windows. Quiet hours hold outbound sends during a recipient's local off-hours and release them in the sendable window, as the quiet-hours send-timing post describes. The same pacing mechanism is the cap's natural complement: a campaign spread across days spends less of each recipient's marketing ceiling per day than the same campaign fired at once, and the quiet-hours settings announcement covers the tenant API that configures those windows.
  • Template discipline and engagement routing. Under Channels → WhatsApp → Templates you author, submit, and revise templates, with each template's category visible — the category is what counts toward the cap. Route re-engagement through the uncapped lanes where intent is transactional: utility templates for genuinely utility content, and inbound entry points for acquisition traffic that can move to a conversation instead of a template.

None of this is a compliance claim — Meta has not published the threshold, so no vendor can honestly promise you stay under it. What these controls do is make cap risk visible on your side first: a suppressed send in your own log is cheaper to learn from than a pattern of Meta-side delivery failures.

Failure modes, concretely

Three template patterns exhaust a recipient's marketing ceiling, and each has a rewrite:

  1. The daily-deal blast. A retail campaign sends one marketing template per recipient per day, and the same recipients sit in the daily segment. By mid-week every recipient's ceiling is spent, and the weekend offer — the one worth sending — fails to deliver. Rewrite: move the cadence from daily to weekly, and let recipients' replies open service windows for the follow-up offers, which travel the uncapped lane.
  2. The promotional "utility" template. An order-update template ends with "20% off your next purchase." Meta re-classifies it as marketing; the send counts against the cap, bills at the marketing rate, and feeds the quality gates as marketing — three penalties for one footer. Rewrite: split it. A clean utility template carries the update; a separate, correctly-tagged marketing template carries the offer, throttled by your own frequency caps.
  3. The win-back loop. A lifecycle flow re-sends an unopened marketing template every 48 hours to dormant recipients — the cohort least likely to engage and the cohort Meta tightens the ceiling on first. Rewrite: stop the loop after one unopened send, and re-acquire dormant recipients through entry points they choose (a Click-to-WhatsApp ad) instead of escalating template volume against a shrinking ceiling.

Frequently asked questions

What is Meta's per-user marketing template frequency cap?

A per-recipient ceiling on how many marketing template messages one business can deliver to one WhatsApp user inside a rolling window. Once a recipient's ceiling is reached, further marketing sends from that business to that recipient fail at delivery rather than landing, until the window resets or the recipient engages.

Does the cap apply to utility and authentication templates?

No — the cap counts marketing-category templates only. Utility and authentication templates deliver without consuming the recipient's marketing ceiling, which is why category drift matters: promotional copy inside a nominally utility template invites marketing re-classification, and then it counts toward the cap alongside the other marketing treatments.

How many marketing messages can I send one user?

Meta does not publish the threshold, and it varies per recipient — chronically disengaged recipients get tighter ceilings than ones who open and reply. The workable posture is not a number but a control: your own tenant-configured frequency caps, set below what your engaged recipients tolerate, so your sends get suppressed on your side before Meta fails them on theirs.

Is a per-user cap failure the same as a template pause or a quality downgrade?

No. The per-user cap is a per-recipient delivery limit — nothing is wrong with your number or template. A template pause (covered in the quality-rating wave explainer) removes one template from your sendable set for all recipients on recipient feedback. The two mechanisms are independent counters; both punish the same underlying pattern, marketing volume to recipients who do not want it.

Resources

Published 14 September 2026.

Meta's Per-User Marketing Template Frequency Cap, Explained — Orbit by Devotel