When your booking engine, online store or portal sends email through an API, nobody sees the messages go out. Statistics are how you know that confirmations are arriving, receipts are not bouncing, and password resets reach customers before they give up. This page explains what to track for a Saint Lucian application and how to respond.
Where the numbers come from
Mailpro gives you three sources: the API’s own responses when you send, webhooks that notify your system of later events, and the dashboard in your account with global statistics. Use the first two to automate reactions, and the third for regular review.
Metrics to watch
Acceptance
Did the API accept your request? Errors here usually mean authentication problems, malformed data or missing fields. Log every rejected call with its error message.
Delivery and bounces
Accepted is not delivered. Track hard bounces (invalid addresses) and soft bounces (temporary problems such as full mailboxes). For a hotel, a bounced confirmation is an operational issue: flag it so staff can contact the guest by phone. The FAQ on transactional delivery status explains each status.
Time to deliver
Password resets and one-time codes must arrive within seconds. If customers in Saint Lucia or abroad report delays, check the timestamps in your logs against delivery events.
Engagement
Opens and clicks matter less for transactional mail, but they reveal useful patterns. Are guests clicking the “add excursions” link in the pre-arrival email? Are customers opening shipping updates? Treat opens as indicative only, since some devices pre-load images.
Complaints and unsubscribes
Transactional messages should rarely draw complaints. If they do, something is wrong: marketing content mixed into receipts, or messages going to people who did not expect them.
Using webhooks well
- Update the customer record automatically when an address hard-bounces.
- Create a task for staff when a booking confirmation fails.
- Record delivery times for audit trails, useful for firms that must show clients when documents were sent.
The FAQ on Mailpro webhook types describes the events available.
Seasonal patterns
Many Saint Lucian systems see traffic rise in the winter season and around major events such as Carnival in July. Compare statistics with the same period last year rather than with the previous month, and check that your sending domain’s reputation is healthy before peak season starts.
Geography of your recipients
Most transactional mail from a tourism business goes abroad, while a local retailer’s goes mainly to Saint Lucian addresses. Geo-tracking shows where messages are opened, which helps you confirm that time-sensitive emails reach people during their daytime, and that your SMS or phone follow-ups target the right time zone.
When numbers change suddenly
A sudden jump in bounces after a website update often means a form field is saving addresses incorrectly. A sudden drop in deliveries to one provider can follow a DNS change that broke SPF or DKIM. Keep a simple change log, so that when a statistic moves you can match it to what changed that day.
A monthly check-list
- Rejected API calls: any new error types?
- Bounce rate: stable or rising?
- Delivery delays: any complaints from customers?
- Webhook failures: is your endpoint receiving every event?
- Domain authentication: SPF, DKIM and DMARC still valid after any website or DNS changes?
Data and privacy
Statistics include personal data such as addresses and activity. Under Saint Lucia’s Data Protection Act 2011, keep only what you need and for no longer than needed. Mailpro stores statistics in Switzerland with the rest of your account data.
New to the API? Start with email API for Saint Lucia, or compare approaches in API versus SMTP.