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:
Variable | AppMeasurement | Analytics extension | Web SDK | Web SDK extension | Hardcoded image request |
---|---|---|---|---|---|
Report suite ID | String argument within s_gi |
Report suites under the Library management section when Configuring the extension | Add Adobe Analytics as a service when Configuring a datastream | Add Adobe Analytics as a service when Configuring a datastream | Part of the URL pathname (after /b/ss/ ) |
Tracking Server | The trackingServer and trackingServerSecure variables |
Tracking Server and SSL Tracking Server under the General section when Configuring the extension | The edgeDomain property when Configuring the Web SDK |
The Edge Domain when Configuring the extension | The hostname of the image request URL |
Experience Cloud ID service | Implement VisitorAPI.js |
Use the Adobe Experience Cloud ID Service extension | Use the Adobe Experience Cloud ID Service extension | Use the Adobe Experience Cloud ID Service extension | Make a separate call to the ID Service servers to obtain the desired ID |
If any of these variables are not consistent across each implementation type, Adobe considers them as separate visitors. If visitors are not seamlessly tracked across implementation types on your site, the most common reason is that the ID Service is configured incorrectly. See Implementation methods in the ID Service user guide for more information.