How to Track WhatsApp Landing Page Ads in Qontak CRM with Konektor.id: Automatic CAPI Feedback

Direct answer: You can track a Meta ad from a WhatsApp landing pageLanding pageThe page an ad points to. It carries 1 offer and 1 action, with no menu pulling the visitor elsewhere.What is a landing page? (LPWA) to a closed deal in Qontak CRM with 1 data chain: the Konektor tracking script on the landing page, a Rotator link that puts the visitor code [K-XXXXX] in the opening message, the Qontak integration in Konektor, rules that change the lead status, and the Conversions APICAPIA server path that sends conversion data from your system to the ad platform, without depending on the buyer browser.What is the Conversions API (CAPI)? (CAPI) that sends events back to Meta. After steps 1 to 9 below, a closed deal in WhatsApp becomes a Purchase event in Meta with no manual input.

Main condition: your business WhatsApp number receives chats through Qontak Omnichannel, your ads send visitors to a landing page, and you have admin access to Meta Business Manager. Limit: Konektor proves that an event was sent and accepted. AttributionAttributionHow a system decides which ad or channel receives the credit for 1 sale.High clicks, low sales: the tracking gap in Meta Ads Manager follows Meta's own rules, and this article promises no CPL or ROASROASRevenue from ads divided by ad spend. A ROAS of 4 means each Rp 1,000 of ad spend returns Rp 4,000 of gross revenue.How to calculate ROAS and break-even ROAS number.

We wrote this guide from the Rama Digital Konektor dashboard on 12 September 2026, the official Konektor documentation, the Mekari Qontak help center, and the Meta documentation. Every step has a screenshot. The dashboard runs in Indonesian; the English interface uses the same layout. Customer data in the images is dummy data or masked.

What gets lost when an ad ends in WhatsApp

The Meta PixelPixelA piece of code on a web page that tells the ad platform somebody opened the page or took an action.What is the Meta Pixel? stops working when a visitor taps the WhatsApp button. The conversation, the qualification, and the payment happen outside the browser. Meta only sees the click, so the algorithm optimises for people who click, not for people who buy. We describe the symptom in Many clicks, few sales: the problem can be tracking (Indonesian source).

The fix is 7 connected checkpoints. Each checkpoint stores the same identity, so the closed deal at step 7 can be returned to the click at step 1.

The diagram shows the 3 jobs Konektor does: it stores the click identity on the landing page, it joins the Qontak chat to that identity, and it sends an event to Meta after the lead status changes. The next sections explain the 2 mechanisms that make the chain work: fbclid and the visitor code.

How fbclid, _fbc, and ctwa_clid work

fbclid in the landing page URL

When a person clicks an ad on Facebook or Instagram, Meta adds the fbclid parameter to the destination URL. Example: https://shop.id/promo?fbclid=IwAR2F4-dbP0l7Mn1Iaw.... The value is case sensitive, so do not change it. Source: Meta documentation for the fbc and fbp parameters.

The _fbc cookie and its 90-day life

The Meta Pixel or your server stores that value as the _fbc cookie in the format fb.subdomainIndex.creationTime.fbclid. Example: fb.1.1757600000000.IwAR2F4-dbP0.... Meta asks you to keep this cookie for 90 days and to send it to the ConversionsConversionThe action you count as a result, for example a paid order, a sign-up, or a chat that becomes a qualified buyer.Open the glossary APIAPIThe official door 2 systems use to exchange data, without anybody copying it by hand.Open the glossary as user_data.fbc without hashing. With this value, Meta can connect a server event to the correct ad click.

ctwa_clid for Click-to-WhatsApp ads

A Click-to-WhatsAppCTWAA Click-to-WhatsApp ad. It sends people from Facebook or Instagram straight into your WhatsApp conversation.How to track CTWA ads (CTWA) ad skips the landing page, so there is no cookie. Meta injects ctwa_clid into the referral object of the first message webhook. Events for this path must use action_source: "business_messaging", messaging_channel: "whatsapp", and the raw ctwa_clid, sent to the WhatsApp Business Account dataset. Sources: Conversions API for business messaging and the Konektor CTWA guide.

