Collections

Overview of Events

By Jitta

Updated 6 days ago

Tags and events are the most common criteria you will use when creating user segments in Gist. They allow you to understand your customers based on their behavior on your site, and as a result, segregate them into user groups effectively.

Tags, events, and custom fields give you greater leverage in deciding how and what to communicate with your users. 

Here's a brief description of each one of them:

1. Tags help you attach a label or a piece of data to a user based on what they do on your site. Tags help you give a visual representation of user actions. Tags are very useful in creating user segments.

2. Events are similar to tags, and they also record time stamps and help you understand how frequently an event is performed by your users.

Events

Events are similar to tags. The biggest difference is that they record the date and keep track of how many times the event has occurred. Events can be recorded multiple times, as opposed to tags which are applied once for the duration it is held by the subscriber.

Events can be configured using integrations, rules, or API calls. For example, if you are using a payment integration such as Gumroad, which sends in the “Made a purchase” event. You can use that event to search for subscribers that have purchased something within the last 3 months.

Naming events

Events describe what a user has done on your website, which is why it is important that you name them properly, just as with tags.

When to track events?

Events should be used to track when a subscriber performed an action, or when something happened to them. For instance, if yours is a Software as a Service (SaaS) product, and you might want to track the critical stages of onboarding. Sending events are going to give you the most concise information along with a date that the event happened.

Did this answer your question?