Track event

Definition

A track event in Reflag is sent by the client when a user interacts with a flagged part of your application. Reflag uses these events to track flag adoption or launch feedback surveys. In most cases, you do not need to create custom track events because you will use the flag key instead.

Attributes

An event entity is a collection of attributes associated with an event name or flag key. Each attribute is a key — value pair supplied by your application. Every event must include userId. You can provide any additional attributes you need.

Event attributes are useful mainly when setting up event-based flags, which can match specific events based on those attributes. They are also useful for automatic feedback surveys, which can trigger on a specific event and attribute combination.

Reflag manages a set of computed attributes when you send data to Reflag:

• First seen, Last seen and Event count of the users and companies,

• First used, Last used and Event count of the companies relative to the flag that matched the event.

In Segment terminology, these events can be thought of as acting as a Track call. Event attributes can be thought of as Event traits.

Do not include PII data when sending in event attributes. It is recommended that any sensitive data should be hashed or otherwise not included.

Next steps

• Learn about feedback and setting up automatic feedback surveys within Reflag UI,

• Learn how to create an event-based flag using user attributes within Reflag UI.