Item	fbclid + _fbc	ctwa_clid
Origin	URL parameter when the visitor lands on the page	referral object in the WhatsApp message webhook
Storage	_fbc cookie, 90 days	Stored on the lead by Konektor
Sent as	user_data.fbc to the Pixel dataset	user_data.ctwa_clid to the WABA dataset
Event type	Standard website events such as Lead and Purchase	Business messaging events with messaging_channel: whatsapp
Used for	Ads that send people to a landing page	Direct Click-to-WhatsApp ads

Konektor reads 4 click IDs on the first visit: gclid, fbclid, ttclid, and li_fat_id. If one of them is present, Konektor records that the lead came from that ad. Source: Konektor visitor identification documentation.

How the visitor code [K-XXXXX] works in the opening message

The first click on a Rotator link sets a cookie with the visitor code. Konektor identifies a visitor in this order: the visitor cookie, the ad click ID, then the UTM parameters. The same visitor goes to the same agent on the next click while that agent is active. Konektor calls this sticky agent.

The same code enters the WhatsApp opening message through the [uniquecode] tag in the default message template. In our test, the template Halo [uniquecode] admin, saya mau konsultasi produced the message Halo [K-CM5NH] admin, saya mau konsultasi. The customer types nothing.

When that message arrives in Qontak, the Qontak webhook forwards it to Konektor. Konektor searches for the [K-...] pattern, finds the visitor with the same code, and turns the lead Visitor K-CM5NH into a lead with the real name and number. The Konektor documentation calls this an identity upgrade, and it runs automatically for partner channels such as Qontak. Source: Automation Rules documentation, section WhatsApp Rules (Partner API).

The point of the diagram: click attribution never changes hands. The customer name and number arrive later, but the fbclid and the campaign from the first click stay on the same lead.

Prerequisites

• A Qontak Omnichannel account with the Admin or Supervisor role, because only those roles can create an API token.
• A business WhatsApp number that is connected to Qontak and receives chats.
• A Konektor workspace with the owner or admin role. Konektor gives a 7-day trial without payment data.
• Admin access to Meta Business Manager, 1 Meta Pixel, and 1 ad account.
• A landing page where you can edit the <head>, or a Google Tag Manager container.
• 1 test number owned by the team to check the flow. Do not use a customer number for tests.

Step 1: Install the Konektor tracking code on the landing page

Open Tracking Website in the Konektor dashboard. The Unified Tracking Code card shows 1 code for all platforms. Click Lihat Kode (View code), then Salin Kode (Copy code). Paste the whole code before the closing </head> on every page you want to track.

The code from the dashboard already contains your workspace ID. Do not copy an ID from the documentation. If you use a custom domain for WhatsApp links, the dashboard adds customDomains to the init call, so copy the code again after the domain becomes active.

<!-- Konektor Tracking Code -->
<script>
  !function(w,d,t,u,k,a,m){ /* loader from the dashboard, do not edit */ }
  (window,document,'script','https://cdn.konektor.id/...','konektor');

  konektor('init', 'WS-XXXXXX', {
    customDomains: ['wa.yourbusiness.com']
  });
  konektor('track', 'PageView');
</script>
<!-- End Konektor Tracking Code -->

Test it in a private window: open the landing page, return to the dashboard, click Periksa lagi (Check again) on the activation panel, and confirm the header shows Event terverifikasi (Event verified). A loaded tracker.min.js file is not proof. The required proof is a received PageView event. Source: Konektor tracking installation guide.

Step 2: Connect Meta CAPI in Tracking Website

Get the token from Meta Events Manager: select the Pixel, open the Settings tab, scroll to Conversions API, and click Generate Access Token. Store the token in a password manager. Meta does not show it again. Source: Konektor Meta CAPI guide.

In Konektor, click Tambah Platform Iklan (Add ad platform), select Meta Ads (Facebook/Instagram), and fill in the 4 fields below.

1. Platform: Meta Ads (Facebook/Instagram).
2. Meta Pixel ID: digits only. Do not put the Test Event Code here.
3. Access Token: the CAPI token from Events Manager.
4. Dataset ID: optional. Fill it only when Meta gives a dataset ID that differs from the Pixel ID.

Click Simpan (Save), then use Uji platform (Test platform) with a Test Event Code from the Meta Test Events tool. The result accepted means Meta received the test event. Add the landing page domain to the Allow List under Traffic Permissions in Events Manager, because events from a new domain can be held until you confirm the domain.

