Open Tracking
WhentrackOpens is enabled in your send request:
- SendPost injects a tracking pixel pointing to SendPost’s
/track/openendpoint - Opens are recorded as CS Open events (ID: 65)
- View open rates in the SendPost dashboard and events page
Click Tracking
WhentrackClicks is enabled:
- SendPost rewrites links to SendPost’s
/track/clickendpoint - Clicks are recorded as CS Click events (ID: 66)
- View click rates and clicked URLs in the dashboard
Unsubscribe Tracking
Unsubscribe headers and links point to SendPost’s/track/unsubscribe endpoint. Use the {{unsubscribe}} template variable or configure unsubscribe headers. Events are stored as CS Unsubscribe (ID: 68).
Viewing Analytics
- Go to Analytics (or Events) in your SendPost dashboard
- Filter by:
- Provider: Select your Custom SMTP provider
- Event Type: Filter by CS event types (58–68)
- Date Range: Choose the time period
- Sub-account: Filter by sub-account
Rate Limiting & Throttling
Default Rate Limit
Custom SMTP TPSPs have a Max Rate Per Hour (default 100) set at creation. This is the global rate limit for this provider. You can change it in the provider settings.Per-Provider Throttling
SendPost supports per-provider throttling across 27 ISP categories (e.g., Gmail, Yahoo, Outlook). Custom SMTP uses the same provider-specific settings (stored in the same JSON columns as other TPSPs). You can set different hourly limits per provider (e.g., cap Gmail at 1,000/hour, others at 10,000/hour). Per-provider limits are configurable up to 100,000 messages per hour per provider.Configuring Rate Limits
Stats Synchronization
Custom SMTP events update the same Redis counters and PostgreSQL stat tables as other TPSPs:- tpspstat – General TPSP stats per sub-account per provider
- tpspdomainstat – TPSP stats per domain per sub-account per provider
- aggregatedtpspsmtpcodestat – SMTP code aggregation for error analysis
Next Steps
- Event types for full list of CS events
- Troubleshooting analytics or rate limiting