Analytics helps Platix understand which workflows succeed, where errors occur, and which features deserve improvement.
Turn analytics on
Use Analytics only in the first-visit banner, or turn on Analytics in the footer. Platix records your choice and begins eligible product measurement only after consent is active.
Control ads measurement separately
Ads measurement tells Platix when a Google ad led to a confirmed new account. It is separate from product analytics. You can accept analytics without ads measurement, or change either setting later in the footer. Platix does not send your email, name, user ID, trip content, or search text in the signup conversion, and this setting does not enable personalized ads.
Turn analytics off
Select Analytics: on, review the confirmation, and turn it off. Platix records the consent change and stops sending consent-dependent analytics from that browser.
Turning analytics off does not erase operational records that must be retained for security, abuse prevention, legal compliance, or service reliability. It also does not retroactively delete events lawfully collected while consent was active.
What product analytics avoids
Product analytics is designed around product actions and limited context. It should not contain passwords, authentication tokens, booking references, private chat text, or complete private content.
Browser scope
Consent is stored for the browser and is also recorded by the backend. A different browser or cleared local storage may require you to choose again.