LPWA Ads Tracking Software with Konektor.id

What is the problem with tracking ads on the landing page to WhatsApp route?

This route has three jumps. A person taps an ad, reads a landing page, then moves to the WhatsApp app. The payment usually happens in that chat. The ad platform does not move along.

The click identifier lives in the address of the landing page. WhatsApp has no such address. The first message of the customer holds only text, so the chat and the click look like two events that have no link.

As a result, the ad report stops at the page visit or the button tap. The platform knows that someone stopped by. It does not know who finally paid.

LPWA solves this with one small code. The code is born on the landing page and travels inside the opening message. That code reconnects the chat to the click.

A fictional example

Imagine a language school named Kursus Contoh. The school runs a Google ad to a landing page for an English class package. The names and numbers below are fictional.

A prospective student named Sari taps the ad. The page address holds a gclid. Sari reads the class schedule, taps the WhatsApp button, then sends a message that holds the visitor code.

Support answers the schedule question, then changes the status of Sari to Qualified. Ten days later Sari pays Rp1,200,000. Support changes the status to Closed won and fills in the Closing value. Google Ads receives a purchase event with that value.

How does Konektor.id track the LPWA route?

The route runs in seven stages.

1. A person taps the ad. The platform adds a click identifier to the destination address. The Ad link templates add the campaign name and the ad ID.
2. The tracking script on the landing page reads the click identifier and the UTM parameters. The script keeps them in the browser for 30 days.
3. The script also creates a visitor code in the form [K-XXXXX], then attaches the click identifier and that code to the Konektor.id links on the page.
4. The visitor taps the WhatsApp Link button. Konektor.id creates a New lead, stores the click identifier on that lead, then opens WhatsApp.
5. WhatsApp opens with an opening message that holds the visitor code. The customer sends that message to the destination number.
6. Konektor.id reads the code from the message text and matches the chat to the lead from stage 4. The name and the phone number of the customer fill in on that lead.
7. The team or an automation rule changes the lead status. Each change reads the Event for each lead status table and sends an event to every connected platform.

Click identifiers for each platform

How a platform creates its identifier follows the documentation of that platform. According to Meta, fbclid is added to the address when a person taps an ad on Facebook or Instagram. According to Google, auto-tagging adds gclid to the destination address. According to TikTok, ttclid is added to the landing page address when a person taps an ad. The source links are in the Sources section.

The visitor code is in the message text

The code [K-XXXXX] enters the message through the Default Message Template in WhatsApp Links. If you write the tag [uniquecode], you decide its position. Without that tag, the code is added at the end of the message.

The code sits in the text, not in a WhatsApp cookie. So the match does not depend on the app that the customer uses. The customer only needs to send the message and keep the code.

If the button uses a wa.me link

The script still adds the visitor code to the text of a wa.me link. But a tap on that link is not recorded as a lead. When the message arrives, Konektor.id matches the chat to the visit, and the lead status stays at Page view. No event goes out until the status changes.

What if the customer opens WhatsApp on another device?

The chat still matches if the message that is sent still holds the visitor code. The code is in the message text, so the sending device does not change the result.

The click identifier is different. It is kept in the browser where the person tapped the ad. If that person opens the landing page again from another browser or device, and the page address holds no identifier, the new lead carries no click identifier.

Two steps help in this case:

• Use the Ad link templates, so that the campaign data stays in the destination address.
• Choose Send all under Send strategy if you want leads without an identifier to go out anyway. The platform then matches them through the hashed email and phone number.

The second choice sends more leads, including leads that did not come from an ad click. Read the Conversion Strategy guide before you choose.

How is LPWA different from an ad that opens WhatsApp directly?

An ad that opens WhatsApp directly has no page, so the tracking script does not run. The click identifier arrives with the first message of the customer. Konektor.id reads that route in a different way for each platform.

For a Meta Click-to-WhatsApp ad, read Meta ads tracking software. For a TikTok messaging ad, read TikTok ads tracking software. Those two pages explain the events, the requirements, and the limits of each route.

This page covers the route that has a landing page. That route gives one advantage: the page address already holds the click identifier before the chat starts. One tracking flow applies to all five ad platforms.

How do you read the result in the Delivery log?

Open Tracking & Ads, then Conversions, then the Delivery log tab. One status change creates one row for each connected platform.

The status Sent means that the platform accepted the event. The status Skipped means that Konektor.id chose not to send that event. The reason shows in that row.

Check three things during a test:

• A test lead without an ad click shows Skipped in Strict mode. That is not a failure.
• A platform that is not in Website Tracking receives nothing.
• Sent does not mean the ad report already holds the conversion. Check Events Manager or Ads Manager on that platform too.

Double events from your own pixel

Konektor.id sends events from the server. The tracking script does not load the browser pixel of a platform by default. If you install your own pixel, make sure that one event does not leave from two places.

Meta and TikTok merge an event from the pixel and an event from the server only when the event name and the event_id are the same. Without that, both events count. The official sources are in the Sources section.

Ad policies

Your ads still follow the policy of each platform: Meta Advertising Standards, Google Ads policies, and TikTok Advertising Policies. This page does not change those rules. Konektor.id only sends the conversion data that your lead already holds. The policy links are in the Sources section.