Guide
Email Reports and Recipient Outcomes
Separate provider acceptance, delivery events, engagement, and attribution.
SoundSync
Interpret the report
| Measure | Meaning |
|---|---|
| Accepted sends | The provider accepted the recipient send; this is the campaign usage boundary |
| Delivery / failure / bounce / complaint | Provider outcome events, where received and processed |
| Opens and clicks | Recorded engagement signals; client privacy features can distort them |
| Unsubscribes and suppressions | Changes that affect future marketing eligibility |
| Attributed revenue / conversions | Recorded attribution, not proof that the email caused every sale |
| Recipient list | Per-recipient accepted, skipped, failed, or pending context |
| Queue/activity | Work still waiting, running, or requiring attention |
Zero can mean pending data
Sending progress and engagement arrive through different processes. An accepted send can precede delivery or click statistics. Check the time range, provider event availability, campaign state, and recipient records before treating an empty chart as no activity.
Do not publish private emails or complete recipient records in a support screenshot. Use redacted examples and the campaign ID when asking for help.
Reconcile with usage separately
Monthly usage aggregates qualifying sends across campaigns and automations. A campaign's engagement chart is not the monthly invoice. Use the usage guide and statement for the charge recorded.