Hajj travel ad tracking scenario: from first chat to deposit with Konektor.id

Why are hajj travel ads hard to read from the number of chats?

Because hajj pilgrims decide slowly, while the ad platform sees only the first chat.

A person who sees a special hajj package ad rarely registers at once. They ask about the facilities and the registration steps. They talk it over with the family. They compare several travel agencies. The deposit arrives long after the click, and the full payment comes even later.

During that time, a Click-to-WhatsApp ad knows one thing only: who started a chat. The ad learns to find people who like to ask questions. Those people may never register.

A long cycle causes three more problems.

• Pilgrims change hands. A CS agent takes leave, moves to another task, or leaves the company. The chat history stays on the phone of a person who no longer holds the lead.
• The stage is hidden. A chat that has been quiet for two months looks the same as a chat that just arrived.
• Ads and deposits are far apart in time. Today's ad report does not show a deposit that arrives months from now.

This page describes one scenario for a hajj travel agency with a cycle like that. If you sell umrah packages with a shorter cycle, read the umrah travel scenario. This page does not repeat it. It covers what changes when the cycle lasts months: status definitions, follow-up, handover, and the age of your data.

Here is ad tracking to WhatsApp for a long cycle. Konektor.id does not promise ad results. Konektor.id records the stage of each pilgrim and sends events to the ad platform when your team changes a status. The ad platform decides attribution and reports.

What does the journey of one hajj pilgrim look like, from click to deposit?

One pilgrim can take months, and Konektor.id keeps the stage of every step.

This example is fictional. The names and the flow are made up, carry no numbers, and do not come from any travel agency.

One evening. Mr. Hendra sees a special hajj package ad on Instagram. He taps the WhatsApp button and asks, "What do the facilities include, and how does registration work?"

Konektor.id records the chat as a New lead with the data of its ad. Because the chat comes from a Click-to-WhatsApp ad, Meta receives one LeadSubmitted event for this lead.

The next morning. CS opens the Inbox, replies, and sends a brochure. CS raises the status to Responded. Meta already holds LeadSubmitted for this lead, so this status sends no new event.

A few days later. Mr. Hendra writes that he wants to talk with his family first. CS taps Snooze, chooses Pick a time…, and sets a follow-up date. CS adds the Label Menunggu keluarga (waiting for family) and writes an Internal note: his questions, the package he viewed, and what the team promised. The note is not sent to the customer.

The snooze date arrives. The chat opens again in the CS list. The 24-hour window closed long ago. On an official connection, CS sends an approved message template. Mr. Hendra replies, and a new window opens.

A few months later. The CS agent who holds the lead moves to another task. The team moves the chat to a new teammate through Assignee. The teammate reads the Internal note and knows the context at once.

Decision day. Mr. Hendra writes, "Kami mau daftar berdua" (we want to register, both of us). An Automation Rule reads that phrase and changes the status to Hot. After CS confirms a package and a schedule that fit, the status goes to Qualified, and Meta receives QualifiedLead.

Deposit day. CS sends the deposit invoice and chooses Invoice Sent. After the deposit arrives, CS opens the Leads page, chooses Purchase, and enters the Closing value. Konektor.id sends a Purchase event to Meta with that value.

Full payment day. The full payment comes much later. CS adds the Label Lunas (paid in full) and one Internal note. The status stays Purchase. No second Purchase goes out, because Konektor.id sends the built-in Purchase once for each lead.

Which lead statuses suit a long cycle?

Use statuses that mark progress in the decision, not how long the chat has run.

Konektor.id has ten lead statuses: New, Contacted, Responded, Qualified, Hot, Proposal, Negotiation, Invoice Sent, Purchase, and Lost. You do not need to use all of them. The table below is only a suggestion. Adapt it to the flow of your travel agency, then write it in the team group.

Three habits keep this table useful.

