Documentation Analytics Implementation Guide

Track across different implementation types

Last update: July 10, 2026

CREATED FOR:

Admin
Leader
Developer

The core architecture of an Adobe Analytics implementation is consistent across all implementation types. The process involves defining variables and compiling them into an image request that is sent to Adobe’s data collection servers. This concept means that you can seamlessly switch between AppMeasurement, the Web SDK, and their respective extensions in Adobe Experience Platform Data Collection across different pages of the same site.

Adobe recommends maintaining consistency across a site’s implementation by using the same implementation type across all pages. However, if parts of your site have different requirements, you can use this page to help make sure that visitors are consistently tracked between pages.

If you use more than one type of implementation (such as AppMeasurement and hardcoded image requests), make sure that the following variables are correctly set and match each other.

NOTE

All implementations types must use the same visitor identification type (legacy Analytics ID, Visitor ID Service, or Experience Platform Identity Service). Adobe recommends using an ECID in all implementations where possible.

Variable

Web SDK tag extension

Web SDK (Alloy)

Analytics extension

AppMeasurement

Hardcoded image request

Report suite ID

Add Adobe Analytics as a service when Configuring a datastream

Report suites under the Library management section when Configuring the extension

String argument in s_gi

Part of the URL pathname (after /b/ss/)

Visitor ID Service

Natively includes the Experience Platform Identity Service; requires idMigrationEnabled to read Visitor ID Service cookies

Natively includes the Experience Platform Identity Service; requires Migrate ECID from VisitorAPI to the Web SDK to read Visitor ID Service cookies

Use the ‘Experience Cloud ID Service’ tag extension, which implements the Visitor ID Service

Implement the Visitor ID Service (VisitorAPI.js)

Make a separate call to the Visitor ID Service to obtain the desired ID and include the mid in the query string

Edge domain

The Edge Domain field when Configuring the extension

The edgeDomain property when Configuring the Web SDK

SSL Tracking Server under the General section when Configuring the extension

The trackingServerSecure variable

The hostname of the image request URL

NOTE

AppMeasurement-based implementations (including the Analytics tag extension) are not compatible with the Experience Platform Identity Service. You must use the lowest common denominator form of visitor identification to synchronize across implementation types, which is typically the Visitor ID Service (VisitorAPI.js).

If any of these variables are not consistent across each implementation type, Adobe likely considers them as separate visitors. If visitors are not seamlessly tracked across implementation types on your site, the most common reason is that visitor identification is configured incorrectly. Ensure that each implementation type correctly obtains the same ECID (mid query string) across your site.

recommendation-more-help

analytics-help-implement