Asset Analytics

Last updated: April 7, 2026

Once your assets are live, Mutiny gives you a built-in analytics layer to measure impressions, track engagement, and dig into individual visitor behavior. This lesson covers how to read asset analytics

Next Lesson: 📄 Connecting Mutiny to your Analytics Stack

The Asset Dashboard

The Assets page shows a summary row at the top with your total views across all published assets, the number of live pages, and pages with recent activity. Each asset card also displays a snapshot of its own views and clicks, so you can quickly compare performance at a glance.

To go deeper on any asset, click the analytics icon on its card or click into the asset and switch to the analytics view.

The Visits Table

Inside the analytics view, you will find the Visits Table. Each row represents a single visit and shows a timestamp, the visitor's location, the number of clicks they made, and how long they were actively engaged with the page.

You will also see a visitor identity column. When Mutiny can resolve who the visitor is, typically through a connected tool like Outreach or Salesloft, it surfaces that identity here. Visits from whitelisted IPs, such as your own team members who have logged into Mutiny or accessed a preview link, will not appear in the table, so your data stays focused on real prospect activity.

Engagement Metrics

Mutiny tracks two engagement signals beyond raw view counts. Clicks tell you whether visitors are interacting with your asset, whether that is a CTA, an embedded form, a video, or another clickable element. Engaged time reflects how long a visitor was actively on the page, which is a stronger signal of interest than a pageview alone.

Individual Visitor Behavior

For any row in the Visits Table, you can click to watch a session replay showing where the visitor scrolled, what they hovered on, and what they clicked. If you want to filter out traffic from a specific IP, the three-dot menu on any row lets you ignore that visitor by IP address, so future visits from that IP are excluded from the table.