Delivery, bounce and engagement reporting by domain, provider and stream, with logs for every message.
Ask questions in plain English and get charts and a written explanation back.
Provider Sent Delivered Bounced Gmail [N] [%] [%] Outlook [N] [%] [%] Yahoo [N] [%] [%] Other [N] [%] [%]
Trends over time with the reasons behind failures.
See how each mailbox provider treats your traffic.
Opens and clicks with automated traffic filtered out.
Search by recipient, subject or message ID.
Email a summary to your team on a schedule.
Take the data into your own tools.
Start from the dashboard or a saved report.
Domain, workspace, stream, tag or time range.
Send a report to your team or export it.
Switch between stages to see what you control at each step. Illustrative interface with sample data.
Provider-level views show where deferrals and bounces start, so you can act early.
If delivery drops only at one mailbox provider, the provider breakdown shows it quickly. You can then drill into those messages to read the deferral reasons.
Use workspaces or tags to separate customers, then schedule a weekly summary email for each. Agencies avoid manual spreadsheet work and keep clients informed. Clients stay informed without extra effort.
Search the message log by recipient or subject to see exactly when an email was accepted, deferred or delivered, and answer the support ticket with facts.
Tag sends by template and compare delivery and engagement. Learn which messages perform best and which need rewriting, without exporting data to another tool. Decisions rest on evidence, not guesses.
Ask questions such as why bounces rose on Tuesday and receive a chart with a written explanation and links to the underlying messages. Answers cite the data they used.
Models learn your normal patterns by provider and stream, alert you to unusual deferral or complaint shifts, and forecast likely volume against plan limits. Thresholds and recipients are yours to set.
A scheduled summary highlights what changed, what needs attention and suggested next steps in plain English. Your team reviews it like any other report. Share it with stakeholders if you wish.
Based on your own engagement history, the system shows which hours tend to perform better for an audience. Treat it as guidance, since each list behaves differently.
AI features are assistive: they explain and highlight, and your team decides which alerts and actions to use. [Confirm which AI features are available at launch.]
Overall rates hide problems. Break results down by provider, domain and stream before concluding that everything is healthy.
Choose bounce and complaint thresholds before there is an incident. Alerts based on your baseline catch drift that dashboards you rarely open miss.
Privacy features and image prefetching distort open data. Lean on clicks, replies and conversions for decisions that matter.
Use a naming convention for tags such as campaign, template and environment. Consistent tags make later comparisons possible.
A bounce percentage tells you something is wrong; the reason codes tell you what. Drill into the logs when numbers move.
Email analytics measures how your email performs through delivery, bounce, complaint, open and click data. It shows whether messages reached mailbox providers and how recipients responded, so you can find and fix deliverability and content problems. Both views help when diagnosing a problem.
Search the message log by recipient, subject or message ID and open the entry. It shows each attempt, the response from the receiving server and the final status. The error reference explains common codes. Compare the response text with the error reference to understand it.
Open tracking is an estimate. We filter known automated opens, but image prefetching and privacy features still distort the numbers. Use opens as a trend indicator and rely on clicks and conversions for important decisions. Pair them with other signals. Pair them with clicks, replies and downstream conversions.
Yes. Use workspaces for full separation or tags for lighter grouping, then filter reports and logs accordingly. Agencies commonly use one workspace per client. Filters let you narrow each report to a single customer, so you can share only the relevant view with them or export the data for your own client reporting needs.
Yes, reports can be emailed to your team on a schedule, and data can be exported as CSV for use in your own tools. Choose a frequency and a recipient list, and each report arrives as a summary your team can read without logging in. Data can also be exported as CSV for your own analysis and long-term storage.
[Confirm retention by plan.] Check the pricing page or your plan details for how long logs and aggregated reports remain available. Logs and reports may be retained for different periods, so export anything you must keep for compliance, audits or year-on-year comparisons before it expires under your plan, and set a regular export if so.
Delivery rate means the receiving server accepted the message. Inbox placement is whether it landed in the inbox rather than spam. We report acceptance and engagement signals, but placement itself is not directly observable by any sender. No sender can see the final folder directly.
You can ask questions in plain language, receive explanations and charts, get anomaly alerts and read a weekly digest. These are aids to interpretation, and your team decides what to do. [Confirm which AI features are available at launch.] Try asking a real question from last week.
Open tracking is an estimate. We filter known automated opens, but no method is perfect.
Yes, use workspaces or tags to separate customers.
Yes, reports can be emailed to your team on a schedule.
Create an account, add your domain and send your first email.