> 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/settings/custom-events-guide/how-to-use-custom-events-in-bot-studio-and-track-them-in-enterprise-analytics.md).

# How to use Custom Events in Bot studio and track them in Enterprise Analytics

Learn how to trigger custom events in Bot Studio and analyze them in Enterprise Analytics.

Once you've created your Custom Events, the next step is to use them in your bot flow. This allows DoubleTick to record important milestones during a customer conversation, which you can later analyze in Enterprise Analytics.

### <mark style="color:$primary;">**Why this is useful**</mark>

Adding Custom Events to your bot helps you connect conversations with business outcomes.

Instead of only knowing that a customer interacted with your bot, you can track important actions such as:

* A lead being qualified
* A demo being booked
* An order being placed
* A form being submitted
* A payment being completed

These events can then be used in Funnel Analytics to understand how customers move through your journey.

***

### <mark style="color:$primary;">**Adding Custom Events in Bot Studio**</mark>

Custom Events should be added at the exact point in your bot flow where an important action is completed.

For example, if your bot qualifies a lead after collecting all the required details, you can trigger the **Lead Qualified** event immediately after the qualification step.

<figure><img src="https://2303112206-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F53n17VnOICC1LtDqlENV%2Fuploads%2FVDb6K05pkV0RJ6HXvkpY%2FUntitled%20design%20-%202026-07-24T171904.413.gif?alt=media&amp;token=ec88655c-7549-42ba-a1b8-0773f8abfbbd" alt=""><figcaption></figcaption></figure>

1. Open **Bot Studio** and edit your bot.
2. Navigate to the flow where you want to track an important milestone.
3. Click the **+** button between two components where you want the event to be recorded.
4. Select the **Custom Event** component.
5. Choose the event you want to trigger.
6. Save and publish your bot.

Whenever a customer reaches that step in the conversation, DoubleTick will automatically record the event.

Let's say your real estate bot follows this journey:

* Customer shares basic details (Name, Email, City)

  **Trigger event:** Lead Captured
* Customer shares property requirements and matches your qualification criteria

  **Trigger event:** Lead Qualified
* Customer books a property visit

  **Trigger event:** Site Visit Booked
* Customer completes the property visit

  **Trigger event:** Site Visit Done

By placing the appropriate Custom Event at each milestone, you can track the customer's journey from the first enquiry to the completed site visit.

***

### <mark style="color:$primary;">**How to Track Custom Events in Enterprise Analytics**</mark>

<figure><img src="https://2303112206-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F53n17VnOICC1LtDqlENV%2Fuploads%2FYOMxF2gZP2wPN10Jdx97%2Fimage.png?alt=media&amp;token=78c58072-bbad-4cc6-a90e-776834f81212" alt=""><figcaption></figcaption></figure>

Once your bot starts triggering Custom Events, you can analyze them using **Funnel Reports**.

Go to:

**Enterprise Analytics → Reports → Funnel Report**

Select the Custom Events you want to analyze in your funnel.

For example:

1. Lead Captured
2. Lead Qualified
3. Site Visit Booked
4. Site Visit Done

DoubleTick will automatically build a funnel showing how customers moved from one stage to the next.

***

### <mark style="color:$primary;">**What you'll see**</mark>

<figure><img src="https://2303112206-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F53n17VnOICC1LtDqlENV%2Fuploads%2FJ7RHgRn2F2KTQeWUcSeO%2Fimage.png?alt=media&amp;token=a8b8cf55-a0a8-4703-9a76-458369f0771d" alt=""><figcaption></figcaption></figure>

The Funnel Report helps you understand your conversion at every stage.

For example:

* Lead Captured → Lead Qualified
* Lead Qualified → Site Visit Booked
* Site Visit Booked → Site Visit Done

You'll also see the overall conversion from the **first event to the last event**, helping you understand how many captured leads completed the entire journey.

### <mark style="color:$primary;">**View the Leads Behind the Numbers**</mark>

Every number in the Funnel Report is **clickable**.

Click on any stage in the funnel to open a detailed list of conversations where that event was triggered. This makes it easy to identify which leads reached a particular stage and investigate individual customer journeys if needed.

***

Custom Events become truly valuable when they're added to your bot flow. By placing them at important milestones, you can accurately track your customer journey and measure conversion rates using Funnel Reports in Enterprise Analytics. This helps you understand where customers move forward, where they drop off, and where your process can be improved.


---

# 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/settings/custom-events-guide/how-to-use-custom-events-in-bot-studio-and-track-them-in-enterprise-analytics.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.