Measure acquisition and matched payment outcomes with a cookieless default and optional first-party collection. Review the data collected, retention by plan, and implementation tradeoffs before deployment.
The tracker sends page, referrer, UTM, visitor/session, device, browser and country-level context. Known user identifiers are hashed before storage, and common property keys associated with personal data are removed by the ingest sanitizer.
Cookieless mode keeps tracker identifiers in tab-scoped session storage. They survive reloads and single-page-app navigation in the same tab, but do not provide durable cross-tab or returning-visitor identity. If session storage is unavailable, the tracker falls back to page memory. Optional first-party mode stores project-scoped identifiers in localStorage, which can improve delayed attribution and changes the privacy and consent analysis.
EU hosting is one control. Before relying on it in procurement, confirm the current locations for the application, database, event store, backups, logs and subprocessors. Hosting location does not decide legal basis, consent, notices or controller responsibilities.
The product behavior below is implemented in the repository. Confirm live infrastructure and contract terms before relying on an operational control.
No. Pseudonymous identifiers and payment-related event data can still be personal data. Review purpose, legal basis, notices, retention and processor terms.
Yes, within the same browser tab. The current default uses tab-scoped session storage, so identifiers survive reloads and single-page-app navigation in that tab. A separate tab receives different identifiers, and the tracker falls back to page memory when session storage is unavailable.
The public security page is currently an outline, not a complete trust center. Request current operational and subprocessor details before relying on a control in procurement or legal review.
Start with cookieless behavior, decide whether delayed journeys justify first-party persistence, and document the fields and retention needed for your reporting purpose.