Documentation Customer Journey Analytics Customer Journey Analytics Guide

Content Analytics guided configuration

April 4, 2025

Topics:
Content Analytics

CREATED FOR:

Admin

AVAILABILITY

The functionality described in this article is in the Limited Testing phase of release and might not be available yet in your environment. This note will be removed when the functionality is generally available. For information about the Customer Journey Analytics release process, see Customer Journey Analytics feature releases.

The guided configuration helps you to configure Content Analytics quickly and easily. The guided configuration uses a wizard to set up the requirements to configure Content Analytics automatically for your organization. In the Configuration screen, you can either create a new configuration or edit an existing configuration.

IMPORTANT

You can only have one Content Analytics configuration per sandbox in your organization.

To access the Content Analytics configuration

Select Data Management > Content Analytics Configuration from the main menu in Customer Journey Analytics.

In the Content Analytics Configurations screen, you see a table of existing Content Analytics configurations.

Content Analytics configurations
For each configuration, the following details are available:

Column

Description

Name

The name of the configuration.

Created by

The technical account that created the configuration.

Created on

The timestamp when the configuration was created.

Modified on

The timestamp when the configuration was last modified.

Sandbox

The sandbox within the organization in which Content Analytics is (planned to be) configured and implemented.

Status

The status of the configuration. The status can be:

Draft: The configuration is Saved for later, and not deployed.

Failed: The configuration has failed. You can select Edit to get information about the failure. Adobe proactively addresses any failed implementations. You can reach out to Customer Care for details.

Complete: the configuration has been completed and implemented successfully.

You can use to customize the table. Select which columns to display in the Customize table dialog and select Apply to apply the changes.

From the Content Analytics Configuration screen, you can create a new configuration or edit an existing configuration.

To create a new configuration:

Select Create configuration. This action opens the guided configuration wizard.

To edit an existing configuration:

Select and then Edit for an existing Content Analytics configuration. This action opens the guided configuration wizard.

Guided configuration wizard

The guided configuration wizard consists of four sections (Details, Data view, Experience capture & definition, and Data collection), each prompting you for details that are required to set up and configure Content Analytics properly. Complete each section before moving to the next section, as some settings in a section might depend on configuration values in earlier sections.

Details

Each configuration requires a unique name. For example, Example Content Analytics configuration. The name is required to save or implement a configuration.

Content Analytics configuration details

Data view

Your configuration requires the selection of a Data view.

Select a Data view
- To select a new Data view for a configuration, use Select Data view.
- To modify a Data view for a configuration, select Edit.
In both scenarios, you see a Data view dialog, where you can select a Data view for your configuration.

For a new configuration, the list only shows Data views that are associated with sandboxes that do not have an active configuration. Also, you only see data views associated with sandboxes that you have access to and connections you have the rights to modify.

If you edit an existing configuration, the list only shows Data views available within the sandbox already associated with the existing configuration.

You can perform the following actions:
- To search for a specific Data view, use the field.
- To filter the list of available Data views, select . You can filter the list on Connection, Owner and Sandbox.
  Use Hide filters to hide the filter pane.
- To define which columns to show in the table, select . Select which columns to display in the Customize table dialog and select Apply to apply the changes.
Select the Data view that you want to use.
Select Save to confirm the selected Data view. Select Cancel to cancel.

In Customer Journey Analytics, a Data view is tied to a Customer Journey Analytics Connection. And a Connection is based on a sandbox within your organization. Once you save the configuration, Sandbox is auto populated with the name of the sandbox, based on the selected Data view.

Experience capture and definition

In this section, you can select to include Experiences in the data you collect with Content Analytics. An experience is all text on a web page that is reproducible using the URL used by the initial user visiting that web page.

By default, Include experiences is turned off. When selected, you have to define for which URLs you want to include experiences.

Only consider to include experiences when the following is applicable:

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 depends on cookies or other personalization mechanisms.

To include Experiences in a new or not implemented configuration:

Content Analytics configuration Experience capture and definition

Enable Include experiences. The toggle to enable experiences affects the following:
- Data collection in the Content Analytics extension
- The process that generates experience attributes from Content Analytics event data
- The reporting template in Customer Journey Analytics.
Specify the parameters for how content is rendered on your website. The parameters are zero or more combinations of a Domain regular expression and Query parameters. The query parameters indicate what parameters affect the content on your page. This input allows Content Analytics to ignore any parameters that don’t affect content on the page, when defining a unique experience.
1. Enter a Domain regular expression, for example /^(?!.*\b(store|help|admin)\b)/. Ensure you escape regular expressions, using /. The domain regular expression indicates which URLs these parameters apply to. For example, you may have multiple sites, and for each site different parameters drive the content. If the query parameters apply to all of your pages, then you can use .* to indicate all pages.
2. Specify a comma separated list of Query parameters, for example outdoors, patio, kitchen.
Select Remove if you want to remove a combination of domain regular expression and query parameters.
Select Add Regex if you want to add another combination of a regular expression and query parameters.

