This page explains how Atrium uses technical storage, assistant-flow continuity, and optional analytics tooling on the public portal.
Atrium uses technical storage for session continuity and can activate GA4 or GTM in production when the deployment includes those identifiers.
The site uses technical storage for basic experience continuity, including session identifiers that help Atrium understand the page journey and preserve assistant-related context during a visit.
These technical elements support usability, security, and lead-routing continuity across the public site and private consultation entry point.
GA4 and GTM are configured as deployment-dependent integrations. They only activate when Atrium provides the relevant production measurement identifiers.
When those tools are enabled, Atrium may measure pageviews, CTA clicks, consultation starts, and related engagement signals to improve the site and the assistant-first funnel.
Atrium intentionally does not expose a public phone-first or inbox-first intake path across these pages. The published contact route is the virtual assistant and private consultation flow.
That means cookie and tracking interpretation on this site should be read in the context of assistant-first lead capture rather than a conventional public contact form model.
Yes. The site uses technical storage for session continuity and may activate analytics tags in production when measurement is enabled.
No. GA4, GTM, and related measurement are deployment-dependent and only activate when Atrium provides the relevant production configuration.
Use the virtual assistant-first consultation path. That is Atrium's published public intake channel on this portal.
Atrium uses assistant-first intake so a policy page can lead directly into a more contextual, private next step instead of a generic inbox exchange.