What Is Changing in the WhatsApp Business Account Model in 2026?
The WhatsApp Business account, the WABA most teams have worked with for years, is splitting into two separate accounts. A WhatsApp account, which Meta abbreviates as WAAC, holds the business's identity: phone numbers, business usernames in future, business profile information and product catalogs. A Messaging account holds template messages, billing and payment methods, and webhook subscriptions. Meta's stated reason is to let one phone number work with several partners without the business appearing as several contacts.
The phrase that matters most for anyone running a live integration comes straight from Meta: your existing IDs and API calls continue to work. Your existing WABA ID becomes your Messaging account ID. Nothing in day-to-day sending has to change at the first phase, unless you are in one specific multi-account situation covered below.
| New account | What it contains | Who owns it |
|---|---|---|
| WhatsApp account (WAAC) | Phone numbers, business usernames (future), business profile information, product catalogs | Always the client or direct developer. Shareable with direct integrations and multiple partners. |
| Messaging account | Message templates, billing and payment methods, webhook subscriptions | The client or a partner. Each partner working with a client gets its own Messaging account. |
Why Is Meta Splitting the WABA in 2026?
Because the old WABA bundled phone numbers, templates, billing, webhooks and partner access into one entity, which meant working with several partners required a separate phone number for each. Customers then saw the same brand as several different contacts in their chat list. Separating identity from templates and billing lets one trusted number work across every integration, with each integration keeping its own isolated templates, billing and analytics.
For a marketing team this solves a real and common problem. A brand that uses one provider for marketing campaigns, another for customer support and its own developers for transactional messages no longer needs three numbers. WhatsApp users see a single contact regardless of how many partners sit behind it.
- Specialist partners on one number: one provider can run marketing, another service, another authentication or calling, all on the same number.
- Separate billing per partner: each partner has its own Messaging account and its own payment method.
- Different currencies on one number: each currency can have its own Messaging account, without separate phone numbers per currency.
- No number migration to add a partner: clients can add or change partners without migrating their phone number, and existing conversations continue uninterrupted.
When Does the New Account Model Arrive in 2026?
Phase 1, general availability, rolled out from 23 September 2026 and was due to reach all businesses by mid-October 2026. Businesses migrate in stages rather than on a single day. Until your business is migrated, WhatsApp Manager and Meta Business Suite keep showing the previous WABA experience, so the documentation can be ahead of what you see on screen for a while.
| Phase | Timing | What it means for you |
|---|---|---|
| Phase 1: General availability | From 23 September 2026, all businesses by mid-October 2026 | Meta migrates accounts automatically. Existing IDs and API calls keep working. No code changes required except multi-Messaging account setups. |
| Phase 2: New Graph API version | H1 2027 | The newest Messages API requires messaging_account_id for multi-Messaging account setups. New endpoints and a distinct WAAC ID arrive. |
| Phase 3: Mandatory transition | H1 2028 | All Messages API versions require messaging_account_id in multi-Messaging account setups, and APIs that target a phone number ID in the path must use WAAC IDs. |
The practical reading: Phase 1 in October 2026 is a migration Meta performs for you. The engineering work belongs to 2027, ahead of the Phase 3 cutover in H1 2028. That is a long runway, which is exactly why it is easy to leave until it is short.
What Stays the Same After the Migration in 2026?
Almost all of the surface you use today. Meta's position is that the migration preserves your data: phone numbers, templates, business profiles and payment methods carry over, and existing clients do not need to re-onboard. The list below is what a team should be able to tell a nervous client on the day their dashboard changes.
- Your WABA ID: it becomes your Messaging account ID, unchanged.
- Your phone number IDs: they continue to work with all APIs during Phases 1 and 2.
- Your access tokens and endpoints: unchanged at Phase 1.
- Template workflows: create, edit, delete and submit for review work the same way, and template management stays on the Messaging account.
- Webhook subscriptions: you continue to subscribe using your Messaging account ID.
What Changes That Teams Will Actually Notice in 2026?
Three operational behaviours change in ways that affect cost, delivery and quality, and none of them are obvious from the headline. Each matters more the moment a second partner is added to a number.
Template isolation and the quality reset
Templates belong to the Messaging account in which they were created and are not shared across Messaging accounts. If a second partner needs the same template, it must be created again in that partner's Messaging account or copied with the Template Migration API. Meta states that when templates are migrated to a new Messaging account, their quality ratings and messaging tier reset to baseline, requiring a ramp-up period of approximately two to four weeks.
A template copied to a new partner's Messaging account starts again at baseline quality and messaging tier, and needs roughly two to four weeks to ramp. If you are moving campaign sending to a new partner ahead of a seasonal peak, start the move a month earlier than the calendar suggests, or the new account will not have the throughput history to carry the volume.
Billing isolation and credit lines
Each Messaging account has its own payment method, completely independent from other Messaging accounts and from ad accounts. Meta adds a specific rule that matters to agencies: if you attach your credit line to a client-owned Messaging account, that Messaging account cannot be shared with another partner. Agencies that extend credit to clients should decide deliberately whose Messaging account carries it.
Shared throughput and shared limits
Throughput stays at the phone number level, so when several partners share a number, they share its throughput capacity. Messaging limits stay at the business portfolio level, so the limit on unique users per 24-hour period is shared across every partner on that number. Two partners on one number do not get double the headroom. They split it.
| Behaviour | Where it sits in 2026 | Consequence with several partners |
|---|---|---|
| Templates | Messaging account | Not shared. Recreate or migrate, with a quality and tier reset. |
| Billing | Messaging account | Isolated per partner. A credit line on a client-owned account blocks sharing. |
| Throughput | Phone number | Shared across all partners on the number. |
| Messaging limits | Business portfolio | Unique users per 24 hours shared across all partners on the number. |
How Does Switching Partner Work Under the New Model in 2026?
It no longer involves moving the number. Clients can add or change partners without migrating their phone number, and existing conversations are not interrupted when a new partner is added. Meta notes that the phone number migration process that used to act as a natural switching barrier no longer applies, and tells partners who extend credit lines to factor that into their risk management.
That is good news for brands and a genuine shift for agencies. Leaving a provider used to be painful enough that it rarely happened. In 2026 the switching cost falls sharply, which means retention depends on results rather than inertia. Before adding a partner, though, read the partner assignment readiness checklist, because adding one can change which integration receives incoming messages.
Why Has Switching BSP Become Easier, and Riskier?
It became easier because the number no longer moves. Under the new business account model, migrating a business phone number from one Solution Partner to another is not how switching works. A client shares its WhatsApp account with the new partner instead, and Meta notes that sharing is additive: whether the client keeps or later removes the previous partner is its own decision, and neither is a prerequisite for onboarding the new one.
It became riskier because several integrations can now share one number, and something has to decide which of them answers each customer. That something is Conversation Routing. When only one integration was connected, every message simply went to it. With two or more, the platform has to pick, and an integration that used to receive everything can find itself receiving nothing.
- No number migration: clients can add or change partners without migrating their phone number, and existing conversations are not interrupted.
- No natural switching barrier: Meta notes that the number migration process that once discouraged switching no longer applies.
- Shared capacity: partners on one number share its throughput and its messaging limit.
- Separate billing: each partner has its own Messaging account and payment method.
How Does Conversation Routing Decide Who Receives Messages?
Conversation Routing assigns each inbound message to a single responder when several integrations are connected to the same WhatsApp account, rather than broadcasting to all of them. It works in two steps: it identifies the entry point, meaning how the user arrived, such as a Click to WhatsApp ad, a reply to a template, or a standard message, and it then resolves which responder is configured as primary for that entry point.
| Role | What it does in 2026 |
|---|---|
| Primary responder | Receives inbound messages for its entry point. When a new thread begins, the primary becomes the thread owner. |
| Thread owner | The responder currently responsible for a thread, and the only party that should send messages to the user on it. |
| Standby partner | Receives copies of traffic on threads it does not own, through the standby webhook. A standby partner must not reply to the user. |
| Escalation partner | A single designated partner that can take control of any thread regardless of who owns it. |
The consequence for everyone else is stark. Only standby partners receive copies of messages they do not own. Every other non-primary integration receives no inbound message traffic at all. Ownership moves between responders through three thread control actions, pass, release and take, and Meta noted on 25 September 2026 that a successful action now returns a request_id to quote to support.
When Does Assigning a Partner Change Routing?
Only when no routing configuration exists yet. Meta states that a configuration is only ever created when the account does not already have one, and that adding another partner does not overwrite an existing configuration. Agency-only access does not change routing. The risky case is therefore specific: a business that has been running one or more integrations with no routing configuration, which then assigns another partner.
| Your situation | Effect of assigning another partner |
|---|---|
| No routing configuration exists | Can create the initial configuration and change delivery for existing integrations |
| A routing configuration already exists | Not overwritten; existing routing roles remain unchanged |
| Agency-only access is granted | Does not change routing |
What an existing integration can lose
When routing applies and an existing integration is not selected as primary, Meta lists three effects. It may stop receiving incoming messages through its normal integration. It may receive standby copies only if standby visibility is granted and it is prepared to process them. And some of its replies may be rejected when it does not own the conversation. Meta also stresses that the type of partner does not determine which integration becomes primary, so review the actual configuration rather than assuming.
Why the damage can arrive slowly
Routing configuration applies to new threads. Existing owned threads keep their current owner until a thread control action or an idle window changes ownership. Saving a configuration does not transfer conversations that already have an owner. In practice that means a broken integration may look fine for days, then degrade as conversations go idle and get re-routed, which is exactly the pattern that makes the cause hard to trace back to the partner assignment.
Which Integrations Can Be Affected?
Any integration that uses a business phone number in the WhatsApp account. Meta's list deliberately includes integrations a business may not think of as "partners" at all.
- An integration managed by an existing partner.
- An integration your business manages directly.
- A technology provider's integration connected through another provider.
- An automated customer-service integration that sends replies, such as a chatbot or helpdesk.
Calling is separate. Incoming calls use webhook-only routing, and call responders never become thread owners, so a team whose integration handles calling must review calling webhooks on their own rather than assuming messaging routing covers them. Our calling rate card guide covers the pricing side of that channel.
What Is the Readiness Checklist Before You Switch BSP?
Meta's guide gives a short sequence. The version below follows its order, with the operational detail a business needs to actually complete each step.
- Open Conversation Routing in Meta Business Suite and check whether a routing configuration already exists.
- If none exists, list every integration across all business phone numbers in the WhatsApp account, including partners, your own direct integration, any provider-of-a-provider, and any chatbot or helpdesk that replies. An account-default configuration applies to every phone number unless a phone-number-specific configuration overrides it.
- Send each responsible partner or developer the readiness resources and ask them to confirm their integration is ready for Conversation Routing.
- Assign the new partner only after every existing integration confirms readiness.
- If a configuration already exists, assigning does not overwrite it, but coordinate with affected partners before changing their roles later.
- After assigning, review the account-default and every phone-number-specific configuration, including the primary responder, standby visibility and escalation partner.
The readiness resources to send
| Resource | Who needs it | What it covers |
|---|---|---|
| Prepare for Conversation Routing | Every integration | How routed delivery differs from single-responder delivery, and how to prepare before routing applies. |
| Standby partners | Integrations that should still see traffic they do not own | Subscribing to standby webhooks, requesting standby visibility, processing unowned conversations. |
| Thread control | Every integration that replies | Subscribing to ownership events, tracking ownership, and implementing pass, release and take. |
| Calling webhooks | Integrations that handle calling | Call routing and webhook delivery, which are separate from messaging thread ownership. |
Who Has to Act When You Switch?
| Party | Responsibility |
|---|---|
| The business that owns the WhatsApp account | Checks routing first, inventories integrations, collects readiness confirmations, and reviews the configuration after assigning. |
| The incoming partner | Gets the client to share its existing WhatsApp account and confirms its own integration handles routing roles. |
| Existing partners and developers | Confirm readiness: standby handling, thread control, and owner-only replies. |
| The chatbot or helpdesk owner | Confirms its replies will not be rejected when it is not the thread owner. |
Templates are a separate consideration. Each partner has its own Messaging account, templates are not shared between Messaging accounts, and templates migrated to a new one reset to baseline quality and messaging tier with roughly a two to four week ramp. Plan the template move before the routing move, especially ahead of a campaign. For the template side, see our guide to template category updates, and for the October cost changes, the service message pricing guide.
What Are the Common Mistakes When Switching?
- Assigning the new partner first and checking later. Without an existing configuration, the assignment itself can create one.
- Forgetting the chatbot. An automated customer-service integration that replies is an integration, and can stop receiving messages.
- Assuming the bigger partner becomes primary. Partner type does not decide it; the configuration does.
- Declaring success on day one. Routing applies to new threads, so problems surface as conversations go idle.
- Checking one phone number. An account-default configuration covers every number unless overridden.
- Letting a standby partner reply. Meta states a standby partner must not reply to the user.
- Assuming calling follows messaging. Calls use webhook-only routing and are reviewed separately.
What Do Developers Need to Do in 2026?
For most direct developers, nothing during Phase 1. The exception is any setup where an access token has messaging access to more than one Messaging account on the same business phone number. That is the case in which Meta cannot tell which Messaging account to bill and attribute a message to, and it is where the messaging_account_id parameter comes in.
- Phase 1:
messaging_account_idis available and optional. The olderpaid_messaging_account_idworks as a deprecated alias. - By 31 December 2026: migrate from
paid_messaging_account_idtomessaging_account_id. After that date the alias is planned for removal in a future Graph API version. - Phase 2, H1 2027: the newest Messages API version requires
messaging_account_idin multi-Messaging account setups. - Phase 3, H1 2028: all Messages API versions require it in those setups, and phone-number-ID paths move to WAAC IDs.
The messaging_account_id migration section covers the rule, the deadline and the attribution consequences in detail.
Why Does messaging_account_id Exist?
Because one phone number can now be linked to more than one Messaging account. Under the new account model, each partner working with a client gets its own Messaging account for templates and billing, and each billing currency can have its own Messaging account too. When a single access token can reach several of those on the same number, Meta cannot tell which one to bill and attribute a message to. messaging_account_id is how you tell it.
Meta states the rule as a single condition: include the parameter whenever the access token you are sending with has messaging access to more than one Messaging account on the business phone number in your request. Everything else, the multi-partner cases, the multi-currency cases, a direct developer holding several Messaging accounts on its own number, is an example of that one rule rather than an exception to it.
When Do You Actually Need to Send It?
Only in multi-Messaging account situations. If your token reaches exactly one Messaging account on the number you are sending from, the question does not arise, because there is only one account to bill. The table below sorts the common setups.
| Setup | Token reaches more than one Messaging account on the number? | Send messaging_account_id? |
|---|---|---|
| One brand, one provider, one currency | No | Not needed |
| Two partners on one number, each using its own token | Usually no, each token sees its own account | Not needed unless a token reaches both |
| Direct developer with several Messaging accounts on its own number | Yes | Yes |
| One number billing in two currencies via two Messaging accounts | Yes, if one token reaches both | Yes |
| Agency token with access to several client Messaging accounts on one number | Yes | Yes |
The timing of the requirement is staged. At Phase 1, general availability in late 2026, the parameter is optional. From Phase 2 in H1 2027 the newest Messages API version requires it for multi-Messaging account setups, while older versions still accept calls without it and Meta attempts to resolve the account from your app's association. From Phase 3 in H1 2028, every Messages API version requires it in those setups.
What Does messaging_account_id Do to Billing and Analytics?
It decides where a message is counted. Meta explains that a message counts toward the analytics and the charges of the Messaging account it was sent from, and that messaging_account_id is what selects that Messaging account when more than one is reachable. Get it wrong and nothing fails loudly. The message is delivered, billed and reported against the wrong account.
If a brand runs marketing through one partner and support through another on the same number, and a shared token sends without the right messaging_account_id, marketing spend can land on the support account or the reverse. Each Messaging account carries its own payment method, so the error shows up as an unexpected invoice on the wrong card, and as campaign metrics that do not add up.
- Analytics: a message appears in the analytics of the Messaging account it was sent from.
- Charges: a message is billed to that Messaging account's payment method.
- Currency: because currencies can sit on separate Messaging accounts, the parameter also decides which currency a message is billed in.
What Is the INR Billing Deadline for Indian Businesses?
WhatsApp billing localisation launched on 1 January 2026 for partners and directly integrated businesses whose Sold-To country is India in Billing Hub. Meta calls these eligible customers. Eligible customers must ensure every account in their business portfolio is migrated to INR by 31 December 2026 to avoid disruption, because from 1 January 2027 Meta will no longer deliver the messages of non-INR accounts belonging to eligible customers.
Meta provides a Currency Migration API, available since 1 June 2026, to make the move faster. Brazil follows the same pattern a year later: eligible Brazilian customers must migrate to BRL by 30 June 2027, with non-BRL delivery stopping on 1 July 2027.
| Market | Localisation launch | Migrate all accounts by | Non-local delivery stops |
|---|---|---|---|
| India (INR) | 1 January 2026 | 31 December 2026 | 1 January 2027 |
| Brazil (BRL) | 1 July 2026 for new accounts | 30 June 2027 | 1 July 2027 |
The link between the two deadlines is direct. The new account model lets one phone number carry several Messaging accounts in different currencies. An Indian business mid-migration may briefly have both a USD and an INR Messaging account on the same number, which is exactly the situation where messaging_account_id decides which one a message is billed to.
Prepaid billing with UPI in India
Meta also added a guide in September 2026 for accounts in India that fund messaging with UPI top-ups instead of invoiced billing. It covers how the funds check works and why a send can return accepted and still be rejected for insufficient funds on the status webhook, with error 131042. Teams on prepaid UPI billing should treat the status webhook, not the API's acceptance response, as the record of whether a message actually went out.
How Do You Migrate Before 31 December 2026?
Treat it as two parallel workstreams: one in the code, one in Billing Hub. Neither is large, and both have the same deadline.
Code workstream
- Search every integration for
paid_messaging_account_id, including any provider SDK you depend on. - Replace it with
messaging_account_id. Meta documents precedence when both are supplied, but the clean state is to send only the new name. - List every access token and, for each phone number, how many Messaging accounts that token can reach.
- Send
messaging_account_idexplicitly wherever a token reaches more than one, rather than relying on Meta's resolution. - Plan the move to the Phase 2 Messages API version for 2027, since that is where the parameter becomes required.
Billing workstream for India
- Confirm your Sold-To country in Billing Hub, since that is what makes you an eligible customer.
- List every account in the business portfolio and its current billing currency.
- Migrate each non-INR account to INR using the Currency Migration API or Billing Hub, well before 31 December 2026.
- Verify sends after each migration by checking status webhooks rather than API acceptance.
- Brief finance that invoices and payment methods will change currency.
Who Has to Act: the Business, the Partner or the Developer?
| Party | What they own |
|---|---|
| The business | Billing Hub settings, the INR migration decision for its own portfolio, and confirming partners are ready. |
| The partner or BSP | Its own integration code, its own Messaging accounts, and any tokens that reach several client accounts. |
| The direct developer | Replacing paid_messaging_account_id, sending messaging_account_id where needed, and the 2027 API version upgrade. |
If you work through a provider, the right question to ask them this quarter is short: have you replaced paid_messaging_account_id, and have our accounts been moved to INR? For the cost changes already live from 1 October 2026, see the service message pricing guide.
What Are the Common Mistakes?
- Treating the INR deadline as a billing preference. From 1 January 2027 non-INR accounts of eligible customers stop delivering.
- Assuming a provider has handled it. Ask, and confirm in Billing Hub.
- Leaving
paid_messaging_account_idin place. Migrate by 31 December 2026. - Relying on Meta to guess the account. Send
messaging_account_idwhenever a token reaches more than one Messaging account. - Ignoring misattribution. A message with the wrong account is billed and reported against the wrong account, silently.
- Trusting
acceptedon prepaid UPI billing. Insufficient funds can still reject the send on the status webhook. - Leaving the 2027 upgrade until 2028. Phase 3 makes the parameter required on every API version.
How Should Brands and Agencies Prepare in 2026?
Map who sends what from each number before October ends, because that map is what every later decision depends on. The checklist below is the minimum a brand or an agency managing client numbers should complete.
- List every phone number and every partner and direct integration that sends from it.
- Note who owns each Messaging account and whose payment method or credit line sits on it.
- Identify any shared-number setups where one access token reaches more than one Messaging account.
- Search your code for
paid_messaging_account_idand schedule its replacement before 31 December 2026. - Plan template moves early, allowing two to four weeks for quality and tier to ramp on a new Messaging account.
- Budget shared throughput and limits across partners on the same number rather than assuming each partner gets its own.
- Brief clients before their dashboard changes, since Meta Business Suite will show separate WhatsApp Accounts and Messaging Accounts tabs after migration.
For the cost side of the same month, see our guide to the 1 October 2026 service message pricing change. For the broader platform, the WhatsApp Business API guide covers the fundamentals.
What Are WhatsApp Landing Page View Events?
A landing page view event is a webhook Meta sends when a WhatsApp user taps a link in your marketing message and the landing page opens in the WhatsApp In-App Browser. Meta added the webhook reference on 23 September 2026. It is available using the Marketing Messages API for WhatsApp and Ads Manager only, and its purpose is precise: to measure how many users actually reached your landing page, not just how many tapped the link.
That distinction is the whole value. A tap tells you intent. A landing page view tells you the page actually loaded in front of someone. The gap between the two is where slow pages, broken links and redirect chains quietly lose a campaign's traffic, and until now a WhatsApp marketer could see only the first number.
Why Does a Landing Page View Event Matter for Attribution?
Because WhatsApp campaigns have had a blind spot exactly where most of the money is lost. A click event tells you a link was tapped. It says nothing about whether the page rendered. If a tenth of your taps never reach a loaded page, every downstream metric, from cost per visit to conversion rate, is computed against an audience that partly never existed.
- Tap-to-load drop-off becomes visible: compare click events to landing page views for the same campaign and you have a direct measure of how much traffic the page itself is losing.
- Page speed gets a WhatsApp-specific number: the In-App Browser is its own environment, and this is a measurement taken inside it.
- Campaign cost becomes honest: cost per landing page view is a more truthful denominator than cost per click.
- Creative and page problems separate: a high click rate with low page views points at the page, not the message.
Meta has also just introduced a way to bid on marketing message delivery, covered in our guide to max price. Paying more for delivery only makes sense if you can see whether the delivered taps reach a page, which is why these two features belong in the same plan.
How Does the Landing Page View Webhook Work?
You subscribe to the whatsapp_business_account webhook topic, and Meta delivers the payload on the messages field. If you already receive click events for marketing messages, you do not need to add a subscription, because landing page views arrive through the same topic and field.
Inside the payload, a user_actions entry carries the event. Its action_type is landing_page_view, and it includes a timestamp plus a marketing_messages_link_click_data object holding the correlation keys.
| Field | Required | What it is |
|---|---|---|
action_type | Required | The name of the action, set to landing_page_view. |
timestamp | Required | Unix timestamp in seconds of when Meta recorded the landing page view. |
marketing_messages_link_click_data.tracking_token | Optional | Internal Meta token used to match the landing page view to the click event for the same marketing message. Omitted when a token is not available. |
marketing_messages_link_click_data.click_id | Optional | Unique identifier for the click that opened the In-App Browser. Omitted when not available. |
Why the container is called link_click_data
Landing page view data arrives in marketing_messages_link_click_data, the same container used by click events. Meta explains that the object holds the payload for every user action on a marketing message, and that its name reflects its original click-only use. The action_type is what tells you which action a given payload describes, so never infer the event type from the container name.
How Do Landing Page Views Relate to Click Events?
A landing page view corresponds to a click event with the same tracking_token. Click events arrive with action_type set to marketing_messages_link_click on the same topic and field. Matching the two is how you build the tap-to-load funnel, but Meta is explicit about three behaviours that a naive implementation will get wrong.
- Order is not guaranteed. Meta does not guarantee which of the two events arrives first, so do not require the click event to have arrived before processing a landing page view.
- A landing page view can arrive with no matching click. Design your store to accept an unmatched view rather than discarding it.
- Both keys can be missing. When
tracking_tokenis absent, useclick_id, which appears on both payloads. When neither is present, the landing page view cannot be correlated to a click event.
| Field | Click event | Landing page view |
|---|---|---|
action_type | marketing_messages_link_click | landing_page_view |
tracking_token | Optional | Optional |
click_id | Optional | Optional |
click_component | Optional, cta or body | Not included |
product_id | Optional, when assigned through Ads Manager or the Marketing API | Not included |
One more detail matters for analytics. The click_id on a click event is appended to the original URL when the user visits it. That means your own landing page analytics can capture the same identifier the webhook carries, which is the cleanest way to join WhatsApp-side events to on-site behaviour.
What Are the Limitations to Know Before You Build?
Two limitations shape any implementation. The feature is currently in limited availability, so not every account will receive these events yet. And landing page view events are only available for tracking links created in the last seven days. Click events carry a parallel restriction: they are only available for messages sent in the last seven days.
This is a live measurement stream, not a historical report. If you want month-over-month funnel analysis, you have to capture and store the events yourself as they arrive. A team that plans to look back at last quarter's tap-to-load rate in Meta's tools will find there is nothing there to look at.
Build for new action types
Meta states that action_type is an open enum, which means new values may be added over time without that being a breaking change. Your webhook handler must ignore action types it does not recognise rather than treating them as errors. A handler that throws on an unknown value will start failing the day Meta adds the next one, so this is a one-line fix worth making before you deploy.
How Should a Team Implement This?
Treat it as a small data pipeline rather than a dashboard toggle. The checklist below is the minimum for a funnel you can trust.
- Confirm availability for your account, since the feature is in limited availability, and confirm you are sending through the Marketing Messages API or Ads Manager.
- Confirm your subscription to the
whatsapp_business_accounttopic. If you already receive click events, nothing else is needed. - Branch on
action_type, not on the container name, and ignore unknown values. - Store every event immediately, since the data is limited to links and messages from the last seven days.
- Join on
tracking_token, then fall back toclick_id, and keep unmatched views rather than dropping them. - Never require the click first. Arrival order is not guaranteed.
- Capture
click_idon your landing page from the URL, so WhatsApp events and site analytics share a key. - Report tap-to-load as a ratio per campaign, and investigate the page whenever it falls.
How Should Marketing Teams Use the Funnel?
Use the gap between taps and page views as a diagnostic, not a vanity metric. The two numbers tell you different things, and the ratio between them points at a specific owner when something goes wrong.
| What you see in 2026 | Likely cause | Who should look at it |
|---|---|---|
| Low taps, healthy tap-to-load ratio | The message or offer is not compelling | Copy and creative |
| Healthy taps, low landing page views | Page loads slowly or fails in the In-App Browser | Web team |
| Ratio drops after a site change | A new script, redirect or broken link | Web team, compared against the release |
| Many unmatched landing page views | Missing correlation keys | Whoever owns the webhook pipeline |
| Nothing arriving at all | Limited availability or wrong API path | Whoever owns the WhatsApp integration |
A landing page that loads fast for a desktop visitor can still struggle inside a mobile in-app browser, so this is one of the few places where WhatsApp campaign performance and page performance can be measured on the same footing. For the cost changes landing in the same month, see our service message pricing guide, and for the broader channel, the WhatsApp sales and open rates guide.
What Are the Common Mistakes?
- Inferring the event type from the container name. Landing page views arrive in
marketing_messages_link_click_data. Useaction_type. - Requiring the click event first. Meta does not guarantee arrival order.
- Dropping unmatched views. A landing page view can arrive without a matching click.
- Joining on
tracking_tokenonly. Fall back toclick_idwhen the token is missing. - Throwing on unknown
action_typevalues. It is an open enum; ignore what you do not recognise. - Expecting history in Meta's tools. Events cover only the last seven days, so store them yourself.
- Adding a duplicate subscription. If you already receive click events, nothing more is needed.
What Are the Common Mistakes in 2026?
- Assuming your integration breaks in October. Meta states existing IDs and API calls continue to work.
- Assuming a copied template keeps its quality. Quality rating and messaging tier reset to baseline with a two to four week ramp.
- Assuming a second partner doubles capacity. Throughput and messaging limits are shared on the number.
- Attaching a credit line without thinking about sharing. A credit line on a client-owned Messaging account prevents sharing it with another partner.
- Leaving
paid_messaging_account_idin the code. Migrate by 31 December 2026. - Treating Phase 3 as distant. H1 2028 needs engineering work planned during 2027.
- Adding a partner without checking routing. It can change which integration receives incoming messages.
Key Takeaways for 2026
The account model change is a migration Meta runs for you in October 2026, with real engineering work scheduled for 2027 and a hard cutover in H1 2028.
- The WABA splits into a WhatsApp account for identity and a Messaging account for templates, billing and webhooks.
- Phase 1 rolled out from 23 September 2026 and was due to reach all businesses by mid-October 2026, in stages.
- Existing IDs, endpoints and access tokens keep working, and your WABA ID becomes your Messaging account ID.
- Templates do not move between Messaging accounts without migration, and migrated templates reset to baseline quality with a two to four week ramp.
- Throughput and messaging limits are shared across every partner on a number.
- Clients can add or change partners without migrating their number.
- Replace
paid_messaging_account_idwithmessaging_account_idby 31 December 2026.
Distk helps growth teams across India and internationally map who sends what from each WhatsApp number, plan partner and template moves around quality ramp-up, and keep the 2027 engineering work on schedule. If the new account model is about to reach your numbers, that map is where we start.
Sources
- Updates to WhatsApp Business accounts, Meta for Developers.
- WhatsApp changelog, Meta for Developers, entry dated 22 September 2026 adding the general availability dates.
- Prepare before assigning another partner, Meta for Developers, updated 30 September 2026.
- Conversation Routing overview, Meta for Developers.
- Pricing on the WhatsApp Business Platform, Meta for Developers, for India and Brazil billing localisation.
- Tracking landing page view events, Meta for Developers, updated 23 September 2026.
- Tracking click events, Meta for Developers.