Back to Help
VisitorsData

TRACK EVENTS

What is an event?

Events are records of specific actions that your visitors have taken in your website. Each action registered as an event is recorded as an event_log.

ConvertLoop automatically records the first time, last time, and total number of times that an event has been executed by a specific visitor.

What to create an event for

Events are for tracking what your website visitors do so that you can filter those visitors according to their interactions. That way, you can send them emails when an event occurs.

Default Event

ConvertLoop has one default event: the Visited Page event.

This event is automatically added to your users’ event history when triggered. This event is automatically triggered when a visitor visits a page where you have included your Java Script tracking code.

Where to find the recorded events

You will find the event data in the following places:

  1. The FILTER BY PERFORMED EVENT filter at the People view. Use this filter to find event_logs performed by your visitors.

  2. The event index that lists all of the events you have created.

  3. The event history for each of your visitors, which you will find in their unique contact profile.

ConvertLoop Marketing Automation for Product People, events history

How to create an event

To create events, use any of our API Libraries.

To better implement the events you want to track, follow these steps:

  1. Identify the visitor’s actions (events) that you want to track in your website.
  2. Define the event details (a.k.a. “event metadata”)
  3. Create the events using ConvertLoop’s API.

Let’s take a more detailed look at each of these steps.

Step 1: Identify the visitor actions ("events") that you want to track on your website

Make a list of all the actions (“events”), such as “Signed up”, “Used ‘x’ feature”, or any other action that is relevant for your business.

Step 2: Define the event details (Optional)

There are some cases where you want to capture details related to each event. We call this additional information Event Metadata.

Imagine that you want to track when a user of your product buys credits. We will call this event “Bought Credits”.

Now, imagine that you also want to capture the amount of money that the user has been billed (for example, US$200), and also the amount of credits that the user has obtained after he paid (for example, 500 credits). In this case, we want to capture the amount and the credits for each “Bought Credits” event.

In our example, the additional information (the event metadata) you want to capture would be: amount: 200; credits: 500.

Step 3: Create the events using ConvertLoop's API

Once you have defined which events to track and their additional information that you want to capture (optional), you can create them using our API Libraries in Ruby, Rails, Java Script, Node, PHP, or Java. You can access all of our API libraries here. You can also learn more about tracking events in our Full HTTP API Reference..

Check out the following example, which creates an event named “Bought Credits”:


_dp("track", "Bought Credits", {
  metadata: {
    amount: 200,
    credits: 5000
  }
});
Implementation using ConvertLoop's JS Library. Check out our API Documentation for additional programming languages.
To include metadata of your events, you need to add a hash called metadata to your tracking event function, with the pairs of key,values related to the attributes you want to capture. In our previous example -> metadata: {amount: 200, credits: 500}.

Best practices for defining your Events

  1. We highly recommend that you track events that correspond to actions that represent goals in your visitor’s journey oas opposed to tracking all the steps that lead to that goal. “Signed Up”, “Bought product” are good examples of Events, instead of creating events for every step before achieving a goal in the visitor journey.

  2. 2. Name your events after the past tense of the action you are tracking to make them easier to read. It is better to name an event “Bought Credits” than “Buy”.

  3. Use event metadata to record the details related to the event.

Track events

  • List the visitor’s events that you want to track based on the main actions in your visitor journey, such as “Signed up”, “Used ‘x’ feature”, “Paid bill”, etc. You can name your events however you want.
  • List the additional information (metadata) for each event that you want to capture. This is optional.
  • Track specific events in your website using ConvertLoop's API Library.

"Events" vs. "Custom Attributes"

Do not confuse Events with Custom Attributes.

An Event represents an action performed by a visitor to your website, which you want to track. Events could be triggered several times by the same person, and you can filter them by the first_time, last_time or a specific time - any_time - that the event has been performed. A few examples of events: Bought Credits, Signed Up, etc.

Custom Attributes are data about They are mainly related to their contact information or the plan they belong to in your service/product. For example: first_name, email, mobile, User Plan, etc.

RECORD EVENT METADATA

What is "Event Metadata"?

“Event Metadata” are details about specific events.

For instance, if you are tracking the event “Purchased Credits” you may want to know the amount of the purchase and the number of credits that your customer has purchased. Event Metadata will help you to send the amount and credits information related to the specific event “Purchased Credits” in our example.

ConvertLoop records the First Record, Last Record, and Any Record for each event metadata you are sending from your website.

What is the default set of event metadata?

By default, ConvertLoop automatically records the following set of event metadata associated to the visitors to your website:

  • city: calculated by the visitor’s address location.
  • country: calculated by the visitor’s address location.
  • referrer: the last page your user visited before accessing your site
  • ip: the IP of the devise used to visit your site.
  • os: the Operating System of the device your visitor used to visit your website.
  • host: the host of the domain that the user visited. Your domain.
  • path: the last path visited by your visitor on your website
  • language: the language set in your visitors’ browser.
  • user_agent: the web browser your visitor used to access your site.

You can find the event metadata in the FILTER BY EVENT METADATA filter at People view. You can also find this information for each person in that contact’s unique profile.

"Event Metadata" vs. "Events"

Do not confuse Events with Event Metadata. One Event (action) could have many Event metadata (event details) records. For example, if you have an Event called Bought Credits, the Event Metadata could be credits (which represents the number of credits that the user has bought), and amount (which represents the money they paid for the credits).

Didn't find what you were looking for?

Get in touch, we're always happy to help. Email us at: [email protected]

Search