Skip to content

Feature Request: Add per-feature opt-in consent options #95522

Open

Description

@phillram

Feature request

Is your feature request related to a problem?

  • Currently we offer an option to Opt in to collecting data.
  • However, this is an all or nothing option.
  • So it becomes difficult if you want to only allow some features of Posthog to apply consent.

Describe the solution you'd like

  • It would be great if you could break down consent by feature.
  • For example opting in to session replay only, or rejecting event capture only.

Describe alternatives you've considered

  • At the moment, there's no real way to split out different features.

Additional context

Debug info

- [ 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]

Activity

  1. mhornbacher commented on Sep 5, 2026

    @mhornbacher
    Contributor

    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

    1. Cookies Consented
      • All features work, Session Recording, product tracking...
    2. 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)
    3. 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

  2. phillram commented on Sep 8, 2026

    @phillram
    ContributorAuthor

    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.

  3. phillram commented on Sep 8, 2026

    @phillram
    ContributorAuthor
  4. mhornbacher commented on Sep 16, 2026

    @mhornbacher
    Contributor

    I am so curious what the company lore is that the main account has the ID of 2 😆 🤔

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions