Prompt
Postmark is fine but we need more event tracking
Latest observation
Nov 22, 2026
OpenAI APIWeb search: off
Understood — if Postmark is working for delivery but you need deeper event tracking, the next step is usually to add a layer for message lifecycle events and product analytics, not just SMTP/send logs.
A few options, depending on what you mean by “more tracking”:
1) Keep Postmark for sending, add event webhooks
Postmark already supports events like:
- delivered
- opened
- clicked
- bounced
- spam complaint
- unsubscribed
You can:
- enable Postmark webhooks
- receive events in your app
- store them in your database / analytics tool
- build a timeline per recipient/message
2) Add event tracking in your product
If you mean user actions around emails, such as:
- signed up after clicking email
- completed onboarding
- purchased after campaign
- reactivated after reminder
…then you’ll want:
- email event tracking
- product event tracking
- a shared
user_id/account_idto connect them
Common tools:
- Segment
- RudderStack
- Amplitude
- Mixpanel
- PostHog
3) Use a dedicated email platform if you need richer attribution
If you want more built-in reporting than Postmark gives, consider:
- SendGrid
- Mailgun
- Customer.io
- Braze
- Iterable
These tend to provide more campaign analytics and customer journey tracking, but may be more complex or expensive.
4) Track custom events with links
For example:
- email sent
- email opened
- CTA clicked
- trial started
- subscription upgraded
Then you can correlate:
- message_id
- recipient email
- campaign_id
- user_id
- timestamp
If you want, I can help you design a simple event-tracking schema for Postmark, or recommend the best stack based on whether you need:
- marketing analytics,
- transactional email analytics,
- or full customer journey tracking.