Also add URL parameters to every Meta ad so the campaign, ad set, and ad are recorded on the lead. Konektor recommends this template in the URL Parameters field in Ads Manager, without a leading question mark.

utm_source=meta&utm_medium=paid&utm_campaign={{campaign.name}}&utm_term={{adset.name}}&utm_content={{ad.name}}&campaign_id={{campaign.id}}&adset_id={{adset.id}}&ad_id={{ad.id}}&campaign_name={{campaign.name}}&adset_name={{adset.name}}&ad_name={{ad.name}}&site_source_name={{site_source_name}}&ad_meta={{placement}}&ad_account_id=YOUR_AD_ACCOUNT_ID

Step 3: Create a Rotator link with the [uniquecode] tag

Open WhatsApp › Link WhatsApp (Rotator) and click Buat Link (Create link). Fill in the rotator name, the slug, the message template, and the agent numbers. The slug becomes the link address, for example konektor.id/wa/sales-utama. A Rotator needs no QR scan. Source: Konektor WhatsApp Rotator guide.

Write [uniquecode] once at the position you want. If the tag is absent, Konektor adds the code at the end of the message. The [k:name] tag reads URL parameters that start with k_. For example, ?k_produk=paket-bisnis becomes the product text in the message. This gives the agent context without a form.

Copy the Direct link, open it on a phone, and confirm that WhatsApp opens with the correct number and message. The Total Clicks value on the rotator row increases after a human visit. Bot previews may not count.

Optional: connect a custom domain under WhatsApp › Domain Kustom so the link uses your business domain, for example wa.yourbusiness.com. Add a CNAME record to custom.konektor.id with the Cloudflare proxy off, then wait for the Aktif (Active) status. Source: Konektor custom domain guide.

Step 4: Get the Qontak Omnichannel API token

Sign in to Qontak Omnichannel as an Admin or Supervisor. Open Settings › API token and select the Omnichannel tab. Click Generate in the Token section. Source: Mekari Qontak help center article on API tokens.

Click Show token, then Copy. The token is valid for 1 year from creation. Qontak shows an expiry label and the Generate button returns when the token expires, so put the date in the team calendar.

Do not paste the token into chat, tickets, or shared documents. Paste it only into the Konektor integration modal in the next step.

Step 5: Connect Qontak in Konektor Partner Integrations

Open Integrasi (Integrations) in the Konektor sidebar and click + Tambah Integrasi (Add integration). Select the Qontak WhatsApp card, enter an integration name, paste the token into the OAuth Token field, and click Hubungkan (Connect). Source: Konektor Qontak integration documentation.

The new integration card shows the Menunggu (Pending) status. Click Verify Connection on that card and wait for the status to change to Terhubung (Active). At this point Konektor registers the webhook in your Qontak account automatically. You do not copy a webhook URL into Qontak.

Once active, the Qontak integration gives you 3 things: incoming chats become leads, ctwa_clid from Click-to-WhatsApp ads is read, and the Tag Room (Qontak) condition becomes available in rules. If chats do not become leads, click Verify Connection again and confirm that the WhatsApp number in Qontak is still active.

Step 6: Put the Rotator link on the landing page and in the ad URL

Replace the wa.me button on the landing page with the Direct link from step 3. Use it on every WhatsApp button, including the floating button. The Rotator link carries the visitor code, and the tracking script from step 1 already stored fbclid and UTM on the same visitor.

In the ad, point the destination URL to the landing page and fill the URL Parameters field with the template from step 2. Do not send the ad straight to the Rotator link if you want the Meta Pixel and the landing page to record the visit. Read how the ad algorithm learns from conversion events to see why the landing page visit matters to Meta.

Test from a private window: open https://your-landing-page/?fbclid=test123&utm_source=meta&utm_medium=paid&utm_campaign=test, tap the WhatsApp button, then send the opening message from the test number. A fake fbclid value is enough to check the flow in Konektor, but Meta will not match it to an ad.

Step 7: Set up Conversion Settings and the event mapping

Open Konversi › Pengaturan Konversi (Conversions › Conversion Settings). The page has 3 parts: the conversion strategy, the ad platforms that receive data, and the event mapping preview per lead status. Source: Conversion Settings documentation.

