All Collections
Tracking Conversions
Tracking Conversions in Mutiny (overview)
Tracking Conversions in Mutiny (overview)

Learn about the different methods for tracking conversions in Mutiny and which is best suited for you.

Updated over a week ago

Tracking conversions allows you to measure whether or not your personalization was a success, and how much impact was driven by the experience. Mutiny also uses conversion data to analyze your audience traffic and performance, and make recommendations on who to personalize for and how you should personalize for them. 

You can add as many conversion events as are relevant to you/your business. Your conversion events should represent leads generated for your company - basically anywhere you are capturing an email.

Mutiny measures unique conversion events deduped by visitor. That means if a visitor takes multiple actions that are defined as a conversion events, they will be counted as only one converting visitor in your test results. You can filter your results to see the impact by conversion event. 

Types of conversion configurations

There are a few different ways in which you can track conversions in Mutiny. Below is a summary and explanation of when you should use each type.

Segment events

Tracking Segment events as conversions in Mutiny is the easiest and most accurate way to track conversions. Segment events are fired from your code base when conversions occur and are tied directly to a user. To track these events in Mutiny, all you need to do is select the event from a drop down list.

Event tracking with Javascript in your front-end code

If you do not use Segment, we recommend tracking conversions in Mutiny by implementing Javascript in your front-end code. You can track events that happen on the same domain as Mutiny is implemented on, or on a sub-domain (ie, within your product). This is a more accurate way to track conversions as you can validate the signups that occur and track leads in the same way you measure them across your other platforms.

Conversion Tracking Using Google Tag Manager

If you already have your conversion events triggers built in GTM for other platforms, you can use those triggers to send your conversion data to Mutiny. See this doc for full instructions.

Configuring conversions using Mutiny's WYSIWYG

If you do not use Segment and you don't have access to engineering resources to implement conversion tracking Javascript code, you can use Mutiny's point and click editor to add your conversion configurations. Directly from Mutiny's interface, you can add page view or click event tracking by entering the page URL and clicking on the element on the page you want to track. 

HubSpot forms

HubSpot forms don't exist natively on your website, so you need to use Mutiny's HubSpot Form tracking conversion type to track these rather than the WYSIWYG point and click options described above.

Tracking Drift conversions

Mutiny integrates out of the box with no configuration required for conversions that come through Drift. Mutiny captures email, phone, and meetings booked without any implementation.

Tracking Calendly conversions

Mutiny can track Calendly conversions from forms that are embedded on your website (as long as the Mutiny script is running on the page). On the conversions page, you can configure which pages should track Calendly conversion events.

Still not sure which method to use or what types of conversions you should be tracking?

This doc should help.

Not sure how to choose?

Feel free to get in touch with us through Intercom chat or by emailing

Did this answer your question?