Events are actions users perform in your messages or on your website, such as:
|
|
Tracking these actions gives you visibility into what these users are doing. You can then use the event data in Brevo to segment and target your contacts based on their behavior, personalize your emails, start an automation, and more.
Why track events?
While contact attributes represent what a contact has, events represent what they do. Tracking events helps you see how your contacts interact with your emails and website. This way, you can identify what works in your customer journeys, identify areas for improvement, and adjust your marketing strategies accordingly.
For example, when a contact adds a product to their wishlist, it shows a strong interest, even if they’re not ready to buy. By tracking the "Added to wishlist" event, you can:
- Create personalized emails, like promotions or reminders, that include that automatically include the specific item each recipient has in their wishlist.
- Trigger an automation that sends these personalized emails.
- Segment contacts who added an item to their wishlist and later purchased it after opening your email.
What events can I track in Brevo and how?
Brevo offers three main categories of events:
- System events are pre-defined actions tracked by Brevo, like when someone opens one of your emails or books a meeting with you.
-
eCommerce events track actions related to purchases on your website. They’re useful for understanding customer buying behavior and analyzing your revenue performance.
- Custom events are actions defined by you and can be tracked using the Brevo tracker, an API, or webhooks.
Use the following tabs to view the different categories and events available in Brevo:
By default, Brevo tracks some predefined actions users perform while interacting with your website and emails, such as:
|
|
Expand the dropdowns below to explore all system events available in Brevo, organized by category. Each event includes its name, technical key, and a brief description.
| Event name | Event key | Description |
|---|---|---|
| Email sent | Sent |
A marketing email is sent to a contact |
| Email received | Delivered | A marketing email is successfully delivered to a contact’s inbox |
| Email opened | Opened | A contact opens a marketing email |
| Link clicked in an email | Clicked | A contact clicks a link in a marketing email |
| Unsubscribed from emails | Unsubscribed | A contact unsubscribes from receiving marketing emails |
| Email classed as "soft bounce" | Soft Bounce | The mail server of the contact temporarily rejected the marketing email |
| Email classed as "hard bounce" | Hard Bounce | The mail server of the contact permanently rejected the marketing email |
| Apple MPP Opens | proxy_open |
An email sent to a recipient using Apple's Mail Privacy Protection has been opened automatically |
| Event name | Event key | Description |
|---|---|---|
| Email sent | Sent |
A transactional email is sent to a contact |
| Email received | Delivered | A transactional email is successfully delivered to a contact’s inbox |
| Email opened | Opened | A contact opens a transactional email |
| Link clicked in an email | Clicked | A contact clicks a link in a marketing email |
| Unsubscribed from emails | Unsubscribed | A contact unsubscribes from receiving transactional emails |
| Email classed as "soft bounce" | Soft Bounce | The mail server of the contact temporarily rejected the transactional email |
| Email classed as "hard bounce" | Hard Bounce | The mail server of the contact permanently rejected the transactional email |
| Event name | Event key | Description |
|---|---|---|
| SMS sent | Sent | A marketing SMS is sent to a contact |
| SMS received | Delivered | A marketing SMS is successfully delivered to a contact |
| Link clicked in an SMS | Clicked | A contact clicks a link in a marketing SMS |
| SMS classed as "soft bounce" | Soft Bounce | The mobile network of the contact temporarily rejected the marketing SMS |
| SMS classed as "hard bounce" | Hard Bounce | The mobile network of the contact permanently rejected the marketing SMS |
| Event name | Event key | Description |
|---|---|---|
| SMS sent | Sent | A transactional SMS is sent to a contact |
| SMS received | Delivered | A transactional SMS is successfully delivered to a contact |
| SMS classed as "soft bounce" | Soft Bounce | The mobile network of the contact temporarily rejected the transactional SMS |
| SMS classed as "hard bounce" | Hard Bounce | The mobile network of the contact permanently rejected the transactional SMS |
| Event name | Event key | Description |
|---|---|---|
| WhatsApp campaign sent | Sent | A WhatsApp campaign is sent to a contact |
| WhatsApp campaign received | Delivered | A WhatsApp campaign is successfully delivered to a contact |
| WhatsApp campaign opened | Read | A contact opens a WhatsApp campaign |
| WhatsApp campaign classed as "soft bounce" | Soft-Bounce | A WhatsApp campaign is sent to a contact but fails to be delivered due to an issue on Meta's side (e.g., maintaining ecosystem health or BSP issues) |
| Event name | Event key | Description |
|---|---|---|
| Push notification clicked | push_notification_clicked | A contact clicks a push notification |
| Session started | push_session_started | A contact opens your website or mobile app for the first time or after 30 minutes of inactivity if they’ve already had it open |
| Subscribed to push notifications | push_subscribed | A contact subscribes to push notifications |
| Unsubscribed from push notifications | push_unsubscribed | A contact unsubscribes from push notifications |
| Event name | Event key | Description |
|---|---|---|
| Subscriber added | subscriber_added | A contact subscribes to your push notifications |
| Subscriber deactivated/disengaged | subscriber_deactivated | A contact can no longer receive web push notifications (e.g., the device was reset, notifications were disabled, or the subscription expired) |
| Subscriber refreshed/updated | subscriber_refreshed | The browser of a contact updates their push subscription details |
| Webpush delivered | webpush_delivered | A contact receives a web push notification |
| Webpush clicked | webpush_clicked | A contact clicks one of your web push notifications |
| Webpush closed | webpush_closed | A contact closes one of your web push notifications |
| Event name | Event key | Description |
|---|---|---|
| Pass installed | pass_installed | A contact adds a pass to their mobile wallet app. |
| Pass downloaded | pass_downloaded | A contact downloads a pass to their device by clicking the link provided |
| Optin updated | optin-updated | A pass is installed or deleted from a mobile wallet app |
| Status changed | status_changed | A contact installs or deletes a pass, and their owner status is updated |
| Enrolled | enrolled | A contact installs a pass for the first time |
| Pass status changed | pass_status_changed | The status of the wallet pass of a contact is updated (used, expired, or canceled) |
| Anonymized | anonymized | A contact is anonymized |
| Redeem failed | redeem_failed | A contact tries to redeem a link, but the redemption fails (code invalid or expired) |
| Redeem success | redeem_succeed | A contact successfully redeems a link |
| Counter value changed | counter_value_changed | The value of a counter linked to the profile of a contact changes |
| Loyalty status changed | loyalty_status_changed |
The loyalty status of a pass owner is updated |
| Notification sent | notification_sent | A notification is sent to a contact |
| Pass moved | pass_moved | A pass has moved from one campaign to another |
| Pass uninstalled | pass_uninstalled | A pass is uninstalled |
| Retargeted | retargeted | A pass owner is redirected to another campaign |
| Anonymization required | anonymization_required | An anonymization is required |
| Counter maximum value reached | counter_max_value_reached | The value of a counter linked to the profile of a contact reaches its maximum value |
| Offer attributed | offer_attributed | An offer is attributed to a pass owner |
| Activated from share | activated_from_share | A pass is activated after it is shared |
| Pass shared | pass_shared | A pass is shared |
| Event name | Event key | Description |
|---|---|---|
| Form submitted | form_submitted | A contact submits a Brevo form |
| Event name | Event key | Description |
|---|---|---|
| Deal created | deal_created | A deal associated with this contact is created |
| Deal stage updated | deal_stage_updated | A deal stage associated with a contact is updated |
| Task completed | task_completed | A task associated with a contact is marked as done |
| Task created | task_created | A task associated with a contact is created |
| Event name | Event key | Description | Availability |
|---|---|---|---|
| Webpage visited | page_visited |
A contact visits a page on a website where the Brevo tracker is installed |
Automation trigger |
| Event name | Event key | Description |
|---|---|---|
| Conversation ended | conversation_ended |
A conversation via email, chat, or socials ends
|
| Conversation started | conversation_started | A contact starts a conversation via email, chat, or socials |
| Message received | message_received | A contact receives a message via email, chat, or socials |
| Sales email clicked | sales_email_clicked | A contact clicks a link in a 1:1 email sent from a mailbox |
| Sales email opened | sales_email_opened | A contact opens a 1:1 email sent from a mailbox |
| Event name | Event key | Description |
|---|---|---|
| Meeting booked | meeting_booked | A meeting is booked by a contact via the booking page or by the user via the Meetings dashboard |
| Meeting canceled | meeting_canceled | A booked meeting is canceled by a contact via the cancellation link or by the user via the Meetings dashboard |
| Meeting started | meeting_started |
A booked meeting begins (start time is reached) |
| Event name | Event key | Description |
|---|---|---|
| Call finished | call_finished | A phone call is completed through the Phone app |
| Event name | Event key | Description |
|---|---|---|
| Payment done | payment_done | A contact makes a payment using one of your payment links or requests |
| Payment request created | payment_request_created | A payment request associated with a contact is created |
| Payment request reminder sent | payment_request_reminder_sent | A payment request reminder is sent to a contact |
| Event name | Event key | Description |
|---|---|---|
| Balance minimum value reached | balance_minimum_value_reached | The loyalty balance of a contact reaches the minimum balance limit |
| Balance maximum value reached | balance_maximum_value_reached | The loyalty balance of a contact reaches the maximum balance limit |
| Balance value updated | balance_value_updated |
The loyalty balance of a contact is updated after earning or redeeming points |
| Balance value expired | balance_value_expired | Part of the loyalty balance value of a contact expires |
| Balance transaction unauthorized | balance_transaction_unauthorized | A balance credit or debit operation is rejected |
| Voucher created | voucher_created | A new voucher is assigned to a contact |
| Voucher redeemed | voucher_redeemed | A contact reedeems one of their vouchers |
| Voucher expired | voucher_expired | One of the vouchers of a contact reaches its expiration date |
| Voucher revoked | voucher_revoked | One of the vouchers of a contact is revoked |
| Membership created | subscription_created | A contact subscribes to a loyalty program |
| Membership year anniversary | subscription_year_anniversary | A contact reaches their annual membership anniversary |
| Membership monthly anniversary | subscription_month_anniversary | A contact reaches their monthly membership anniversary |
| Membership revoked | subscription_revoked | A contact unsubscribes from or is deleted from a loyalty program |
| Tier association updated | tier_association_updated | The subscription tier of a contact changes (e.g., from Bronze to Silver) |
eCommerce events let you track and record actions related to customer purchases on your website. These events can be generated when you've connected your eCommerce store to the Brevo eCommerce dashboard using one of our plugins or via the API.
➡️ To learn more about the Brevo eCommerce dashboard, check our dedicated article Discover our eCommerce Dashboard.
Using one of our plugins
The events available to you depend on whether you've connected your store to the Brevo eCommerce dashboard.
Expand the following dropdowns to view the events available in each case:
When your store is connected to the Brevo eCommerce dashboard using a compatible plugin, you can access the following standard eCommerce events:
| Event name | Event key | Description |
|---|---|---|
|
Cart updated |
cart_updated | A contact adds a product to their cart on your website |
| Cart deleted | cart_deleted | A contact removes a product from their cart on your website |
|
Order created |
order_created |
A contact completes a purchase on your website |
Some plugins may also generate additional non-standard eCommerce events, such as:
| Event name | Event key | Description |
|---|---|---|
|
Order completed |
order_completed | Similar to the order_created event but includes more detailed information, such as the price before tax, VAT, total price including tax, and shipping and billing information. |
Non-standard events appear under the Custom events section in various areas of Brevo, including:
- When personalizing messages
- In the new automation editor
- When segmenting contacts
If your plugin is not compatible with the Brevo eCommerce dashboard or you've connected a compatible plugin but haven't activated the dashboard, you can still access the following non-standard eCommerce events:
| Event name | Event key | Description |
|---|---|---|
|
Cart updated |
cart_updated | A contact adds a product to their cart on your website |
| Cart deleted | cart_deleted | A contact removes a product from their cart on your website |
|
Order completed |
order_completed |
A contact makes a purchase on your website |
These non-standard events appear under the Custom events section in various areas of Brevo, including:
- When personalizing messages
- In the new automation editor
- When segmenting contacts
Via the API
To create eCommerce events via the API, import your store's eCommerce data to the Brevo eCommerce dashboard. Then, use the Brevo API's events endpoint to create custom events for eCommerce actions.
To learn more, check our dedicated developer documentation:
Custom events are specific actions or interactions that you choose to track on your website or within your emails. Brevo does not automatically track these events, so you need to implement them manually using the Brevo tracker or API.
Depending on your business and needs, these events can include various user interactions such as:
|
|
➡️ To learn more about custom events and how to track them, check our dedicated article Create custom events in Brevo.
Where to find and use event data in Brevo?
When a contact performs an action that triggers a system, eCommerce, or custom event, the event data is automatically sent to Brevo. You can access this data in multiple areas of the platform and use it to create more personalized and relevant experiences for your contacts.
👤 View events on the contact details page
Some tracked events appear on the details page of your contacts, such as when a contact is added to a list, opens an email, or completes a call. This page is available when you click a specific contact from the Contacts page. It gives you a centralized view of their activity history and timeline, helping you better understand their behavior and engagement.
➡️ To learn more about the contact details page, check our dedicated article Overview of the contact details page.
💾 Check your event logs to view a complete list of tracked events
You can check the Event logs page to view a complete list of all tracked events across your Brevo account. This page displays detailed information for each event, including the event type, timestamp, and payload (metadata and properties sent with the event). It’s a useful tool for troubleshooting, verifying event tracking, and understanding how contacts interact with your messages or website.
➡️ To learn more about event logs, check our dedicated section in the article What are automation logs? (workflow logs, event logs, contacts in workflow).
✂️ Segment contacts using event-based conditions
Segments are a powerful tool for filtering contacts based on specific criteria, such as actions they've performed or haven't performed on your website and emails. For instance, you could create segments for contacts who visited a certain product page, did not open your emails in the last few months, or downloaded a specific resource. This segmentation helps you target specific groups with relevant content.
➡️ To learn more, check our dedicated articles What conditions are available to segment my contacts? and Create a segment to filter your contacts.
🤖 Trigger automations using event data
Events or segments based on events can be used to automate certain marketing or sales tasks. For example, if a contact adds a product to their cart and does not make a purchase within the next few hours, an abandoned cart email is automatically sent. This is based on the user's action of adding a product to their cart, which is tracked by the "cart updated" event, along with the details of the cart content.
The following table provides some examples of use cases where automations are based on events or segments:
| Use case | Explanation | Trigger |
|---|---|---|
| Abandoned cart | Send an abandoned cart email with the details of the products left behind | Cart updated (event) |
| Purchase confirmation | Send a purchase confirmation email with the details of the products purchased | Order completed (event) |
| Re-engagement | Send a re-engagement email to try and win back contacts who have not interacted with your emails in a while | Email not opened in the last # months (segment based on event) |
| Sales follow-up | A follow-up email is sent to newly qualified leads when a deal stage is updated to the "Qualified" stage | Deal stage updated to Qualified (segment based on event) |
➡️ To learn more, check our dedicated articles Available triggers, actions, and rules in an automation and About the new automation editor.
💬 Personalize messages with dynamic content
You can include dynamic content in your emails and SMS messages based on a contact’s past events, such as a recent purchase, website visit, or form submission. By tailoring your message to their behavior, you create more relevant and engaging experiences that can boost conversions and strengthen customer relationships.
| Email template in Brevo | Email received in the inbox |
|---|---|
➡️ To learn more, check our dedicated articles Personalize your emails using Brevo Template Language and Personalize your SMS messages with contact attributes and event data.
🤔 Have a question?
If you have a question, feel free to contact our support team by creating a ticket from your account. If you don't have an account yet, you can contact us here.
If you’re looking for help with a project using Brevo, we can match you with the right certified Brevo Agency partner.