LinkedIn Ads Tracking Software with Konektor.id

What is the problem with tracking LinkedIn ads to WhatsApp?

A B2B sale rarely closes in one visit. A decision maker sees an ad, opens your page, then sends a WhatsApp message. The price talk, the quote, and the internal approval run for weeks inside the chat.

The Insight Tag on your website sees the pages that open and the actions that happen on the website. LinkedIn knows the people who dropped by, but not who finally signed the contract in the chat. Your campaign report stops at the click or at the first chat.

LinkedIn also states its own limit. According to the LinkedIn documentation, a conversion can be attributed only to a member that LinkedIn matched with the conversion data. So each conversion needs an identifier that can be matched, and that identifier must be stored when the conversation starts.

This page explains what Konektor.id does for LinkedIn ads, what it does not do, and who should use it. It is also plain about one point: this route is built for leads that close on WhatsApp, so not every LinkedIn advertiser will fit.

A made-up example

Take a company called Kantor Contoh that sells attendance system subscriptions to factories. The names and amounts below are made up.

Ms. Sari, the operations head of a factory, taps a LinkedIn ad of Kantor Contoh. LinkedIn adds li_fat_id to the landing page address. Ms. Sari taps the WhatsApp button on that page. Konektor.id stores li_fat_id on her new lead.

The sales team answers the technical questions, then changes the status of Ms. Sari to Qualified. LinkedIn receives one conversion. Six weeks later the factory signs a contract of IDR 48,000,000. Sales changes the status to Closed won and enters the Closing value. LinkedIn receives a second conversion with that value.

How does Konektor.id track it?

The landing page route has six stages.

1. A person taps the LinkedIn ad. When Enhanced conversion tracking is on, LinkedIn adds li_fat_id to the destination address.
2. The tracking script on the landing page stores li_fat_id and the UTM parameters in the browser, then adds a visitor code to the WhatsApp link.
3. The WhatsApp Link button is tapped. Konektor.id creates a New lead and stores li_fat_id on that lead.
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 sends the conversion from the server to LinkedIn through the Conversions API. The result shows in the Delivery log.

The Konektor.id tracking code also loads the LinkedIn Insight Tag from the Partner ID that you save. You do not need a separate Insight Tag, unless your page already has one.

The data that goes to LinkedIn

Konektor.id sends the data that the lead holds. A lead without an email can still go out when it carries li_fat_id.

Why does one conversion rule change how you set the statuses?

Konektor.id sends every conversion to one conversion rule, the rule of the Conversion ID that you save. A name such as QUALIFIED_LEAD or PURCHASE in the table is only a label on the Konektor.id side. LinkedIn judges the conversion by the type of the rule that you create in Campaign Manager.

The effect is real. If your rule has the type Purchase or Add to Cart, LinkedIn states that each event is counted on its own. A lead that passes five statuses can produce five counts.

Decide first which stage LinkedIn should count. Then open the LinkedIn Ads column in the Event for each lead status table and choose Not sent for the other statuses. For B2B, the usual choice is Qualified or Closed won.

LinkedIn offers a Qualified Leads optimization goal. According to LinkedIn, the conversion rule must have the type QUALIFIED_LEAD to be eligible for that goal, and qualified lead data must be shared within 30 days to count for ad set optimization. You choose the rule type in LinkedIn, not in Konektor.id.

Once for each event name

Konektor.id sends each built-in event name once for each lead. Qualified and Hot both use the label QUALIFIED_LEAD in the Sales type. The first status reached is sent, and the second shows Skipped in the Delivery log.

This rule keeps the number of conversions close to the number of leads. An event that you set yourself in the table does not follow this rule.

Send strategy: Strict mode or Send all

Strict mode is the default. It sends leads that carry li_fat_id or are recorded as coming from a LinkedIn ad. An organic lead shows Skipped. Send all sends every lead that qualifies. You choose it in Conversions, under Send strategy.

Under Send all, a lead with no li_fat_id and no email has a small chance to match on LinkedIn. Strict mode keeps the numbers clean.

Is LinkedIn a good fit for a business that closes on WhatsApp?

The honest answer: it fits some businesses, and not others.

This route fits when your buyers are companies or professionals, the deal value is large, and the decision involves several people. When the final negotiation happens in a WhatsApp chat, Konektor.id connects the ad click with that stage.

This route fits less when you sell a cheap product to general buyers who decide fast. LinkedIn sets the ad cost and the audience, and Konektor.id does not change them. First consider whether your buyers are really on LinkedIn.

What does Konektor.id not do for LinkedIn?

• Konektor.id does not create or change your LinkedIn campaigns. You manage them in Campaign Manager.
• A lead from a LinkedIn Lead Gen Form stays on LinkedIn. Konektor.id tracks leads that arrive through a landing page and WhatsApp.
• Konektor.id does not pick the conversion rule type for you. That choice sits in LinkedIn.
• Konektor.id does not replace the Campaign Manager report. The numbers in LinkedIn remain the numbers of your ads.

What to weigh for a long sales cycle

LinkedIn states time limits that you should know before you decide.

So change the lead status when the stage is really reached. A status changed weeks later makes the conversion arrive late for LinkedIn.

How do you read the result in the Delivery log?

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

The result has two layers. The first layer: did LinkedIn accept the request. The status Sent answers it. The second layer: did LinkedIn match the conversion with a member and attribute it to a campaign. That layer sits with LinkedIn. Campaign Manager shows the status of the conversion rule, including a warning when the match rate is low.

Things that often appear in a test:

• A test lead with no ad click shows Skipped under Strict mode. This result is normal. It does not mean Konektor.id failed.
• Test send uses the same conversion rule as a real delivery. A test event can show in the LinkedIn report.
• The status Sent does not mean your ad is already counted. LinkedIn needs up to 72 hours for complete reporting.

Ad policy

Your ads still follow the LinkedIn Advertising Policies. According to those policies, the advertiser is responsible for compliance with privacy and data protection laws, and ads must not target by sensitive data. LinkedIn also advises that the Insight Tag stay off pages that collect sensitive data.

This page does not change those rules. Konektor.id sends only the conversion data that already exists on your lead. The policy links are in the Sources section.