Strict Mode sends an event only when a verified click ID such as fbclid is present. Ads Manager reports stay clean, but you see fewer conversions. Send All Events sends every qualifying event and relies on hashed data such as the phone number and email for matching. Rama Digital recommendation: start with Strict Mode for 2 weeks to confirm the flow, then move to Send All Events when you want the algorithm to learn from cross-device leads. Source: Konektor conversion strategy guide.

Lead status	Dashboard label	Meta event	GA4 event
pageview	Lihat Halaman	PageView	page_view
new	Baru	AddToCart	generate_lead
contacted	Dihubungi	Contact	working_lead
responded	Merespons	Lead	working_lead
qualified	Berkualitas	Lead	qualify_lead
hot	Hot	SubmitApplication	working_lead
proposal	Proposal	InitiateCheckout	working_lead
negotiation	Negosiasi	AddPaymentInfo	working_lead
invoice	Faktur Dikirim	AddPaymentInfo	add_payment_info
won	Closing	Purchase	purchase
lost	Loss	LeadLost (custom event)	close_unconvert_lead

The table shows the default mapping in the Preview Event Mapping panel on 12 September 2026. Konektor sends 1 event per category. A status that moves back and forth to won does not create 2 Purchase events.

Also enable Modal Trigger Statuses for the won status. The agent is then asked for the deal value when the status changes to Closing, so the Purchase event carries a rupiah value and Meta can calculate ROAS. Read our Knowledge entry on CAPI if your team is new to server events.

Step 8: Build automatic feedback rules

Open WhatsApp › Aturan Otomatisasi (Automation Rules). Every rule has 3 parts: a trigger, conditions, and an action. For partner channels such as Qontak, rules apply automatically to every incoming chat without selecting a session. Source: Konektor Automation Rules documentation.

We recommend the 4 rules below for an LPWA flow with Qontak. Rules 1 to 3 use the incoming customer message as the trigger. Rule 4 uses a message from the team.

Rule	Conditions	Action	Event to Meta
1. Customer replies	Sender type = Customer, Chat count ≥ 2, Lead status in list Baru, Dihubungi	Change Lead Status → Merespons (responded)	Lead
2. Price question	Message contains harga, berapa, paket, Lead status = Merespons	Change Lead Status → Berkualitas (qualified)	Lead
3. Purchase intent	Message contains order, pesan, booking, transfer	Change Lead Status → Hot	SubmitApplication
4. Payment confirmed	Sender type = Team/CS, Message contains Pembayaran diterima	Update Lead Value (regex Rp\s*([0-9.]+)), then Change Lead Status → Closing	Purchase with value

An example rule that already runs in our workspace: Otomatis HOT. It changes the status to Hot when the chat count is above 10 and the status is still Baru, Dihubungi, or Merespons.

The Tag Room (Qontak) condition reads the conversation tags that agents set in Qontak, with the operators Contains or Does not contain. Example: an agent tags the room vip, and a rule raises the lead priority to High. Other conditions that help on the Qontak channel: Partner source = qontak, First contact, and Time window, which uses the workspace time zone.

