Add components to the framework that gather the data to send to Adobe Analytics. Components that are designed to gather analytics data store the data in the appropriate CQ variable. When you add such a component to a framework, the framework displays the list of CQ variables so that you can each to the appropriate Analytics variable.

When the AEM view is open the Analytics variables appear in the content finder.

You can map the same Analytics variable with multiple CQ variables. You can also map multiple Analytics variables with the same CQ variable.

The mapped data is sent to Adobe Analytics when the page loads and the following conditions are met:

The page is associated with the framework.

The page uses the components that are added to the framework.

Use the following procedure to map CQ component variables with Adobe Analytics report properties.

In the AEM view, drag a tracking component from sidekick onto the framework. For example, drag the Page component component from the General category.

There are several default component groups: General, Commerce, Communities, Search&Promote, and Other. Your AEM instance may be configured to display different groups and components.

To map Adobe Analytics variables with variables that are defined in the component, drag an Analytics variable from the content finder onto a field on the tracking component. For example, drag Page Name (pageName) to pagedata.title.

Note:

The Report Suite ID that is selected for the framework determines the Adobe Analytics variables that appear in the content finder.

When an RSID is selected all the variables belonging to that RSID get added to the list.
The cf# is needed in order to map Analytics variables to the CQ variables present on the different tracking components. See Setting Up a Framework for Basic Tracking.

Depending on the view selected for the framework, the content finder will be populated by either Analytics variables (in AEM view) or CQ variables (in Analytics view).

The list can be manipulated in the following ways:

When in AEM view, the list can be filtered depending on what variable type is selected using the 3 filter buttons:

If No button is selected, the list shows the full list.

If the Traffic button is selected, the list will only show the variables belonging to the Traffic section

If the Conversion button is selected, the list will only show the variables belonging to the Conversion section.

If the Events button is selected, the list will only show the variables belonging to the Events section.

Note:

Only one filter button can be active at once.

Note:

Search&Promote variables belong to the Conversion section as well.

The list also has a search feature, which filters the elements according to the text entered in the search field.

If a filter option is activated while searching for elements in the list, the results displayed will be filtered according to the active button as well.

The list can be reloaded at any time using the swirly-arrows button.

If multiple RSIDs are selected on the framework, all variables in the list will be displayed using all labels used within the RSIDs selected.

When in Adobe Analytics view, the Content Finder displays all CQ variables belonging to the tracking components dragged in CQ view.

e.g. in case the Download component is the only one dragged in CQ view (which has two mappable variables eventdata.downloadLink and eventdata.events.startDownload), the Content Finder wil look like this when switching to Adobe Analytics view:

The variables can be dragged&dropped onto any Adobe Analytics variable belonging to either one of the 3 variable sections (Traffic, Conversion and Events).

When dragging a new tracking component onto the framework in CQ view, the CQ variables belonging to the component get automatically added to the Content Finder(cf#) in Adobe Analytics view.

Note:

Only one CQ variable can be mapped to a Adobe Analytics variable at once

Using CQ view and Adobe Analytics view

At any given time, users have the option to switch between 2 ways of viewing the Adobe Analytics mappings when on a framework page. The 2 views provide a better overview of the mappings within the framework, from 2 distinct perspectives.

CQ View

Taking the above image as an example, the CQ view has the following properties:

This is the default view the framework opens to.

Arrow 1 - the content finder(cf#) is populated by Adobe Analytics variables based on the RSID(s) selected

Arrow 2 - this is where you can swich between the 2 views

Arrow 3 - if the framework has components that are inherited from its parent, they will be listed here, along with the variables mapped to the components.

Notice that the inherited Download component is "locked"

To unlock the inhertited component, just double-click on the padlock next to the component's name

In order to revert the inheritance you must delete the unlocked component; after which it will regain its "locked" status.

Arrow 4 - You can find all of the components that are currently included in the analytics framework

To add a component drag&drop one from the SideKick's Components tab

To delete a component and all of its mappings:

press Delete if you're on Windows OR press Function+Delete if you're on a Mac; then accept the deletion on thE confirmation dialogue

Right-click and select Delete from the menu then accept the deletion on the confirmation dialogue

Keep in mind that a component can only be deleted from the framework it was created in, and cannot be deleted from child frameworks in the traditional sense. (they can only be overwritten)

Drag components here to include them in the analytics framework - Components from the Sidekick can be drag&dropped here.

Adobe Analytics View

This view can be accessed by switching to the Adobe Analytics tab on the framework.

Arrow 1 - Content Finder(cf#) populated by CQ variables based on the components dragged onto the framework in CQ view.

Arrow 2 - Switch back to CQ view from here

The 3 tables (Traffic, Conversion, Event) list all available Adobe Analytics variables belonging to the RSID(s) selected. The mappings shown here should be the same as in CQ view: