Ad Tracking Software for Umrah and Hajj Travel with Konektor.id

What is the problem with tracking Umrah and Hajj ads to WhatsApp?

A prospective pilgrim rarely signs up on the first click. People see a package ad, then ask about dates, hotels, and airlines on WhatsApp. Family members join the decision. Your team sends a brochure. Some prospects visit the office or join a manasik class. The deposit arrives after all of that, and the final payment follows.

A pixel on your website sees only the pages that open. A Click-to-WhatsApp ad opens no page at all. The brochure, the package talks, and the deposit invoice all happen in chat. The ad platform knows only that someone started a conversation.

So your ad numbers count chats, not pilgrims. Two ads can bring the same number of chats. One ad brings people who only ask a price. The other brings people who pay a deposit. From chat counts alone, you cannot tell them apart.

Two more problems follow. First, a service team is usually more than one person. The same prospect can get two different answers from two numbers. Second, chat volume rises sharply in busy seasons. Without a record of stages, your team cannot tell who to contact today.

A fictional example

Picture a travel agency called Travel Contoh. The names and the flow below are fictional.

Travel Contoh runs a Click-to-WhatsApp ad for one Umrah package. A prospect called Mrs. Sari taps the ad and asks about dates. Konektor.id creates a lead for Mrs. Sari and stores the ctwa_clid from her first message.

Customer service sends a brochure and changes the status to Contacted. Mrs. Sari talks it over with her family. Some time later she asks for the registration form, and the team changes the status to Hot. The team sends the deposit invoice, then picks Invoice Sent.

After the deposit arrives, the team picks Purchase and enters the Closing value. Meta receives Purchase with that value. Travel Contoh can now judge the ad by the prospects who paid a deposit, not only by the chats that came in.

How does Konektor.id track it?

Konektor.id serves four ad routes that end on WhatsApp. All of them end in the same lead and the same event table.

• Meta Click-to-WhatsApp. Meta adds ctwa_clid to the first message. Konektor.id creates a lead from the ad and stores that identifier. The details of this route are in Meta ad tracking software.
• Meta to a landing page. The tracking script stores fbclid and adds a visitor code to the WhatsApp Link. A click on the button creates a New lead.
• Google Ads to a landing page. The script stores gclid from the destination address of the ad. The lead carries that data until the status changes.
• TikTok to a landing page. The script stores ttclid in the same way.

On the three landing page routes, a coded message in the chat matches the conversation to the lead from the click. On the Click-to-WhatsApp route, ctwa_clid does the matching.

Once the lead exists, every status change reads the Event for each lead status table. That table picks the event for each platform. Konektor.id sends events from a server, so delivery does not depend on the browser of the prospect. How delivery to the Meta conversation dataset works is explained in WhatsApp CAPI software.

Some agencies create a WhatsApp group for the prospects of one departure. A Group mode rule can change a lead status when a person joins the group. That feature exists only on Scan QR numbers, and its limits are written in ad tracking to a WhatsApp group.

The identifiers and the data that go out

Chat text does not travel as event content. A lead without an email still goes out with the data it has.

How does a long sales cycle map to lead statuses?

A travel sales cycle is long because the decision of a pilgrim is long. Lead statuses break it into stages that you can count. Statuses run from New to Lost. You decide what each status means for your team. The table below is only one example mapping. For the full story of a hajj cycle, read the hajj travel ad tracking scenario.

Know three things before you use this table.

• Two statuses that use the same event name send it once. Responded and Qualified are both Lead in Meta, so the second status shows Skipped.
• A chat from a Click-to-WhatsApp ad through the CTWA dataset uses three event names only: LeadSubmitted, QualifiedLead, and Purchase. The Meta column in the table applies to landing page leads.
• The Leads campaign type uses a shorter mapping. Pick Sales if you want the stages from Hot to Invoice Sent to go out.

You can change the event in each cell, or pick Do not send. You make that change in Tracking & Ads > Conversions.

How does a customer service team share prospects?

For ads that go to a landing page, use a WhatsApp Link. One link splits visitors across several service numbers. You set the share of each number with Distribution Weight. A returning visitor goes to the same agent while that agent number stays active. For a travel business with slow decisions, this keeps one prospect with one person.

Create one link for each package or campaign. Fill the Default Message Template with the package name, so your team knows at once which package the prospect asks about, and reports can tell campaigns apart. The WhatsApp Links page shows Total Clicks and Total Leads for each link.

If your team needs starting data, such as city of origin, number of pilgrims, and planned month of departure, use Create Form. The answers of the form flow into the opening message through tags. The guide is in lead form with custom fields.

A Click-to-WhatsApp ad is different. The ad button opens a chat to one destination number. Your team replies from Inbox, and the lead status shows the stage of each person.

How do the deposit, the final payment, and the closing value reach the ad platform?

A closing happens when your team picks the Purchase status. Konektor.id opens the Closing value box. Your team enters the value and clicks Save closing. The Purchase event then goes to the connected platforms.

Decide one thing at the start: does Purchase mean the deposit or the final payment? Konektor.id sends Purchase once per lead. If Purchase means the deposit, the final payment sends no new signal. If Purchase means the final payment, the signal comes later and is firmer. Both choices are valid. What matters is that the whole team uses the same one.

Also decide what goes in the Closing value. Examples are the full package price or the deposit amount. Pick one way and write it in your team guide. A report means something only when the numbers are counted the same way.

Why the time of logging matters

Meta accepts only events that are at most 7 days old when sent. The official source is in the Sources section. Konektor.id sends an event when the status changes. So log the status on the day it happens. A deposit that your team logs weeks later reaches the ads with the same delay.

The gap between click and deposit can be long. Whether Meta still links that deposit to the original ad is Meta's decision. Konektor.id cannot confirm it, and this page gives no number. The Delivery log proves only one thing: the platform accepted the event.

What should you watch for in ad policies and prospect data?

Konektor.id sends conversion data. Konektor.id does not create or approve your ad content. Each platform has its own policy, and you are responsible for the ads you run.

Meta has a policy on personal attributes. According to the Meta Advertising Standards, ads must not state or imply personal attributes of the viewer, including religion and beliefs. Read the policy before you write ad text. TikTok also has its TikTok Advertising Policies. Both links are in the Sources section.

Konektor.id does not check the licence of your agency. Konektor.id also gives no legal or religious advice. For the rules on running pilgrimage travel, contact the official Hajj and Umrah authority.

For prospect data, keep two habits.

• Use standard events. Do not put sensitive data in custom event names.
• Ask for personal documents through the official registration route of your agency, not through an ad form.

How to read the result

Open Tracking & Ads > Conversions > Delivery log. A row with the status Sent means the platform accepted the event. A Skipped row in Strict mode means the lead did not prove it came from a click on that platform's ad. This result is normal in a test without an ad.

Reports and attribution stay in Ads Manager. The numbers can differ from the Konektor.id numbers because each platform uses its own attribution rules. Check both separately.