The local build creates a random session identifier and stores campaign parameters and up to 100 interaction events in browser storage. No analytics property or event endpoint is active until it is configured. A production launch must name every active analytics or attribution provider, the data sent, retention, and opt-out route.
Browser storage
This site stores a random session ID, page path, event name, campaign parameters, and an offer or tool identifier in the browser. It does not ask for a name, email address, precise location, medical information, pet record, or water result.
Analytics status
No third-party analytics or attribution endpoint is active. This policy will name any provider before data collection begins.