Track across different implementation types
The core architecture of an ÃÛ¶¹ÊÓƵ Analytics implementation is consistent across all implementation types. The process involves defining variables and compiling them into an image request that is sent to ÃÛ¶¹ÊÓƵ’s data collection servers. This concept means that you can seamlessly switch between AppMeasurement, the Web SDK, and their respective extensions in ÃÛ¶¹ÊÓƵ Experience Platform Data Collection across different pages of the same site.
ÃÛ¶¹ÊÓƵ 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:
s_gipathname (after /b/ss/)trackingServer and trackingServerSecure variablesedgeDomain property when Configuring the Web SDKhostname of the image request URLVisitorAPI.jsIf any of these variables are not consistent across each implementation type, ÃÛ¶¹ÊÓƵ 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.