Amazon SES events are tracked with specific event type IDs in SendPost, allowing you to distinguish between native SendPost events and Amazon SES events.Documentation Index
Fetch the complete documentation index at: https://docs.sendpost.io/llms.txt
Use this file to discover all available pages before exploring further.
Amazon SES Event Types
| Event Type | ID | Description |
|---|---|---|
| SES Processed | 27 | Email accepted by Amazon SES for delivery |
| SES Delivered | 28 | Email successfully delivered to recipient |
| SES Hard Bounced | 29 | Permanent delivery failure (invalid address, domain doesn’t exist) |
| SES Soft Bounced | 30 | Temporary delivery failure (mailbox full, temporarily blocked) |
| SES Spam Report | 31 | Recipient marked email as spam (complaint event) |
| SES Dropped | 32 | Email rejected by Amazon SES (invalid address, etc.) |
| SES Open | 33 | Recipient opened the email (automatically tracked) |
| SES Click | 34 | Recipient clicked a link (automatically tracked) |
| SES Rendering Failure | 35 | Email rendering failure event |
| SES Unsubscribe | 36 | Recipient unsubscribed |
Bounce Type Details
Amazon SES categorizes bounces into two types:Hard Bounce (ID: 29)
Hard Bounce (ID: 29)
Permanent failure (invalid email, domain doesn’t exist). These addresses should be removed from your list.
Soft Bounce (ID: 30)
Soft Bounce (ID: 30)
Temporary failure (mailbox full, temporarily blocked). Amazon SES may retry these automatically. Consider these as temporary issues.
Event Data
Each Amazon SES event includes:- Message ID (for correlation)
- Recipient email
- Timestamp
- SMTP response code (for bounces)
- User agent (for opens)
- Clicked URL (for clicks)
- SES-specific metadata
Event Type Quick Reference
| Event | ID | SES Event Name |
|---|---|---|
| Processed | 27 | Send |
| Delivered | 28 | Delivery |
| Hard Bounce | 29 | Bounce (permanent) |
| Soft Bounce | 30 | Bounce (transient) |
| Spam Report | 31 | Complaint |
| Dropped | 32 | Reject |
| Open | 33 | Open |
| Click | 34 | Click |
| Rendering Failure | 35 | Rendering Failure |
| Unsubscribe | 36 | Subscription |
Next Steps
- View analytics to see event statistics
- Troubleshoot issues with event processing