CTWA Ads Tracking Software with Konektor.id
Konektor.id is CTWA ads tracking software. CTWA means Click to WhatsApp: a Meta ad that opens a chat when tapped. Meta adds the click identifier ctwa_clid to the first message. Konektor.id stores it on the lead, then sends the chat result to Meta when the lead status changes. Each WhatsApp path has its own rule for this identifier.
From Rp199.000/month. 14-day trial.
What is CTWA, and why does the pixel not see it?
CTWA means Click to WhatsApp. It is a Meta ad that opens a WhatsApp conversation with your business when someone taps it. Meta documents that the chat opens with a greeting message that you can set yourself.
A pixel is code on a web page. A CTWA ad opens no web page. So no code runs, no fbclid sits in the address, and no visit exists to record.
The conversation, the offer, and the payment all happen in WhatsApp. Meta only knows that someone started a chat. Meta does not know which chat ended as a paying customer.
This page answers one question: how does Konektor.id capture the CTWA click through the different WhatsApp paths, and how do you check it? The event details for each platform are on other pages, and the links are near the end.
Fictional example
Picture a shop called Contoh Tea. It sells tea sets through CTWA ads. The names and amounts below are fictional.
Sari taps the ad and writes, "Do you have a gift set?" The message carries the click identifier. Konektor.id creates a lead for Sari and stores the identifier. The team answers, then Sari's status becomes Qualified.
Three days later Sari pays IDR 275,000. The team changes the status to Purchase and enters the Closing value. Meta receives the result, not only the news that Sari once asked a question.
Why does the first chat decide the whole tracking?
The click identifier of a CTWA ad is called ctwa_clid. Meta does not put it in a web address. Meta puts it in the referral data of the message that the person sends after tapping the ad.
The referral data holds more than the identifier. It also carries the ad ID, the ad link, the headline, and the main text of the ad. Konektor.id stores this data on the lead, so your team knows which ad brought the person.
Two things follow from this.
- Konektor.id reads only the messages of a linked number. A message that arrives before the link is active is not read.
- A chat without the identifier cannot be credited to an ad click through this route. Examples are an organic chat and a chat from an ad in WhatsApp Status. Meta sends no
ctwa_clidfor an ad in Status.
So the first step is not to set up events. The first step is to make sure that your WhatsApp path passes on the ad data.
How does Konektor.id capture CTWA on each WhatsApp path?
The answer depends on how you link the number. The Connect WhatsApp page shows two facts on every path card: CTWA ad data and Phone stays in use.
| Path | CTWA ad data | What you need to know |
|---|---|---|
| Official WhatsApp Business | Yes | Konektor.id reads the ad data from the message that Meta passes on. Every chat from a new number becomes a lead. You must first release the number from the app on the phone. |
| QR session | Yes | An unofficial route that can break the Meta terms. The ad data is read only when WhatsApp includes it. A lead forms from a message that carries a visitor code or ad data. |
| Kapso | Yes | Kapso passes on the ad data, and the phone stays in use. A lead forms from a message that carries a visitor code or ad data. |
| Kirimdev, Qiscus, Qontak, HaloAI, Kirimchat | Yes | The provider passes on the ad data. Qiscus and Kirimdev give the WABA ID in the incoming message. The other three providers use the WABA link. |
| Pancake | No | Pancake does not pass on the ad data. An ad lead through Pancake has no ctwa_clid. |
| Repliz | Not a WhatsApp path | Repliz carries Instagram and Messenger DMs from Click-to-Message ads. When Meta includes the ad data, the lead has an ad source. There is no ctwa_clid. |
This table follows the path support table inside the app, so the values match what you see in Connect WhatsApp. If a path card shows No, change the path before you run your ads.
For daily work, use Official WhatsApp Business. QR session fits only a short transition. The risk is explained in the Ad policy part below.
What does Set up CTWA do?
The click identifier alone is not enough. For Meta to count the result of a chat as a business messaging conversion, the event must reach the dataset that belongs to your WhatsApp Business Account. Set up CTWA builds that link.
The Set up CTWA panel works in three steps.
- You enter the WhatsApp Business Account ID (WABA ID) of that number.
- You click Log in with Meta, then pick the WhatsApp account of that number in the Meta dialog.
- Konektor.id asks Meta to use the existing dataset or to create a new one. You do not need to look up a Dataset ID.
After that, your number shows Ready - Meta login. This status proves only that the local set-up is ready. It does not prove that Meta accepted an event.
The Manage CTWA button opens the same panel for a number that you linked before. There you can click Check connection at any time.
If you skip Set up CTWA
Konektor.id still stores the click identifier and still sends events. But the event goes out as a normal chat event through the general Meta route. The Delivery log marks it CTWA fallback.
Meta does not attribute that event as a business messaging conversion. So your ad does not get full credit. Finish Set up CTWA, then create one new conversion.
How does a CTWA lead show in the Inbox and in Leads?
The first message from the ad arrives in the Inbox. Konektor.id creates a lead from that message and gives it a Meta ad source.
| Where | What you see |
|---|---|
| Inbox | The conversation row and the contact panel show the source chip Meta ad |
| Leads | The Source column shows ads for a lead from an ad |
| Lead detail | The Source shows as Meta ad, with the Ad platform below it. The owner sees ctwa_clid under Attribution Parameters, in Click Identifiers |
A new lead starts at New. The template Ads Lead to Responded moves an ad lead to Responded after three messages. This rule applies only to leads from ads.
The conversation count in Meta Ads Manager can be higher than the lead count. Meta also counts people who open WhatsApp and leave without sending a message. Konektor.id creates a lead only after a message really arrives.
Where are the event details for each platform?
This page stops at click capture and link set-up. The event content and its rules are on three other pages.
- For all Meta events, including the landing page route, read Meta ads tracking software.
- For the content of one business messaging event, read WhatsApp CAPI software.
- For a TikTok messaging ad that opens WhatsApp, read TikTok ads tracking software. That format is not CTWA.
How do you check that your CTWA works?
Check in this order. Each step proves a different thing.
- The path passes on the ad data. In Connect WhatsApp, the fact CTWA ad data on your path is Yes.
- The local link is ready. In Numbers & CTWA, the number shows Ready - Meta login.
- The chat from the ad arrives. Tap the ad from another account, then send a message. Open Leads. The new lead shows the source ads, and the lead detail shows Meta ad.
- The identifier is stored. Open the lead detail. The owner sees
ctwa_clidin Click Identifiers. - Meta accepts the event. Change the lead status. Open Conversions, then the Delivery log tab. A Meta CTWA row with the status Sent means Meta accepted the event.
- Ads Manager reports it. This is Meta's decision. Check it yourself in Ads Manager.
Common problems
| Symptom | Most likely cause | Action |
|---|---|---|
An ad lead has no ctwa_clid | The chat was not an ad click, the ad ran in WhatsApp Status, or the path passes no ad data | Check the fact CTWA ad data on your path, then test with a real ad click |
| A chat from the ad does not become a lead | The number in the ad differs from the linked number | Match the number in Meta Ads Manager with the linked number |
| The Delivery log shows CTWA fallback | Set up CTWA was not finished | Open Manage CTWA, click Check connection, then create one new conversion |
| A row shows Skipped | Strict mode skips a lead without a Meta ad click | This result is normal in a test without an ad |
Ad policy
Your ads 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 part.
QR session uses an unofficial route. It can break the Meta terms and get the number limited. Weigh that risk before you use it for ads.
Which events does Konektor.id send to Meta through CTWA?
| Event | When it is sent |
|---|---|
| LeadSubmitted | For an ad chat on a number whose CTWA is ready. Sent once for each lead, when the lead status reaches an early or middle status that has an event for Meta, for example New or Responded. |
| QualifiedLead | When the lead status becomes Qualified, as long as the Meta cell of that status still holds the built-in event. Sent once for each lead. |
| Purchase | When the lead status becomes Purchase. The closing value goes along if you turn on Send conversion value. Sent once for each lead. |
| Chat event (fallback route) | When a lead carries ctwa_clid, but the CTWA of that number is not ready. The event still goes out as a normal chat event, and the Delivery log marks it CTWA fallback. Meta does not count it as a business messaging conversion. |
| No event for a chat without a click identifier | A chat that did not come from an ad click carries no ctwa_clid. In Strict mode, such a lead shows Skipped in the Delivery log. |
Click identifiers: ctwa_clid
What do you need?
- A Click-to-WhatsApp ad that runs on Meta, and its destination number is the same as the number linked to Konektor.id.
- A WhatsApp path that passes on the ad data. The path card in Connect WhatsApp shows the fact CTWA ad data with the value Yes or No.
- The WhatsApp Business Account ID (WABA ID) of that number, and the Facebook account of the business admin who owns the number, for Set up CTWA with Log in with Meta.
- Meta is added in Website Tracking, so the events have a place to go.
- The template Ads Lead to Responded is installed in Automation Rules, so an ad lead that starts chatting moves to Responded.
- Your team or a rule changes the lead status. Without a status change, no event goes out.
What are the limits?
- The click identifier arrives with the message from the ad. A message that arrives before the number is linked to Konektor.id is not read, and Konektor.id reads only the chats of a linked number.
- Meta does not include ctwa_clid in a chat from an ad shown in WhatsApp Status. A lead from that source carries no click identifier.
- Pancake does not pass on CTWA ad data. An ad lead that comes through Pancake has no ctwa_clid.
- QR session reads the ad data through an unofficial route, which can break the Meta terms. The number can be limited or disconnected. Use Official WhatsApp Business for daily work.
- Without Set up CTWA, the event of an ad lead goes out as a normal chat event. Meta does not build business messaging attribution from that event.
- Repliz carries Instagram and Messenger DMs, not WhatsApp chats. A DM from an ad carries no ctwa_clid.
- Konektor.id proves that Meta accepted an event: the Meta CTWA row shows Sent. You check reporting and attribution in Ads Manager yourself, in Meta.
- Each kind of event goes out once for each lead, because Meta does not filter repeated business messaging events.
- 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, then serve and close the sale in chat.
- Teams that want to know which leads came from an ad, with the click identifier attached, without a guess from the phone number.
- Support teams that already record the lead status and are ready to make that status a signal for the ads.
Not a fit for
- Businesses that advertise to WhatsApp through Pancake and need attribution from ctwa_clid.
- Businesses whose ads appear only in WhatsApp Status and that need a click identifier on every chat.
- Businesses that look for a promised ad result or a set cost per result.
How do you set it up?
Choose a WhatsApp path with CTWA ad data set to Yes
Open Connection > Connect WhatsApp. Read the facts CTWA ad data and Phone stays in use on each path card, then link your number through the path that fits.
Add Meta as the place for events
Open Tracking & Ads > Website Tracking, click Add ad platform, then choose Facebook and Instagram. Enter the Meta Pixel ID and the Access Token, then click Save.
Open the Set up CTWA panel
After the connection succeeds, click Set up CTWA for this number. Or open Connection > Numbers & CTWA and click Set up CTWA on the number row.
Enter the WABA ID and log in with Meta
Enter the WhatsApp Business Account ID (WABA ID), click Log in with Meta, then tick the WhatsApp account of this number in the Meta dialog. The number shows Ready - Meta login.
Check the CTWA connection
Click Manage CTWA on the same number, then click Check connection. This button checks permissions and access, and it sends no test purchase.
Install the template Ads Lead to Responded
Open Conversations > Automation Rules > Templates, choose Ads Lead to Responded, then click Install.
Send one chat from an ad, then read the result
Tap your ad from another account and send a message. Open Leads and check the Source column. Change the status, then open Conversions > Delivery log and look for a Meta CTWA row with the status Sent.
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 CTWA?
CTWA stands for Click to WhatsApp. It is a Meta ad that opens a WhatsApp conversation with the business when someone taps it. The ad opens no web page, so the website pixel does not see the click.
What is a CTWA tracker, and is Konektor.id one?
A CTWA tracker stores the click identifier of a Click-to-WhatsApp ad on the lead, then sends the result of the chat back to Meta. Konektor.id does both, and the Delivery log shows whether Meta accepted the event.
What is ctwa_clid and where do I see it?
ctwa_clid is the click identifier that Meta assigns to a Click-to-WhatsApp ad. Open the lead detail in Leads. The workspace owner sees the value under Attribution Parameters, in the Click Identifiers part.
Which WhatsApp paths pass on the CTWA ad data?
Official WhatsApp Business, QR session, Kapso, Kirimdev, Qiscus, Qontak, HaloAI, and Kirimchat pass it on. Pancake does not. The path card in Connect WhatsApp shows the answer in the fact CTWA ad data.
Why does a lead from an ad have no ctwa_clid?
There are three likely causes: the chat did not start from an ad click, the ad ran in WhatsApp Status, or your path does not pass on the ad data, as with Pancake. On QR session, the data is read only when WhatsApp includes it.
Do I need a pixel on my website for CTWA ads?
Not for the chat itself. A CTWA ad opens no web page, and Konektor.id reads the click identifier from the WhatsApp message. You still add Meta in Website Tracking as the place for events.
Is the number of conversations in Meta the same as the number of leads in Konektor.id?
Not always. Meta counts people who open WhatsApp from the ad, including those who never press send. A lead exists once the message of the customer reaches the linked number.
Is a TikTok ad that opens WhatsApp the same as CTWA?
No. CTWA is a Meta format. Konektor.id marks a chat from a TikTok messaging ad as TikTok ad, but that chat does not use ctwa_clid and sends no event to Meta.
Next steps
Sources
- Ads that Click to WhatsApp · Meta for Developers · Checked October 14, 2026
- Messages webhook: referral and ctwa_clid from a Click to WhatsApp ad · Meta for Developers · Checked October 14, 2026
- Conversions API for business messaging · Meta for Developers · Checked October 14, 2026
- Customer information parameters (ctwa_clid, hashing) · Meta for Developers · Checked October 14, 2026
- Advertising Standards · Meta Transparency Center · Checked October 14, 2026