How to set up a CTWA pixel on the WhatsApp Business API
Click-to-WhatsApp Ads (CTWA) send people from Facebook and Instagram straight into a WhatsApp chat with your business. But those ad clicks are worthless to your media buyer if Meta can't see what happened after the conversation started. A CTWA "pixel" setup — really the linking of your Meta Pixel and Conversions API events back to the WhatsApp thread — is what closes that loop, so Ads Manager can attribute leads, qualified conversations and purchases to the exact ad that drove them. This tutorial walks through wiring up CTWA conversion tracking on the official WhatsApp Business API with InfiQ, in the correct order, with the mistakes that quietly break attribution.
What you'll do
Connect your Meta Pixel and Conversions API to your WhatsApp Business API number through InfiQ, capture the ad referral each inbound chat carries, and post back conversion events (lead, qualified, purchase) to Ads Manager so CTWA campaigns are optimised and attributed correctly.Before you start: what a CTWA pixel actually is
There is no separate "WhatsApp pixel" you install on the phone. CTWA tracking is the combination of three things: your existing Meta Pixel (or dataset), the referral data that every Click-to-WhatsApp Ad attaches to the first inbound message, and conversion events posted back to Meta via the Conversions API (CAPI). When someone taps a CTWA ad, the first message their chat delivers to your WhatsApp Business API number carries a referral object containing the source ad ID, headline and a ctwa_clid click identifier. InfiQ reads that object automatically, so the job is to make sure the right Meta assets are connected and that meaningful events are fired back. Get this right and Ads Manager can optimise for real outcomes instead of just clicks.
- Meta Pixel / dataset ID — the destination your events land in
- Conversions API access — server-side event posting from InfiQ
- The referral payload — ctwa_clid and source ad ID on the first inbound message
- Standard events — Lead, Contact, Qualified conversation, Purchase
Step 1 — Prepare your Meta assets and WhatsApp number
Groundwork first. In Meta Business Manager, confirm the Business Portfolio that owns your ad account also owns (or has access to) the WhatsApp Business Account connected to InfiQ — mismatched ownership is the single most common reason events never attribute. Make sure your WhatsApp Business API number is live and verified with InfiQ, your Meta Pixel exists, and your display name is approved so ads can point to the number. If your CTWA ads are already running, note down the Pixel/dataset ID you use for those campaigns; you will connect that same one, not a new pixel.
- Business Portfolio owns both the ad account and the WhatsApp Business Account
- WhatsApp Business API number active and verified with InfiQ
- Meta Pixel / dataset created and accessible in Events Manager
- Display name approved so CTWA ads can route to your number
Step 2 — Connect the Pixel and Conversions API in InfiQ
In the InfiQ dashboard, open the CTWA / Ads integration settings and link your Meta ad account. You will select the Pixel (dataset) that your Click-to-WhatsApp campaigns already optimise against, and authorise InfiQ to send server-side events to it through the Conversions API. Because CTWA conversions happen inside a chat rather than on a website, everything is posted server-side — there is no browser pixel firing. InfiQ maps the ctwa_clid from the inbound referral to the event so Meta can match the conversation back to the originating ad, ad set and campaign.
- Authorise the Meta ad account connection from InfiQ
- Choose the same Pixel/dataset your CTWA ads use
- Enable Conversions API (server-side) event posting
- Confirm InfiQ is passing the ctwa_clid with each event
Step 3 — Define which conversation moments count as conversions
Decide what a "conversion" means for your funnel and map each moment to a standard Meta event. A raw first reply is a weak signal; a qualified reply or a completed order is what your media buyer should optimise toward. In InfiQ you attach these events to points in your flow — for example fire a Lead when a contact answers the qualifying question, and a Purchase (with value and currency) when an order is confirmed. Sending value on purchase events unlocks value-based optimisation and honest ROAS reporting in Ads Manager. Keep the event list short and meaningful so Meta's model has a clean signal to learn from.
- Contact / Lead — first meaningful reply or opt-in captured
- Qualified conversation — contact passes your qualifying criteria
- Purchase — order confirmed, sent with value and currency
- Avoid firing on every inbound message — it dilutes optimisation
Step 4 — Test end to end before you scale spend
Never trust CTWA tracking until you have seen a real event land. Create a low-budget CTWA ad (or use an existing one), tap it from your own phone, and complete the journey through to whichever event you configured. Then open Events Manager and use the Test Events / event activity view to confirm the event arrived with the correct ctwa_clid and, where relevant, a match to the source ad. Check that the event is de-duplicated and shows a healthy Event Match Quality. Only once you can see your own test conversion attributed to the right ad should you raise budgets.
- Click your own CTWA ad and finish the tracked journey
- Confirm the event appears in Meta Events Manager
- Verify ctwa_clid is present and attribution resolves to the ad
- Check Event Match Quality and de-duplication look healthy
Step 5 — Go live, optimise and monitor
With a verified event, switch your CTWA campaign objective to optimise for the conversion event you fire (Leads or Sales) rather than for messaging or link clicks. Give Meta's delivery system a few days and enough conversions to exit the learning phase before you judge results. On the InfiQ side, keep an eye on message delivery, template quality rating and your number's quality tier — a throttled or flagged number will silently starve your CTWA funnel of conversations even when the tracking is perfect. Review attribution weekly and prune events that don't map to real business value.
- Set the campaign to optimise for your posted conversion event
- Allow the ad set to exit the learning phase before judging
- Watch WhatsApp delivery and number quality tier in InfiQ
- Review attribution and event value in Ads Manager weekly