> This page is for version Scripted.
> For other versions, use one of these documentation indexes:
> - Generative (default): https://developers.ada.cx/generative/llms.txt
> - Scripted: https://developers.ada.cx/scripted/llms.txt

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://developers.ada.cx/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://developers.ada.cx/_mcp/server.

# Create and track chatter actions

## Overview\[#UUID-50f844b1-939e-6296-8a94-3f873f4170e6_id_1500004098482_id_h_01FN4XFBWPECRHJDZ7REKS6YRJ]

With Events, you can measure how often Ada helps your customers succeed
by tracking actions on your website, both inside and outside of their
conversations with your bot.

> **Note**
>
> This feature may not be included with your organization's subscription
> package. For more information, see Ada's
> [Pricing](https://www.ada.cx/pricing) page, or contact your Ada team.

Tracking Events is helpful for a variety of use cases, such as:

* When customers complete a checkout

* When customers complete onboarding flows

* When customers complete a return

* When customers complete a specific action

* When customers click a link from your bot

* When prospective customers book a demo request

These are just a few examples, but you can use Events to track any
customer interaction you wish.

## Create an Event\[#UUID-50f844b1-939e-6296-8a94-3f873f4170e6_id_1500004098482_id_h_01F0Y9255971JE7S4MH5554H2N]

Before you can track an Event, you need to create one using the Events
Manager.

1. On the Ada dashboard, go to **Measure Events**.

2. Click **New Event**. The Create a new event dialog appears.

3. In the **Display Name** field, enter a name for the Event.

   > **Note**
   >
   > The Event Key generates automatically based on the name you enter.
   > If you like, you can change it to something more memorable or
   > specific. Event keys are never shown to chatters.

4. Enter a description in the **Description** field. This helps you
   remember what the Event tracks.

![](/_fern-files/_img/27e76e50a339eec564a15d98e4b8061963eb44cf8db80b855fd0d7dbe09b192a.webp)

## Track an Event\[#UUID-50f844b1-939e-6296-8a94-3f873f4170e6_id_1500004098482_id_h_01F0Y92E6Y4KKPX6VF2GEP3NGQ]

Events are only tracked for users who trigger them after receiving a
message from your bot. A bot message can be either a Proactive Campaign
or a greeting message displayed when a user opens your bot. No Events
are logged for a user if they visit your website, but never receive a
message from your bot. This is to ensure that tracked Events includes
only data from actual chatbot users.

There are four ways to track an Event:

* [**In Answers**](/scripted/docs/measure-success/plan-and-collect-feedback/create-and-track-chatter-actions#UUID-50f844b1-939e-6296-8a94-3f873f4170e6_id_1500004098482_id_h_01FB61FXVXDN8NF6XBTVTDBWHC)
  — Using the Track Event block.

* [**URL Conditions**](/scripted/docs/measure-success/plan-and-collect-feedback/create-and-track-chatter-actions#UUID-50f844b1-939e-6296-8a94-3f873f4170e6_id_1500004098482_id_h_01FB61G8Z1YSFVFRVZXN05VTZM)
  — When users visit specific URLs on your website.

* [**In Blocks**](/scripted/docs/measure-success/plan-and-collect-feedback/create-and-track-chatter-actions#UUID-50f844b1-939e-6296-8a94-3f873f4170e6_id_1500004098482_id_h_01FB63X7J29YT1DECQGVYW6NC8)
  — Directly in handoff blocks and other select Answer blocks.

* [**With Code**](/scripted/docs/measure-success/plan-and-collect-feedback/create-and-track-chatter-actions#UUID-50f844b1-939e-6296-8a94-3f873f4170e6_id_1500004098482_id_h_01FB61YSCPSD3YW2FCD763RHBN)
  — Using Ada’s Embed2 JavaScript API.

### Track Events with the Track Event block\[#UUID-50f844b1-939e-6296-8a94-3f873f4170e6_id_1500004098482_id_h_01FB61FXVXDN8NF6XBTVTDBWHC]

With the Track Event block, you can track Events that occur in
conversations in your bot.

To use the Track Event block:

1. Drag the Track Event block into any Answer.

2. Position the Track Event block immediately after where the Event
   takes place.

3. In the **Event** drop-down, click **select or create an Event.**

4. When a chatter reaches the Track Event block in the conversation,
   the Event is tracked. The block will not affect the chatter’s
   experience—Events are invisible to chatters.

5. You can also assign a monetary value to an Event, either through a
   fixed value or using a numeric variable. Read [Save chatter information using the Capture block](/scripted/docs/build-and-maintain-your-bot/work-with-blocks-and-apps/save-chatter-information-using-the-capture-block)
   and [Get started with variables](/scripted/docs/build-and-maintain-your-bot/personalize-conversations/get-started-with-variables)
   to learn more about variables.

### Track Events using URL Conditions\[#UUID-50f844b1-939e-6296-8a94-3f873f4170e6_id_1500004098482_id_h_01FB61G8Z1YSFVFRVZXN05VTZM]

You can track Events by defining them based on visits to a specific URL
on your website. This is useful when the desired action occurs on your
website, outside of the chat. You can also assign a monetary value to
the Event.

For example, let's say you want to track when users successfully
complete a checkout after chatting with your bot. Add a URL Condition to
your Event that tracks when your chatters land on the URL ending with
**checkout-confirmation**.

> **Info**
>
> You must deploy [Ada’s Embed2 script](https://developers.ada.cx/reference/embed2-reference#trackevent)
> on the individual webpages associated with your URL Conditions. If a
> tracked URL's webpage does not include the Embed2 script, an Event won't
> be counted when your chatter lands on that page. If you don't want your
> bot to appear on a webpage where you'd like to track an Event, deploy
> the Embed2 script in Lazy Mode on that page.

#### URL Conditions and Persistence settings\[#UUID-50f844b1-939e-6296-8a94-3f873f4170e6_id_1500004098482_id_h_01FN4XGKD5WFXJRYPQFNHSRNX3]

Your bot’s [persistence settings](/scripted/docs/build-and-maintain-your-bot/personalize-conversations/manage-when-your-bot-forgets-customers)
may impact whether or not an Event is tracked on a URL.

* **Never Forget** – As long as a chatter doesn't clear their browser
  cookies, your bot's "memory" of them persists. This is true even if
  they close their browser. Because of this, a chatter can complete an
  Event at any point in time after they have received a message from
  your bot. This could be hours, days, or even weeks later.

* **Forget After Tab Close** – The Event is tracked if the user
  completes it prior to closing their browser tab. Once they close their
  tab, the bot's "memory" of the chatter is erased. Because of this,
  they won't be tracked if they return to that webpage and complete an
  Event without first receiving a new message from your bot.

* **Forget After Reload** – The Event is tracked if the user completes
  it prior to refreshing the webpage or closing the browser tab.

#### Configure URL Conditions\[#UUID-50f844b1-939e-6296-8a94-3f873f4170e6_id_1500004098482_id_h_01FN4XGS65DC5BHVFYZC0TE478]

1. Navigate to **Measure** > **Events** and select the Event you wish
   to track. Alternatively, create a new Event.

2. In the **URL Conditions** section, configure the URLs you wish to
   map to this Event. You can choose whether to include an exact URL,
   or what the URL contains, ends with, or a regular expression.

   <table>
     <thead>
       <tr>
         <th>
           Option
         </th>

         <th>
           Definition
         </th>

         <th>
           Example
         </th>
       </tr>
     </thead>

     <tbody>
       <tr>
         <td>
           **Exactly Matches**
         </td>

         <td>
           Looks for an exact URL match.

           Query parameters are not part of the matching logic.
         </td>

         <td>
           Specifying `https://www.example.com/checkout` in
           the configuration matches to:

           `https://www.example.com/checkout/`

           or

           `https://www.example.com/checkout?q=hello`
         </td>
       </tr>

       <tr>
         <td>
           **Contains**
         </td>

         <td>
           Matches to URLs and query parameters containing the string you
           specify.
         </td>

         <td>
           Specifying `example` in the configuration could
           match to:

           `https://www.hello.com?q=example`

           or

           `https://www.example.com/checkout`
         </td>
       </tr>

       <tr>
         <td>
           **Ends With**
         </td>

         <td>
           Matches to URLs ending with your specified string.

           Query parameters are ignored.
         </td>

         <td>
           Specifying `/checkout` in the configuration
           matches to `https://www.hello.com/checkout?q=example`

           and

           `https://www.example.com/checkout`
         </td>
       </tr>

       <tr>
         <td>
           **Regular Expression**
         </td>

         <td>
           Use the [regular expression pattern matching language](https://regex101.com/) to match characters or character
           combinations in a URL, including query parameters.
         </td>

         <td>
           Specifying `product[0-8]+[^9]*$` matches any page
           that includes the string ‘product’ and any number of any length
           afterwards, as long as the number 9 never appears.
         </td>
       </tr>
     </tbody>
   </table>

3. You can assign monetary value to Events tracked via URLs, as well.
   This can only be a fixed value, and is not related to the value(s)
   you might have entered in Track Event blocks.

![](/_fern-files/_img/285531cdd74f80d3f60fe89e5448f2cde0d2e6b5e5da06c6d9fa2cfc816a4e6b.webp)

### Track Events within Blocks\[#UUID-50f844b1-939e-6296-8a94-3f873f4170e6_id_1500004098482_id_h_01FB63X7J29YT1DECQGVYW6NC8]

You can track Events directly in Event trackable blocks, including:

* **Handoff blocks** – Track handoffs initiated by any of Ada's handoff
  blocks.

* **HTTP Request block** – Track successful HTTP Requests from your bot.

* **Link block** – Track link clicks in the Ada chat window.

#### Track Events in Event trackable blocks\[#UUID-50f844b1-939e-6296-8a94-3f873f4170e6_id_1500004098482_id_h_01FN4XJGDB03CKAA7CQ2CWH8WY]

1. Add an Event trackable block to an Answer, and configure it as
   normal.

2. At the bottom of the block, click the **Track Event** drop-down
   menu.

3. Select the Event to log when the block triggers.

4. Click **Save**.

The Event you assigned to the block will track each time this instance
of the block triggers during a conversation.

> **Note**
>
> You add Events to blocks on an individual basis. This means that even if
> you add more than one version of the same block to your bot, those
> versions won't affect the Event data unless they are also each assigned
> the same Event.

#### Track Events in handoff blocks\[#UUID-50f844b1-939e-6296-8a94-3f873f4170e6_id_1500004098482_id_h_01FN4XK0XPPDWKA819GKJ7GGE6]

An Event titled *Handoff* exists by default in the Events view of the
Ada dashboard. You should use this Event when you want to track live
agent escalations and you want those escalations to count against your
containment rate. Handoffs are considered *not contained*.

![](/_fern-files/_img/2cbdd6ef35a3fbed5769e3e032ad78e3586ec45e4bd6a23442fba6967512a923.webp)

When you add a handoff block to an Answer, the Track Event drop-down
menu comes preset to this default Event. You can change this to a
different Event, or remove the Event entirely from the block by clicking
the trash can icon.

### Track Events with the Ada Embed2 JavaScript API\[#UUID-50f844b1-939e-6296-8a94-3f873f4170e6_id_1500004098482_id_h_01FB61YSCPSD3YW2FCD763RHBN]

You can track more complex user actions that occur on your website with
the **trackEvent** method in Ada’s Embed2 Javascript API.

Track Events programmatically with Ada’s Embed2 JavaScript API:

```
window.adaEmbed.trackEvent("<event_key>", <monetary value as number>)
```

\***Example:** *To track an event when a meeting is booked on your
website, and assign it a value of \$500:*

```
window.adaEmbed.trackEvent("book_meeting", 500)
```

## Events Reporting\[#UUID-50f844b1-939e-6296-8a94-3f873f4170e6_id_1500004098482_id_h_01F0Y92MBFK86D7N48JV9F8296]

Events reporting gives you an overview of all Events tracked during a
selected timeframe.

1. Navigate to **Measure Reports**.

2. Select the **Events Overview** report.

   The metrics include:

   * **Total Count:** The number of times the event was recorded. This
     includes events that occur multiple times from the same user.

   * **Total Value:** The total monetary value of the event.

   ![](/_fern-files/_img/f85158fbbf0aa1b972daaa890bf4dff8851aa427d7e4361f3a3c89bb6e5e7ebf.webp)

3. You can click on the individual event names in the **Event Name**
   column to see specific metrics for each Event.

4. The individual Event report shows Total Count and Total Value in a
   chart, which illustrates performance over time. You can toggle
   between the two metrics using the selector on top right.

## Archive Events\[#UUID-50f844b1-939e-6296-8a94-3f873f4170e6_id_1500004098482_id_h_01F3XA629NRR70D5KHRHSW51PC]

To archive an Event, click into the Event you'd like to archive, and in
the upper-right, click **More Options** > **Archive Event**. Archived
Events cannot be unarchived, and reporting will still be available for
archived events.

---

Have any questions? Contact your Ada team, or email us at [](<mailto:help@ada.support%20%E2%80%9CHelp Docs inquiry%E2%80%9D>).