• Do not mark a quiet chat as Lost. A quiet pilgrim is often still thinking. Use Snooze and Labels for that. Lost asks for confirmation before it saves, and a Lost lead leaves the Active tab on the Leads page.
• Raise the status when the event happens, not at the recap. Events go out when the status changes. A status changed weeks later reaches the ad platform with the same delay.
• One person, one holder. In the contact panel, only the assignee of a lead can change the Lead stage. This rule stops two CS agents from overwriting each other.

Which status sends an event to the ad platform, and when?

For chats from Click-to-WhatsApp ads, Meta receives three event names, and each name goes out once for each lead.

Conversion Settings maps each status to an event. For chats from Click-to-WhatsApp ads, Konektor.id sends events through the business messaging route of Meta, and turns each event on that route into one of three names. Meta does not help remove duplicate events (Meta for Developers). So Konektor.id holds back repeats itself.

Read this table with care.

• A second change to Purchase sends nothing. The built-in Purchase goes out once for each lead. If a status moves back and forth between Invoice Sent and Purchase, the first change is the one that goes out. Change to Purchase only when the point your team agreed on has really happened.
• An event that you set yourself does not follow this rule. The once-only rule applies to built-in events. An event that you change in the Event for each lead status table can go out each time the status changes.
• The event time is the time of the status change. Meta accepts events with a time up to 7 days before sending (Meta for Developers, checked on 14 October 2026). Change the status on the day it happens.
• The Delivery log proves receipt, not attribution. A Sent row means Meta received the event. How long Meta keeps linking a deposit to its source ad is Meta's decision, and this page gives no number.

For ads that lead to a landing page, Meta, Google Ads, and TikTok use a fuller set of event columns. That table is in umrah and hajj travel ad tracking software, so this page does not copy it.

How does the CS team keep follow-up going for months?

Use Snooze, Labels, Internal notes, and the Inbox views, then set a weekly habit in the team.

Konektor.id does not send date reminders for a lead that has been quiet for a long time. Automation Rules read incoming WhatsApp messages, not the clock. Your team builds a follow-up routine from these features.

Snooze. The Snooze button above a conversation hides the chat until a time you choose: In 1 hour, This evening, Tomorrow morning, Monday morning, or Pick a time…. You can snooze up to 30 days ahead. The chat opens again by itself when the time comes, or when the pilgrim replies. For a longer pause, snooze again after the chat opens. A snoozed chat shows in the Snoozed view.

Labels. Labels sort chats by your own categories, for example Menunggu keluarga or Menunggu pelunasan. Only owners and admins can create labels, and one workspace keeps at most 20. Because of that limit, use labels for waiting stages, not for every detail.

Internal notes. The Internal note tab keeps context that is not sent to the customer. Type @ and a teammate's name to mention them. The teammate you mention gets a notification. A good note holds what the pilgrim asked, what the team promised, and when the team will write again.

Daily views. In the Inbox rail, Assigned to me shows the chats you hold. Unreplied and Reply due soon show the queue that waits for your team. Snoozed shows chats saved for later.

Weekly list. On the Leads page, the Active tab shows leads that are neither Purchase nor Lost. Filter by Status to see who stopped at Hot or Invoice Sent. Ask each CS agent to open that list on the same day each week.

After the 24-hour window closes

On an Official WhatsApp Business connection, WhatsApp limits free-text replies to 24 hours after the last message from the pilgrim. After the window closes, the message box accepts only approved message templates. Send one template. A new window opens as soon as the pilgrim replies. The guide is at WhatsApp message templates.

A template needs time for approval, so submit it before CS needs it. Do not wait until hundreds of chats need a greeting.

QR scan has no 24-hour limit, but that route is unofficial, can break Meta terms, and the number can be blocked. Do not make QR scan your daily follow-up tool.

How do CS agents share pilgrims without overlap?

For ads that lead to a landing page, use a WhatsApp Link. For Click-to-WhatsApp ads, split chats with the Assignee in the Inbox.

Ads to a landing page or a link. Open Links & Domains › WhatsApp Links, click Create Link, enter the Rotator Name, then click Add Number for each CS agent. Distribution Weight sets the share. A WhatsApp Link remembers the agent who received a visitor before, so a returning visitor goes to the same agent while that agent's number is active. That matters when a pilgrim comes back after weeks.

