Email Statistics

📘
API - Statistics

by application (GET) | by campaigns (GET) | by shipment (GET) | by campaign id (GET)

To find the reports of all email campaigns, you must go to the menu Statistics>Email.

KPIs

Card	Description
Messages sent	Total number of emails sent in the period.
Open rate	Percentage of sent emails that were opened. Includes the comparison with the previous period.
CTR	Click-through rate: percentage of emails in which a link was clicked. Includes the comparison with the previous period.

Sent campaigns

Column	Description
Sending ID	Identifier of the sending. A dash (—) means the sending has no specific ID.
Campaign	Campaign name. Click it to open the campaign.
Sending date	Date (and time, for scheduled sendings) of the sending.
Sendings	Number of emails sent.
Open rate	Open rate of the sending.
CTR	Click-through rate of the sending.

Campaign statistics

Click the chart icon at the end of a row to open the campaign statistics. This page includes:

Summary: total Sent, Opened, Clicked and CTR for the campaign.
Chart: evolution of Sent, Opened and Clicked emails over time.
Scheduled sendings: upcoming sendings of the campaign, with Sending ID, Creation Date, Status, Date of dispatch and Actions. These statistics are based on the latest 3-month period.
Send history: every past sending of the campaign, with Sending ID, Sending date, Sent, Opened, Clicked, Failed and CTR.

Click Back to statistics to return to the main view.

Sendings evolution

Daily chart with three metrics: Sendings (dashed line), Open rate and CTR.

Download the CSV files

Click Download .csv.
Choose one of the options:
- Download .CSV of statistics by day
- Download .CSV of statistics with device data
- Download .CSV of statistics by campaign

Statistics by day

One row per day with activity.

