---
title: "Enriching Page and Content Analytics via CMS APIs"
slug: "enriching-page-and-content-analytics-via-cms-apis"
updated: 2026-01-29T10:41:46Z
published: 2026-01-29T10:41:46Z
canonical: "docs.mapp.com/enriching-page-and-content-analytics-via-cms-apis"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mapp.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Enriching Page and Content Analytics via CMS APIs

This best practice describes how page- and content-level analytics data can be enriched using structural information from a CMS, independent of client-side tracking.

---

### Context & Challenge

- Page analytics often relies on client-side tracking only
- Browser-based tracking has limitations:
  - consent and privacy restrictions
  - limited contextual data at runtime
- As a result, page and content context is often missing in analytics

---

### Focus of This Best Practice

- This best practice focuses on **page- and content-level enrichment**
- It enriches analytics data with **structural information from a CMS**
- It does **not** address:
  - user or customer attributes
  - campaign or product data

---

### Core Idea

- Content structure already exists in the CMS
- This data is stable, authoritative, and centrally maintained
- Instead of sending it via the tracking pixel:
  - it is retrieved via CMS APIs
  - processed outside the browser
  - imported periodically into Mapp Intelligence
- Page analytics gains context without increasing tracking complexity

---

### Typical CMS-Based Enrichment Data

- Content categories and hierarchies
- Navigation or documentation structure
- Content or page type
- Editorial metadata
- Stable classifications not available at runtime

---

### Conceptual Architecture

- Tracking sends a **stable page or content identifier**
- The same identifier exists in the CMS
- CMS APIs expose structural metadata for that identifier
- Data is imported into Mapp Intelligence on a regular schedule
- Page-level analytics is enriched independently of user traffic

---

### Using Data Feeds for CMS-Based Page Enrichment

In Mapp Intelligence, CMS-based page and content enrichment is typically implemented using Data Feeds as a server-side import mechanism.

- Data Feeds provide a server-side import mechanism for structured data
- They allow page- or content-level metadata to be uploaded independently of page views
- Imported data can be mapped to existing pages using a stable page or content identifier
- This makes Data Feeds a natural fit for CMS-driven content enrichment scenarios

---

### Relation to Pixel-Based Tracking

- Pixel tracking captures behaviour and interactions
- CMS-based enrichment adds structure and context
- Both approaches complement each other

---

### Example Scenario

- A CMS manages structured content and taxonomy
- Tracking sends a unique page or content identifier
- The CMS exposes structural metadata for the same identifier via API
- This metadata is imported into Mapp Intelligence
- Pages are automatically assigned to meaningful content groups
- No changes to the live tracking setup are required

---

### When to Consider This Approach

- Page context cannot be reliably sent via the tracking pixel
- Content structure changes independently of page views
- Consistent content classification is required over time
- Analytics should not depend on browser execution

---

### Benefits

- Richer page and content analysis
- Cleaner client-side tracking
- Clear separation of behaviour and structure
- More robust analytics architecture