From 8d010719fae1c5d735d87c5d84e801ec032f2d0e Mon Sep 17 00:00:00 2001 From: "Reichenbach, Michael" <755327+Silthus@users.noreply.github.com> Date: Mon, 9 Nov 2026 11:45:29 +0000 Subject: [PATCH 1/2] docs(emails): say capture_engagement keeps open and click tracking 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 --- posthog/emails.py | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/posthog/emails.py b/posthog/emails.py index c53528c7c..84867745d 100644 --- a/posthog/emails.py +++ b/posthog/emails.py @@ -242,8 +242,11 @@ class CodeEmailArgs(_RecipientArgs): without a plain-text part. from_: A verified sender, such as ``"Acme "``. reply_to: One address or a list of addresses. An empty list sends no reply-to. - capture_engagement: Capture the email's opens and clicks as events of - the recipient. Defaults to ``True``. A project whose admin turned + capture_engagement: Capture the email's engagement events, such as + opens and clicks, on the recipient's person. Defaults to ``True``. + Turning it off doesn't change the email: PostHog still adds its + open pixel and rewrites links to count opens and clicks. A project + whose admin turned engagement capture off captures nothing, whatever the send asks. A template made in PostHog follows the project's setting, so the template form doesn't take it. From 2f75765106966fea688ce5105eb8fa3cb68a1bbe Mon Sep 17 00:00:00 2001 From: "Reichenbach, Michael" <755327+Silthus@users.noreply.github.com> Date: Mon, 9 Nov 2026 12:07:09 +0000 Subject: [PATCH 2/2] docs: say a code send never rewrites its links 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 --- posthog/emails.py | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/posthog/emails.py b/posthog/emails.py index 84867745d..2b08db745 100644 --- a/posthog/emails.py +++ b/posthog/emails.py @@ -243,10 +243,10 @@ class CodeEmailArgs(_RecipientArgs): from_: A verified sender, such as ``"Acme "``. reply_to: One address or a list of addresses. An empty list sends no reply-to. capture_engagement: Capture the email's engagement events, such as - opens and clicks, on the recipient's person. Defaults to ``True``. - Turning it off doesn't change the email: PostHog still adds its - open pixel and rewrites links to count opens and clicks. A project - whose admin turned + deliveries and opens, on the recipient's person. Defaults to + ``True``. Turning it off doesn't change the email: PostHog still + adds its open pixel to count opens. It never rewrites the email's + links, so it counts no clicks. A project whose admin turned engagement capture off captures nothing, whatever the send asks. A template made in PostHog follows the project's setting, so the template form doesn't take it.