Show Menu
TOPICS×

Adobe Analytics Extension

Use this reference for information about configuring the Adobe Analytics extension, and the options available when using this extension to build a rule.

Configure the Adobe Analytics extension

This section provides a reference for the options available when configuring the Adobe Analytics extension.
If the Adobe Analytics extension is not yet installed, open your property, then click Extensions > Catalog , hover over the Adobe Analytics extension, and click Install .
To configure the extension, open the Extensions tab, hover over the extension, and then click Configure .

Library Management

Select an option from the Library Management section of the configuration page. The following configuration options are available:

Manage the library for me

Report Suites

Specify one or more report suites for each of the following environments:
  • Development
  • Staging
  • Production

Use the library already installed on the page

Set the following report suites on tracker

If you select this option, specify one or more report suites for each of the following environments:
  • Development
  • Staging
  • Production

Tracker is accessible on the global variable named

Checking this box allows the tracker object to be used globally. For example, you could define the variable window.s.pageName anywhere on your site.

Load the library from a custom URL

HTTP URL

Specify the URL where the library is located.

HTTPS URL

Specify the URL where the library is located.

Set the following report suites on tracker

If you select this option, specify one or more report suites for each of the following environments:
  • Development
  • Staging
  • Production

Tracker is accessible on the global variable named

Specify the tracker object to be used globally.

Let me provide custom library code

Open Editor

Lets you insert core AppMeasurement code . This code is populated automatically when using the automatic configuration method.
The validator used in the Launch code editor is designed to identify issues with developer-written code. Code that has gone through a minification process--such as the AppMeasurement.js code downloaded from the Code Manager--might be falsely flagged as having issues by the Launch validator, which can usually be ignored.

Set the following report suites on tracker

If you select this option, specify one or more report suites for each of the following environments:
  • Development
  • Staging
  • Production

Tracker is accessible on the global variable named

Specify the tracker object to be used globally.

General

Select an option from the General section of the configuration page. The following configuration options are available:

Enable EU compliance for Adobe Analytics

Enables or disables tracking based on the EU privacy cookie.
When you check the EU Compliance check box, the Tracking Cookie Name field appears. The Tracking Cookie overrides the default tracking cookie name. You can customize the name that Launch uses to track your opt-out status for receiving other cookies.
When a page is loaded, the system checks to see if a cookie called sat\_track is set (or the custom cookie name specified on the Edit Property page). Consider the following information:
  • If the cookie does not exist or if the cookie exists and is set to anything but true, the loading of the tool is skipped when this setting is enabled. Meaning, any portion of a rule that uses the tool will not apply. If a rule has analytics with EU compliance on and third-party code, and the cookie is set to false, the third-party code still runs. However, the analytics variables will not be set.
  • If the cookie exists but it is set to true, the tool loads normally.
You are responsible for setting the sat\_track (or custom named) cookie to false if a visitor opts out. You can accomplish this using custom code:
_satellite.setCookie("sat_track", "false");

You must also have a mechanism to set that cookie to true if you want a visitor to be able to opt in later:
_satellite.setCookie("sat_track", "true");

Character Set

Determines how the image request is encoded. If your implementation or site uses non-ASCII characters, it is important to define character set here. You can select a preset character set or specify a custom character set. Adobe recommends using the same character coding as your site. Typically this value is UTF-8.
Character Set can be set in Analytics custom code using the variable s.charSet .
For more information about character sets, see the Multi-Byte Character Sets whitepaper .

Currency Code

Determines the conversion rate to be applied to revenue and currency events. If your site allows visitors to purchase in multiple currencies, setting the currency code ensures the monetary amount is converted and stored correctly.
For more information about the supported currency codes, see the Multi-Currency Support whitepaper .

Tracking Server

Used for first-party cookie implementations to dictate where the first-party cookie is stored. If you use the Experience Cloud ID Service, Adobe advises against populating this field.
Tracking Server can be set in Analytics custom code using the variable s.trackingServer .
See trackingServer in the Adobe Analytics Implementation guide.

SSL Tracking Server

