The receiver for provider delivery events. Each event is mapped into the platform's own vocabulary and stored against the message. Opens fetched by a mail provider's proxy are recorded but flagged, using the provider's own bot field first rather than sniffing user agents.
Also called: bounced email · delivery events · spam complaint · unsubscribe · did they open it · delivered · bounced · click tracking · email analytics
- 1Verified with the same HMAC-SHA256 (timestamp + token) scheme as the inbound route, but the payload is JSON with the signature nested
- 2Provider event names are mapped to a stable internal set
- 3The provider's own bot flag is the authority for machine detection and is checked first
- 4Message ids are stripped of angle brackets so both sides of the join agree
Handing a message to a provider is not the same as it arriving, and nowhere near the same as it being read — but handed over was all the platform knew, so a bounced estimate looked exactly like a delivered one. Delivered, opened, clicked, bounced, complained and unsubscribed are now recorded per message as the provider reports them. Machine-generated opens are flagged rather than quietly counted, because a number that overstates itself is worse than no number at all.
- No knowledge of what happened after handoff
- Spam complaints and bounces invisible
- Machine opens counted as readership
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →