Table of Contents
ToggleWhatsApp BSUID conversion tracking is the new reality for anyone sending business messaging events to Meta. If you already run Click-to-WhatsApp ads and send Conversions API events, you may have noticed the customer’s phone number going missing from your webhook. Business-scoped user IDs are the reason.
This post covers the tracking side of WhatsApp BSUID conversion tracking only. It explains what a BSUID is, which webhook fields carry it, when the phone number disappears, and what to store so your attribution survives. CRM contact merging is a separate topic.
A BSUID is a business-scoped user ID. Per Meta’s business-scoped user IDs documentation, it is an identifier for a WhatsApp user that is unique to your business portfolio, used to message someone when you do not know their phone number.
Its format is a two-letter country code, a period, then up to 128 alphanumeric characters, for example US.13491208655302741918. Meta began sharing BSUIDs and they started appearing in webhooks in early April 2026. Sending messages to a BSUID has been supported since July 2026, and business username reservations began on 29 June 2026.
Meta also states that Click-to-WhatsApp advertisers must support BSUIDs, so for ad-driven businesses this is not optional.
The BSUID shows up in several places in your webhook, depending on the event. Knowing each one keeps your parsing correct.
When you send a message, the recipient request parameter takes the BSUID, and the response contacts array returns user_id. Businesses enrolled in parent BSUID accounts also receive parent_user_id, which is shared across their enrolled portfolios.
This is the part that breaks tracking. Per Meta, if a user adopts a username, their phone number is left out of your webhooks.
There are two exceptions. The number still comes through if you exchanged a message or call with that number in the last 30 days, evaluated per business phone number, or if the user is already in your contact book. Outside those cases, you get a BSUID and no phone number.
Here the two Meta documents meet. Meta’s Conversions API for Business Messaging documentation says to send ctwa_clid whenever you have it. Without ctwa_clid, the hashed customer information path requires page_id, at least one customer information parameter, an ad interaction within the last seven days, and it works only in a subset of countries, with no guaranteed match.
Now the conclusion, and this is my reasoning from the two documents, not something Meta states. Meta’s BSUID page does not mention the Conversions API or ctwa_clid at all.
The link is simple. The hashed fallback matches on customer information like the phone number. When a username hides that number, the fallback has nothing to hash. So for those conversations, ctwa_clid stops being merely the preferred option and becomes the only reliable one for WhatsApp BSUID conversion tracking.
That raises the stakes on capturing ctwa_clid from the first message after an ad click. If it goes missing, see ctwa_clid missing from the WhatsApp webhook, and for how the seven-day window behaves, Click-to-WhatsApp ads attribution. The wider setup is in the business messaging CAPI guide.
Store three things against each contact, from the first inbound message onward.
A BSUID stays the same within your portfolio, but it is regenerated when the user changes their phone number. The system message carries previous_user_id precisely so the old and new identities can be stitched together. Storing it is what keeps WhatsApp BSUID conversion tracking intact across that change.
If you send events from your own Cloud API app, the baseline is in track WhatsApp conversions.
Before you rely on your WhatsApp BSUID conversion tracking, run these checks.
Running WhatsApp BSUID conversion tracking end to end, so missing phone numbers never silently break your attribution, is the kind of work I take on as a service.
Get WhatsApp conversion tracking set up
It is a business-scoped user ID, an identifier unique to your business portfolio that lets you message a WhatsApp user when you do not know their phone number. Its format is a country code, a period, then up to 128 alphanumeric characters.
If the user adopted a username, Meta leaves the phone number out unless you interacted with that number in the last 30 days, evaluated per business phone number, or the user is already in your contact book.
No. Meta’s BSUID page does not mention the Conversions API or ctwa_clid. The connection to conversion tracking is my own reasoning from the two documents, not a Meta announcement.
Rely on ctwa_clid, which Meta advises sending whenever you have it. The hashed customer information fallback needs data like the phone number, so it cannot help when the number is hidden.
When a user changes their phone number, their BSUID is regenerated. The system message carries previous_user_id so you can link the old and new BSUID and keep attribution connected.
Yes. Meta states that CTWA advertisers must support BSUIDs, so ad-driven businesses need to handle them.