PostHog transactional email evaluation¶
Assessed 17 November 2026 for AIM Store project 743463. This is a separate, read-only assessment; no sender, template, DNS, API key or sending rule was changed.
Recommendation¶
Pilot a noncritical customer email before moving authentication emails. PostHog can place delivery and engagement events beside customer journey events, which could help explain whether customers receive a receipt and return to the app. Its transactional email feature is currently in beta and shares workflow email billing and quotas. Do not assume the analytics free allowance includes email. Keep infrastructure alerts in Grafana/Kuma so product email configuration does not become a dependency of monitoring.
Current project readiness¶
- No email sender is configured: the integrations query returned zero results and no further page.
capture_workflows_engagement_eventsis false. Enabling it would add send, delivery, open, click and bounce events to project event usage.- The supplied
phc_token is a public analytics ingestion key. Email sending requires a separate server-only project secret key with Transactional email Write permission. Never put this key in a client bundle or chat. - A verified sending domain and its DNS records are needed before sending.
For a pilot, keep content in application code, use the customer's existing UUID as the distinct ID, and use a durable business-event idempotency key. Persist delivery state for retries beyond the provider's 24-hour idempotency window. Respect suppression/quota errors. Following an uncertain network outcome, retry with the same key instead of sending through a second provider.
Authentication messages need explicit sensitive-data protection and a reviewed logging policy. The provider supports one recipient per transactional send. Any migration should include delivery, bounce, suppression and retry tests before changing the application's active email route.
Sources¶
- Transactional email documentation
- Project sender configuration
- Live read-only project checks:
integrations-listwithkind=emailandworkflows-sending-rules-get.