Tracking & Analyzing Mutiny Assets in Adobe Analytics

Mutiny asset pages can be measured in Adobe Analytics just like any other page on your site.

This guide explains how to ensure tracking is set up correctly and how to analyze asset performance by account, asset, or traffic source using Analysis Workspace.

Setup

1. Add Adobe Launch to Your Mutiny Pages

If your site already uses Adobe Experience Platform Launch (Tag Manager), add the same Launch container code to your Mutiny asset pages.

This ensures your standard Adobe Analytics tracking works automatically.

Resources:

• Add Launch to your site
• Configure the Adobe Analytics Extension

2. Define Core Dimensions

Make sure these page values are being captured (or mapped to eVars if needed):

If your implementation uses these dimensions for other purposes, store them in eVars like:

• eVarX → Mutiny Asset
• eVarY → Target Account

3. Use URL Parameters for Attribution

Include consistent asset parameters in your links (e.g. med=paid&src=google&cmp=mutiny_q1-demo).

These values feed into your Marketing Channel Processing Rules for attribution.

Analyze Your Asset Performance

1. Page Views & Engagement

Use Analysis Workspace → Freeform Table

• Dimensions:
  • Page (or Target Account eVar)
  • Site Section (or Mutiny Asset eVar)
• Metrics:
  • Page Views, Visits, Visitors
• Filter: Create a Segment for your Mutiny subdomain or asset prefix.

Example:

Segment condition: “Page contains q1-demo” or “Server equals discover.yoursite.com”

You can also use a Key Metric Summary Panel for a quick view of total engagement.

2. On-Page Events (Custom Engagements)

If you track specific interactions (like button clicks or form submissions), these should be configured as Success Events in Adobe Admin.

• Metrics: any Success Event (e.g. CTA Click, Form Submit)
• Dimensions: Page, Site Section, or eVars
• Segments: by asset or account

Use a consistent event naming convention across Mutiny pages so you can aggregate easily.

Tips to View on-page Events for: 

• A Specific Target Account:
  • Drag the Page or your Target Account eVar from Dimensions, and add any of the custom events you have tracked from Metrics.
  • Add a Segment on your report to include only Hits where the Page or your Target Account eVar matches the account that you want to view engagement for. 
• A Specific asset: 
  • Drag the Site Section or your Mutiny Asset eVar from Dimensions, and add any of the custom events you have tracked from Metrics.
  • Add a Segment on your report to include only Hits where the Site Section or your Mutiny Asset eVar matches the asset that you want to view engagement for. 
• All Assets Pages combined: 
  • If available, drag your Page Domain eVar from Dimensions, and add any of the custom events you have tracked from Metrics. 
    • If your implementation does not include a Page Domain or similar eVar, you may use Site Section as the Dimension and rely on the summary row in the table for metric totals. Or, you may opt to use a Key Metric Summary panel instead of a Freeform Table to see Metrics aggregated without a Dimension. 
  • Add a Segment on your report to include only Hits where the ‘Page Domain’ matches your custom sub-domain. If ‘Page Domain’ or a similar eVar is not available in your implementation, you may also use ‘or’ conditions in a Segment to include hits where the ‘Site Section’ matches any of your assets.

3. Traffic Sources

To understand which channels drive visitors to your Mutiny pages:

• Dimensions:
  • Marketing Channel
  • Marketing Channel Detail
  • (Optional) Entry Page or Entry Site Section
• Metrics:
  • Entries, Visits, Visitors, Page Views

Example:

Add a segment: “Entry Site Section equals q1-demo” to see which marketing channels are contributing to that asset.

Tips to View Traffic Sources for: 

• A Specific Target Account:
  • Drag Marketing Channel and/or Marketing Channel detail from Dimensions, and add any of ‘Entries’, ‘Visits’, ‘Visitors’, ‘Page Views’, or your custom events from Metrics.
  • Add a Segment on your report to include only Visits where the Entry Page  matches the account that you want to report on. 
• A Specific Asset: 
  • Drag Marketing Channel and/or Marketing Channel detail from Dimensions, and add any of ‘Entries’, ‘Visits’, ‘Visitors’, ‘Page Views’ or your custom events from Metrics.
  • Add a Segment on your report to include only Visits where the Entry Site Section matches the asset that you want to report on. 
• All Assets Pages combined: 
  • Drag Marketing Channel and/or Marketing Channel detail from Dimensions, and add any of ‘Entries’, ‘Visits’, ‘Visitors’, ‘Page Views’ or your custom events from Metrics.
  • Add a Segment on your report to include only Visits where the Entry Site Section matches any of your assets.

4. Attribution & Conversions

Adobe’s Attribution Panel lets you see how Mutiny visits influence conversions on or off your asset pages.

To analyze:

1. Add an Attribution Panel in Workspace
2. Choose your success event (e.g., “Form Submission”)
3. Select your attribution dimension (e.g., Marketing Channel or Site Section)
4. Compare models like First Touch, Last Touch, and Linear

Common Use Cases:

• Which marketing channels drive conversions on Mutiny pages?
• How do Mutiny visits contribute to downstream conversions?

Resources:

• Attribution Overview
• Marketing Channel Analysis

Quick Tips

• Use the same Launch container and Processing Rules as your main site.
• Segment by subdomain or asset prefix to isolate Mutiny data.
• Use Freeform Tables for performance views, Attribution Panels for conversion impact.
• Maintain consistent asset naming (mutiny_) across URLs.