Event tracking

Now that you have added the main tracker, you can start tracking events and build your customer journey.

Conversion event

Customer journey has to be finite and defined by a conversion event. Depending on your use case it can be Purchase, Sign up, Booking, or any other action you consider to be successful end of your customer's journey. To notify Dripit about a conversion, you have to send an event which indicates an end of journey. For example like this:

// track order event

"order" is an example and you can name the event as you like. This small snippet is the bare minimum you need to identify a conversion. In the dashboard you can set this event as the conversion event!

Tracking Revenue

You can also track the transaction value. This value will be used to report Revenue and to calculate ROI. Simply add a variable with the name value and monetary value in cents.

// track order event with the price
dripit.track("order", {
  value: 49999

This will be interpreted as 499.99 $.

Customer journey events

In a similar fashion you can track events that define your customer journey.

Depending on your specific website, you define what are the important milestones of your customer journey. For example, typical events for an e-commerce site are adding to cart and initiating checkout process. For Saas it might be important to track demo request or visiting a specific page on your site. Either way, the code looks something like this:

// track 'add to cart' event

After starting tracking these events, you can set up your customer journey in the dashboard.

User information

At any point you can provide more information about the user with the dripit.identify method.

// tracking user_id with segment
  'user_id' : <Unique string>,
  'segments': ['Female']

The dripit.identify method can be used at any point of a session.

Identifying users

By providing a user_id you can improve the mapping of entire customer journeys for users. This is easily done if you are using backend tools like CRM.

// tracking user_id
  'user_id' : <Unique string>

We don't recommend using e-mail address as user_id.

Tracking customer segments

A lot of times you would have different kind of customer segments defined by their conversion type or activities in a journey. In e-commerce, these could be customers with purchases in different categories. In SaaS, there might be different pricing plans. Or, in general, you might be interested in demographical segments, like gender. Dripit allows you to analyze each segment's customer journey and marketing performance separately. To segment users, you have to use dripit.identify method with segments parameter! For example, if you want to assign the product category segment to the user right after a purchase:

// track order event with the price
dripit.track("order", {
  value: 49999

// tracking segment
  'segments': ['Apparel']

There can be multiple segments separated by commas e.g., ['Apparel','Female']

Custom channel events

Sometimes you want to track specific marketing events. For example, how your company blog assists conversions or how your on-site marketing campaign works.

To do so, you can use the same dripit.track method with the identifying parameter. For example, blog.

// track a visit to blog

Afterwards, you can set up to use "blog" as a custom channel.

Now Dripit will track how your blog performs across customer journey!

By adding id you can track sub-channels. In this case those would be particular blog articles.

// track a visit to a specific blog article
dripit.track("blog", {
  id: 'Nice blog article title'

As a result, now you can see in the Dashboard how your blog performs in general, and compare how each article assists the conversions.

results matching ""

    No results matching ""