Click-to-WhatsApp ads. The ad button opens a chat to one destination number. Put the number connected to Konektor.id in the ad, not an outside rotator link. The Inbox guide explains why: an outside rotator cuts the ad data. Chats arrive in one Inbox. Choose an Assignee on each chat, or use Select multiple and then Assign to move many chats at once when CS changes.

One lead has one assignee. When a CS agent moves on, change the assignee and make sure the Internal notes are complete.

Does Purchase mean the deposit or the full payment?

Choose the deposit if the team wants an earlier signal for the ads, and the full payment if the team wants a more certain signal.

Konektor.id does not detect payments and does not read transfer proof. Purchase goes out after CS or an automation rule changes the status to Purchase. Because the built-in Purchase goes out only once for each lead, the closing point is a business decision that your team must take at the start.

Both are valid. What matters is that the whole team uses the same choice. Write that choice in the team guide.

Decide the Closing value too. Use one method, for example the full package price, and write it down. Reports mean something only when each CS agent fills the value the same way.

Record later stages outside the status. The Labels Menunggu pelunasan and Lunas, plus an Internal note, keep the history without a second event.

How do I set it up in Konektor.id?

Setup takes about one to two hours, in nine steps. Follow them from the top, because each step feeds the next.

1. Connect your WhatsApp number

Open Connection › Connect WhatsApp. Choose a connection that reads ad data, and use the same number as in your ad. An Official WhatsApp Business connection and some chat providers read ad data. The full list is in the Click-to-WhatsApp guide.

2. Connect Meta

Open Tracking & Ads › Website Tracking, then choose Add ad platform › Meta.

1. Enter the Meta Pixel ID and Access Token from Events Manager.
2. Click Save.
3. From the row menu, choose Test send and send one Test Event.

Without an active Meta platform here, no event goes to Meta.

3. Set up CTWA

Open Connection › Numbers & CTWA.

1. On the row of the ad number, click Set up CTWA.
2. Enter the WhatsApp Business Account ID (WABA ID).
3. Choose Connect your Meta account, then Log in with Meta.
4. Click Check connection. The status must be CTWA configured.

4. Set the Conversion Settings

Open Tracking & Ads › Conversions. Only the workspace owner can save.

Click Save changes.

5. Agree on the meaning of each status

Copy the status table above into the team group. Set one closing point and one way to enter the Closing value.

Change the status to Purchase from the Leads page, or from Lead stage in the contact panel of the Inbox. Both ask for the Closing value.

6. Prepare the Inbox for long follow-up

• Ask an owner or admin to create labels for waiting stages, for example Menunggu keluarga.
• Set the SLA threshold to the reply target of your team.
• Save frequent messages in Conversations › Quick Replies.
• Submit message templates so CS can write after the 24-hour window.

7. Add an Automation Rule

Open Conversations › Automation Rules, then Create rule.

Rule: ready to register becomes Hot

• Action: Change Lead Status, status Hot.
• Condition: Message · Contains · the phrases from the template below.
• Condition: Sender Type · Customer (incoming).
• Condition: Lead Status · Not In List · Hot, Invoice Sent, Purchase, Lost.

Do not add an automatic rule for Lost. A pilgrim who writes "batal" (cancel) sometimes only asks about the cancellation rules. Let CS confirm first, then choose Lost by hand.

8. Set up the CS split

For ads to a landing page, open Links & Domains › WhatsApp Links, create a link, then add the CS numbers with Distribution Weight. For Click-to-WhatsApp ads, set the Assignee in the Inbox.

9. Test before a large campaign

• In Website Tracking, check that Meta receives the Test Event.
• In Numbers & CTWA, check that the CTWA status is configured.
• When the first deposit arrives, open Conversions › Delivery log. Purchase must show Sent.

Do not mark a test chat as Purchase. That sends a fake Purchase to Meta, and it cannot go out again for the same lead. Mark test chats as Lost.

Which templates and rules are ready to use?

Replace the text in curly braces with the data of your travel agency. All texts below are neutral, with no promise about departure, seats, or price.

