How it works – serving experiences, behavioral tracking
Your users request the web page, in the same way they do today.
Your server returns a web page, in the same way it does today.
That web page contains our Tag, before any visual elements. This triggers as the page loads in the browser. At this point, we mask the page (optionally, to avoid flickering).
A request is made to Optimize to see if there is anything on the page that needs to executed (a test/target) or tracked - clicks, page loads, revenue, etc.
Our servers respond with instructions of transformations to make to the page (with Javascript and CSS), and things to track. These are executed when the response is handled on the page.
The optional masking is removed, and the final page is ready for a user
This experience may include additional steps for Single Page Apps, and depending on how you handle Consent Management.