Learn how to map data captured from an Adobe Experience Manager Site to metrics and dimensions in Adobe Analytics report suites. Learn how to build a detailed reporting dashboard using the Analysis Workspace feature of Adobe Analytics.
The WKND marketing team wants to understand which Call to Action (CTA) buttons perform best on the home page. In this tutorial, we will create a new project in the Analysis Workspace to visualize the performance of different CTA buttons and understand user behavior on the site. The following information gets captured using Adobe Analytics when a user clicks a Call to Action (CTA) button on the WKND home page.
Analytics Variables
Below are the Analytics variables currently being tracked:
eVar5
- Page template
eVar6
- Page Id
eVar7
- Page last modified date
eVar8
- CTA Button Id
eVar9
- Page Name
event8
- CTA Button Click event
prop8
- CTA Button Id
This tutorial is a continuation of the Track clicked component with Adobe Analytics and assumes that you have:
The Custom Insight Conversion Variable (or eVar) is placed in the Adobe code on your site’s selected web pages. Its primary purpose is to segment conversion success metrics in custom marketing reports. An eVar can be visit-based and function similarly to cookies. Values passed into eVar variables follow the user for a predetermined period.
When an eVar is set to a visitor’s value, Adobe automatically remembers that value until it expires. Any success events that a visitor encounters while the eVar value is active are counted toward the eVar value.
eVars are best used to measure cause and effect, such as:
Success events are actions that can be tracked. You determine what a success event is. For example, if a visitor clicks a CTA button, the click event could be considered a success event.
From the Adobe Experience Cloud home page, select your organization, and launch Adobe Analytics.
From the Analytics toolbar, click on Admin > Report Suites and find your Report Suite.
Select the Report Suite > Edit Settings > Conversion > Conversion Variables
Using the Add new option, let’s create Conversion Variables to map the schema as below:
eVar5
- Page Template
eVar6
- Page ID
eVar7
- Last Modified Date
eVar8
- Button Id
eVar9
- Page Name
Provide an appropriate name and description for each eVars and Save your changes. We will be using these eVars to create an Analysis Workspace project in the next section. So, a user-friendly name makes the variables easily discoverable.
Next, let’s create an even to track the CTA Button click.
From the Report Suite Manager window, select the Report Suite Id and click Edit Settings.
Click Conversion > Success Events
Using the Add New option, create a new custom success event to track the CTA Button click and then Save your changes.
Event
: event8
Name
:CTA Click
Type
:Counter
Analysis Workspace is a flexible browser tool that allows you to build analyses and share insights quickly. Using the drag-and-drop interface, you can craft your analysis, add visualizations to bring data to life, curate a dataset, share, and schedule projects with anyone in your organization.
Next, create a new project to build a dashboard to analyze the performance of the CTA buttons throughout the site.
From the Analytics toolbar, select Workspace and click to Create a New Project.
Choose to start from a blank project or select one of the pre-built templates, either provided by Adobe or custom templates created by your organization. Several templates are available, depending on the analysis or use case you have in mind. Learn more about the different template options available.
In your Workspace project, panels, tables, visualizations, and components are accessed from the left rail. These are your project building blocks.
Next, build a table to create a visual representation of how users interact with Call to Action (CTA) buttons on the WKND Site home page. To build such a representation, let’s use the data collected in the Track clicked component with Adobe Analytics. Below is a quick summary of data tracked for user interactions with the Call to Action buttons for the WKND Site.
eVar5
- Page template
eVar6
- Page Id
eVar7
- Page last modified date
eVar8
- CTA Button Id
eVar9
- Page Name
event8
- CTA Button Click event
prop8
- CTA Button Id
Drag-drop the Page dimension component onto the Freeform Table. You should now be able to view a visualization that displays the Page Name (eVar9) and corresponding Page Views (Occurrences) displayed within the table.
Drag-drop the CTA Click (event8) metric onto the occurrences metric and replace it. You could now view a visualization that displays the Page Name (eVar9) and a corresponding count of CTA Click events on a page.
Let’s break down the by page by its template type. Select the page template metric from components, and drag-drop the Page Template metric onto the Page Name dimension. You could now view the page name broken down by its template type.
Before
After
To understand how users interact with CTA Buttons when they are on the WKND Site pages, we need to further breakdown the Page Template metric by adding the Button ID (eVar8) metric.
Below you can see a visual representation of the WKND Site broken down by its page template and further broken down by user interaction with the WKND Site Click to Action (CTA) Buttons.
You could replace the Button ID value with a more user-friendly name using the Adobe Analytics Classifications. You could read more about how to create a classification for a specific metric here. In this case, we have a classification metric Button Section (Button ID)
setup for eVar8
that maps button id to a user-friendly name.
Analytics Classification is a way of categorizing Analytics variable data, then displaying the data in different ways when you generate reports. To improve how Button ID gets displayed in the Analytics Workspace report, let’s create a classification variable for Button Id (eVar8). When classifying, you are establishing a relationship between the variable and the metadata related to that variable.
Next, let’s create a Classification for Analytics variable.
From the Admin toolbar menu, Select Report Suites
Select the Report Suite Id from the Report Suite Manager window and click Edit Settings > Conversion > Conversion Classifications
From the Select Classification Type drop-down list, select the variable (eVar8-Button ID) to add a classification.
Click on the arrow right next to the Classification variable listed under the Classifications section to add a new Classification.
In the Edit a Classification dialog box, provide a suitable name for the Text Classification. A dimension component with the Text Classification name gets created.
Save your changes.
Use the importer to upload classifications into Adobe Analytics. You can also export the data for updating before an import. The data that you import using the import tool must be in a specific format. Adobe provides you with the option to download a data template with all the proper header details in a tab-delimited data file. You can add your new data to this template and then import the data file in the browser using FTP.
Before importing classifications into marketing reports, you can download a template that helps you create a classifications data file. The data file uses your desired classifications as column headings, then organizes the reporting data set under the appropriate classification headings.
Next, let’s download the Classification Template for the Button Id (eVar8) variable
Navigate to Admin > Classification Importer
Let’s download a Classification template for the conversion variable from the Download Template Tab.
On the Download Template tab, specify the data template configuration.
Click Download and save the template file to your local system. The template file is a tab-delimited data file (.tab filename extension) that most spreadsheet applications support.
Open the tab-delimited data file using an editor of your choice.
Add the Button ID (eVar9) and a corresponding button name to the tab-delimited file for each eVar9 value from Step 9 in the section.
Save the tab-delimited file.
Navigate to the Import File tab.
Configure the Destination for the file import.
Click on the Choose File option to upload the tab-delimited file from your system, and then click on Import File
A successful import immediately displays the appropriate changes in an export. However, data changes in reports take up to four hours when using a browser import and up to 24 hours when using an FTP import.
From the Analytics toolbar, select Workspace and open the workspace we created in Create a new project in Analysis Workspace section of this tutorial.
Next, replace the Button Id metric in your workspace that displays the ID of a Call to Action (CTA) button with the classification name created in the previous step.
From the component finder, search for WKND CTA Buttons and drag-drop the WKND CTA Buttons (Button Id) dimension onto the Button Id metric and replace it.
You can notice the Button Id metric that contained the button id of a Call to Action (CTA) button is now replaced with a corresponding name provided in the Classification Template.
Let’s compare the Analytics Workspace table to the WKND Home page and understand the CTA Button click count and its analysis. Based on the workspace freeform table data, it is clear that 22 times users have clicked on the SKI NOW button and four times for the WKND Home Page Camping in Western Australia Read More button.
Make sure to save your Adobe Analytics Workspace project and provide a proper name and description. Optionally, you could add tags to a workspace project.
After successfully saving your project, you could share your workspace project with other co-workers or teammates using the Share option.
You just learned how to map data captured from an Adobe Experience Manager Site to metrics and dimensions in Adobe Analytics report suites, perform a Classification for the metrics, and build a detailed reporting dashboard using the Analysis Workspace feature of Adobe Analytics.