What data fields are reported in individual level tracking CSV exports?

This article refers to the data fields available in the export tables of the Email Analytics report (Learn more).  The individual-level tracking CSV 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. Here's a quick guide to what you'll find in this report:

created_at

Type: timestamp

A date/time stamp for when this individual open was recorded. All timestamps used in Email Analytics reports are in GMT (0:00).

custom_type

Type: varchar (100)

An optional field containing custom data. It's typically used for including information about the segment the email was sent in. How to add in a custom parameter to your tracking code.

mail_client

Type: varchar (255)

The email client used for this open. For example, "Outlook".

mail_client_specific

Type: varchar (255)

The specific details of the client the email was opened in. Sometimes this is a version number, such as "Outlook 2007", it can also be a specific model number of a device, "Samsung Galaxy S9", a web browser used to open a web-based email client, "Using Internet Explorer" or even a range of versions, such as "Outlook 2000-2003".

rendering_engine

Type: varchar (255)

The rendering engine used to display the email. This is a superset of the email client. For example, many version of Outlook, as well as Lotus Notes, use the Internet Explorer engine to render emails. Other versions of Outlook use the Word engine.

platform

Type: varchar (255)

We categorize platform as Desktop, Web-based or Mobile.

read_seconds

Type: integer (11)

The number of seconds the email was opened for. This value will increase if the email is left open, up to a total of 20 seconds, which is when we stop recording. More about engagement tracking.

read_category

Type: varchar (255)

We group the read_seconds into three broader categories - Glanced, Skimmed and Read. More about engagement tracking.

city

Type: varchar (255)

The city the subscriber was in when they opened your email. If the reader is using their network's mobile data service (such as 3G), the location may not be as accurate as when using a standard internet connection. More information on geolocation tracking.

region

Type: varchar (255)

The region the subscriber was in when they opened your email. In the USA, this will typically be a state. In other countries it may be a county or province. If the reader is using their network's mobile data service (such as 3G), the location may not be as accurate as when using a standard internet connection. More information on geolocation tracking.

country

Type: varchar (255)

The country the subscriber was in when they opened your email. If the reader is using their network's mobile data service (such as 3G), the location may not be as accurate as when using a standard internet connection. More information on geolocation tracking.

long

Type: varchar (255)

An obsolete data field for newer tracking campaigns. To support our commitment to PII compliance, Litmus no longer stores the longitude and latitude coordinates of where an open took place. More information on geolocation tracking.

lat

Type: varchar (255)

An obsolete data field for newer tracking campaigns. To support our commitment to PII compliance, Litmus no longer stores the longitude and latitude coordinates of where an open took place. More information on geolocation tracking.

referrer

Type: varchar (200)

This applies only to opens that happened in a web-based email client, such as Outlook.com. We provide the full referrer header, which will list out the full web address for the email provider.

user_agent

Type: varchar (1000)

This applies only to opens that happened in a desktop or mobile email client. We'll list the full user agent of the email software.

campaign_guid

Type: varchar (50)

The GUID is the unique identifier for your campaign's tracking code that Litmus uses internally. It's helpful if you wish to combine multiple CSV exports in a single spreadsheet.

custom_data

Type: varchar (100)

An obsolete data field for newer tracking campaigns. This field exists to support older tracking codes’ data points that are now deprecated.

custom_id

Type: varchar (255)

The custom_ID field is populated when an ESP with a corresponding Unique User ID (UUID) merge tag is selected during the tracking code creation steps.  The data shown is the ID reference the ESP generates for a specific contact record (also known as Contact ID, record ID, Recipient ID, Subscriber key etc- depending on what terminology the ESP employs.). It is this ID that you should use to link all the information in a given row back to a particular subscriber/recipient within your ESP. 

reliability_category

Type: varchar (255)

The reliability_category field is populated for each open to indicate whether Litmus deems the open to be from a reliable source. We refer to the email opens that exclude Apple Mail Privacy opens as “reliable opens”. We populate this field with "Reliable" to indicate the subscriber opened from an email client other than Apple Mail Privacy.   The opens received from the Apple Mail Privacy feature are labeled "AppleMailPrivacy"

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us