When your application sends thousands of emails a day, you cannot check each one by hand. You need data: which messages were delivered, which bounced, which were opened or clicked, and where recipients are. Mailpro’s API and webhooks provide that data so your engineering and growth teams can act on it.
What the statistics cover
- Delivery status for each message, so support teams can answer “I never got my OTP email” with facts. See delivery status for transactional email.
- Bounces, separating permanent failures (invalid addresses) from temporary ones (full mailbox, server busy).
- Opens and clicks, downloadable through the API, including breakdowns by country through geo-tracking.
- Campaign-level reporting in the Mailpro dashboard through campaign statistics and global emailing statistics.
Webhooks: statistics in real time
Polling an API for results works, but webhooks are faster. Mailpro can push events to your endpoint as they happen; the three webhook types are explained in the FAQ, and payloads are described in the webhooks documentation.
How Indian teams use the data
Fintech: prove delivery
For payment confirmations and statements, a timestamped delivery record helps support teams resolve complaints and shows that customers were informed. Store it with the transaction in your own system.
E-commerce: clean addresses at checkout
Hard bounces on order emails often mean a typo at checkout. Use bounce events to prompt the customer to correct their email address in the app or by SMS, so later dispatch and delivery emails reach them.
SaaS: separate domestic and overseas traffic
Many Indian SaaS companies serve customers in the US, Europe and the Middle East. Country-level statistics show whether engagement differs by region and help you schedule sends for each market’s time zone rather than IST.
Edtech: spot disengaged learners
If a student stops opening class reminders, that is an early signal. Feed engagement data into your product analytics to trigger a check-in from a mentor.
Statistics and the DPDP Act
Engagement data linked to an individual is personal data under the Digital Personal Data Protection Act 2023. Use it for the purposes you told users about, keep it only as long as you need it, and include it in your data-retention policy. Mailpro stores data in Switzerland, outside US jurisdiction, and never sells or rents it.
Acting on the numbers
- Rising bounce rate: review how addresses are collected and validated.
- Falling clicks on a transactional email: check the buttons and links render on mobile.
- Uneven results by time: use scheduled sending for non-urgent messages.
Setting up alerts that matter
Raw statistics are only useful if someone looks at them. Most teams set a few automatic alerts from webhook data instead of reading dashboards every day:
- Bounce spike: if hard bounces on sign-up verification emails jump above your normal level, a form or app release may have broken address validation.
- Delivery delay: if OTP or login emails are not confirmed as delivered within your expected window, alert the on-call engineer and fall back to SMS where your DLT templates allow it.
- Complaint signals: a rise in unsubscribes or complaints on a marketing stream is a sign to pause and review consent and frequency.
Keep transactional and marketing messages on separate streams so that a problem with a promotional campaign never hides a delivery issue with your payment receipts.
Festive-season load
Indian e-commerce and payments traffic peaks during the Navratri-to-Diwali period and big online sale events. Order, payment and delivery emails rise with it. Review your statistics from the previous festive season, warm up any new sending domain well in advance, and agree in advance who watches the numbers on the busiest days.
Developer resources
Start with the API documentation and the SMTP and API FAQ. For an overview of sending through the API, see email API in India.