Automatic Events de Meta en WhatsApp
Meta Automatic Events on WhatsApp
How it works, how to enable it in WOZTELL, and where to see the results.
In this article
When a customer arrives through a Click-to-WhatsApp ad, the sale happens inside a conversation. Meta cannot see that: there is no web page, no form, no pixel. The only thing Meta can count is how many conversations were opened.
Automatic Events solves this: Meta reads the conversations that arrive from your ads and determines on its own when a lead or a purchase occurred. That outcome is recorded as a conversion, with no need for anyone to label it.
1. The problem it solves
Compare the two scenarios:
| Ad to a web page | Click-to-WhatsApp ad | |
|---|---|---|
| Where does the conversion happen? | On the website | In the chat |
| How is it measured? | Pixel: form submitted, purchase confirmed | It is not measured |
| What does Meta optimize for? | Leads, purchases, revenue | Conversations started |
Optimizing for conversations started rewards volume, not quality: a campaign that brings in 500 browsers looks better than one that brings in 40 buyers.
2. Two ways to record conversions in WOZTELL
This is the key point and the most common source of confusion. WOZTELL supports two different mechanisms, and they are not the same:
| Manual events (already available) | Automatic Events (new) | |
|---|---|---|
| Who decides a conversion happened | You, when designing the chatbot | Meta, by analyzing the conversation |
| How it is implemented | Send Conversion Event node in the flow, specifying WABA ID, Ads Account ID and Ads ID | Turn on a few toggles. No development required |
| Accuracy | Exact: it fires where you place it | Probabilistic: Meta interprets natural language |
| Purchase value | You define it (currency + value) | Only if the amount is written in the message |
| Coverage | Only what passes through the bot flow | Any free-form conversation, including what the bot does not see |
| Effort | Requires designing the flow | None |
When to use each one
- Manual when the business has a purchase flow defined inside the bot (catalog, checkout, order confirmation). Accuracy is total there and the sale value is exact.
- Automatic when the sale closes through conversation: real estate, clinics, car dealerships, services, B2B. This is where the bot cannot know what happened.
- Both at once, with care. Meta does not deduplicate events: if the chatbot already sends conversion events and automatic forwarding is also enabled, the same sale can be counted twice. Before enabling it on an existing account, check whether the flow already includes the Send Conversion Event node.
3. Requirements
Technical requirements
- Meta Business Verification approved
- Ads Permission granted to WOZTELL
- At least one active Click-to-WhatsApp ad pointing to that number
About Ads Permission: the Facebook user who completes the Login for Business flow needs Full Control over the relevant ad account. With partial access the flow still completes, but the conversion features do not become operational. This is the most common cause of "everything is enabled and nothing is coming through".
Geographic availability
Not available for businesses registered in the European Union, the United Kingdom or Japan. Meta also states that the feature is limited to certain countries or regions without publishing the full list, so in less common markets it is worth verifying directly in the account.
4. Step-by-step activation
Step 1 — Enable identification in Meta
This step comes first. If forwarding is enabled in WOZTELL beforehand, no events will arrive.
- Go to business.facebook.com
- In the top left, select the business asset
- Settings → Accounts → WhatsApp accounts
- Select the WhatsApp account
- Under Summary, scroll down to Privacy and data sharing
- Turn on the toggles:
- Automatically identify order events from conversations in this account
- Automatically identify lead events from conversations in this account
Depending on the account, these may appear as two separate toggles or as a single combined one. Either way, turn them on.
Shortcut: from the channel in WOZTELL, the Enable in Meta button opens this screen directly.
For a new business this step is not needed: in the Embedded Signup, the "Instruct Meta to automatically identify order and lead events" checkbox is pre-selected by default. Just leave it checked.
Step 2 — Enable forwarding in WOZTELL
- Go to platform.woztell.com/channels/
- Edit the relevant channel
- Permission section, Automatic Events (Meta) block
- Turn on:
- Forward purchase events to Conversions API automatically
- Forward lead events to Conversions API automatically
If only lead events are needed, leave the purchase toggle off.
What each toggle does
This distinction matters, because these are two independent permissions:
- The Meta toggles authorize Meta to identify the events
- The WOZTELL toggles control whether those events are forwarded to the Conversions API
Identification can be active without forwarding: the event still reaches WOZTELL, it simply is not recorded as a conversion in Meta.
5. How to test that it works
Meta defines two phrases that force detection. They must be written exactly, in English, from the business account, replying to a chat that came in through a real CTWA ad:
| To test | Send from the business account |
|---|---|
| Purchase | Your tracking number is AB123456789BR |
| Lead | I am interested in learning more about the product |
Full test flow: click the ad → send a message to the business → reply from the business with the phrase → verify in Events Manager.
Always do this on a test channel first, never directly in production.
6. Where to see the results
In Events Manager — to verify events are arriving
eventsmanager.facebook.com/events_manager2 → select the dataset → Overview
How to find the dataset: WOZTELL creates it automatically from the waba_id and links it to the connected page. In Events Manager it appears under the name of that page, not under the phone number or the WABA. This is the detail that keeps people from finding it.
Lead and purchase events appear there with Conversions API as the integration, which distinguishes them from web or app events.
For a one-off check, the dataset's test events tab shows them in real time, without waiting for the report to consolidate.
In Ads Manager — to make decisions
This is where the business question gets answered: which campaign brought those leads and purchases, and at what cost. Events are attributed to the campaign through the ctwa_clid, the ad click identifier.
Be aware of this: the number in Ads Manager will come in below the real figure. Meta only attributes the conversion if it happens within the attribution window, and in conversational selling the cycle usually stretches longer than that. This is not a fault of Automatic Events, it is how attribution works. If exact revenue figures are needed, that remains the job of the CRM.
In WOZTELL — conversation context
WOZTELL does not show automatic events in a report of its own, but it does provide what Meta does not: conversations that come from an ad are identified as such, both in the conversation history and in the inbox thread. This lets the team see which ad brought each person in while handling the chat.
7. Limitations
Campaign optimization for leads or purchases does not yet work on Click-to-WhatsApp.
The maximize number of leads and maximize number of purchases through messaging performance goals that these events feed are available only for ads that click to Messenger and to Instagram Direct. Meta will be enabling this for WhatsApp progressively, but it is not available today.
On WhatsApp, automatic events are for measurement, not yet for optimization.
The case for enabling it now is that events start accumulating from day one. When Meta opens up optimization, the account arrives with history instead of starting from zero.
Other points to be clear about
- Detection is probabilistic. Meta interprets natural language: it may miss conversions or flag one that did not happen. There is no confirmation step and no way to correct an event.
- It only covers new chats originating from CTWA ads. Organic conversations, wa.me links, QR codes and pre-existing conversations are out of scope.
- The amount is only captured if it is written out. If the close was "great, I'll set it aside for you", the event arrives with no value. Revenue reports will be incomplete.
- It does not replace the CRM. It complements it. Exact revenue attribution still requires one.
8. Frequently asked questions about Automatic Events on WhatsApp
Will Meta read my conversations?
Meta uses regular expressions and natural language processing on new threads that originate from Click-to-WhatsApp ads. Not organic conversations, and not conversations from before activation. It is an opt-in feature: nothing happens until the business explicitly enables it, and the setting lives in the Meta section called precisely Privacy and data sharing.
What Meta's public documentation does not specify is how long the analyzed content is retained or the details of how it is processed. For businesses that are sensitive to this — healthcare, legal, financial — do not improvise an answer; escalate it to your Meta KAM.
Can Automatic Events on WhatsApp be turned off?
Yes, at any time and from both sides: the Meta toggles and the WOZTELL toggles. It is fully reversible.
How many conversions will Automatic Events on WhatsApp detect?
There is no figure that can be guaranteed. It depends on how the business's customers write, on the language and on the sector. The sensible approach is to enable it, measure for a month and compare against what the business knows it sold.
Do Automatic Events work on Instagram and Messenger?
Yes, Meta's feature covers all three channels. In fact it is further along on Messenger and Instagram: campaign optimization already works there.
9. References
For the technical team