DocumentationAnalyticsImplementation Guide

Configuration variables overview

Last update: June 19, 2026

CREATED FOR:

  • Admin
  • Developer

Configuration variables control the way data is captured and processed in reporting. They do not typically contain dimension or metric values.

Setting configuration variables

In implementations using the Web SDK extension or Analytics extension, configuration variables are typically found in the extension’s settings:

  1. Log in to Adobe Experience Platform Data Collection using your Adobe ID credentials.
  2. Click the desired tag property.
  3. Click the Extensions tab, then Click Configure under the extension.

In JavaScript implementations using AppMeasurement.js, configuration variables are typically set at the top of the JS file.

IMPORTANT
Make sure that all configuration variables are set before calling a tracking method (t() or tl()). Avoid setting configuration variables in the doPlugins() function.

Retired configuration variables

The following configuration variables are retired. They are documented here for reference if you encounter them in a legacy implementation.

  • account: Determined the report suite that data was sent to. Report suite is now handled through tracking object instantiation (the s_gi() method). Use the s.sa() method if you need to change the report suite after the tracking object is instantiated.
  • cookieDomain: Determined the domain on which AppMeasurement set cookies. Current versions of AppMeasurement automatically detect the correct cookie domain, making this variable obsolete.
  • cookieDomainPeriods: Helped AppMeasurement determine where to store cookies when a domain contained multiple periods. Current versions of AppMeasurement automatically detect the correct domain, making this variable obsolete.
  • fpCookieDomainPeriods: The first-party equivalent of cookieDomainPeriods, used to set cookies in the correct location when a first-party domain’s suffix contained an extra period (such as example.co.uk). Current versions of AppMeasurement automatically detect the correct domain, making this variable obsolete.
  • trackingServer: Specified the domain used to send data to Adobe over HTTP. It is deprecated in favor of secure data collection over HTTPS. Use trackingServerSecure instead.
  • trackInlineStats: Enabled or disabled previous versions of Activity Map.
  • visitorMigrationKey: Carried a key used to migrate visitors from third-party to first-party cookies. It is retired because modern libraries set a first-party fallback cookie (fid) and rely on the Experience Cloud ID Service for identity.
  • visitorMigrationServer: Specified the server used during the third-party to first-party cookie migration.
  • visitorMigrationServerSecure: The HTTPS equivalent of visitorMigrationServer.
  • visitorNameSpace: Helped determine the third-party cookie domain. It is retired in favor of using the trackingServerSecure variable for implementations that do not use the Experience Cloud ID Service.
recommendation-more-help
analytics-help-implement