버전용 도움말 콘텐츠:

Add components to the framework that gather the data to send to SiteCatalyst. Components that are designed to gather analytics data store the data in CQ variables. When you add such a component to a framework, the framework displays the list of CQ variables so that you can map them to SiteCatalyst variables. The SiteCatalyst variables appear in Content Finder. 

chlImage_1

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

chlImage_1

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

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

  1. Drag a tracking component from SideKick onto the framework. For example, drag the Page component component from the General category. 

    drag-component

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

  2. To map SiteCatalyst variables with variables that are defined in the component, drag a SiteCatalyst variable from Content Finder onto a field on the tracking component. For example, drag Page Name (pageName) to pagedata.title.

    drag-variable

    참고:

    The Report Suite ID that is selected for the framework determines the SiteCatalyst variables that appear in Content Finder.

  3. Repeat the previous two steps with other components and variables.

    참고:

    You can map multiple SiteCatalyst variables (i.e. props, eVars, events) to the same CQ variable (e.g. pagedata.title)

    경고:

    It is highly recommended that eVars and props are mapped to CQ variables beginning with either pagedata.X or eventdata.X whereas events should be mapped to variables starting with eventdata.events.X

  4. To make the framework available on the Publish instance of your site, on the Page tab of  idekick, click Activate Framework.

Mapping Product-Related Variables

AEM uses a convention for naming product-related variables and events that are meant to be mapped to SiteCatalyst product-related properties:

CQ Variable SiteCatalyst Property Description
product.category product.category (conversion variable) The product category.
product.sku product.sku (conversion variable) The product sku.
product.quantity product.quantity (conversion variable) The number of products being purchased.
product.price product.price (conversion variable) The product price.
product.events.eventName The success event(s) to associate with the product in your report. product.events is the prefix for events named eventName.
product.evars.eVarName The conversion variable(s) (eVar) to associate with the product. product.evars is the prefix for eVar variables named eVarName.

Several AEM eCommerce components use these variable names.

참고:

Do not map the SiteCatalyst Products property to a CQ variable. Configuring product-related mappings as described in the table is effectively equivalent to mapping the Products variable. 

Editing and deleting SiteCatalyst Configurations and Frameworks

To delete a particular SiteCatalyst configuration or framework, do the following:

  1. From the Welcome screen, go to Tools > Cloud Services Configurations > Adobe SiteCatalyst
    • To delete frameworks, go one node deeper by choosing the SiteCatalyst configuration the framework belongs to.
  2. Choose the configuration or framework you want to delete from the panel on the right.
  3. Right-click it and select Delete from the menu that pops up.
  4. Confirm the deletion of the configuration or framework.

There are two possible ways to edit SiteCatalyst configurations and frameworks within AEM.

  1. Go to Tools > Cloud Services Configurations > Adobe SiteCatalyst
  2. Choose a configuration/framework from the panel on the right.
    • To open up a framework page for editing, you need to go at least one node deeper, by first choosing the SiteCatalyst configuration the framework belongs to.
  3. Double click the configuration or framework in the panel to the right to open it for editing.

The other way is:

  1. Go to the Cloud services dashboard from the Welcome screen
  2. Select the SiteCatalyst menu item on the dashboard
  3. Press the Show configurations button
  4. Select one of the configurations or frameworks from the tree to open it for editing.

참고:

When editing SiteCatalyst configurations, you also need to press the Edit button when on the configuration page itself in order to bring up the Edit panel.

Checking reports on SiteCatalyst

  1. Go to the Sitecatalyst website (https://sitecatalyst.omniture.com) and log in using the same credentials provided within AEM.
  2. Make sure the RSID selected is the one used in the previous steps.
  3. In Reports (on the left side of the page) select Custom Conversion > Custom Conversion 1-10 and select the variable coresponding to eVar7
  4. Depending on the SiteCatalyst version you are using, you need to wait on average 45 minutes in order for the report to get updated with the search term used as an example (i.e. aubergine)

Using the Content Finder (cf#) on a SiteCatalyst Analytics framework

Initially, when you open a SiteCatalyst framework the Content Finder contains the following predefined SiteCatalyst variables:

  • Traffic variables: channel, pageName, pageType, pageURL, server, hier1, hier2, hier3, hier4, hier5
  • Conversion variables: purchaseID, campaign, transactionID, visitorID, products, product.category, product.sku, product.quantity, product.price, state, zip, list1, list2, list3
  • Events: prodView

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 SiteCatalyst 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 SiteCatalyst variables (in AEM view) or CQ variables (in SiteCatalyst view).

The list can be manipulated in the following ways:

  1. 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.

참고:

Only one filter button can be active at once.

참고:

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

  1. The list also has a search feature, which filters the elements according to the text entered in the search field.
  2. 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.
  3. The list can be reloaded at any time using the swirly-arrows button.
  4. If multiple RSIDs are selected on the framework, all variables in the list will be displayed using all labels used within the RSIDs selected.
  1. When in SiteCatalyst 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 SiteCatalyst view:

  • The variables can be dragged&dropped onto any SiteCatalyst 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 SiteCatalyst view.

참고:

Only one CQ variable can be mapped to a SiteCatalyst variable at once

Using CQ view and SiteCatalyst view

At any given time, users have the option to switch between 2 ways of viewing the SiteCatalyst 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:

  1. This is the default view the framework opens to.
  2. Arrow 1 - the content finder(cf#) is populated by SiteCatalyst variables based on the RSID(s) selected
    • For more information on how to use the Content Finder please consult this tutorial
  3. Arrow 2 - this is where you can swich between the 2 views
  4. 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.
  5. 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)
  6. Drag components here to include them in the analytics framework - Components from the Sideckick can be drag&dropped here.

SiteCatalyst View

  1. This view can be accessed by switching to the Sitecatalyst tab on the framework. 
  2. Arrow 1 - Content Finder(cf#) populated by CQ variables based on the components dragged onto the framework in CQ view.
    • For more information on this please consult this tutorial.
  3. Arrow 2 - Switch back to CQ view from here
  4. The 3 tables (Traffic, Conversion, Event) list all available SiteCatalyst variables belonging to the RSID(s) selected. The mappings shown here should be the same as in CQ view:
    • Arrow 3.a - Traffic variable (prop1) mapped to a CQ variable (eventdata.downloadLink)
      • Notice that the component has a Padlock next to it - this means it is inherited from a parent framework and thus cannot be edited
    • Arrow 3.b - Conversion variable (eVar1) mapped to a CQ variable (pagedata.title)
    • Arrow 3.c - Conversion variable (eVar3) mapped to a javascript expression added inline by double-clicking on the CQ variable field and entering the code manually
    • Arrow 3.d - Event variable (event1) mapped to a CQ event (eventdata.events.pageView)

참고:

Only one CQ variable can be mapped to a SiteCatalyst variable at any given time.

  1. Every table’s CQ variable column can be filled inline as well, by double-clicking on the field and adding text to it. These fields accept javascript as an input.
    • e.g. next to prop3 you can add
      'Adobe:'+pagedata.title+':'+pagedata.sitesection
      to send the title of a page concatenated with its sitesection using : (colon) and prefixed with Adobe as prop3
  2. The side pod is the same for both views.

이 작업에는 Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License의 라이센스가 부여되었습니다.  Twitter™ 및 Facebook 게시물은 Creative Commons 약관을 적용받지 않습니다.

법적 고지 사항   |   온라인 개인 정보 보호 정책