To track web data from your AEM pages in SiteCatalyst, create a SiteCatalyst Cloud Services configuration and a SiteCatalyst framework:
- SiteCatalyst Configuration: The information about your SiteCatalyst account. The SiteCatalyst configuration enables AEM to connect to SiteCatalyst. Create a SiteCatalyst configuration for each account that you use.
- SiteCatalyst Framework: A set of mappings between SiteCatalyst report suite properties and CQ variables. Use a framework to configure how your website data populates your SiteCatalyst reports. Frameworks are associated with a SiteCatalyst configuration. You can create multiple frameworks for each configuration.
When you assocate a web page with a framework, the framework performs tracking for that page and the descendents of that page. Also, the Polling Data Importer service retrieves page impressions from SiteCatalyst. This information appears in the Impressions column of the Websites console.
To track AEM data in SiteCatalyst, you must have a valid Adobe Marketing Cloud SiteCatalyst account. The SiteCatalyst account needs to be assigned to the Web Service Access user group.
Before proceeding, ensure your credentials allow you to log in to SiteCatalyst. ( https://sc.omniture.com/login/)
Providing Administrator privileges is not enough to allow a user to connect from AEM to Site Catalyst. That user must have Web Service Access privileges.
SiteCatalyst data centers collect, process and store data associated with your Site Catalyst report suite. You must configure AEM to use the data center that hosts your SiteCatalyst report suite. The following table lists the available data centers and their URL.
AEM uses the San Jose (https://api.omniture.com/admin/1.3/rest/) data center by default. Use the Admin Console to add the URL for each data center that hosts a report suite for which your AEM pages collect data.
Create a SiteCatalyst configuration so that AEM can authenticate with the SiteCatalyst server. To create the configuration you provide the credentials for your SiteCatalyst account.
When the Edit dialog opens, specify values for the following properties:
- Company name: your company's name as featured on SiteCatalyst
- Username: the name used to log in to SiteCatalyst
- Password: the SiteCatalyst password for the above account
- Data Center: The location of the SiteCatalyst data center that your account is associated with.
- Do Not Include Tracking Code: Select this option when you are using SiteCatalyst reports in the Content Insights feature, and you are also using Dynamic Tag Management (DTM) with AEM and the DTM web property has the Adobe Analytics tool installed. In this case, selecting this option prevents two instances of the tracking code to be added to pages.
Please contact your SiteCatalyst representative to make sure you fill in these credentials correctly.
For the Report Suite ID (RSID) that you are using, you can control which server instances (author, publish, or both) contribute data to the Report Suite:
- All: Information from both the author and the publish instance populates the Report Suite.
- Author: Only information from the author instance populates the Report Suite.
- Publish: Only information from the publish instance populates the Report Suite.
Selecting the type of server instance does not restrict calls to Sitecatalyst, it merely controls which calls include the RSID.
For example, a framework is configured to use the geometrixxauth report suite and author is the selected server instance. When pages are published along with the framework, calls are still made to SiteCatalyst, however these calls do not contain the RSID. Only calls from the author instance include the RSID.
These settings determine where your data is sent and how, so it is imperative that you do not tamper with these settings and let your Sitecatalyst representative set it up instead.
- Tracking server
- contains the URL used to send SiteCatalyst calls
- cname - defaults to the SiteCatalyst account's Company name
- d1 - corresponds to the data center the information will be sent to (can be either d1, d2 or d3)
- sc.omtrdc.net - domain name
- contains the URL used to send SiteCatalyst calls
- Secure Tracking Server
- Has the same segments as the Tracking server
- This is used for sending data from secure pages (https://)
- Visitor Namespace
- The namespace determines the first part of the tracking URL.
- e.g. changing the namespace to CNAME will cause the calls made to SiteCatalyst to look like CNAME.d1.omtrdc.net instead of the default.
When a page is associated with a SiteCatalyst framework, the page sends data to SiteCatalyst when the page loads. The data that is sent are any CQ variables that the page populates with data that are also mapped to SiteCatalyst variables in the framework. Also, the framework also causes AEM to retrieve page impresions from SiteCatalyst.
Descendents of the page inherit the association with the framework. For example, when you associate the root page of your site with a framework, all pages of the site are associated with the framework.
- From the Welcome screen, go to Websites and select the page you wish to set up with tracking.
- e.g. Websites > Geometrixx Outdoors > English
- Double click on the page to open it for editing.
- Go to the Page tab of the Sidekick (second from the left) and select Page properties.
- On the Page Properties panel, go to the Cloud Services page and click the Add service button.
- Select Adobe SiteCatalyst from the available options and click Ok.
- Click on the dropdown menu and select the framework created in the previous section
- i.e. my-sc-framework.
- Click Ok again to make the selection final.
- In order to activate the page and any connected configurations/files, select Activate page from the Page tab of the Sidekick.
- The final step is to visit the page on the publish instance and searching for a keyword (e.g. aubergine) using the Search component.
- Check the calls made to SiteCatalyst using an appropriate tool, like Adobe DigitalPulse Debugger or any web debugging tool.
- Using the example provided, the call should contain the value entered (i.e. ‘aubergine’) in eVar7 and the events list should contain event3.
When a page is associated with a SiteCatalyst framework, the number of page impressions appears in the Impressions column of the Websites console. The association of the page with a framework causes the SiteCatalyst Imporessions Importer service to automatically retrieve the information:
- Impressions information is retreived from SiteCatalyst and updated in the Websites console once a day by default. You can configure a different polling interval.
- Impressions data is available as soon as the simplest tracking calls to SiteCatalyst occur. No special reports are required on SiteCatalyst to enable the retrieval of the impressions data.
- The SiteCatalyst Impressions Importer service calls SiteCatalyst asynchronously to minimize the use of AEM resources.
- Impressions are shown for a single page. For example, you cannot see the total number of impressions for all child pages.
Use of the Sitecatalyst Impressions Importer service requries no special licencing.
Impressions information is for use only on the author instance. The Polling Data Importer service should be disabled on the publsh instance. (See the Import failure | Invalid polling configuration | SiteCatalyst Impressions Knowledge Base article.)
Configure the Day CQ Analytics SiteCatalyst Impressions Importer service:
- Change the interval at which the service retrieves page impressions data from Adobe Analytics. The default interval is 43200000 ms (12 hours).
- Disable or enable the service. By default, the service is enabled.
|Web Console Property||OSGi Property||Description|
|Import interval||cq.analytics.sitecatalyst.importer.interval||The interval at which to retrieve page impressions data, in milliseconds (ms). The default value is 43200000.|
Controls whether the service is enabled. The service is enabled by default.
The impressions importer is included in the active list of polling importers shown using the endpoint
To delete a particular SiteCatalyst configuration or framework, do the following:
- 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.
- Choose the configuration or framework you want to delete from the panel on the right.
- Right-click it and select Delete from the menu that pops up.
- Confirm the deletion of the configuration or framework.
There are two possible ways to edit SiteCatalyst configurations and frameworks within AEM.
- Go to Tools > Cloud Services Configurations > Adobe SiteCatalyst
- 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.
- Double click the configuration or framework in the panel to the right to open it for editing.
The other way is:
- Go to the Cloud services dashboard from the Welcome screen
- Select the SiteCatalyst menu item on the dashboard
- Press the Show configurations button
- 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.