The rule phrases stay in Indonesian because pilgrims write in Indonesian. In English they read: we want to register, I want to register, please send the registration form, I want to come to the office, ready to pay the deposit, deposit already transferred.

How does lead data last through a long cycle?

Lead and message data stays as long as your plan allows, then is deleted automatically after the limit.

As of 14 October 2026, the Data retention policy gives the limit for Leads, contacts, and Inbox messages and notes: 30 days on Trial, 360 days on Starter, 720 days on Pro, and 1400 days on Enterprise. Read that page for the latest numbers.

This limit matters for a long cycle. A lead that passes the plan limit loses its chat history and notes, including the markers that link it to an ad.

Three steps protect you.

• Match your plan to the age of your cycle. Count how long a pilgrim usually stays on the follow-up list.
• Export on a schedule. On the Leads page, click Export. Only the workspace Owner can export.
• Keep key decisions in the registration system of your agency. Konektor.id is a tracking and conversation tool, not a registration archive.

What should you check about licenses, ads, and pilgrim data?

This list is a reminder, not legal or religious advice.

• Organizer license. Konektor.id does not check the license of your agency. Check licenses and organizer rules with the official authority, and make sure your license is active before you advertise.
• Meta ad policy. Ads must not assert or imply personal attributes of the viewer, including religion and beliefs (Meta Transparency Center, checked on 14 October 2026). Avoid wording that addresses the viewer as a person of a given religion. Write the package only. Also read the Meta Advertising Standards before you run ads.
• Promises. Do not promise a departure date, seats, or the result of document processing that is not certain, in ads or in Quick Replies.
• Price. The price and facilities in the ad, in CS messages, and in the contract must match.
• Pilgrim money. Give the account and payment steps through the official channel of your agency. Konektor.id does not read transfer proof, so CS checks the payment and changes the status by hand.
• Personal documents. Do not ask for a passport or ID photo through an ad form. Ask through the official registration channel of your agency.
• Data to the ad platform. Konektor.id sends the event name, value, time, ad data from the chat, and hashed identity, for example the WhatsApp number. The conversation content is not sent.
• QR scan. This route reads ad data in an unofficial way and can break Meta terms. Use an official connection for daily work.

How much does an ad cost for each pilgrim deposit?

The cost depends on the cost per chat, the share of chats that end in a deposit, and the ad budget.

The calculator below starts at zero, because this page gives no cost or result numbers. Fill it with numbers from Ads Manager or Ad Spend, then take the chat count and the Purchase count from Konektor.id. Because the hajj cycle is long, use a period long enough that late deposits count too.

Compare the cost for each Purchase with your margin for one pilgrim. A cost close to your margin means the ad or the way your team follows up needs work first.

When do results start to show, and when should you raise the budget?

The first events show on day one, but Purchase follows the speed of the pilgrim's decision.

• Day one. Setup is done. Meta receives the Test Event, and the CTWA status is configured.
• The first weeks. Leads are recorded for each ad, and the team gets used to changing statuses. LeadSubmitted and QualifiedLead start to show in the Delivery log.
• After that. The first Purchase appears when the first deposit arrives. The timing follows your cycle, not a Konektor.id schedule.

Do not judge the ads from the first week. Do not promise numbers to your team or your manager.

Raise the budget when all of this is true

1. The team changes statuses with discipline, and the Active tab in Leads is tidy.
2. The Delivery log shows Purchase as Sent, with no failures.
3. Deposits come from the same ad again and again, not once.
4. The cost for each deposit pilgrim is still safe against your margin.
5. The team can keep up. The Unreplied view does not pile up.

Raise the budget in steps, and do not change many things at once. Prepare your CS team and templates before the budget goes up.

Hold off if

• The cost per chat falls, but Purchase does not rise.
• The Unreplied or Reply due soon view keeps growing.
• The team changed the Purchase definition midway.

Which numbers should you watch in Konektor.id?

Watch the cost for each deposit pilgrim first. The other numbers explain why that cost rises or falls.