Frequently asked questions about implementation, and links to more information.
The Identity Service assigns a unique, persistent identifier that can be shared among other solutions in the Experience Cloud. The Analytics visitor ID is only used by Analytics. Adobe recommends using the Experience Cloud Visitor ID Service in your implementation.
AppMeasurement creates an image object within the HTML page, and the browser then requests the image object from Adobe data collection servers. If data collection servers were slow or unresponsive, the thread handling that request would be delayed until the image returns or a timeout occurs. Because browsers handle images with multiple threads, an Adobe outage would have a minimal impact on the page load time, tying up one thread while the others continue to function.
Sometimes an organization would like to remove an implementation due to contract expiration or to reduce the number of server calls.
s_code.js file with the following line of code:
var s = new Object();
s_code.js file altogether, unless you also remove all references to the file on each page.
trackingServer variable to point away from Adobe. AppMeasurement still sends image requests, which return 404 errors.
Math.random() as a potential security risk. Is
Math.random() used with any sensitive data?
No. The numbers that use
Math.random() are not used to mask, send, or receive any sensitive data. Data sent to Adobe data collection servers rely on the security of the underlying HTTPS connection.
Math.random() in three key areas:
Math.random() is used to determine if a given visitor should send data. Most implementations do not use sampling.