Data discrepancy between Mutiny and other platforms

When looking at your results from Mutiny and other Analytics platforms, it's recommended to focus on the trends between the two systems — not comparing X visits from Mutiny to Y visits on the other.

If you see unexpected results when analyzing the trends of the tools, several factors could be causing inconsistencies:

Tracking code installation

If the Mutiny and other platform's tracking codes are not installed on the same pages on your site, then the tools will not be recording sessions for the same number of pages. 

Learn how to install the Mutiny Client here: Installing the client code

Cross-domain tracking

Cross-domain tracking consolidates data across multiple monitored domains. When a visitor navigates from firstdomain.com to seconddomain.com by clicking on a link, cross-domain tracking ensures that this interaction is recorded within the same session. Without Cross-domain tracking, these visits would be considered separate events. Mutiny does not support Cross-domain tracking, so if it is set up on your other platform, it can lead to a discrepancy with Mutiny.

Cookie consent banner

If you have a cookie consent banner that requires opt-in, it could affect the number of sessions and views tracked. For example, if you have the platforms set for different levels of opt-in, then one platform could be approved for tracking while the other is not.

Learn about cookie consent implementation here: Implementing cookie consent rules

Adblockers

If a visitor to your site has an ad-blocking service or browser extension enabled, Mutiny may be listed under the block list for this ad blocker. Certain ad-blocking extensions (like uBlock Origin) have been known to block Mutiny from loading on the page. When Mutiny does not load on the page, no personalization loads, and no visitor data is tracked. Not all ad blockers will prevent Mutiny from loading.

Note: This is true for any client-side website technology, including any optimization or analytics platforms.

"Do not track" from Google Chrome

Our platform respects the "Do not track" setting from Google Chrome. This automatically tells our website not to track the visitors when they are on the page and can lead to skewed data if they are being tracked by other platforms not respecting this setting.

Logged into Mutiny

If you are currently logged into Mutiny, we will blacklist your IP from showing up as conversions or impressions on your experiences. 

Comparing different kinds of data

When contrasting the outcomes between Mutiny and your other analytics platforms, disparities may arise because of the comparison of mismatched data (like comparing apples to oranges).

For instance, if you were to examine Mutiny's tracked visitors with page views on Google Analytics, a significant inconsistency would probably emerge as Mutiny is tracking unique visitors here and Google Analytics is tracking each view. Each platform employs its methods of analytics reporting, requiring a clear understanding of how the data is tracked to effectively compare data sources.

Segment logic

Discrepancies can also appear when you are expecting a certain number of visitors for a segment based on a 3rd party platform's data. When comparing the data between Mutiny, it is important to understand the filters you are using in your Audience Segmentation and the operators. Using the AND operator will require the visitor to meet all of the requirements, so keeping this in mind while reviewing the data is key.

Learn more about creating segments here: Creating a segment

​Don't be a stranger

If you have any questions, we’re here to help! Please feel free to contact us at any time through support@mutinyhq.com.