Landing Page to WhatsApp: Meta Event Order
This guide shows the Meta event that Konektor sends at each step, from the landing page visit to the closed sale. Use it to select the event for ad optimization.
The flow that Konektor records
Konektor records these four steps:
- The visitor opens the landing page. The lead status becomes Page View. Konektor sends no event to Meta at this step.
- The visitor clicks the WhatsApp Link button. Konektor records the click, creates a New lead, then sends the event for the New status.
- WhatsApp opens with a message that carries the
[K-XXXX]code. - The visitor sends that message. The connected destination number matches the message to the same lead. Each time the team or a rule moves the lead status further, Konektor sends the next event to Meta.
Before you start
Prepare the following:
- The tracking script is installed and verified.
- One WhatsApp Link exists.
- The Meta platform is added in Website Tracking with a Meta Pixel ID and Access Token. Read Set up Meta CAPI. Without an active Meta platform, no Meta event goes out.
- The destination number is connected to Konektor, so a chat matches its lead. Read Official WhatsApp Business, WhatsApp Session, or Partner Integrations.
Set up the flow
- Install the tracking script on every landing page.
- Set the button URL to the Direct link of the WhatsApp Link, not a
wa.melink. The Konektor script adds the visitor code and Meta click data to a Konektor link. If the button uses your custom domain, add that domain in Konektor first. - Optional: use the
[uniquecode]tag once in the Default Message Template. - Open Automation Rules > Template, select Auto Mark as Contact, then click Install.
- Open Conversion > Conversion Settings, select the Sales or Leads campaign type, then read Event Mapping Preview.
- Test it: open the landing page in a private window, click the button, then send the message. Check Leads (the status moves from New to Contacted) and Conversion > Sync Logs. A test with no Meta ad click shows a
skippedstatus in Strict Mode, and this is correct.
Meta event order
| Step | Lead status | Meta event (Sales) | Meta event (Leads) |
|---|---|---|---|
| Visitor opens the landing page | Page View | None | None |
| Visitor clicks the WhatsApp Link button | New | AddToCart | Contact |
| Visitor sends the message with the code | No change (Contacted if the Auto Mark as Contact rule is on) | None | None |
| Status becomes Contacted | Contacted | Contact | Contact |
| Status becomes Responded | Responded | Lead | Lead |
| Status becomes Qualified | Qualified | Lead | Lead |
| Status becomes Hot | Hot | SubmitApplication | None |
| Status becomes Proposal | Proposal | InitiateCheckout | None |
| Status becomes Negotiation | Negotiation | AddPaymentInfo | None |
| Status becomes Invoice Sent | Invoice Sent | AddPaymentInfo | None |
| Status becomes Purchase | Purchase | Purchase | Purchase |
| Status becomes Lost | Lost | LeadLost | LeadLost |
The table uses the default map. A new workspace uses the Sales campaign type and Strict Mode. Custom Event Mapping can change the event names.
Konektor records the visit, but it does not send PageView to Meta. By default, the Konektor script does not load the Meta browser pixel. Your own Meta pixel still sends PageView. See also Pixel Deduplication when you run a browser pixel and Konektor together.
In Strict Mode, Konektor sends a Meta event only for a lead that came from a Meta ad click. Other leads show skipped in Sync Logs.
Choose the event to optimize
| Event | When Konektor sends it | Use it when |
|---|---|---|
| Lead | Status becomes Responded or Qualified | You want Meta to find people who reply in the chat |
| Purchase | Status becomes Purchase | Your sales close often |
| AddToCart (Sales) / Contact (Leads) | Visitor clicks the WhatsApp Link button | As an early click signal, not a closing signal |
| LeadLost | Status becomes Lost | To exclude an audience, not for optimization |
- Use Lead if you want Meta to find people who reply in the chat. Lead goes to Meta when the status becomes Responded or Qualified.
- Use Purchase when you close sales often. Purchase goes to Meta when the status becomes Purchase.
- AddToCart (Sales) and Contact (Leads) go to Meta when the visitor clicks the button. The visitor may not send a message.
- With the Leads type, Contact goes to Meta two times for one lead: at the click and at Contacted. Do not use Contact for optimization with this type.
- Do not use LeadLost for optimization. Use it to exclude people from an audience.
- Meta can hold a custom event name until you confirm it. Read why a custom event is blocked by Meta.
If your button uses a wa.me link
The Konektor script adds the [K-...] code to the wa.me message text, but Konektor does not record the click as a lead. When the message arrives, Konektor matches the chat to the visit, and the status stays Page View. No event goes to Meta until the status changes.
Fix it one of these ways:
- Change the button to use the Direct link of the WhatsApp Link.
- Or add an automation rule: Action Change Lead Status → New; Condition 1 Message · Contains ·
[K-; Condition 2 Message · Contains ·]; Condition 3 Lead Status · Equal · Page View. Test this rule once. It sends the New event.
Common problems
| Symptom | What to do |
|---|---|
| No lead after a click | Make sure the button uses the Direct link of the WhatsApp Link. Check the workspace period in Billing. After the period ends, Konektor does not record clicks as leads. |
| Status stays Page View | The button uses a wa.me link. Change it to the WhatsApp Link, or add the rule from the previous section. |
A skipped row in Sync Logs | Strict Mode is on, and the lead did not come from a Meta ad click. This is correct for a test without an ad. |
| Status changes, but no event goes out | Add the Meta platform in Website Tracking. Also check Event Mapping Preview, because some statuses send no event with the Leads type. |
| The chat does not attach to the lead | Connect the destination number to Konektor. The message must keep the [K-...] code. |
Related guides
Need More Help?
Our team is ready to help you maximize ad tracking and business attribution.
Try or continue
© 2026 Konektor. All rights reserved.
