# How to use Template Website Button Clicked Webhook in DoubleTick

You send a promotional WhatsApp template to 2,000 customers. The message looks great. The website button is right there. But two days later, when your marketing manager asks how many people actually clicked the link — and who they were — you have no answer. You know the message was delivered. You know some people opened it. But the click? That data never made it anywhere useful.

Now imagine a different scenario: The moment any customer clicks the website button in your template, your CRM is updated with their name, their phone number, their location, the exact time they clicked, and the assigned agent for that customer — all automatically, with no manual work from anyone on your team.

That is what the **Template Website Button Clicked Webhook** does.

***

#### <mark style="color:$primary;">**What Is the Template Website Button Clicked Webhook?**</mark>

In DoubleTick, template messages can include a website button — a clickable button that takes the customer to a URL when tapped. The **Template Website Button Clicked** webhook fires the moment any customer taps that button in any template message.

This is not a delivery confirmation or a read receipt. This is a click event — meaning the customer did not just receive the message and did not just open it. They actively engaged with it by clicking the button. That is a significantly stronger signal of intent.

Think of it like a heat map for your WhatsApp campaigns. Instead of guessing who engaged with your message, you know exactly who clicked, at what time, from which city, and on which template — all captured automatically the moment it happens.

***

#### <mark style="color:$primary;">**When Does This Webhook Trigger?**</mark>

This webhook activates when:

* A customer receives a template message sent through DoubleTick that contains a website button
* The customer taps that website button

It fires for every click — so if the same customer clicks the button more than once, each click is captured as a separate event.

***

### <mark style="color:$primary;">**Step-by-Step Setup Guide**</mark>

<figure><img src="https://2303112206-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F53n17VnOICC1LtDqlENV%2Fuploads%2FKVc0mxdnC6tJ5qeWyyfe%2FUntitled%20design%20-%202026-03-31T120306.393.gif?alt=media&#x26;token=2878afea-2fb5-4092-a0eb-ad0d8a5d8056" alt=""><figcaption></figcaption></figure>

#### <mark style="color:$primary;">**Step 1: Open Webhooks in DoubleTick**</mark>

1. Log in to your DoubleTick account
2. Go to **Settings**
3. Click on **Webhooksx**

#### <mark style="color:$primary;">**Step 2: Create a New Webhook**</mark>

1. Click **New Webhook**
2. Give it a clear name — for example: `Template Link Click Tracker`

#### <mark style="color:$primary;">**Step 3: Get Your Webhook URL**</mark>

You need a destination URL — this is where DoubleTick will send the click data the moment a customer taps the button.

You can connect it to:

* A **CRM** like Zoho, HubSpot, or Salesforce
* An **automation tool** like Zapier or Pabbly
* A **spreadsheet** like Google Sheets
* Your own **backend or internal analytics dashboard**

**For testing purposes**, you can use DoubleTick's **Bot Studio** to capture and preview the data first:

1. Open a new tab and go to **Bot Studio**
2. Click **Create New Bot**
3. Set the trigger to **On Webhook**
4. **Copy the webhook URL** that appears

#### <mark style="color:$primary;">**Step 4: Fill in Webhook Details**</mark>

1. Go back to the **Webhooks** page
2. Paste the webhook URL
3. Select your **API Number** (your WABA/WhatsApp Business number)
4. Click **Continue**

#### <mark style="color:$primary;">**Step 5: Choose the Event**</mark>

1. Select **Template Website Button Clicked** from the event list
2. Click **Create Webhook**

Your webhook is now live and tracking every button click the moment it happens.

***

#### <mark style="color:$primary;">**How to Test It**</mark>

1. Send a template message that contains a website button to a test customer number
2. On that test number, tap the website button in the message
3. Go to **Bot Studio → Capture Response → View Response Data**

You will see all the click data captured at the exact moment the button was tapped.

***

#### <mark style="color:$primary;">**What Data Do You Receive?**</mark>

When this webhook fires, it sends the following information to your system:

| Field               | What It Tells You                                        |
| ------------------- | -------------------------------------------------------- |
| Short Link ID       | The unique identifier of the short link that was clicked |
| IP Address          | The IP address of the device that clicked the link       |
| City                | The city the customer was in when they clicked           |
| State               | The state the customer was in when they clicked          |
| Country             | The country the customer was in when they clicked        |
| Exact URL           | The actual URL the customer was taken to after clicking  |
| Timezone            | The timezone of the customer's location                  |
| Visited At          | The exact date and time the button was clicked           |
| Target URL          | The template URL pattern used in the button              |
| Template ID         | The unique ID of the template that contained the button  |
| WABA Number         | Which WhatsApp Business number sent the template         |
| Customer Name       | The name saved for this customer in DoubleTick           |
| Template Name       | The name of the template that was clicked                |
| Customer Phone      | The customer's WhatsApp number                           |
| Assigned User Phone | The phone number of the agent assigned to this customer  |

The combination of **location data**, **exact timestamp**, **customer identity**, and **assigned agent phone** makes this one of the richest webhook payloads available in DoubleTick. You know not just that someone clicked — you know who, where, when, and which agent is responsible for that customer.

