fix: preserve PostHog cookieless identity fields - #193
Merged
Merged
Conversation
|
React Doctor found no new issues. 🎉 Reviewed by React Doctor for commit |
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
tagium | f03b55c | Commit Preview URL Branch Preview URL |
Aug 30 2026, 06:13 PM |
flamboh
force-pushed
the
t3code/posthog-app-errors-usage
branch
from
August 30, 2026 17:24
97a7bd3 to
fc9f156
Compare
flamboh
force-pushed
the
t3code/posthog-app-errors-usage
branch
from
August 30, 2026 18:12
fc9f156 to
f03b55c
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Note
🤖 GPT-5.6 Sol on behalf of Oliver
problem
Tagium's privacy sanitizer removed PostHog fields required for cookieless identity. PostHog needs
$cookieless_mode,$raw_user_agent,$host, and the request IP; missing$hostcauses the event to be dropped before identity generation.This does not fix PostHog's query-time traffic classification. PostHog deliberately removes the raw user agent and IP after computing the cookieless identity, so stored cookieless events may still appear as
Automation / no_user_agent.solution
$cookieless_mode: truetagium.apporsave.tagium.apphuman review
Setup: use the production PostHog project with cookieless server hash mode enabled and send fresh events through
t.tagium.app.tagium.appandsave.tagium.app.cookieless_missing_hostingestion warnings.$posthog_cookieless.$raw_user_agentor$ip.Important edge cases: malformed, empty, foreign, wrong-app, and non-cookieless host inputs are rejected. Historical dropped events cannot be repaired.
Decision for review: this PR improves cookieless ingestion and identity quality only. Query-time bot classification remains an upstream PostHog limitation; the app does not duplicate raw identifiers to bypass PostHog's privacy boundary.
Automatically verified with 100 test files / 660 tests, TypeScript typecheck, targeted lint, and diff validation. The PostHog project setting and production proxy IP behavior still require manual verification after deployment.
Changes were implemented and reviewed by GPT-5.6 Sol and GPT-5.6 Luna in T3 Code through the Codex harness.