Definition
A mapping groups pages that meet the same rules, or page conditions, into named page groups. For example, a team might group all product-detail pages together, or separate product pages by category so each group can be analyzed on its own.
A page can belong to only one page group within the same mapping. This makes the conditions important: overlapping conditions create conflicts, while incomplete conditions can leave some page traffic outside the groups. Contentsquare describes the completeness of a mapping using exhaustivity, where 100% means all traffic on the site’s pages is included.
Teams can create several mappings for different analysis needs, such as a high-level reference mapping for an overview and a more detailed mapping for specific page types. Selecting a mapping changes how page groups appear in Experience Analytics, including in Journey Analysis and Page Comparator.
What does that mean
Think of a mapping like sorting a large box of books into labeled shelves. The books are still the same, but the labels make it easier to study one shelf or compare shelves.
Why this matters
A useful mapping turns page-level UX data into views that match the question a team is asking. High-level groups help reveal broad journey patterns, while detailed groups help compare particular templates or categories. Reviewing conflicts and exhaustivity helps teams avoid drawing conclusions from incomplete or overlapping groups.
Use cases
Create a consistent site-wide view
Relevant for: Data and Marketing. When a site has many URLs, looking at every page separately can make broad patterns difficult to see. A global or reference mapping groups similar page templates so teams can analyze aggregated behavior across the site. This creates a shared baseline for reporting and reduces the need for repeated manual filtering.
Compare product and category experiences
Relevant for: Ecommerce and Product. When different product pages or category pages are mixed together, important differences can be hidden in the aggregate. A detailed mapping uses page conditions to keep meaningful page types or categories in separate groups. Teams can then compare performance more precisely and prioritize improvements where they are most likely to help.
Adapt analysis to different team questions
Relevant for: UX/UI and Marketing. Different teams may need different views of the same site—for example, a high-level journey view for campaign analysis and a detailed page view for experience design. Teams can create, edit, or duplicate mappings for specific projects and select the appropriate mapping before analysis. This makes the same collected UX data easier to reuse across distinct questions without changing the site’s content.
How Contentsquare helps.
Mappings organize site pages into page groups through conditions, so teams can choose a page structure that fits their analysis.
Mapping Assistant helps create AI-generated starter mappings from recent page activity, URLs, and custom variables; teams can edit and refine the result.
Journeys reflects the selected mapping in its journey visualization, so paths can be studied at a high level or with more detailed page groups.
Page Comparator updates the available page groups according to the selected mapping, helping teams compare the pages that matter for a specific question.
FAQs on mapping
A mapping is an analysis structure that organizes a site’s pages into page groups through conditions. It helps teams decide whether to view data for individual pages or aggregate data for pages that share a template or other defining characteristics.