Meta now lets businesses set a maximum price for delivered WhatsApp marketing messages through the Marketing Messages API, in open beta since October 1, 2026. Since November 1, max-price traffic is billed under a separate SKU, and the old conversation_analytics field is retired. Here is how it works and what to check if you send WhatsApp marketing at scale.
What max price is
Instead of paying the published per-message rate, a business can set a cap per template. Meta's documentation says it will charge that max price or lower for each delivery, and the cap can be set the same as, lower than or higher than the published rate. Meta describes it as a bid cap, not a budget.
The feature moved from a limited beta in May to open beta on October 1, 2026. General availability is listed as tentative for Q2 2027, and fixed rate-card pricing remains available.
How it is set up
The cap lives on the template in an optimization_spec object. The bid_amount field is the maximum price per 1,000 deliveries, in the smallest unit of your messaging account currency, and the only supported strategy is LOWEST_COST_WITH_BID_CAP. Country multipliers can raise or lower the cap by market.
It only works through the Marketing Messages API on an onboarded account in an eligible country. Sending a max-price template through the standard Cloud API messages endpoint returns an error. Once an account is enrolled, eligible existing templates can switch between rate-card pricing and max price without creating a new template.
- Lower caps reach fewer recipients at lower cost; Meta offers a reach-estimation endpoint
- A per-message multiplier can adjust the cap at send time (subject to change in beta)
- The older bid_spec field is no longer supported
What changed on November 1
Starting November 1, 2026, max-price traffic appears under its own billing SKU and identifiers, shown as MARKETING_LITE_DYNAMIC in pricing analytics. Meta's analytics documentation also lists the conversation_analytics field as unavailable from that date, so cost and volume reporting should come from pricing_analytics.
If you run click-to-WhatsApp ads and follow up with template marketing, update dashboards and invoice reconciliation now, or November messaging spend can look like it is missing or double counted.
What it means for you
- Max price is optional and still in beta; rate-card pricing remains
- Switch reporting from conversation_analytics to pricing_analytics
- Map the MARKETING_LITE_DYNAMIC SKU in your invoice reconciliation
- Test caps on one template and market before rolling out widely
Sources
- Meta for Developers: Marketing Messages API pricing
- Meta for Developers: Marketing Messages API changelog
- Meta for Developers: WhatsApp Business analytics
