Content Analytics - Create configuration

Hi, this is Shay O’Reilly, a product manager with Adobe. Join me to learn about how to configure content analytics using our streamlined implementation workflow. Before setting up content analytics, you will need to covered the following of customer journey analytics already in place. Know the data view you would like to use for content analytics reporting permissions for all aspects of configuring this implementation. The onboarding workflow makes it easy to take all the steps involved in a setup, but you’ll need permission for all the actions needed to implement content analytics, and you’ll need rights to administer. Create an experienced platform. You will need rights to create data sets and schemas as well as data flows. Finally, in tags, you’ll need permission to create and edit tags properties as well as create and configure data streams. Lastly, as part of content analytics, Adobe will retrieve images and text from your site. Refer to our documentation to ensure our retrieval service can access the relevant parts of your site. Let’s jump into it. For content analytics, we provide a streamlined way to implement content analytics from end to end. This includes configuring data collection with tags, data processing and storage, and experience platform and reporting in CJA. To get started, choose Content Analytics Configuration from the Data Management menu. This will show a list of configurations that have been created. A configuration is a full end to end implementation of content analytics from data collection through to reporting. From this page, you can choose to create a new configuration or edit existing configurations. Let’s start with creating a new configuration by clicking Create Configuration in the top right.

This will take you to a form that collects the minimal amount of information needed to set up a Content analytics configuration. First, notice the options at the top right. You can discard your work so far, save it for later or when you’ve provided enough information you can implement. First, let’s provide a name the next piece of information is a data view. When you select data view, you will be taken to a list of data views available for selection. From here we will choose a single data view to save. We get a message about the changes that are made. This will indicate which data view should get updated with relevant dimensions components for reporting. You will update the connection that is relevant pull in Content Analytics data sets, and will indicate which sandbox is used.

The next section is Experience Capture and Definition. Experiences are only suitable for sites where the text on the page is determined solely by the URL. If there is a dynamic content or other factors, Adobe will not be able to reproduce the content that the user saw. For this reason, we default the experience to others. If you do want to capture and report on experiences, turn the tackle to on.

This exposes some additional settings that indicate what parts of the URL drive text content to your site. For the first setting domain, regular expression lets you specify which domains or parts of your site should be affected. So in this case, we’re talking about Adobe store products. Next, you provide query parameters to indicate which query parameters are most relevant. These parameters apply to pages specified in the domain. Regular expression. You can add additional pairs of domain regular expression and query parameters if you want.

Finally, the last piece of information is around data collection. First, you indicate a tags property. You can choose an existing one or create a new one. We’re going to choose an existing one. In this case. And you configure the content analytics extension itself within the tags property. First you indicated which pages to include or exclude. So for here I’m providing a regular expression that says you can ignore parts of the URLs that include documentation in them. So we don’t want to do content analysis for that. It’s not something I optimize content performance for. And then for pages that do collect data, you can indicate which assets should be included or excluded. In this case, I’ve indicated that logos can be excluded from data collection whenever the URL of the asset has a as the word logo in it, it will be excluded. Since this is not something I particularly want to analyze. That’s it. You’ve read enough information to configure content analytics. At the bottom of the page, you can see a list of what will be added if you click implement. Note that you can choose save for later if you want to return to implementing. Let’s review what’s going to be created. You create a project template in the chosen data view. We’ll update the chosen data view to include content analytics components. The connection associated with the chosen data. You will be updated to include the new data sets created for content analytics. So this data will be blended with whatever data is already present in the connection. In experience platform, we will create three 2 to 3 data sets. One will capture content interaction events directly from the web SDK. The others will be look up data sets for assets and experiences in your content event data set. If you configured experiences, there will be a second look up for the experiences themselves. Finally, in the data collection side, we will create a data stream to receive content analytics events from the web SDK and route them to the Content Analytics event data set. You will configure a tags property to collect the data based on the inputs provided. And that’s it. To implement you just click implement and this will begin your process. It will be done in a matter of minutes.