The reports available in Email Analytics are a great start to learning more about who is opening and reading your emails. Downloading the CSV file of your results puts even more actionable data in your hands. There are four different reports that are available for export in CSV format from your Email Analytics reports.
- Recent Activity
- Email Client Data
- Engagement Data
- Individual Tracking
Exporting your reports
You may export your CSV reports at any time within the Export tab on the lefthand side of your campaign report page.
Individual Level Tracking Report
This file contains very detailed information—it may contain millions of rows of records and be quite large in file size. This report displays one unique open on each row for the email(s) associated with the tracking code. You’ll see the time/date stamp for each open (all timestamps are in GMT), the email address or unique ID passed in the merge tag, mail client, engagement, platform, geolocation, IP address and more. A full description of the fields available in the individual level tracking report is available.
If you did not include a merge tag in your tracking code, you’ll still see each open, but there will be no data in the ’email_address’ field. Similarly, if you included a campaign ID or other secondary identifier, you’ll find that in the ‘custom_type’ column.
Haven’t received your individual level CSV report email?
If your export email has not arrived within the ETA we provided on the export page, you may want to check our status page for any delays, and also ensure that your local email settings allow for .zip/.csv downloads. Some workplaces may block emails that contain these links. If you know that your workplace does block these kinds of links, you may want to contact your IT team to change this setting for you.
Alternatively, you may want to send your CSV download emails to a third party email address (a personal Gmail or Outlook.com email account, for example) if you are not receiving your emails at your primary address. We also recommend adding firstname.lastname@example.org to your whitelist as well.
Email Client Usage Report
This file contains aggregated email client usage information across the email(s) associated with your tracking code. This information is broken down by the mail clients used and summarizes the total number of opens Email Analytics collected for each email client.
|151||Apple Mail||Apple Mail 5|
In the above example, we see 1,794 opens in Outlook.com when the user accessed their mail using the Internet Explorer browser, 151 opens from Apple Mail version 5, 44 opens from the default mail client on an Android device, and 2 opens from Gmail when accessed from an iPhone’s browser (rather than the mail app installed by default on the device).
This file will contain all print and forward activity, the mail client that was used for the activity, and a date/time stamp (all timestamps are in GMT) for each activity. For tracking codes that have used a merge tag with their tracking code, you’ll see an additional field that includes the email address or other unique ID associated with the activity:
|Activity Type||Activity Detail||MailClient||LoggedAt|
|Forwardedemail@example.com||Apple Mail||9/1/11 18:37|
For codes that were used without a merge tag, the Activity Detail field will be left blank.
This file contains aggregated engagement information across the email(s) associated with your tracking code. This information is broken down by the mail clients used and summarizes the total number of opens Email Analytics collected for each of three categories: glanced, read and skimmed. It also includes which platform (mobile, desktop or webmail) that we classify the mail client under.
In the above example, this means that for Outlook 2010, Email Analytics detected 592 users that ‘read’ the email (viewed for 12-20 seconds), 275 that ‘skimmed’ (viewed for 4-11 seconds), and 28 that ‘glanced’ (viewed for 3 seconds or less). No merge data is included in this report.
Need more help?
Ask the world's largest community of email designers.Post a discussion in the Litmus Community