Skip to content

fix(usage): keep $ip so PostHog can hash cookieless events - #9

Merged
devchaudhary24k merged 2 commits into
mainfrom
dev
Sep 27, 2026
Merged

devchaudhary24k merged 2 commits into
mainfrom
dev

Conversation

@devchaudhary24k

@devchaudhary24k devchaudhary24k commented Sep 27, 2026 •

Copy link
Copy Markdown
Member

No events have been reaching PostHog. The app sends cookieless events, and PostHog builds each visitor's anonymous ID by hashing their IP, user agent and host. Our `before_send` set `$ip: null` on every event. PostHog's capture endpoint still answered 200, but ingestion then dropped every event as `cookieless_missing_ip` (PostHog's notes).

  • Remove `before_send`. The PostHog project's Discard client IP data setting removes the IP after hashing.
  • Replace the test that required `$ip: null` with one that requires the IP to be left alone.
  • Update ADR 0005, `implementation.md` and the privacy page to match.
  • Also on this branch: `DEPLOY.md` now describes the PostHog project settings.

`pnpm validate` passes (538 tests).

🤖 Generated with Claude Code


View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.

devchaudhary24k and others added 2 commits September 28, 2026 02:43
PostHog computes the cookieless distinct ID from the IP, user agent and
host, and drops cookieless events without $ip (cookieless_missing_ip).
before_send set $ip to null on every event, so PostHog accepted them and
then discarded all of them. The project's "Discard client IP data"
setting removes the IP after hashing instead.

Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
@devchaudhary24k
devchaudhary24k merged commit 50936a0 into main Sep 27, 2026
16 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant