Overview

Often, a single event is not specific enough to represent a behavior. For example, to track signups from an app, a pageview or button click isn't enough. You need a valid signup submission where the user has properties showing they came from the specific app.

Also, multiple events might represent the same behavior. For example, "trying a feature" could include visiting its page, enabling it, or generating a related backend event.

Events are a collection of raw events fitting event types and filters that represent a single behavior. They are created using a combination of auotracked or custom events along with filters. They can then be further used in segments, journeys, experiments, reports, and playbooks.

The Events object can be accessed under the Audiences section. From the Events page you can:

• Access the list of created events
• Access the event itself
• Search for the created event
• Filter the events
• Create new events
• Edit created events names'
• Delete the created events
• Duplicate the created events
  

📘

Important

Events are retroactive, meaning they also apply to past events, not only events that happen after the event was created.

Types of Events

Autotracked

Autotracked actions are based on frontend elements from your website or iOS app, such as a button or an input. You can also set them manually if you wish by providing something to identify the element, like a selector.

Our autotrack functionality captures a lot of frontend elements by default, but you'll need to manually set anything else you want to be captured.

Currently, autotrack captures any click or change of input or submission of a, button, form, input, select, textarea, and label tags. All other elements need to be set manually. This is important to note if you deviate from established HTML practices, such as using a div as a button.

There are three ways to match your elements:

1. Text: The text on the element, if applicable. If you have buttons across your site, all saying ‘Sign Up’, you can track ALL of them, site-wide, as the same action, by choosing Text: "Sign Up" and not matching the URL.

2. Page URL: The URL where this action needs to take place. If you choose to match the URL as well, it will track any button on that page if it contains the ‘Sign Up’ text (which could be more than one button).

3. Matching selectors: details below.

   1. ID selectors. Example: #speciallink will match elements with ID "speciallink".
   2. Class selectors. Example: .importantlink will match elements with CSS class "importantlink".
   3. Type selectors. Example: input will match any elements.

Custom even collection

Custom collections allow you to bring specific customer data into your event collections. Custom events are not auto-created so you need to specifically define and pass each custom event parameter and their collections from your sources.

Depending on the type of business, these events could be anything like:

• Purchase
• Subscribed to Newsletter
• Checkout Started / Checkout Completed
• Review Submitted

You can refer to how to create a custom event collection in the Collections section.