To edit existing or include new Experiences in an implemented configuration:

Content Analytics configuration Experience capture and definition

Toggle Include experiences to enable or disable the availability of experience components, visualizations, panels and templates in Analysis Workspace.
Select Edit to further edit the configuration of data collection for experiences in Content Analytics. You are redirected to the Adobe Content Analytics extension in the Tags property that is associated with the current configuration.

Data collection

In this section, you configure how to collect your content analytics data.

New configuration

In a new configuration, you need to define whether you want to use an existing Tags property or create a new Tags property. And you need to define the pages and assets you want to include or exclude, using regular expressions.

To use an existing Tags property:
1. Select Choose existing.
2. Select an existing property from the Tags property dropdown menu. You can start typing to search for and limit the available options. You cannot select a Tags property that already is used by another implemented Content Analytics configuration.
To create a new Tags property:
1. Select Create new.
2. Specify a Tags name, for example ACA Test for Documentation.
3. Specify Domains, for example, example.com.
Indicate which pages should be included or excluded when collecting data for Content Analytics.

Specify a Regular expression string for Pages to include / exclude.
For example: ^(?!.*documentation).* to exclude all documentation pages from Content Analytics.
Indicate which assets should be included or excluded when collecting data for Content Analytics.

Specify a Regular expression string for Assets to include / exclude.
For example: ^(?!.*(logo\.jpg|\.svg)).*$ to exclude all logo JPEG and SVG images from Content Analytics.

IMPORTANT

In case you have an existing Web SDK implementation using Javascript, and not using Tags, you have to manually remove the automatic included Web SDK extension from the newly created Tags property.

Existing configuration

For an existing configuration, you cannot edit the Tags property. You can, however, edit the pages and assets to include or exclude.

To edit which pages should be included or excluded when collecting data for Content Analytics, select Edit underneath Experience. You are redirected to the Adobe Content Analytics extension that is associated with the Tags property for the current Content Analytics configuration. You can edit the regular expression to include or exclude pages. Ensure you publish your changes.
To edit which assets should be included or excluded when collecting data for Content Analytics, select Edit underneath Asset. You are redirected to the Adobe Content Analytics extension that is associated with the Tags property for the current Content Analytics configuration. You can edit the regular expression to include or exclude assets. Ensure you publish your changes.

Summary

Once you have provided all necessary details, a summary provides details on the artifacts that are created or modified.

You see a You’re almost ready to implement configuration name for Content Analytics summary when you implement a new configuration.
For existing implemented configurations, you see a You have implemented configuration name for Content Analytics summary.

Content Analytics Configuration Summary

Actions

When you create or edit a configuration you have these options:

Discard: All changes made as part of configuration are discarded.
Save for later: Changes made to a configuration are saved. You can revisit the configuration at a later stage to make further changes, or implement the configuration. Only a value for Name is required to save a configuration.
Implement: Settings for or changes made to a configuration are saved and implemented. All fields marked as required need to have proper values. The implementation consists of:
- Customer Journey Analytics configuration:
  - The selected Data view is updated to include Content Analytics dimension and metrics.
  - The Connection tied to the selected Data view is modified to include Content Analytics events and attributes datasets.
  - A Content Analytics reporting template is added to Workspace.
- Adobe Experience Platform configuration:
  - The creation of schemas to model Content Analytics events, asset attributes, and (if configured) experience attributes.
  - The creation of datasets to collect Content Analytics events, asset attributes and (if configured) experience attributes.
  - The creation of a dataflow that uses the featurization service to generate and update content attributes from Content Analytics events.
- Data collection configuration:
  - The new or existing Tags property is configured to support Content Analytics data collection. This configuration implies the inclusion of the Adobe Content Analytics extension for Tags.
  - A datastream is created for Content Analytics events.
  - The Adobe Content Analytics extension is configured to ensure that Content Analytics events are sent to the datastream for Content Analytics.
  - If the Web SDK is not configured for the Tags property, a new Web SDK configuration is created to send only Content Analytics events.
  - If the Web SDK is configured for this Tags property, no changes are made to the existing Web SDK configuration.
Save: Changes made to an implemented configuration are saved and the implementation is updated.
Exit. Exits the guided configuration. All changes made to an implemented configuration are discarded.

Publish

To start collecting data for your Content Analytics configuration, you need to manually publish the Tags property that is created after you selected Implement.

recommendation-more-help