> For the complete documentation index, see [llms.txt](https://learn.doubletick.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.doubletick.io/troubleshoot-errors/why-do-i-see-a-difference-between-meta-ad-clicks-and-chats-initiated-on-doubletick.md).

# Why Do I See a Difference Between META Ad Clicks and Chats Initiated on DoubleTick?

When running Click-to-WhatsApp ads, it’s common to notice that the number of clicks reported by META (Facebook Ads Manager) is **higher** than the number of chats initiated as reported by DoubleTick (DT). This is expected and normal.

#### ✅ **How It Works**

* **META reports:** *Clicks on your Click-to-WhatsApp ad*
* **DoubleTick reports:** *Actual chats initiated by users on WhatsApp after clicking the ad*

#### **Why the Difference?**

Not everyone who clicks the ad will complete the action of sending a message. For example:

* Some users may click the ad but drop off before sending a message.
* Some may accidentally click the ad and close WhatsApp immediately.
* Some may open the chat but never type anything.

#### **Example**

**Ad Clicks Reported by META:** `500`\
**Chats Initiated Reported by DoubleTick:** `320`

➡️ In this case, 180 users clicked but did not send a message on WhatsApp.

A difference between META’s reported clicks and the chats you see in DoubleTick does **not** mean there’s an issue — it simply shows user drop-off between the ad click and actually starting a conversation.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://learn.doubletick.io/troubleshoot-errors/why-do-i-see-a-difference-between-meta-ad-clicks-and-chats-initiated-on-doubletick.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.