You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- [ X ] PostHog Cloud, region and project ID: [please provide, you can find both at https://app.posthog.com/settings/project-details#variables]
- [ ] PostHog Hobby self-hosted with `docker compose`, version/commit: [please provide]
- [ ] PostHog self-hosted with Kubernetes (deprecated, see [`Sunsetting Kubernetes support`](https://posthog.com/blog/sunsetting-helm-support-posthog)), version/commit: [please provide]
Hey @phillram I didn't realize answering the email would open a ticket 😳
To provide some clarity here, it is not all or nothing exactly. There are functionally 3 modes
Cookies Consented
All features work, Session Recording, product tracking...
Cookieless (opted out, cookieless set to on_reject)
✅ Web analytics work. identify() is a no-op
🤷♂️ Product analytics (I think events are being swollowed)
❌ Group targeted Feature Flags (e.g. on for company x)
❌ Surveys (even if they enter their name to consent)
🤷♂️ Error Reporting seems to be a no-op (good chance I am wrong here and missing a config)
Nothing (opted out, cookieless not configured)
Normally this is fine and privacy compliant, just a pain.
Ideally features which are not tied to analytics consent can have their own "functional" or "necessary" GDPR cookie so users can opt-in to things like feature flags without opting into session recording
I just opened this for the team as a whole to track, and to brainstorm ideas here on my side. This issue helps us track the efforts and thoughts we have.
Appreciate this feedback too! This makes perfect sense to me.
Activity
mhornbacher commentedon Sep 5, 2026
Hey @phillram I didn't realize answering the email would open a ticket 😳
To provide some clarity here, it is not all or nothing exactly. There are functionally 3 modes
Webanalytics work.identify()is a no-opNormally this is fine and privacy compliant, just a pain.
Ideally features which are not tied to analytics consent can have their own "functional" or "necessary" GDPR cookie so users can opt-in to things like feature flags without opting into session recording
phillram commentedon Sep 8, 2026
Hey @mhornbacher!
I just opened this for the team as a whole to track, and to brainstorm ideas here on my side. This issue helps us track the efforts and thoughts we have.
Appreciate this feedback too! This makes perfect sense to me.
phillram commentedon Sep 8, 2026
+1 https://us.posthog.com/project/2/support/tickets/71346
mhornbacher commentedon Sep 16, 2026
I am so curious what the company lore is that the main account has the ID of 2 😆 🤔