Export of SMS statistics

FTP-based data synchronizations are not available by default (additional charges will apply), contact your account manager to receive a quotation.

In order to have a data synchronization set up, you need to have an active MailUp account (not a free trial).


In case you need any further information or custom integrations, please do not hesitate to contact your sales representative.

This export type displays the statistical data about SMS channel related to one or more Mailup lists in a certain time frame.

The eventual layout is partly configurable.

What data is to be included in the report

The CSV report will report as many rows as many were the actions taken by a recipient towards a certain SMS campaign.  In details this report provide the change of the delivery state of every SMS messages sent registered in the choosen timeframe 


You can set the instance to generate reports that contains one or more of the following data except for the mobile number, the MailUp list id, the numeric identifier of the sent SMS message, the sending date of the SMS message, the date of the delivery receipt and the delivery status of the SMS message, which are mandatory columns/values that will always be displayed in the report


Data

Header Display Name

Description

Examples

Mobile

recipient

mobile phone number of the recipient

391234567890

MailUp list id

idList

Unique identifier of the MailUp list from which the SMS message was sent and where the statistical data are registered

1

SMS numeric id

idSMS

Unique identifier of the of the MailUp SMS Message that was sent 

1

Date sent SMS

sentdate

The date when the SMS message was sent

20220121T111244

Result dateresponsedateThe date when the delivery receipt provided by the mobile phone service provider is communicate to MailUp.20220121T111333

Status

status

The delivery state of the SMS Message. 
The delivery of an SMS change based on the delivery receipt that the the mobile phone service provider possibly provides MailUp with,

Values are:

  • 0 Delivered: The message was successfully delivered to the recipient's mobile device, although not necessarily seen.

  • 1 Pending, no receipt has been received.
    T
    he delivery process is in progress with the mobile operator, or may have stalled for some reason, which could include the recipient not having a phone signal, network issues, an issue with their subscription, or their phone is simply switched off
  • 2 Failure, the mobile operator isn't able to deliver the SMS message to the recipient's mobile device
    The message could have been blocked by the operator’s spam filters, the number may not exist, or the recipient’s subscription may have been suspended for some reason, or the mobile device has not been accessible for the maximum validity period defined by the mobile operator

  • 0
  • 1
  • 2
Detail of the delivery report (DLR)reason

The detail of the Delivery Receipt.

Reason codes are built following this schema:

STATUS_ROUTINGCODE_ERRORCODE. Here for details.

  • DELIVRD_AG_000
  • UNDEFINED_AG_UNDEFINED
  • REJECTD_AG_004
Subject of the SMS messagesubjectSubject of the MailUp SMS Message
Recipient fields 
Data saved in the recipients personal data fields. You can select those of your interest to the report


 Examples

It is required to export Mobile, MailUp list id, SMS numeric idDate sent SMS, Result date, Status, Detail of the delivery report (DLR) for each event

Report CSV
idlist;idSMS;recipient;sentdate;responsedate;status;reason
12020;7459;39XXXXXXXXX;20230109T074812;20230109T074816;0;DELIVRD_AG_000
12020;7459;39YYYYYYYYY;20230109T074812;20230109T074818;0;DELIVRD_AG_000
32350;18695;39UUUUUUUUU;20230109T093551;20230109T093551;1;UNDEFINED_AG_UNDEFINED
32351;18696;39ZZZZZZZZZ;20230109T094148;20230109T094158;2;REJECTD_AG_004

It is required to export Mobile, MailUp list id, SMS numeric idDate sent SMS, Result date, Status and a recipient field  (the recipient field 12 that in your business case store the customer code defined in your CRM and provided to MailUp by your CRM) for each event

Report CSV
"idlist";"idSMS";"recipient";"sentdate";"responsedate";"status";"campo12"
"1";"40";"39aaaaaaaaaaa";"20230104T151525";"20230104T151525";"1";"0142575751"
"1";"40";"39bbbbbbbbbbb";"20230104T151525";"20230104T151531";"0";"0134162821"

Environments and export timeframe

You can define which MailUp lists you want to extract data from and the extraction period.

Extraction period is the timeframe which the report refers.
Usually you can configure an Instance to generate report containing:

  • all events arose in the last 24 hours for the MailUp lists you have indicated
  • all events arose from the last export executed for the MailUp lists you have indicated

DLR (DeLivery Receipt)

Delivery Receipt (or DeLivery Reporting) is a feature of SMS MT that reports back on the delivery status of every SMS message that has been sent.

A DLR is generated when the recipient mobile device acknowledges that it has received the message.

MailUp will receive DLR from the mobile phone service provider which the recipient mobile device is served.

Based on the DLR received the delivery status of a sent SMS message can be changed ever days after sending it.

Here it is possible find more detail about possible causes of missing delivery.

Click on SMS Message

It is possible add to the report if at least one url contained in SMS messages has been clicked or not 

This is a optional functionality, if you need it please do not hesitate to contact your sales representative.

Enabling this functionalty means adding an additional columns to the report in addition to those already described.  

Data

Header Display Name

Description

Examples

Clicked

clicked

boolean field that show if at least one url contained in SMS messages has been clicked or not

  • 1 at least one url was clicked
  • 0 no url was clicked 


 Examples

It is required to export Mobile, MailUp list id, SMS numeric idDate sent SMS, Result date, Status, Detail of the delivery report (DLR) and if at least an url has been clicked or less for each event

Report CSV
idlist;idSMS;recipient;sentdate;responsedate;status;reason;clicked
12020;7459;39XXXXXXXXX;20230109T074812;20230109T074816;0;DELIVRD_AG_000;1
12020;7459;39YYYYYYYYY;20230109T074812;20230109T074818;0;DELIVRD_AG_000;1
32350;18695;39UUUUUUUUU;20230109T093551;20230109T093551;1;UNDEFINED_AG_UNDEFINED;0
32351;18696;39ZZZZZZZZZ;20230109T094148;20230109T094158;2;REJECTD_AG_004;0

It is required to export Mobile, MailUp list id, SMS numeric idDate sent SMS, Result date, Status, and if at least an url has been clicked or less for each event and a recipient field  (the recipient field 12 that in your business case store the customer code defined in your CRM and provided to MailUp by your CRM) for each event

Report CSV
"idlist";"idSMS";"recipient";"sentdate";"responsedate";"status";"clicked";"campo12"
"1";"40";"39aaaaaaaaaaa";"20230104T151525";"20230104T151525";"1";"0";"0142575751"
"1";"40";"39bbbbbbbbbbb";"20230104T151525";"20230104T151531";"0";"1";"0134162821"
"1";"40";"39ccccccccccc";"20230104T151525";"20230104T151618";"0";"0";"0166183844"

MailUp trace only click of shortened URL inserted in the SMS message.

All other URLs, extented or shortened using others services, will not be tracked.