Content Analytics data collection

Last update: May 30, 2025

CREATED FOR:

  • Admin

This article explains in detail how Content Analytics collects data

Definitions

The following definitions are used in the context of this article:

  • Experience: An experience is defined as the text content on a whole web page. For data collection, Content Analytics records the Experience ID which is based on the page url. Later, the text on the page is captured via the retrieval service.

  • Experience ID: A unique combination of relevant URL (base URL plus any parameters that drive content on the page) and experience version.

    • You specify, as part of the configuration, which parameters are relevant for any given full URL.
    • You define a version identifier to use, so you properly collect changes to your experiences.

  • Asset: An image. Content Analytics records the asset URL.

  • Asset ID: The URL of the asset.

  • Relevant URL: The base URL plus any parameters that drive content on the page.

Functionality

Content Analytics requires the Experience Platform Edge Network Web SDK to collect content event data. That event data collection is combined with the (existing) data collection of behavioral event data through mechanisms like Experience Platform Edge Network (Web SDK, Server API) or Analytics source connector (for example, using AppMeasurement).

The Content Analytics library collects data when:

  • Content Analytics is included in the Tags library that is loaded on the page.
  • The page URL is configured in the Content Analytics extension, part of the included Tags library.

Content Analytics event

A Content Analytics event consists of:

  • Standard fields

    • Timestamp
    • Identity

  • Experience views (if any, and if configured)

  • Experience clicks (if any, and if configured)

  • Asset views (if any, and if configured)

  • Asset clicks (if any, and if configured)

Content Analytics events are collected as a sequence of:

Content Analytics does collect data this way to reflect that sequence, instead of collecting a view or click separately from collecting the event immediately following that view or click. This way of collecting content analytics data also reduces the amount of data collected.

Recorded view or click

An asset view is recorded when:

  • The asset has not been excluded per Content Analytics extension configuration.
  • The asset is 75% in view.
  • That asset has not already been recorded for this page.

An asset click is recorded when:

  • The asset has been viewed.
  • The asset has not been excluded per Content Analytics extension configuration.
  • A click directly on the asset, which is a link, that leads to another page.

An experience view is recorded when:

  • Experiences are enabled in the Content Analytics configuration.

An experience click is recorded when:

  • Any click occurs on a link on the page for which experiences are enabled.