If you do not want to start from zero, click Template. The Auto Mark as Contact template marks a lead as Dihubungi (contacted) when the message contains the [K- pattern, which is the visitor code from step 3.

The AI button opens the Smart Rule Assistant. You write 1 sentence, for example "If a lead from Ads has chatted more than 2 times, change the status to Responded", and the assistant drafts the conditions and the action. Review the draft before you save it.

For the deal value regex, select a preset in the Update Lead Value action. The pattern Rp\s*([0-9]{1,3}(?:\.[0-9]{3})+) reads "Rp 1.500.000" as 1.500.000. The part inside the parentheses is the value the system captures.

Step 9: Test the flow from the click to the sync log

Run 1 full flow with the test number. Open the landing page with the test parameters, tap the WhatsApp button, send the opening message, then reply 2 times from the test number. Check the 3 places below.

Leads: the new lead shows the name Visitor K-XXXXX, the source whatsapp, and the status Baru (new). After the message arrives from Qontak, the customer name and number replace the visitor name. Open the lead detail to see the attribution parameters and the click identifier.

Konversi › Log Sinkronisasi (Sync log): every status change creates 1 row. A row with the Meta CAPI badge and the success status (the documentation calls it accepted) means Meta received the payload. The skipped status means Konektor did not send on purpose. In our test without fbclid, the tooltip gave the reason "Strict mode: adPlatform mismatch or missing click_id".

Meta Events Manager: open the Test Events tab while you use a Test Event Code, or the Overview tab after production data arrives. Check the Event Match Quality column. Konektor sends the phone number, name, city, and email as SHA-256 hashes, so complete the contact data in Qontak to raise the EMQ score. Source: Konektor EMQ guide.

Sync log status	Meaning	Action
queued, sending	The event waits in the queue or is in transit	Wait, then click Refresh
accepted / success	The platform received the payload	Check Events Manager
partial_failure	Part of the data was rejected	Read the message on the Attempts icon
failed	The request failed before it was received	Fix the token or permission, then Resend
skipped	Minimum data, consent, or the click ID is missing	Check fbclid on the lead and the conversion strategy

Step 10 (optional): Add the Click-to-WhatsApp path

If you also run Click-to-WhatsApp ads without a landing page, connect the WhatsApp Business Account to Konektor. Open WhatsApp › Sesi QR (lanjutan) (Sessions), save a session for the number that receives the ads, select Siapkan CTWA (Set up CTWA), enter the numeric WABA ID, and connect a Meta App token with the whatsapp_business_management and whatsapp_business_manage_events permissions. Konektor asks Meta to select or create the CTWA dataset, so you do not look up a Dataset ID.

Once active, leads from Qontak that carry ctwa_clid are sent as business messaging events. A Meta CTWA badge with the accepted status in the sync log is the proof of receipt. A CTWA fallback badge means the event went through the standard CAPI path for now, and you can resend it as Meta CTWA after the connection is ready. Source: Konektor Click-to-WhatsApp conversion tracking guide.

Worked example: 1 day at a fictional coffee shop

The example below is a simulation with dummy data. Sinar Kopi runs a Meta ad for office coffee packages with the landing page sinarkopi.id/kantor, a Rotator link, and Qontak Omnichannel.

Time	Event	What Konektor records	Event to Meta
09:10	A visitor clicks the ad and lands on the page	PageView, fbclid, campaign_id, UTM	PageView (optional)
09:12	The visitor taps the WhatsApp button	Lead Visitor K-7Q2ZD, status Baru, visitor cookie	AddToCart
09:13	The message "Halo [K-7Q2ZD] admin, saya mau tanya paket kantor" arrives in Qontak	Identity upgrade: the real name and number replace Visitor	No new event
09:20	The customer replies 2 times and asks for the price	Rules 1 and 2: status Merespons, then Berkualitas	Lead
11:05	The customer writes "oke saya order 20 paket"	Rule 3: status Hot	SubmitApplication
14:30	The agent writes "Pembayaran diterima Rp 2.400.000"	Rule 4: value 2,400,000, status Closing	Purchase, value 2,400,000

At the end of the day, the sync log holds 4 accepted rows for this lead. Meta received 1 Purchase with the value 2,400,000 and the fbc from the 09:10 click. The numbers in the table are an illustration, not a customer result.

Checklist before you raise the budget

1. The Tracking Website header shows Event verified. Owner: landing page developer. Evidence: screenshot of the activation panel.
2. The Meta platform test returns accepted with a Test Event Code. Owner: ads admin. Evidence: a row in Test Events.
3. Every WhatsApp button on the landing page uses the Rotator link, not wa.me. Owner: developer. Evidence: link check.
4. The default message template contains [uniquecode] once and the test message shows the code. Owner: Konektor admin. Evidence: screenshot of the opening message.
5. The Qontak integration card shows Connected. Owner: Konektor admin. Evidence: screenshot of the card.
6. The URL Parameters of every active ad contain campaign_id, adset_id, and ad_id. Owner: ads admin. Evidence: ad export.
7. The test lead changed from Visitor to a real name and kept the fbclid. Owner: Konektor admin. Evidence: lead detail.
8. 4 rules are active and Modal Trigger Statuses is active for won. Owner: CS lead. Evidence: rule list.
9. The sync log shows accepted for the test Lead and Purchase within the last 24 hours. Owner: ads admin. Stop criterion: a failed row that nobody has explained.

Konektor compared with a generic ad tracker such as Voluum

When we searched Google for "software tracking iklan terbaik" (best ad tracking software) on 12 September 2026, the AI Overview named Voluum and FunnelFlux, while the first organic result was Konektor.id. We describe that ranking journey in our Konektor.id SEO-AI case study (Indonesian).

The difference is not the word "best" but the work the tool does. Voluum calls itself an "Affiliate Tracker" and an "Ad Tracker for Media Buyers" on its pricing page, and it tracks events through redirect or direct tracking. Konektor is built for businesses that close deals in WhatsApp. The table below uses the pricing pages of both products on 12 September 2026.

Item you can verify	Konektor.id	Voluum
Product focus	Ad tracking, WhatsApp, and lead status for Indonesian businesses	Affiliate and media buyer tracker
Matching a WhatsApp chat to an ad click	Yes, through the visitor code and the partners Qontak, Qiscus, Kirimdev, kirim.chat, and Halo AI	Not mentioned on the pricing page
Lead status and CRM rules	11 statuses, no-code rules, Smart Rule Assistant	Auto-rules for campaigns, not for lead status
Sending conversions to Meta	Meta CAPI and business messaging CTWA	Auto-rules and API Integrations exist on every plan. Profit and Scale limit them to $1,000 of ad spend for free. Start-up, $539 per month billed annually, lists FB Ads, Google Ads, and TikTok integrations
Entry price	Starter Rp199,000 per month, 7-day trial without payment data	Profit $119 per month billed annually, 1,000,000 events
Numbers claimed by the vendor	500+ businesses, 1.5 million+ leads, 48 thousand+ feedback events, 99.5% success rate, 13-second median feedback (Konektor home page)	No comparable figures on the pricing page

Sources: the Konektor.id home page and the Voluum pricing page. We have not audited the vendor figures. Rama Digital recommendation: choose Konektor when your deals close in WhatsApp and your agents use Qontak or a similar partner. Choose a generic tracker when you sell through affiliate networks and do not need lead status.

Frequently asked questions

Does the customer have to type the [K-XXXXX] code? No. The code enters the opening message from the [uniquecode] tag in the template. If the customer deletes the code before sending, Konektor still creates a lead from the Qontak webhook, but the click attribution from the landing page is not attached.

Is an event sent twice when the status moves back and forth? No. Konektor sends 1 event per event category. A status that returns to won does not create a second Purchase.

How long can fbclid be used for attribution? Meta asks you to keep the _fbc cookie for 90 days and to refresh it on a new click. Send the closing event inside that window so the fbc value is still valid, and check the attribution window of your campaign in Ads Manager.

Strict Mode or Send All Events for a new business? Start with Strict Mode until the test flow returns accepted. Move to Send All Events when many customers see the ad on a phone and then chat from another device, because that mode uses hashed data matching.

Does Konektor send customer personal data to Meta? Konektor sends the phone number, email, first name, and city as SHA-256 hashes in the Meta format. The fbc and ctwa_clid values are sent without hashing, as Meta requires. You remain responsible for customer consent under your privacy policy.

Does Qontak need the official WhatsApp Business API for this integration? Yes. Qontak Omnichannel runs on the WhatsApp Business API, and Konektor reads messages through the Qontak webhook, not through a QR scan. The Qontak API token is valid for 1 year and must be regenerated before it expires.

Next step

This flow gives Meta a real closing signal, but ad results still depend on the offer, the creative, the agent response time, and lead status discipline. If you want us to install and run this flow together with your campaign, the Meta Ads Performance Management service covers Konektor.id, an official WABA CRM, the funnel, creative, and weekly reports. If you only want to see the data flow, book a 30-minute Konektor.id demo and bring your technical questions.

Sources

• Konektor: Qontak WhatsApp Integration
• Konektor: Automation Rules
• Konektor: WhatsApp and visitor identification
• Konektor: WhatsApp Rotator
• Konektor: Install and verify the tracking script
• Konektor: Meta Conversions API
• Konektor: Click-to-WhatsApp conversion tracking
• Konektor: Conversion Settings
• Konektor: Conversion strategy
• Konektor: Meta Event Match Quality
• Konektor: Custom domain setup
• Mekari Qontak: How to Generate API Token on Qontak Omnichannel
• Meta for Developers: fbp and fbc parameters
• Meta for Developers: Conversions API for Business Messaging
• Voluum: Pricing