Used for SSL first-party cookie implementations to dictate where the first-party cookie is stored. If you use the Experience Cloud ID Service, Adobe advises against populating this field. If not defined, SSL data uses Tracking Server.
SSL Tracking Server can be set in Analytics custom code using the variable s.trackingServerSecure .

Global Variables

Use this section to set up eVars and Props , and to create hierarchies.
Global variables are variables that are set on the Analytics tracking object when that object is initialized on the page. Any variables you set here will be set when the tracking object is created on each page. Once these variables are set, they are just like any other variables set any other way. Specifically, this means that a rule can modify, change, or clear these variables.
If your web application typically sends one beacon per page, this section can help make it simple to set your variables in one place. If your application sends more than one beacon per page (such as in a single-page application), and you need to clear your variables and reset them using the same tracking object, it is simpler to rely on rules to set and clear your variables.

Cookies

Configure field descriptions for the Cookies global settings used for deploying the Adobe Analytics extension. The following configuration options are available:

Visitor ID

Unique value that represents a customer in both the online and offline systems.

Visitor Namespace

Variable to identify the domain with which cookies are set.

Domain Periods

The domain on which the Analytics cookie s_cc and s_sq are set by determining the number of periods in the domain of the page URL. This variable is also used by some plug-ins in determining the correct domain to set the plug-in's cookie.

First-Party Domain Periods

The fpCookieDomainPeriods variable is for cookies set by JavaScript ( s_sq , s_cc , plug-ins) that are inherently first-party cookies, even if your implementation uses the third-party 2o7.net or omtrdc.net domains.

Customize Page Code

Use the editor to customize your page code.

Adobe Audience Manager

Use this section of the extension configuration to specify how Audience Manager works with Analytics.
Enable Automatically share Analytics data with Audience Manager .
The following options appear:
The Audience Manager subdomain is assigned by Adobe Audience Manager. It is sometimes referred to as your "Partner Name" or "Partner Subdomain." Contact your Adobe consultant or Customer Care if you do not know your Partner Name.
You can configure advanced settings by showing the advanced settings and entering your preferences.
For information about each setting, click the info icon, or refer to the Adobe Audience Manager documentation .

Analytics extension action types

This section describes the action types available in the Analytics extension.
The Analytics extension provides the following actions:

Set Variables

Important: Using a "set variables" action won't send the beacon. You must use the "send beacon" action.

eVars

Set one or more eVars .
  1. Select an eVar from the dropdown.
  2. Specify whether you want to set the eVar as the value (Set As) or copy (Duplicate From) another eVar.
  3. Provide a Set As value, or select the eVar you want to duplicate.
  4. (Optional) Click Add eVar to set more eVars.
  5. Click Keep Changes .

Props

Set one or more props .
  1. Select a prop from the dropdown.
  2. Specify whether you want to set the prop as the value (Set As) or copy (Duplicate From) another eVar.
  3. Provide a Set As value, or select the eVar you want to duplicate the prop from.
  4. (Optional) Click Add prop to set more props.
  5. Click Keep Changes .

Events

Set one or more events .
  1. Select an event from the dropdown.
  2. (Optional) Select or specify a data element used for event serialization .
  3. (Optional) Click Add event to set more events.
  4. Click Keep Changes .

Hierarchy

Set the Analytics Hierarchy variable.
Specify each level in the hierarchy.
If desired, configure additional hierarchies.

Other information

Specify other information used by your pages.
These settings include:
  • Page Name
  • Page URL
  • Server
  • Channel
  • Referrer
  • Campaign
    Specify either a value or a query parameter
  • State
  • Zip
  • Transaction ID

Custom Page Code

Description
Use the editor to specify your custom page code.
Settings
  1. Click Open Editor .
  2. Type the custom code.
  3. Click Save .

Send Beacon

Increment a pageview - s.t()

Select if you want to increment a pageview.

Do not increment a pageview - s.t()

Select if you do not want to increment a pageview.
Settings
  1. Select a link type.
    You can select one of the following:
    • Custom Link
    • Download Link
    • Exit Link
  2. Set the parameter for the selected link.
    • Custom Link: Specify the link name.
    • Download Link: Specify a file name.
    • Exit Link: Specify the destination URL.
  3. Click Keep Changes .

Clear Variables

There are no configuration options if the Clear Variables action type is selected.