Repository navigation
Conversation
Turning engagement capture off only keeps the email's engagement events off the recipient's person. The email still carries PostHog's open pixel and tracked links, so the docs no longer read as "no open or click tracking". Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
posthog-python Compliance ReportDate: 2026-11-09T12:12:52.270869+00:00 ✅ All Tests Passed!121/121 tests passed Capture_V1 Tests✅ 95/95 tests passed View Details
Capture_Ai Tests✅ 5/5 tests passed View Details
Feature_Flags Tests✅ 17/17 tests passed View Details
Feature_Flags_Local_Evaluation Tests✅ 4/4 tests passed View Details
|
SDK performance: posthog-python1 change worth reviewing: 1 observed improvement. Flags require at least a 5% change in the median and all six pairs agreeing on direction. This is a noise filter, not proof of a performance change or a CI gate.
View all results
Values are medians of paired measurements. Not flagged does not mean unchanged. Unavailable means a measurement could not be provided, not zero. Estimated allocation measurements retain their instrumentation uncertainty. RSS measures the whole process, not just SDK allocations; observed peaks are sampled checkpoints. Paired ranges in the diagnostics describe variability, not confidence intervals. Each shard uses its own runner; compare Before PR against With PR within a row, not across shards. Compared 102 metric rows; 102 rows shown in all results. Omitted or shortened data remain in |
Code sends are sensitive, so PostHog leaves their links alone and only the open pixel counts anything. The earlier wording said PostHog rewrites links to count clicks, which is false for a code send. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
There was a problem hiding this comment.
Approved.
The diff is limited to documentation, with no runtime or API contract changes and no open review concerns. Server-side tracking behavior cannot be independently verified from this SDK checkout.
- Author wrote 100% of the modified lines and has 1 merged PRs in these paths (familiarity STRONG).
- PostHog Review (Standard) reviewed the current head: no findings.
- posthog[bot] reviewed the current head.
Gate mechanics and policy version
| Gate | Result | |
|---|---|---|
| prerequisites | ✓ | all clear |
| deny-list | ✓ | no deny categories matched |
| size | ✓ | 7L, 1F substantive — within ceiling |
| tier | ✓ | T1-agent / T1a-trivial (7L, 1F, single-area, docs) |
| stamphog 2.8.0 | .stamphog/policy.yml @ 2f75765 · reviewed head 2f75765 |
|
Note 🤖 Claude Opus 5.5 responding on behalf of Michael Closing: #1216 replaced this. It deprecates |
💡 Motivation and Context
capture_engagement=Falseon a code send as "no open or click tracking", which is wrong.💚 How did you test it?
📝 Checklist
If releasing new changes
🤖 Agent context
Autonomy: Human-driven (agent-assisted)
claude-opus-5-5), in a T3 Code thread that came out of a code-send trial.🤖 Generated with Claude Code