Field	Description
`statsDate`	Day the data refers to.
`numContactsSent`	Number of contacts the email was sent to.
`numContactsClicked`	Number of contacts who clicked a link.
`numContactsOpened`	Number of contacts who opened the email.
`numContactsSpammed`	Number of contacts who marked the email as spam.
`numContactsSoftBounced`	Number of soft bounces (temporary delivery failures, such as a full inbox).
`numContactsHardBounced`	Number of hard bounces (permanent delivery failures, such as an address that doesn't exist).
`numContactsBlocked`	Number of emails blocked and not sent (for example, addresses previously blocked).
`numContactsDelivered`	Number of emails delivered: contacts sent minus soft bounces, hard bounces and blocked emails.

Statistics with device data

One row per email sent to each recipient. Use this file to see exactly what happened with each address.

Field	Description
`applicationId`	ID of your indigitall project.
`campaignId`	Campaign ID.
`campaignName`	Campaign name.
`campaignCreatedAt`	Date and time the campaign was created (UTC).
`campaignUpdatedAt`	Date and time the campaign was last updated (UTC).
`sendingId`	Sending ID.
`email`	Recipient's email address.
`sentAt`	Date and time the email was sent (UTC).
`openedAt`	List of the dates and times the email was opened. Empty (`[]`) if it wasn't opened.
`clicks`	List of the clicks made in the email, with the date and time of each one (`clicked_at`).
`spammedAt`	Date and time the recipient marked the email as spam, if applicable.
`softBounces`	Soft bounce details, if any.
`hardBounces`	Hard bounce details, including the date (`bounced_at`), if any.
`blocked`	Block details, including the date (`blocked_at`) and the reason (for example, `preblocked`), if the email was blocked. Below, we outline all possible causes of the block so you can address and resolve them accordingly.
`replacements`	Personalization values used in the email, in JSON format.
`customData`	Custom data sent with the email, if any.
`categoryId`	ID of the category assigned to the campaign, if any.
`categoryName`	Name of the category assigned to the campaign, if any.

spammedAt: It's possible to download a report where a specific date appears in the spammedAt field, but there's no corresponding entry in the blocked field. This happens because the email was initially marked as spam (and the spammedAt field logs the exact time it occurred), but in subsequent delivery attempts, the message successfully reached the recipient. As a result, the blocked field remains empty.

Statistics by campaign

One row per campaign.

Field	Description
`campaignId`	Campaign ID.
`name`	Campaign name.
`createdDate`	Date and time the campaign was created (UTC).
`numContactsSent`	Number of contacts the email was sent to.
`numContactsClicked`	Number of contacts who clicked a link.
`numContactsOpened`	Number of contacts who opened the email.
`numContactsSpammed`	Number of contacts who marked the email as spam.
`numContactsSoftBounced`	Number of soft bounces.
`numContactsHardBounced`	Number of hard bounces.
`numContactsBlocked`	Number of blocked emails.
`numContactsDelivered`	Number of emails delivered.
`categoryId`	ID of the category assigned to the campaign, if any.
`categoryName`	Name of the category assigned to the campaign, if any.

Custom Data

We’ve updated our email reports to automatically display the custom columns selected by your business. Whenever you view or export your campaign reports, your custom data fields will appear seamlessly integrated alongside standard platform metrics.

Key Features & Benefits

Immediate User Identification: Eliminates the need for manual data cross-referencing in Excel between campaign metric reports and your CRM or database to identify specific user actions.
Tailored, Relevant Insights: Reports display the exact variables that matter most to your business (e.g., Member_ID, City, Customer_Type, Assigned_Store).
Faster Decision-Making: Enables quick filtering of opens, clicks, or conversions by any custom attribute from your own customer database.

Block Reasons

The final field in the email data statistics refers to emails that were blocked, along with the specific underlying reason. We’ll explain it to you:

Each of the following fields represents a specific reason why an email was blocked from reaching the recipient. These details help diagnose and resolve deliverability issues.

recipient: The email address of the recipient serves as the identifier for the failed delivery. Pay close attention when entering email addresses—typos are a common cause of delivery failure.
mailbox inactive: The recipient's mailbox is no longer active. This typically occurs when the email account has been closed or deactivated.
quota exceeded: The recipient's inbox has exceeded its storage limit and cannot accept new messages until space is freed.
blacklisted: The sender’s domain, IP, or server is on a blacklist used by the recipient’s email provider, which prevents delivery.
spam reporter: The email address or domain has previously been reported for sending spam by users, leading to automatic blocking.
domain: Issues related to the recipient's domain, such as DNS misconfiguration or a non-existent domain.
no mail host: The recipient’s domain does not have a valid mail server, making delivery impossible.
relay/access denied: The sending server is not authorized to relay messages to the recipient’s server. This may be due to strict server policies or authentication issues.
greylisted: The recipient's server temporarily rejects the message as a spam-prevention measure. Delivery will be re-attempted.
typofix: The recipient email appears to contain a typo (e.g., "gmial.com" instead of "gmail.com"). The system identifies and flags these as likely delivery failures.
content: Bad or empty template. Make sure the template you're using contains content and isn't corrupted.
error in template language: The email template contains invalid or malformed syntax, preventing successful rendering and delivery.
spam: The message was flagged as spam by the recipient's email system due to factors like language, formatting, or reputation. You should contact us to investigate this issue.
content blocked: Specific content elements—such as attachments, URLs, or keywords—were blocked by the recipient’s filtering system. Please contact us so we can review the email content.
policy issue: The email was rejected due to a policy violation, such as sending to a restricted address or exceeding rate limits. Although we do receive alerts when this happens, make sure to contact us for further information.
system: A generic server-side error occurred during delivery. Please contact us if you receive an event of this type.
protocol issue: An error occurred in the communication protocol between the sender and recipient’s email servers. We will fix it.
connection issue: A network or connectivity problem prevented the sender from establishing a connection to the recipient’s mail server.
preblocked: The system preemptively blocked the email before attempting delivery, usually based on known high-risk patterns or prior negative signals. We didn't try to send it to avoid damaging your reputation.
duplicate in campaign: The email was identified as a duplicate within the same campaign and was not sent again to avoid redundancy.