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:

  1. The visitor opens the landing page. The lead status becomes Page View. Konektor sends no event to Meta at this step.
  2. The visitor clicks the WhatsApp Link button. Konektor records the click, creates a New lead, then sends the event for the New status.
  3. WhatsApp opens with a message that carries the [K-XXXX] code.
  4. 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:

Set up the flow

  1. Install the tracking script on every landing page.
  2. Set the button URL to the Direct link of the WhatsApp Link, not a wa.me link. 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.
  3. Optional: use the [uniquecode] tag once in the Default Message Template.
  4. Open Automation Rules > Template, select Auto Mark as Contact, then click Install.
  5. Open Conversion > Conversion Settings, select the Sales or Leads campaign type, then read Event Mapping Preview.
  6. 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 skipped status in Strict Mode, and this is correct.

Meta event order

StepLead statusMeta event (Sales)Meta event (Leads)
Visitor opens the landing pagePage ViewNoneNone
Visitor clicks the WhatsApp Link buttonNewAddToCartContact
Visitor sends the message with the codeNo change (Contacted if the Auto Mark as Contact rule is on)NoneNone
Status becomes ContactedContactedContactContact
Status becomes RespondedRespondedLeadLead
Status becomes QualifiedQualifiedLeadLead
Status becomes HotHotSubmitApplicationNone
Status becomes ProposalProposalInitiateCheckoutNone
Status becomes NegotiationNegotiationAddPaymentInfoNone
Status becomes Invoice SentInvoice SentAddPaymentInfoNone
Status becomes PurchasePurchasePurchasePurchase
Status becomes LostLostLeadLostLeadLost

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

EventWhen Konektor sends itUse it when
LeadStatus becomes Responded or QualifiedYou want Meta to find people who reply in the chat
PurchaseStatus becomes PurchaseYour sales close often
AddToCart (Sales) / Contact (Leads)Visitor clicks the WhatsApp Link buttonAs an early click signal, not a closing signal
LeadLostStatus becomes LostTo 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.

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

SymptomWhat to do
No lead after a clickMake 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 ViewThe 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 LogsStrict 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 outAdd 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 leadConnect the destination number to Konektor. The message must keep the [K-...] code.

Need More Help?

Our team is ready to help you maximize ad tracking and business attribution.

© 2026 Konektor. All rights reserved.