Meta Ads Tracking Software with Konektor.id
Konektor.id is Meta ads tracking software for businesses that close sales on WhatsApp. Konektor.id stores the ad click identifier from Click-to-WhatsApp ads and landing pages. When a lead status changes, Konektor.id sends an event to Meta through the Conversions API, for example QualifiedLead and Purchase. Meta still decides attribution and reporting.
From Rp199.000/month. 14-day trial.
What is the problem with tracking Meta ads to WhatsApp?
Ads on Facebook and Instagram often end in a chat. A person taps the ad, then asks your support team for a price. The purchase happens in WhatsApp. Meta takes no part in that conversation.
A pixel on your website sees only the pages that open. A Click-to-WhatsApp ad does not open a page at all. So Meta knows only that someone started a chat. It does not know which chat became a paying customer.
This gap causes two problems. Your ad report stops before the most valuable step. And Meta receives a signal that is too early to judge which ad brings buyers.
There is one more point. Meta does not help to deduplicate business messaging events. The advertiser must make sure that one event does not go out twice. The official source is in the Sources section.
Two routes from a Meta ad to WhatsApp
Konektor.id serves two routes. Both end in a WhatsApp chat.
- Click-to-WhatsApp (CTWA). The ad opens a chat directly. There is no landing page.
- Landing page to WhatsApp (LPWA). The ad opens your page, and a button on that page opens the chat.
A made-up example
Take a shop called Kopi Contoh. It sells coffee bean subscriptions with a Click-to-WhatsApp ad. The names and amounts below are made up.
A possible buyer named Rina taps the ad and asks about the monthly plan. Konektor.id creates a lead for Rina and stores the ctwa_clid of the first message. Support answers, then changes the status of Rina to Qualified. Meta receives QualifiedLead.
Two days later Rina pays IDR 450,000 for the plan. Support changes the status to Purchase and enters the Closing value. Meta receives Purchase with that value. Kopi Contoh can now judge the ad by its buyers, not only by the chats it brought in.
How does Konektor.id track it?
The Click-to-WhatsApp route has six stages.
- A person taps the ad and sends a first message. Meta adds
ctwa_clidto that message. - Konektor.id creates a lead with the source ads and stores
ctwa_clid. An owner can see the value under Attribution Parameters in the lead detail. - Your team replies from the Inbox. The team or an automation rule changes the lead status as the chat moves on.
- Each status change reads the Event for each lead status table. That table decides the event for Meta.
- If the number is linked with Set up CTWA, Konektor.id sends that event to your CTWA dataset as business messaging, together with
ctwa_clid. - The result shows in the Delivery log. A Meta CTWA row with the status Sent means that Meta accepted the event.
The landing page route differs at the start. The tracking script adds a visitor code and Meta click data to the WhatsApp link. A click on the button creates a New lead. A message with the code [K-XXXX] matches the chat to the same lead. After that, each status change sends the standard Meta event of that status.
Both routes use the Conversions API as the way to send. That is its only role on this page. The technical guide for the token is in the docs, and the link is under Next steps.
The identifiers and data that go out
| Data | Used for | Form when sent |
|---|---|---|
ctwa_clid | Link the chat to a Click-to-WhatsApp ad | As it is, with no hash |
fbclid and fbc | Link a landing page lead to a Meta ad click | fbc is built from fbclid when the lead has none. A business messaging event does not carry fbc |
fbp | Recognize the browser of a landing page visitor | As it is |
| Email and phone number | Help Meta match the person | SHA-256 hash |
| Event ID | Prevent double counting | One unique ID for each event |
Konektor.id sends the data that the lead has. A lead without an email still goes out with its phone number.
Once for each lead
Konektor.id sends each kind of Meta event once for each lead. For an ad chat on the CTWA dataset route, there are three kinds: LeadSubmitted, QualifiedLead, and Purchase. A later status change that repeats one of them shows as Skipped in the Delivery log.
This rule keeps the numbers in Meta in line with the number of leads.
Send strategy: Strict mode or Send all
Strict mode is the default. It sends only leads that clearly came from a Meta ad click. An organic lead shows Skipped. Send all sends every lead that qualifies, and Meta matches them through contact data. You choose it in Conversions, under Send strategy.
Ad policy
Your ads still follow the Meta Advertising Standards. This page does not change those rules. Konektor.id only sends the conversion data that your lead already holds. The policy link is in the Sources section.
Which events does Konektor.id send to Meta Ads?
| Event | When it is sent |
|---|---|
| LeadSubmitted | For a lead from a Click-to-WhatsApp ad whose number is linked to the CTWA dataset. Sent once for each lead, when the status reaches the first status that has an event for Meta, for example New or Responded. |
| QualifiedLead | When the lead status becomes Qualified, for a Click-to-WhatsApp ad lead on the CTWA dataset route. Sent once for each lead, as long as you did not replace the built-in event of that status. |
| Purchase | When the lead status becomes Purchase. The event carries the Closing value that your team enters, and goes out once for each lead. |
| Standard Meta events for landing page leads | For a landing page lead, each status change sends the standard event from the Event for each lead status table, such as AddToCart, Contact, Lead, InitiateCheckout, and Purchase. Each built-in name goes out once per lead. |
| LeadLost | When the status becomes Lost, for a landing page lead. Use this event to exclude audiences, not to optimize. |
| Chat event (backup route) | When a Click-to-WhatsApp ad lead carries a click identifier, but its number is not linked to the CTWA dataset. The event still reaches your Meta pixel as a normal chat event, and the Delivery log marks it CTWA backup. |
Click identifiers: ctwa_clid, fbclid, fbc
What do you need?
- The Meta platform is added in Website Tracking, with the Meta Pixel ID and the Access Token from Meta Events Manager.
- For Click-to-WhatsApp ads: a business WhatsApp number linked to Konektor.id, through Official WhatsApp Business, a QR scan, or a partner provider that passes on ad data.
- For the CTWA dataset: the WhatsApp Business Account ID of that number, and a Facebook account that is admin of the business that owns the number. You use both with Set up CTWA and Log in with Meta.
- Your Click-to-WhatsApp ad uses the same number as the linked number.
- For landing pages: the tracking script is installed, and the WhatsApp button uses the Direct link of a WhatsApp Link.
- Your team or a rule changes the lead status. That status change triggers the event to Meta.
What are the limits?
- Konektor.id proves that Meta accepted an event: a Meta CTWA row with the status Sent in the Delivery log. Konektor.id does not prove reporting or attribution in Ads Manager. Check that in Meta.
- Without the CTWA dataset, a Click-to-WhatsApp ad lead goes out as a normal chat event. Meta does not count it as a business messaging conversion.
- For an ad chat on the CTWA dataset route, Meta accepts only LeadSubmitted, QualifiedLead, and Purchase. The built-in event of the Lost status is not sent to Meta for that lead.
- Strict mode is the default strategy. A lead that did not come from a Meta ad click shows Skipped. This result is normal in a test without an ad.
- Meta does not filter repeated business messaging events. For that reason Konektor.id sends each kind of event once for each lead.
- Meta leaves out ctwa_clid on messages that come from an ad in WhatsApp Status. A lead from that source carries no ad click identifier.
- The Pancake provider does not pass ctwa_clid to Konektor.id. A Click-to-WhatsApp ad lead through Pancake cannot use the CTWA dataset route.
- A QR scan reads ad data through an unofficial route, which can break Meta terms. For daily operation, use Official WhatsApp Business.
- Konektor.id does not promise cheaper ads or a set ad result.
Who is it for, and who is it not for?
Good fit for
- Businesses that run Click-to-WhatsApp ads on Facebook and Instagram, and close the sale in chat.
- Businesses that send Meta ads to a landing page, then to a WhatsApp button.
- Support teams that change lead statuses, and want each important change to reach Meta.
Not a fit for
- Businesses that use Pancake for Click-to-WhatsApp ads and need attribution through the CTWA dataset.
- Businesses that do not record lead statuses in Konektor.id, so no change exists to send.
- Businesses that look for a promised ad result or a set cost per result.
How do you set it up?
Add Meta in Website Tracking
Open Tracking & Ads > Website Tracking, then click Add ad platform. At Where do your ads appear?, choose Facebook and Instagram.
Enter the Meta Pixel ID and Access Token
Enter the Pixel Name, the Meta Pixel ID, and the Access Token from Meta Events Manager, then click Save. Choose Test send in the Meta row menu, and paste the Test event code (Test Event Code).
Connect your WhatsApp number
Open Connection > Connect WhatsApp and choose the path of your number. After the connection succeeds, open Connection > Numbers & CTWA.
Set up CTWA
On the number row, click Set up CTWA. Choose Manage CTWA if you connected the number before. Enter the WhatsApp Business Account ID (WABA ID), then click Log in with Meta.
Set the event for each lead status
Open Tracking & Ads > Conversions. Choose a Campaign type, read the Event for each lead status table, choose Strict mode or Send all under Send strategy, then click Save changes.
Install the status rules
Open Conversations > Automation Rules > Templates. For Click-to-WhatsApp ads, install Ads Lead to Responded. For landing pages, install Auto Mark as Contact.
Test with one ad chat
Send a chat through your ad, then change the lead status. Open Conversions > Delivery log. A Meta CTWA row with the status Sent means that Meta accepted the event.
How much does it cost?
From Rp199.000/month. 14-day trial.
| Plan | Per month |
|---|---|
| Starter | Rp199.000 |
| Pro | Rp499.000 |
| Enterprise | Rp1.999.000 |
Frequently asked questions
What is Meta ads tracking software for WhatsApp?
It is software that records a WhatsApp chat from a Meta ad together with the ad click data, then sends events to Meta as the lead moves forward. Konektor.id does this for Click-to-WhatsApp ads and for landing pages that end in WhatsApp.
Which events does Konektor.id send to Meta?
For a Click-to-WhatsApp ad lead on the CTWA dataset: LeadSubmitted, QualifiedLead, and Purchase. For a landing page lead: the standard Meta event of each status, such as Lead and Purchase. You can see and change the mapping in Conversions.
Does Konektor.id use the Meta Conversions API?
Yes. Konektor.id sends events from the server to Meta through the Conversions API. You give Meta the Pixel ID and the Access Token in Website Tracking. For Click-to-WhatsApp ads, you also set up CTWA with Log in with Meta.
Do I need a pixel on my website for Click-to-WhatsApp ads?
Not for the chat itself, because a Click-to-WhatsApp ad opens no web page. Konektor.id reads ctwa_clid from the WhatsApp message. You still add Meta in Website Tracking, so the events have a place to go.
Why does my event show Skipped in the Delivery log?
The most common cause: Strict mode is on, and the lead did not come from a Meta ad click. This result is normal in a test without an ad. Choose Send all under Send strategy if you want to send leads without an ad click.
Can Meta count the same event twice?
Meta does not help to deduplicate business messaging events. For that reason Konektor.id sends each kind of event once for each lead. A repeated status change shows as Skipped in the Delivery log.
Is the click identifier sent as a hash?
Not for ctwa_clid. Meta asks for that value as it is. The email and phone number of the lead go out as a SHA-256 hash, as Meta requires.
How long until the event shows in Meta?
Konektor.id sends the event when the status changes, and the Delivery log shows the result. The time to show in Events Manager and Ads Manager follows Meta, so check both places separately.
Next steps
Sources
- Conversions API for business messaging · Meta for Developers · Checked October 13, 2026
- Customer information parameters (ctwa_clid, fbc, fbp, hashing) · Meta for Developers · Checked October 13, 2026
- Messages webhook: referral and ctwa_clid from a Click to WhatsApp ad · Meta for Developers · Checked October 13, 2026
- Handling duplicate pixel and server events · Meta for Developers · Checked October 13, 2026
- Ads that Click to WhatsApp · Meta for Developers · Checked October 13, 2026
- Advertising Standards · Meta Transparency Center · Checked October 13, 2026