Google Ads Tracking Software with Konektor.id

What is the problem with tracking Google ads to WhatsApp?

Many Google ads end in a conversation. A person searches on Google, taps an ad, opens a landing page, and then writes to your support team. The price is discussed and the payment is made on WhatsApp. Google takes no part in that conversation.

A tag on your website sees only the pages that open. Google knows the person who visited, but it does not know the person who paid in the end. Your ad report stops at the click or at the first chat.

The import guide of Google requires a Google Click ID on every conversion that comes from a click. So you need to keep the click identifier with the lead data, then send it back when the lead becomes a sale. Konektor.id does both for you.

A fictional example

Picture a course called Kursus Contoh. It runs a Google search ad to a landing page with the class schedule. The names and numbers below are fictional.

A prospect named Budi searches for a class, taps the ad, opens the landing page, and taps the WhatsApp button. Auto-tagging already added a gclid to the page address. Konektor.id stores the gclid with Budi's new lead. Support answers the schedule question, then changes Budi's status to Qualified. Google Ads receives a qualify_lead upload.

Three days later Budi pays Rp2.500.000. Support changes the status to Closed won and enters the Closing value. Google Ads receives a purchase upload with the value. Kursus Contoh now has a conversion that points to one specific ad click.

How does Konektor.id track it?

The route runs in seven stages.

1. A person taps the Google ad. Auto-tagging adds gclid to the destination address. For a click that moves between an iOS app and a web page, the address can carry wbraid or gbraid.
2. The tracking script on the landing page stores the click identifier and the UTM parameters, then adds the visitor code to the WhatsApp link.
3. The WhatsApp Link button is tapped. Konektor.id creates a lead with the status New and stores the gclid, wbraid, and gbraid of that click.
4. A message with the code [K-XXXX] arrives at your number. The code matches the chat to the same lead.
5. Your team or an automation rule changes the lead status. Each change reads the Event for each lead status table.
6. Konektor.id uploads the conversion from the server to the conversion type you chose in Google Ads.
7. The result shows in the Delivery log, with the status Sent, Failed, or Skipped.

The Direct link from WhatsApp Links reads gclid, wbraid, and gbraid from the address that was clicked. So put the Direct link on the landing page button, and test with one click before the ads go live.

The data sent to Google Ads

Konektor.id sends only the data that the lead holds. A lead without an email still goes out with its gclid or phone number.

Strict mode and Send all on this route

Strict mode is the default. On the Google Ads API route, Strict mode lets through a lead that has a gclid, an email, or a phone number. A lead that has none of the three shows Skipped.

This rule differs from TikTok or Meta. A test lead without an ad click still goes out if it has a phone number. Google decides whether that contact data matches a click on your ad. Send all sends every lead that has any identity.

Why does Konektor.id upload directly instead of using a browser tag?

A browser tag records only what happens on a page. The WhatsApp conversation happens outside the page, so the tag does not see it. A direct upload carries the result of the conversation from the Konektor.id server to Google Ads, without waiting for the visitor to open a page again.

The Google Ads API documentation describes gclid as the identifier taken from the address parameters when a user taps an ad. The same documentation says that a conversion with only hashed user data is still useful. Konektor.id uses both: gclid when it exists, and the hashed email or phone number as an addition.

GA4 or the Google Ads API?

Konektor.id has two routes for Google. The GA4 route sends events to Google Analytics, then you import them into Google Ads. This route needs ga_client_id when the event is sent.

The Google Ads API route uploads to Google Ads directly and uses the conversion type ID. For the landing page to WhatsApp flow, the Konektor.id guide recommends the second route. You pick the route in the Delivery Mode field in Website Tracking.

How do you stop every status from counting as a conversion?

On the Google Ads API route, Konektor.id sends each mapped status as a separate upload. If you use one conversion type ID for all statuses, all uploads go to the same conversion type.

That means the statuses New, Contacted, and Loss go to the same place as Closed won. The event name in the table decides only when Konektor.id sends, and what shows in the Delivery log. The name does not choose the conversion type in Google Ads.

There are three ways to keep your numbers clean.

• Choose Not sent in the Google Ads cell for a status that must not become a conversion. Loss is the clearest example.
• Enter a conversion type ID per status in the Event for each lead status table. One conversion type for Qualified and one for Closed won lets Google keep the two apart.
• Use the Leads preset if you need only new leads, qualified leads, and closings.

A cell with its own conversion type ID counts as an event that you set yourself. Konektor.id does not limit it to one time per lead.

How do you read the result in the Delivery log?

Open Tracking & Ads, then Conversions, then the Delivery log tab. Choose the platform Google Ads to see the Google events only.

The result has two layers. The first layer: did Google accept the upload. The status Sent answers it. The second layer: does the Google Ads report show and attribute the conversion. That layer is in the hands of Google. The Google import guide says data can take 24 to 48 hours to show fully.

A few things often appear during a test:

• A new conversion type needs time before it takes uploads. The Google import guide advises you to wait 4 to 6 hours after you create a new conversion type.
• The test send checks the account and the conversion type, but it does not prove that the tracking code is on the landing page.
• A Failed row marks an upload that Google rejected. Check the conversion type and the account connection, then click Resend on that row.
• The status Sent does not mean your ad is already counted in the report. Check the Goals > Conversions page in Google Ads too.

One condition concerns your account. The Google documentation lists a prerequisite for hashed user data: the account turns on enhanced conversions for leads and accepts the customer data terms. If that setting is off, Konektor.id still uploads with the gclid, but it leaves out the email and the phone number.

How do the Google ad policies apply?

Your ads still follow the Google ad policies. This page does not change those rules. Google asks advertisers to comply with applicable law and with its ad policies in every place where the ads appear.

Konektor.id only uploads conversion data that your lead already holds. You are responsible for the basis on which you collect customer data, including email and phone number. The policy link is in the Sources section.