
Table of Contents
ToggleThis page tracks the Meta business messaging changes that move over time: pricing, Graph API versions, account rules, onboarding, identity and Conversions API requirements. It exists so every other guide on this site can link here for a date instead of repeating it. If a rule is not on Meta's page yet, the row says "not published yet" rather than guessing.
How Meta charges for business messaging, from the source: Meta's WhatsApp pricing documentation.
| What the rule is | Applies from | Source |
|---|---|---|
| Per-message pricing applies. Conversation-based pricing is deprecated. | 1 July 2025 | Pricing |
| Each business phone number gets 1,000 free delivered service messages per month. Charging starts from the 1,001st. Unused messages do not roll over. | 1 October 2026 | Pricing |
| A business with no payment method on file may lose service message delivery once the free tier is used. | 1 October 2026 | Pricing |
| Service messages remain free beyond the monthly free tier only for eligible government and non-profit organizations. Meta states this pricing policy is in effect through 31 December 2027. | 1 October 2026 | Pricing |
| Utility messages sent in response to users inside an open customer service window are chargeable. They were free before this. | 1 October 2026 | Pricing |
| The free entry point window may remain open for up to 7 days. Marketing, utility, authentication and service messages are free while it is open. | Current | Pricing |
| Meta Business Agent messages are charged per delivered message by token use, at 2.00 USD per 1 million tokens. A message typically uses 20,000 to 25,000 tokens, roughly 4 to 5 cents. Free and volume tiers do not apply, and they stay chargeable inside the free entry point window. | Current | Pricing |
The full pricing playbook is in WhatsApp Business API pricing.
Release and expiry dates for recent versions, from Meta's Graph API versions page. Expired versions are marked so you can see at a glance what is dead.
| Version | Released | Expiry |
|---|---|---|
| v27.0 Current | 4 November 2026 | not published yet |
| v26.0 | 29 July 2026 | not published yet |
| v25.0 | 18 February 2026 | 29 July 2028 |
| v24.0 | 8 October 2025 | 18 February 2028 |
| v23.0 | 29 May 2025 | 8 October 2027 |
| v22.0 | 21 January 2025 | 20 May 2027 |
| v21.0 | 2 October 2024 | 21 January 2027 |
| v20.0 Expired | 21 May 2024 | 24 September 2026 |
| v19.0 Expired | 23 January 2024 | 21 May 2026 |
| What the rule is | Applies from | Source |
|---|---|---|
| The Marketing API keeps its own version table and its own auto-upgrade. When a version is no longer available, a call may fail or be upgraded to the next available version, not the newest. Auto-upgrade does not apply to endpoints that were changed in that version, so those calls fail. An upgraded call returns an X-Ad-Api-Version-Warning header, and auto-upgrade can be turned off in the Marketing API Version setting. | Current | Marketing API versions |
Why expiry matters for your Conversions API and WhatsApp calls is in Graph API version expiry.
The rules that decide who owns a number, from Meta's WhatsApp Business Platform changelog.
| What the rule is | Applies from | Source |
|---|---|---|
| Phone number migration is not supported for accounts on the new WhatsApp account model. The request is rejected unless the destination account already owns the number, and disconnecting the number from its current account does not make it available. | 18 August 2026 | Changelog |
| The documented alternative is account sharing: the client shares the WhatsApp account that owns the number to give a partner access. | 18 August 2026 | Changelog |
| A WhatsApp account is linked to exactly one business phone number. Use messaging_account_id to select the messaging account when an access token can reach more than one on the same number. | 29 August 2026 | Changelog |
| A WhatsApp account (WAAC) holds a single business phone number and represents the business presence on WhatsApp. | Current | WhatsApp accounts |
| A Messaging account holds message templates and billing details, and each partner a business works with has its own Messaging account. | Current | WhatsApp accounts |
| An existing WABA ID now identifies the Messaging account, not a WhatsApp account. The ID and the field name are unchanged, so existing API calls still work. | Current | WhatsApp accounts |
| Meta Business Accounts are initially limited to 20 WhatsApp account hierarchies, and a WhatsApp account or a Messaging account must belong to only one business portfolio. | Current | WhatsApp accounts |
What to ask a provider before you sign is in how to choose a WhatsApp BSP.
How businesses get connected, from Meta's changelog.
| What the rule is | Applies from | Source |
|---|---|---|
| Embedded Signup v2 reaches its deprecation date. | 8 October 2026 | Changelog |
| The Embedded Signup v4 Phone Number First flow enters Coexistence automatically when the number is already in use with the WhatsApp Business app. | 3 September 2026 | Changelog |
Getting verified and approved first is the WhatsApp business verification step.
These Meta business messaging changes to contact identity come from Meta's business-scoped user IDs documentation.
| What the rule is | Applies from | Source |
|---|---|---|
| BSUIDs started appearing in webhooks. | Early April 2026 | BSUID |
| Sending to a BSUID became supported. | July 2026 | BSUID |
| Business username reservations began. | 29 June 2026 | BSUID |
| BSUID format is a two-letter country code, a period, then up to 128 alphanumeric characters. Parent BSUIDs use an ENT prefix. | Current | BSUID |
| Webhook fields: user_id, from_user_id, recipient_user_id, recipient_participant_user_id, previous_user_id, parent_user_id. | Current | BSUID |
| When a user adopts a username, the phone number is left out of webhooks unless a message or call was exchanged with that number in the last 30 days, evaluated per business phone number, or the user is in the contact book. | Current | BSUID |
| Phone numbers and related data are retained for a maximum of 30 days. | Current | BSUID |
| The REQUEST_CONTACT_INFO button is available to ask a user for their phone number. | Early July 2026 | BSUID |
| Meta hosts a contact book at business portfolio level. A read-only GET request to the contact_book edge returns a boolean present flag. | Current | BSUID |
What this means for a CRM is in WhatsApp business usernames, and the build is the WhatsApp CRM and Cloud API service.
What each channel needs, from Meta's Conversions API for Business Messaging documentation.
| What the rule is | Applies from | Source |
|---|---|---|
| Send ctwa_clid whenever it is available. | Current | CAPI |
| Without ctwa_clid, the hashed path requires page_id and the event is rejected if page_id is missing. It also needs at least one customer information parameter, an ad interaction within 7 days, works only in a subset of countries, and the match is not guaranteed. | Current | CAPI |
| WhatsApp: action_source is business_messaging and messaging_channel is whatsapp. | Current | CAPI |
| Messenger: page_events permission; page_id, dataset_id and the page-scoped user ID; user_data carries page_id and page_scoped_user_id; messaging_channel is messenger. Purchase optimization is available for ads that click to Messenger. | Current | CAPI |
| Instagram: instagram_manage_events permission; instagram_user_id for dataset setup, dataset_id and the Instagram-scoped ID; sample user_data uses instagram_business_account_id and ig_sid; messaging_channel is instagram. Purchase optimization is not available for Instagram ad optimization at this time. | Current | CAPI |
| Meta documents no click ID for Messenger or Instagram. ctwa_clid is WhatsApp only. | Current | CAPI |
| Supported event names: Purchase, LeadSubmitted, InitiateCheckout, AddToCart, ViewContent, OrderCreated, OrderShipped, OrderDelivered, OrderCanceled, OrderReturned, CartAbandoned, QualifiedLead, RatingProvided, ReviewProvided. | Current | CAPI |
Test a payload in the free CAPI debugger.
The inbound referral field differs by Business Solution Provider. Only the Twilio field is confirmed here from a primary source.
| Provider | How the ad click ID is handled | Source |
|---|---|---|
| Twilio | Exposes the Click-to-WhatsApp click ID as ReferralCtwaClid in the inbound webhook. | Twilio changelog, 15 March 2024 |
| Other providers | Field names and behaviour vary. Some pass Meta's raw referral object, some rename the field, and some send Conversions API events themselves instead of handing the data over. Confirm the exact field, or whether the provider sends CAPI for you, with your provider. | Confirm with provider |
A provider's behaviour can change without notice. Always confirm the current field name and Conversions API handling with your own provider before you rely on it.
If you want these Meta business messaging changes handled in your own setup, from ad tracking to CRM identity, that is the kind of work I take on as a service. Start with WhatsApp conversion tracking or the WhatsApp CRM and Cloud API service.
Quick answers about this Meta business messaging changes reference.
It is a single reference that tracks the dated rules for Meta business messaging, so every other guide can link here instead of repeating dates.
The "Last checked" date at the top shows when it was verified. Treat anything after that date as unconfirmed until the page is rechecked.
Meta had not published that date or detail at the last check. No date is ever guessed or calculated here.
No. Meta documents ctwa_clid for WhatsApp only, with no click ID for Messenger or Instagram.
Paste a payload into the CAPI debugger, linked in the Conversions API section above.