Skip to main content
Managing users

Track custom events

Send events when people act in your product. Then filter people by those events and start Journeys with them.

Written By Bruno

Last updated About 3 hours ago

Overview

Events record what people do in your product, for example invited-teammate or upgraded-plan. Each event belongs to one user or lead. Featurebase counts each event per person and records when the person first and last did it. You can then filter people and build segments on that data.

You can see all your events in Settings → Users → Events.


Send events

JavaScript SDK

Call track with the Messenger SDK installed and the user identified:

Featurebase('track', 'invited-teammate', {
  plan: 'pro',
  seats: 12,
})

The event goes to the signed-in user.

REST API

Send each event to POST /v2/events with an API key. Identify the person with contact.id, contact.userId or contact.email. Only contact.id works for leads. To send up to 100 events in one request, use POST /v2/events/bulk.

Note: Events never create a contact. If the person does not exist yet, Featurebase does not record the event.

Event names and properties

  • Name - 1-100 characters. Use letters, digits, spaces and _ - . : /, and start with a letter or digit. Names are case-insensitive. The fb: prefix is reserved

  • Properties - Up to 20 keys per event, 4 KB in total. Featurebase sets the type of each property from the first value it receives: text (up to 255 characters), number, true/false, date, link, rich link or money


Manage events

Each row shows the event name, its description, its properties with their types, how many times it happened in total, and when it was last received. To find an event, use the search box. Counts update about once a minute.

From the ··· menu you can:

  • Rename - Change the display name. Your code still sends the original name

  • Edit description - Describe the event for your team. You can also click an existing description to edit it

  • Archive - Stop recording new events with this name. Featurebase keeps the data that it already recorded, and you can unarchive the event later

You cannot delete an event. If a live Journey uses an event, you must change or stop the Journey before you can archive the event.

Featurebase events

Events with the Featurebase badge are recorded automatically for users and leads:

  • Started a conversation

  • Conversation was closed

  • Rated a conversation - Includes the rating

  • Voted on a request

  • Their request changed status - Recorded for the author and the voters of the request

You can edit their descriptions. You cannot rename or archive them.


Use events

  • Filters and segments - Filter people by an event's count, first seen date or last seen date, for example "has done" or "has not done"

  • Audience rules - Target Outbound messages with the same conditions

  • Journeys - Start a Journey when someone sends one of your events, or check whether they did an event since a step

  • Contact profile and inbox - See each person's events next to their conversations

Only your own events can start a Journey. Featurebase events are not available as Journey triggers.


Limits

You can have 200 active events at a time. Featurebase events do not count toward this limit. The counter shows your current total, for example 1 of 200 active events.

Note: When you have 200 active events, Featurebase does not record events with a new name. Archive an event you no longer need to make room. Your workspace can also hold no more than 1,000 event names in total, and archived events count toward that limit.