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

Tracking methods

Below, we'll introduce each of the ways you can track events. Based on this, you should decide which method is best for you, and click through to the relevant article for more details on that tracking method.

Segment

If you already use Segment on your website, you can choose to send any of your Segment events to Mutiny. 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. Learn more here.

Custom Javascript

Mutiny allows you to fire off custom Javascript on your website to track events. This may be a good option if you already have conversion events set up on your site for other platforms (i.e. Meta and Google Ads). Learn more here.

Google Tag Manager

If you use Google Tag Manager on your site, you can add our custom Javascript to your GTM container and take advantage of already existing triggers you may have. Learn more here.

HubSpot forms

If you have HubSpot forms embedded on your site, you can track when a user fills out one of your HubSpot forms. Learn more here.

Drift

If you use Drift on your site, you can track when a user takes specific actions within your Drift bot. Learn more here.

Calendly

If you have Calendly forms embedded on your site, you can track when a user fills out one of your Calendly forms. Learn more here.

WYSIWYG editor

If none of the above methods are possible, Mutiny has a WYSIWYG editor that allows you to track specific elements or pages using directly from the Mutiny app. This tracking method can have varying levels of accuracy depending on your website so we typically recommend using one of the methods above instead. Learn more here.

Default events

When you first login to Mutiny, you may see a number of default events, including "All Form Submissions". This event simply tracks the default form submit event and depending on your website, can vary in its reliability. We include this event as a jumping off point so that you can start running your experiences as quickly as possible, but we highly recommend against using this event for reporting.

FAQs

What events should I track on my site?

You can add as many 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. Some examples may include:

• Sign ups
• Trial Requests
• Demo Requests
• Contact Us Submission
• Subscriptions to Blog

• Downloads or form submits on any gated assets (e.g. whitepapers)

Which method of tracking should I use?

This is largely dependent on your existing website's current tech stack. Typically, the question you want to ask is how are you currently tracking conversion events for other platforms, like Meta or Google. It often makes sense to have your conversion events consolidated into one place so keeping with your existing systems is recommended.

How does Mutiny count a conversion?

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.