***

#### <mark style="color:$primary;">**Template Website Button Clicked Webhook – Sample Payload**</mark>

{% code expandable="true" %}

```json
{
  "shortLink": {
    "id": "XyZ12Ab",
    "ip": "49.36.128.210",
    "lat": 19.0760,
    "lon": 72.8777,
    "city": "Mumbai",
    "state": "Maharashtra",
    "country": "India",
    "exactUrl": "https://exampletravel.com",
    "timezone": "Asia/Kolkata",
    "visitedAt": "2026-04-01T14:20:15.456Z"
  },
  "targetUrl": "https://exampletravel.com",
  "templateId": 2056789,
  "wabaNumber": "919845672310",
  "customerName": "Rahul Mehta",
  "templateName": "travel_offer_v1",
  "customerPhone": "919876123456",
  "assignedUserPhone": "919812345678"
}
```

{% endcode %}

***

#### <mark style="color:$primary;">**Real-Life Business Use Case: A Real Estate Developer Using Button Clicks to Trigger Hyper-Targeted, Location-Based Follow-Up in Real Time**</mark>

**The Situation**

A real estate developer is running a WhatsApp campaign for the launch of a new residential project in the outskirts of Mumbai. They send a template message to 5,000 prospects on their database. The message describes the project briefly and includes a website button that says "View Project Details" — which takes the customer to the project microsite showing floor plans, pricing, amenities, and a contact form.

The developer has a team of 12 sales agents, each assigned to a specific geographic territory. Prospects from Thane are assigned to one agent, prospects from Navi Mumbai to another, prospects from South Mumbai to a third, and so on. The assignment is based on the assumption that a prospect who lives closer to the project is a higher-priority lead — they are more likely to attend a site visit and more likely to convert.

**The Problem**

The campaign was sent and the microsite started receiving traffic. But the sales team had no way to connect website visits back to specific WhatsApp contacts. The microsite analytics showed 340 visits from the campaign link, but it could not identify who those visitors were by name or phone number. The sales team could not follow up with people who had shown interest because they did not know who had clicked.

Additionally, the geographic assignment of leads was being done manually at the start — based on addresses collected during lead generation, which were often incomplete or outdated. By the time a prospect clicked the link, they might actually be living in a different area than what was on record — but no one knew because location was never captured at the point of engagement.

Assigned agents were making follow-up calls to their entire list of contacts regardless of who had actually shown interest, wasting time on low-intent contacts while high-intent clickers — people who had actually visited the microsite — were not being prioritised.

**How the Template Website Button Clicked Webhook Solves This**

The developer connects this webhook directly to their CRM.

The moment any prospect clicks the website button in the template, the webhook fires and the CRM is automatically updated with a high-intent activity entry on that prospect's record — including their name, phone number, the exact time they clicked, and their location at the time of the click captured from the city, state, and latitude and longitude fields.

The CRM is configured to immediately update the prospect's lead score when a click event is logged — moving them from a standard lead to a hot lead automatically.

Simultaneously, because the assigned user phone field is included in the webhook data, the CRM triggers an instant task for the assigned agent — notifying them on WhatsApp that their assigned prospect has just clicked the project link, along with the prospect's name, phone number, and the city they were in when they clicked.

The agent receives this notification within seconds of the click. They call the prospect while they are still on the microsite — or within minutes of having looked at it — striking while interest is at its absolute peak.

The location data from the click serves a second purpose. If a prospect's recorded address says Pune but their click location shows Mumbai, the CRM flags this discrepancy and the lead is reassigned to the Mumbai territory agent. Lead assignments are automatically corrected based on real engagement location, not stale registration data.

For prospects who click the button multiple times — indicating repeated visits to the microsite — each click is logged separately and the CRM escalates their priority level further, flagging them for a senior sales manager to personally follow up.

**The Result**

* Agents receive an instant, real-time alert the moment their assigned prospect clicks the template link — enabling follow-up calls while interest is at its highest
* Hot leads are automatically separated from cold ones based on actual click behaviour, not assumptions — agents spend their time on prospects who have demonstrated genuine intent
* Lead assignments are continuously corrected using real click location data, ensuring the right agent always handles the right territory
* The marketing team has a precise, named list of every prospect who clicked — not just an anonymous traffic count — enabling them to measure campaign effectiveness at the individual level
* Prospects who click multiple times are automatically escalated to senior agents, ensuring the most interested leads receive the most senior attention
* The developer's conversion rate on the campaign improves significantly because follow-up is faster, more targeted, and better informed than any previous campaign

***

#### <mark style="color:$primary;">**Summary**</mark>

The Template Website Button Clicked Webhook is one of the most powerful intent signals available in DoubleTick. A customer who clicks a button in your template has moved beyond passive reception — they have actively engaged. This webhook captures that moment with exceptional richness: who clicked, where they were, what time it was, and which agent is responsible for them. For any business running WhatsApp campaigns where the goal is to convert interest into action, this webhook is the difference between guessing who is interested and knowing it — in real time.

Set it up once, and every button click becomes an immediately actionable lead signal your team can act on before the moment passes.