Click-to-WhatsApp (CTWA) conversion tracking

Konektor.id tracks conversions from Click-to-WhatsApp (CTWA) ads through the Meta Conversions API. Meta adds ctwa_clid to the first message, and Konektor.id stores it on the lead. When the lead status changes, Konektor.id sends a business messaging event to the CTWA dataset of your number. Each WhatsApp path has its own rule for ctwa_clid.

Click-to-WhatsApp (CTWA) ads send people from Facebook or Instagram straight into a WhatsApp conversation with your business. A summary of the WhatsApp paths that pass ad data is in CTWA ads tracking software.

How is CTWA tracked through to Meta?

When a customer taps a CTWA ad and sends their first message, Meta injects a ctwa_clid (Click-to-WhatsApp Click ID) into that message's webhook. Konektor stores the ctwa_clid on the lead. When the lead later progresses (for example to qualified or won), Konektor sends a conversion event to Meta.

For Meta to attribute that conversion to the CTWA ad, the event must be sent as business messaging, not as a regular website event. Konektor sends the three required fields:

• action_source: "business_messaging"
• messaging_channel: "whatsapp"
• user_data.ctwa_clid (raw value, not hashed)

plus the business identifier (whatsapp_business_account_id), delivered to your account's dedicated CTWA dataset. Each part of the event is explained in WhatsApp CAPI software.

Which WhatsApp partners pass ctwa_clid?

ctwa_clid detection depends on which WhatsApp partner you use.

Prerequisites

1. You run Click-to-WhatsApp ads on Meta.
2. Your business WhatsApp number receives messages through one of the supported partners above.
3. You have access to Meta Business Manager to grant permissions.

How do you connect CTWA to Meta?

1. Open Connection > Connect WhatsApp and connect your number. After an official or partner connection succeeds, click Set up CTWA for this number. For a number that is already connected, open Connection > Numbers & CTWA, then click Use a connected number.
2. For a QR session, create a Session or complete the Session for the business number that receives messages from your CTWA ads, then select Save Changes.
3. On the number row, select Set up CTWA. Select Manage CTWA if the number was previously connected.
4. Enter the WABA ID for that number in WhatsApp Business Account ID in the Set up CTWA panel.
5. Select Log in with Meta. Meta login is the main method. Follow the Meta CTWA connection guide.

The local configuration is ready when the number shows its CTWA readiness status. This local status does not prove that Meta accepted an event.

Once active, conversions from CTWA leads are automatically sent as business messaging events to your CTWA dataset.

Meta does not remove repeated business messaging events. Konektor therefore sends one LeadSubmitted event, one QualifiedLead event when the lead becomes qualified, and one Purchase event for each lead. A later status change that would repeat one of them shows as Skipped in the Delivery log.

If the dedicated CTWA connection is not ready, Konektor continues sending new conversions as regular chat events through your default Meta dataset. This keeps conversion delivery running, but Meta does not receive CTWA-specific business messaging attribution until you complete the WABA connection.

How do you check the CTWA delivery result?

• Open Tracking & Ads > Conversions, then the Delivery log tab.
• The Meta CTWA badge identifies the dedicated CTWA channel. The badge is not acceptance proof.
• The Sent status on a Meta CTWA row proves that Meta received the dedicated event.
• The CTWA backup badge identifies the backup route through Meta CAPI.
• Other statuses: Failed, Skipped, and Queued. Skipped because of Strict mode is normal during a test without a Meta ad click.
• The Meta is not connected row means Meta is not added in Website Tracking. Add Meta there.
• Check reporting or attribution separately in Meta Ads Manager.

Konektor proves local configuration readiness and Meta acceptance of a dedicated event. Konektor does not prove Ads Manager reporting or attribution.

Troubleshooting

CTWA conversion is sent as chat

The lead has a ctwa_clid, but its dedicated CTWA dataset or authorization is not ready. Konektor sends the conversion as a regular chat event so delivery can continue. Meta will not treat that event as an attributed business messaging conversion.

Fix: open Connection > Numbers & CTWA, then select Manage CTWA. Run Check connection, then create one new conversion.

A CTWA backup row with Sent or Failed status can be eligible for Resend as Meta CTWA. A Meta CTWA row with a final Failed status can also be eligible. A row with Queued status is not eligible. A Meta CTWA row with Sent status blocks a duplicate. A regular Meta CAPI row does not offer CTWA resend.

"WABA not set"

The WhatsApp number that received the lead is not connected to Meta. Open Numbers & CTWA, select Set up CTWA on your number, then enter the WABA ID in the CTWA panel. Follow the Meta CTWA connection guide.

Pancake leads have no CTWA click ID

Pancake does not pass ctwa_clid to Konektor. Kapso does pass it. If you run CTWA ads, use a channel marked Yes in the table above, or contact our team.

Messages don't become leads at all

That's a partner connection issue, not CTWA. See the relevant partner guide (e.g. Qiscus, Kirimdev).

Next steps

• Click-to-WhatsApp Ads from Zero
• Set up Meta CTWA with Meta login
• Set up Meta CAPI
• Optimize EMQ Score
• WhatsApp Partner Integrations
• Why Initiate Checkout does not appear
• An ad chat is not a lead
• Track ads to a WhatsApp group
• How to choose ad tracking software