Opting Into Adobe Analytics and Adobe Target

You are reading the AEM 6.1 version of Opting Into Adobe Analytics and Adobe Target.
This documentation is also available for the following versions:  AEM 6.2 

AEM 6.1 has simplified the procedure for integrating with Adobe Analytics and Adobe Target. When you log in as an administrator you are presented the following options for configuring the integration:

Configuring the Integration

Opt into the integration with Analytics and/or Target to enable the use of their page tracking and analysis capabilities, and personalization capabilities. When you opt in you need to provide the user account information and specify the pages that are tracked.

Note

You can optionally provide Analytics and Target account information using a properties file that is read upon server startup. See Providing Account Information Using a Properties File.

When you opt into the integration, AEM performs the following tasks:

  • Creates the cloud configurations that enable the connection to Analytics and Target.
  • Creates the frameworks that determine the data that is tracked.
  • Configures the web pages to enable tracking.

After you opt into the configuration, you need to publish the affected pages to replicate these changes to your publish instance. 

  1. On the Configure Analytics And Targeting dialog box, select Configure Analytics & Targeting Now and click Next.

    file
  2. To enable AEM to collect anonymous usage data, select Allow Sending of Anonymous Usage Data, and then click Continue.

  3. Enter the user account information for Analytics and/or Target then click the corresponding Add button.

    For Analytics, the credentials are authenticated and AEM retrieves the Analytics report suites that are associated with the account.

    file
  4. When the Analytics account is authenticated, select the Analytics report suite to use, and then click Next.

    file
  5. Select the sites that you want to associate with the configurations and then click Done.

  6. In the Sites console (http://localhost:4502/sites.html/content), select a site that you are tracking and click the publish icon.

    file

Configuring the Integration Later

Postpone the integration with Analytics and Target if you are not ready to perform the configuration. When you postpone the integration, you are prompted to perform the configuration again the next time that you log in. 

  1. On the Analytics And Targeting Configuration dialog box, click or tap Cancel > Remind Me Later.

Note

If you cancel the integration without selecting Remind Me Later , you can still access the wizard directly through this link: http://localhost:4502/libs/cq/cloudservicesprovisioning/content/wizard/opt-in.html

Opting Out of the Integration

Opt out of the integration with Analytics and Target when you do not want to be presented with the Analytics and Targeting Configuration dialog box upon logging in. Opt out when you prefer to configure the integrations manually or do not want to integrate with the products. 

For information about configuring the integrations manually, see Integrating with Adobe Analytics and Integrating with Adobe Target.

  1. On the Analytics And Targeting Configuration dialog box, click or tap Cancel > Don't Ask Again.

Providing Account Information Using a Properties File

Install a properties file that AEM reads on server startup to configure the account properties for the integration with Analytics and Target. When you use the properties file, the opt-in wizard automatically uses the properties from the file and the cloud configuration is created accordingly.

The properties file is a text file named marketingcloud.properties that you save in the working directory that the AEM process is using (typically the same directory as the JAR file). The file includes the following properties:

  • analytics.server: The URL of the Analytics data center that you use.
  • analytics.company: The company that is associated with your Analytics user account.
  • analytics.username: Your Analytics user name.
  • analytics.password: The password that is associated with your Analytics user name.
  • analytics.reportsuite: The name of the Analytics report suite to use.
  • target.clientcode: The client code that is associated with your Target account.
  • target.email: The email address that you use to authenticate your Target account.
  • target.password: The password that is associated with your email address.

Properties and values are separated with equal signs (=). The Analytics properties are prefixed with analytics, and the Target properties are prefixed with target. To configure a service, provide values for all of the properties for that service. If you do not want to configure a service, provide no values for that service.

The following example properties file includes the property values for creating a cloud configuration for Analytics.

analytics.server=https://api5.omniture.com/admin/1.4/rest/ 
analytics.company=Geometrixx
analytics.username=sbroders 
analytics.password=12345678 
analytics.reportsuite=myreportsuite 
target.clientcode=
target.email=
target.password=
        

Code samples are intended for illustration purposes only.

The following procedure describes how to opt into the integration using the properties file.

  1. Create the marketingcloud.properties file in the working directory that the AEM process is using (author instance).

  2. Add the property values according to your Analytics and/or Target accounts.

  3. Start or restart the server, and then log in using an administrator account.

  4. Use the Analytics And Targeting Configuration dialog box as described in Configuring the Integration. Instead of entering your account information, the wizard uses the values from the properties sheet. You only need to click Add for the service to continue with the wizard. 

    file

About the Cloud Configurations

When you configure the integration with Analytics and Target, AEM automatically creates the required cloud configurations and frameworks. For example, the Analytics cloud configuration is called Provisioned Analytics Account.

You do not need to alter the cloud configurations. However, you can configure the frameworks as needed. (See Mapping Component Data with SiteCatalyst Properties and Add a Target Framework.)

​