> ## Documentation Index
> Fetch the complete documentation index at: https://help.getvero.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Events overview

> Track customer actions to trigger campaigns and build segments in Vero.

Events are actions that customers take in your product or on your website. They form the foundation of behavioral messaging in Vero, allowing you to trigger campaigns and build segments based on what your customers actually do.

<Card title="Setting up event tracking" icon="code" href="/vero-2/events/setting-up-event-tracking">
  Learn how to install Vero's tracking library and start capturing events.
</Card>

## What is an event?

An event represents a specific action a customer takes, such as:

* Signing up for an account
* Viewing a product
* Making a purchase
* Completing onboarding
* Clicking a button

Each event can include **event properties** that provide additional context. For example, a `Viewed product` event might include properties like `product_name`, `product_price`, and `product_category`.

## Reserved events

Vero includes two reserved system events that are tracked automatically:

* **Identified** - Recorded when a user is identified via the API
* **Visited site** - Recorded when a user visits your website (if pageview tracking is enabled)

Reserved events are marked with a lock icon in the events list and cannot be renamed or deleted.

## Viewing your events

Navigate to **Data > Events** in the sidebar to view all events tracked to your Vero account.

### Events list

The events list displays:

* **Event name** - The name of each event tracked to Vero
* **Event type** - Custom events and reserved events are distinguished by different icons
* **Campaigns** - The number of campaigns using the event as a trigger
* **Last seen** - When the event was most recently tracked

Use the search field to filter events by name. The total count of events is displayed at the top of the page.

### Event details

Click on any event row to open the detail panel, which shows:

* **Event name and type** - Including a reserved label for system events
* **Description** - Add your own description to help identify the event's purpose
* **Recent occurrences** - A list of the most recent times this event was triggered, including the date and a link to the user profile
* **Properties** - The event properties included with the most recent occurrence
* **Campaigns** - All campaigns configured to trigger when this event occurs, along with their status (live, paused, draft)

## Tracking events

Events are tracked to Vero using the Track API or through supported integrations like Segment or Rudderstack.

```javascript theme={null}
// Example: Track an event using the JavaScript library
_vero.track('Viewed product', {
  product_name: 'Red T-shirt',
  product_price: 29.99,
  product_category: 'Apparel'
});
```

See the [Track API reference](/api-reference/events/track) for complete documentation on tracking events.

## Using events

Once tracked, events can be used to:

* **Trigger campaigns** - Start a broadcast or journey when a customer performs a specific action. See [Event triggers](/vero-2/campaigns/journeys/event-trigger).
* **Build segments** - Create dynamic segments based on whether customers have or haven't performed certain events. See [Segment conditions](/vero-2/segments/segment-conditions).
* **Personalize content** - Use event properties in your messages with Liquid. See [How to personalize your message using Liquid](/vero-2/message-content/how-to-personalise-your-message-using-liquid).