تخطَّ إلى المحتوى الرئيسي
كل الأخبار
Pricing

Meta now lets you cap what a marketing message costs — and most businesses have not noticed

Since October 1, 2026 you can set a maximum price you are willing to pay per marketing message delivery — the first cost control Meta has given businesses over template pricing. It is in Open Beta, it is documented, and almost nobody is using it.

ماذا حدث

Meta's documentation page is titled Set a max price for marketing messages (BETA). It describes "the first pricing feature" that allows a business to "set a maximum price (max price) per marketing message delivery".

The rollout has three stages. Limited Beta started May 15, 2026. Meta's Marketing Messages changelog entry of September 15, 2026 announced that the feature enters Open Beta on October 1, 2026. General Availability is listed as Q2 2027, tentative.

You set it with an optimization_spec object, using bid_amount for the ceiling and bid_strategy set to LOWEST_COST_WITH_BID_CAP.

The unit is the part that catches people. bid_amount is a cap per 1,000 deliveries, not per message. Meta's own examples make this concrete: 87000 means ₹0.87 per delivery, and 5000 means $0.05 per delivery.

The old field is dead. optimization_spec replaced bid_spec as of June 18, 2026, and bid_spec was accepted only until July 31, 2026. Anything still sending it now fails with error 131061 — "Marketing templates containing bid_spec are not supported by the Cloud API."

Meta's own page contradicts itself here. The section headed "Adjust max price when sending messages" still shows a request example built on a bid_spec object, on the same page that declares bid_spec unsupported. We are reporting the inconsistency rather than guessing which half is current.

ماذا يعني ذلك لعملك

This is the first ceiling you have ever been able to put on marketing delivery cost. Until now a marketing template cost whatever your market's rate card said, and the only lever was sending fewer messages. A cap changes the shape of the decision: you can commit a budget per delivery rather than per campaign.

Check the unit before you set anything. A team that reads bid_amount as a per-message figure will be out by a factor of a thousand in whichever direction hurts. ₹0.87 per delivery is written as 87000. There is no friendlier way to say it.

If you have an older integration, this is worth ten minutes today. bid_spec stopped being accepted on July 31, 2026, so a template that silently stopped sending in August may be failing on error 131061 rather than anything to do with content or quality rating.

One thing the documentation does not answer, and it matters. A bid cap set below your market's going rate has to resolve somehow — either the message is not delivered, or the cap is ignored. Meta's page does not say which. Until it does, treat max price as a spend ceiling that may cost you reach, not as a discount, and test it on one campaign before you apply it across an account.

The honest summary: this is a real lever, it is documented, and it is in open beta — which is exactly the stage where the behaviour is worth verifying on your own account rather than trusting anyone's blog post, including ours. Our walkthrough of the October changes is in the service message pricing guide.

What changed in WhatsApp pricing on October 1, 2026