Connecting to Adobe Analytics and Creating Frameworks
- Topics:
- Administering
CREATED FOR:
- Admin
To track web data from your AEM pages in Adobe Analytics, create a Adobe Analytics Cloud Services configuration and a Adobe Analytics framework:
- Adobe Analytics Configuration: The information about your Adobe Analytics account. The Adobe Analytics configuration enables AEM to connect to Adobe Analytics. Create an Adobe Analytics configuration for each account that you use.
- Adobe Analytics Framework: A set of mappings between Adobe Analytics report suite properties and CQ variables. Use a framework to configure how your website data populates your Adobe Analytics reports. Frameworks are associated with a Adobe Analytics 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. Page views can then be retrieved from Adobe Analytics and displayed in the Sites console.
Prerequisites
Adobe Analytics Account
To track AEM data in Adobe Analytics, you must have a valid Adobe Marketing Cloud Adobe Analytics account.
The Adobe Analytics account needs to:
- Have Administrator privileges
- Be assigned to the Web Service Access user group.
Before proceeding, ensure your credentials let you sign in to Adobe Analytics using either one of the following methods:
Configuring AEM to Use Your Adobe Analytics Data Centers
Adobe Analytics data centers collect, process and store data associated with your Adobe Analytics report suite. You must configure AEM to use the data center that hosts your Adobe Analytics report suite. The following table lists the available data centers and their URL.
Data Center | URL |
---|---|
San Jose | https://api.omniture.com/admin/1.4/rest/ |
Dallas | https://api2.omniture.com/admin/1.4/rest/ |
London | https://api3.omniture.com/admin/1.4/rest/ |
Singapore | https://api4.omniture.com/admin/1.4/rest/ |
Oregon | https://api5.omniture.com/admin/1.4/rest/ |
AEM uses the San Jose (https://api.omniture.com/admin/1.4/rest/) data center by default.
Use the Web Console to configure the OSGi bundle Adobe AEM Analytics HTTP Client. Add the Data Center URL for the data center that hosts a report suite for which your AEM pages collect data.
-
Open the Web console in your web browser. (http://localhost:4502/system/console/configMgr)
-
Enter your credentials to access the console.
NOTE
Contact you site administrator to find out if you have access to this console. -
Select the Configuration item named Adobe AEM Analytics HTTP Client.
-
To add the URL for a data center, press the + button next to the Data Center URLs list, and type the URL in the box.
-
To remove a URL from the list, click the - button next to the URL.
-
Click Save.
Configuring the Connection to Adobe Analytics
Configuring for the Activity Map
Creating a Adobe Analytics Framework
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.
-
Using Navigation, select Tools, Cloud Services, then Legacy Cloud Services.
-
Scroll to Adobe Analytics and click [+] next to Available Configurations.
-
Click the [+] link next to your Adobe Analytics configuration.
-
In the Create Framework dialog:
- Specify a Title.
- Optionally you can specify the Name, for the node that stores the framework details in the repository.
- Select Adobe Analytics Framework
And click Create.
The framework opens for editing.
-
In the Report Suites section of the side pod (right side of main panel), click Add Item. Then use the drop-down to select the Report Suite ID (for example,
geometrixxauth
) with which the framework will interact.NOTE
The content finder on the left is populated with Adobe Analytics variables (SiteCatalyst Variables) when you select a Report Suite ID. -
Then use the Run Mode drop down (next to the Report Suite ID) to select the server instances that you want to send information to the Report Suite.
-
To make the framework available on the publish instance of your site, on the Page tab of sidekick, click Activate Framework.
Configuring Server Settings for Adobe Analytics
The framework system lets you change the server settings within each Adobe Analytics framework.
Start by opening the panel. Press the downward arrow next to Servers:
-
Tracking Server
-
contains the URL used to send Adobe Analytics calls
- cname - defaults to the Adobe Analytics 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
-
-
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 Adobe Analytics to look like CNAME.d1.omtrdc.net instead of the default.
Associating a Page with a Adobe Analytics Framework
When a page is associated with an Adobe Analytics framework, the page sends data to Adobe Analytics when the page loads. Variables that the page populates are mapped and retrieved from Adobe Analytics variables in the framework. For example, page views are retrieved from Adobe Analytics.
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 Sites console, select the page you wish to set up with tracking.
-
Open the Page Properties, either directly from the console, or the page editor.
-
Open the Cloud Services tab.
-
Use the Add Configuration drop down to select Adobe Analytics from the available options. If inheritance is place you need to disable that before the selector becomes available.
-
The drop down selector for Adobe Analytics will be appended to the options available. Use this to select the required framework configuration.
-
Select Save & Close.
-
Publish the page to activate the page and any connected configurations/files.
-
The final step is to visit the page on the publish instance and search for a keyword (e.g. aubergine) using the Search component.
-
You can then check the calls made to Adobe Analytics using an appropriate tool; for example, Adobe Experience Cloud Debugger.
-
Using the example provided, the call should contain the value entered (i.e. aubergine) in eVar7 and the events list should contain event3.
Page Views
When a page is associated with a Adobe Analytics framework, the number of page views can be shown in the List view of the Sites console.
See Seeing Page Analytics Data for further details.
Configuring the Import Interval
Configure the appropriate instance of the Adobe AEM Managed Polling Configuration service:
-
Poll Interval:
The interval, in seconds, at which the service retrieves page view data from Adobe Analytics.
The default interval is 43200000 ms (12 hours).
-
Enable:
Enable or disable the service. By default, the service is enabled.
To configure this OSGi service, you can either use the Web Console or an osgiConfig node in the repository (the service PID is com.day.cq.polling.importer.impl.ManagedPollConfigImpl
).
Editing Adobe Analytics Configurations and/or Frameworks
As when creating an Adobe Analytics configuration or framework, navigate to the (legacy) Cloud Services screen. Select Show Configurations, then click on the link to the specific configuration you want to update.
When editing an Adobe Analytics configuration, you also need to press the Edit button when on the configuration page itself in order to open the Edit Component dialog.
Deleting Adobe Analytics Frameworks
To delete an Adobe Analytics framework, first open it for editing.
Then select Delete Framework from the Page tab of the sidekick.
Experience Manager
- Administering User Guide overview
- Sites Features
- Website Administration
- Reusing Content: Multi Site Manager and Live Copy
- Live Copy Overview Console
- Configuring Live Copy Synchronization
- Creating and Synchronizing Live Copies
- MSM Rollout Conflicts
- MSM Best Practices
- Translating Content for Multilingual Sites
- Managing Translation Projects
- Identifying Content to Translate
- Preparing Content for Translation
- Creating a Language Root Using the Classic UI
- Connecting to Microsoft Translator
- Configuring the Translation Integration Framework
- Language Copy Wizard
- Translation Enhancements
- Translation Best Practices
- Configurations and the Configuration Browser
- AEM FAQs
- Operations
- Dashboards
- Operations Dashboard
- Backup and Restore
- Data Store Garbage Collection
- Monitoring Server Resources Using the JMX Console
- Working with Logs
- Configure the Rich Text Editor
- Configure the Video component
- The Bulk Editor
- Configuring Email Notification
- Configuring RTE for Producing Accessible Sites
- The Link Checker
- Troubleshooting AEM
- Audit Log Maintenance in AEM 6
- Editor
- Managing Access to Workflows
- Using cURL with AEM
- Configuring Undo for Page Editing
- Proxy Server Tool (proxy.jar)
- Configuring for AEM Apps
- Administering Workflows
- Configuring Search Forms
- Tools Consoles
- Reporting
- Administering Workflow Instances
- Configuring Layout Container and Layout Mode
- Enabling Access to Classic UI
- Starting Workflows
- Configure the Rich Text Editor plug-ins
- Admin Consoles
- Security
- User Administration and Security
- User, Group and Access Rights Administration
- Security Checklist
- OWASP Top 10
- Running AEM in Production Ready Mode
- Identity Management
- Adobe IMS Authentication and Admin Console Support for AEM Managed Services
- Creating a Closed User Group
- Mitigating serialization issues in AEM
- User Synchronization
- Encapsulated Token Support
- Single Sign On
- How to Audit User Management Operations in AEM
- SSL By Default
- SAML 2.0 Authentication Handler
- Closed User Groups in AEM
- Granite Operations - User and Group Administration
- Enabling CRXDE Lite in AEM
- Configuring LDAP with AEM 6
- Configure the Admin Password on Installation
- Service Users in AEM
- Encryption Support for Configuration Properties
- Handling GDPR Requests for the AEM Foundation
- Content Disposition Filter
- Personalization
- eCommerce
- Integration
- Integrating with Third-Party Services
- Integrating with Salesforce
- Integrating with Adobe Target
- Integrating with Adobe Analytics
- Connecting to Adobe Analytics and Creating Frameworks
- Configuring Link Tracking for Adobe Analytics
- Mapping Component Data with Adobe Analytics Properties
- Configuring Video Tracking for Adobe Analytics
- HTTP2 Delivery of Content FAQ
- Troubleshooting your Adobe Campaign Integration
- SharePoint Connector Licenses, Copyright Notices, and Disclaimers
- SharePoint Connector
- DHTML Viewer End-of-Life FAQs
- Integrating with Adobe Campaign Classic
- Related Community Articles
- Integrating with Adobe Campaign Standard
- Flash Viewers End-of-Life Notice
- Integrating with Adobe Creative Cloud
- Integrating with Adobe Dynamic Tag Management
- Opting Into Adobe Analytics and Adobe Target
- AEM Portals and Portlets
- Integrating with Dynamic Media Classic
- Troubleshooting Integration Issues
- Integrating with BrightEdge Content Optimizer
- Best Practices for Email Templates
- Catalog Producer
- Integrating with Silverpop Engage
- Integrating with Adobe Campaign
- Integrating with ExactTarget
- Analytics with External Providers
- Integrating with the Adobe Marketing Cloud
- Manually Configuring the Integration with Adobe Target
- Prerequisites for Integrating with Adobe Target
- Adobe Classifications
- Solutions Integration
- Target Integration with Experience Fragments
- Best Practices
- Content Management