Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. The file adrum.js is injected into each instrumented page, as close to the top as possible, as the page is served. Although it loads synchronously, it's a very small file, around 30 KB (10 to 12 KB with compression), and generally, executes in less than 5 ms in modern browsers and less than 15 ms in older browsers.
  2. This first JavaScript file starts a timer and does some quick configuration and setup.
  3. At the onload event, adrum-ext.js is fetched asynchronously, specifically to not block the page from loading. This is the code that does most of the heavy lifting. Once it has been fetched, it is cached for 24 hours on the browser. 
  4. When cross-domain session correlation is enabled, the first time a user visits a domain, the browser additionally loads the file adrum-xd.html to generate or load a piece of common information that enables cross-domain sessions. Future visits will not load adrum-xd.html again.
  5. When the page has completed loading, the collected data is bundled into a beacon and sent to the EUM Cloud by Server by adrum-ext.js
  6. The data is processed by the EUM Cloud Server and then made available for pickup by the Controller.

...