Repository navigation
posthog-v7.89.0
Minor changes
-
ac25b4bf A send with
template_keynow takestrackingandsensitive. The template form doesn't take either one.trackingchooses what PostHog tracks for the email.tracking=Trueturns on opens, clicks and engagement events.tracking=Falseturns them all off. A dict such as{"clicks": True}or{"engagement": False}turns each kind on or off, and a key you leave out keeps its default. Without it, PostHog counts opens, captures engagement events, and counts clicks only when the email isn't sensitive.sensitivemarks an email that carries login links, reset tokens or codes. A sensitive email keeps its links as they are unlesstrackingturns clicks on, leaves its subject off engagement events, and keeps its content out of PostHog's logs. Without it, a send whosetemplate_keymatches a template saved in PostHog follows that template's setting, and any other send is sensitive. A send that sets neither option works exactly as before.posthog.emails.send( to="user@example.com", template_key="newsletter", subject="What's new at Acme", html=rendered_html, sensitive=False, )
capture_engagementis deprecated in favor oftracking={"engagement": False}. It keeps working, but PostHog refuses a send that sets both.trackingandsensitiveneed PostHog's API support, which is rolling out. Until it reaches your PostHog instance, PostHog refuses a send that sets either one. — Thanks @Silthus!