Configure Content Analytics
This article documents, on a high level, how to configure Content Analytics.
Before you configure Content Analytics, you must ensure the prerequisites are met, you do have the required access control, and you are aware of the limitations.
High-level steps
-
Use the Content Analytics guided configuration wizard to guide you through all steps required to set up the prerequisites for a configuration of Content Analytics. You can save your configurations at any time and return later.
-
Once you are comfortable with the configuration values, you can implement the configuration. This implementation creates all the required artifacts, based on what you have configured in the wizard.
-
Only when you manually publish the Tags property, your Content Analytics configuration is effectively deployed and data collection is started.
-
You can only make some minor changes to an implemented configuration using the guided configuration wizard. For example, change the data view.
-
You can make other changes to an implemented configuration using the Adobe Content Analytics extension in the associated Tags property.
-
Only when you manually re-publish the Tags property, the configuration modifications are effectively deployed and data collection, based on your changes, is started.
Prerequisites
Before you configure Content Analytics, ensure that the following prerequisites are met:
-
You have allow-listed the User Agent and IP address for the featurization service that is used in Content Analytics. The User Agent string to configure is:
AdobeFeaturization/1.0. -
If you have implemented the Web SDK using JavaScript for regular behavioral data collection, ensure you are using the default name
alloyfor the JavaScript library. -
You have a Customer Journey Analytics Product Administrator role, with the additional permissions to manage connections and to manage data views.
-
If you consider to collect Content Analytics experiences, ensure you setup and update Content Analytics versioning based on changes on your web pages.
-
You must have permissions for data collection:
-
You have carefully considered the following important configuration options:
-
Your site is suited for experience reporting. Proper experience reporting is only possible when the following conditions are met:
- The pages on the site must be reproducible using the page URL.
- The text content seen by any given user can be reproduced using the page URL and does not depend on cookies or other personalization mechanisms.
-
You have a clear understanding for which pages you want to capture content engagement analysis and insights.
-
You have a clear understanding for which (type of) assets you want to capture content engagement analysis and insights.
-
Access control
To provide a user or group of users access to Content Analytics, you must provide the user or group of users access to one or more data views that are configured for Content Analytics.
This access implies:
- The Content Analytics enabled data view is included as part of the Data View permissions for a specific Customer Journey Analytics product profile.
- That specific Customer Journey Analytics product profile is one of the product profiles assigned to the user or group of users.
Limitations
The schema used for Content Analytics event data is system-owned. A system-owned schema cannot be modified, which implies:
- You cannot include field groups for the support of functionalities like geolocation, bot detection, or device lookup.
- You cannot add a specific identifier to support field-based stitching.