Guides

Create Export

In this page you'll learn how to export data from your applications. From the list of export jobs, click in the New Job button top right corner:

To access this page expand the Data menu and click in Export:

Main Menu

In this page, click in the New Export button in the top right corner:

new export job button

This will open a page where you will actually create your export job. You should start by choosing which type job you want to create:

types

Read further to learn how to export all the types of data that we collect for your app.

Export Devices/Contacts/Numbers

To export the device data stored in your application, select the Export Devices from the Job Type selector:

job type devices

This job will generate confirmation emails throughout its processing steps. If you wish to disable that you should toggle ON the following options:

skip emails

To export all the devices including the inactive ones, toggle the following option:

export all

By default we will export all the devices (with any medium), to export only devices with a certain medium use the following option:

medium

If you wish to include the device tags in the export job, toggle the following option:

include tags

When you toggle this option, you will be able to specify the tag separator. By default we will use the vertical bar (a.k.a pipe) as the separator but you can use this field to define another character:

tags separator

If you wish to limit the export of your devices, you can use the familiar Criteria selection to filter out the devices you need.

criteria

Learn how to set up a custom criteria by reading our guides located here.

Resulting export file

ColumnDescription
deviceIDThe unique Notificare's device identifier.
subscriptionIdThe push token, email contact or SMS number.
p256dhAn Elliptic curve Diffie–Hellman public key on the P-256 curve (that is, the NIST secp256r1 elliptic curve). The resulting key is an uncompressed point in ANSI X9.62 format. Only available for web push devices.
authAn authentication secret to use with the p256dh public key. Only available for web push devices.
userIDA unique string assigned to a device. This value will be auto-generated if none provide by the client's application.
userNameA string assigned to the device's user profile which can be used as a placeholder in messages. This column will be assigned as anonymous if none is provided by the client's application.
autoGeneratedA binary representation if a device was auto-generated or not. This value will be 1 if a userID was not assigned to a device.
platformThe platform which a device uses. Possible values are: Android, iOS, WebPush, Email and SMS.
transportThe transport technology used to deliver messages to a device. Possible values are: Notificare, Android, iOS, WebPush, Email and SMS.
originThe protocol and domain where the device was registered. Only available for web push devices.
mediumThe type of channel for a specific device. Possible values are: Android, iOS, WebPush, Email and SMS.
osVersionThe version of the device's operating system.
sdkVersionThe version of the SDK used by the device.
appVersionThe version assigned by the application, if applicable.
osStringA string identifying the version of the device's operating system.
browserNameA string describing the browser name. Only available for web push devices.
browserVersionThe version of the browser used by the device. Only available for web push devices.
deviceStringA string identifying the device model.
countryAn ISO 3166-1 alpha-2 string identifying the device's country. This value is only present for devices using location services.
languageAn ISO 639-1 or 639-2/T string identifying the device's language.
regionAn ISO 3166-1 alpha-2 string identifying the device's region.
latitudeA floating point indicating the geographic coordinate that specifies the north–south position of a point on the Earth's surface. This value is only present for devices using location services.
longitudeA floating point indicating the geographic coordinate that specifies the east–west position of a point on the Earth's surface. This value is only present for devices using location services.
locationAccuracyThe distance in meters of the accuracy of a geographic coordinate of a point on the Earth's surface. This value is only present for devices using location services.
altitudeThe altitude of a geographic coordinate. Can be positive (above sea level) or negative (below sea level). This value is only present for devices using location services.
courseThe course of the location in degrees true North. Negative if course is invalid. This value is only present for devices using location services.
speedThe speed of the location in m/s. Negative if speed is invalid. This value is only present for devices using location services.
locationLastUpdatedThe timestamp when the device's location was last collected. This value is only present for devices using location services.
locationLastUpdatedFormattedAn ISO 8601 string representing the date and time when the device's location was last collected. This value is only present for devices using location services.
lastActiveThe timestamp when the device was last active.
lastActiveFormattedAn ISO 8601 string representing the date and time when the device was last active.
registrationDateThe timestamp when the device was first registered.
registrationDateFormattedAn ISO 8601 string representing the date and time when the device was first registered.
inboxSizeThe number of inbox items in the device's local inbox.
inboxUnreadThe number of unread inbox items in the device's local inbox.
inboxLastUpdatedThe timestamp when the device was first registered
inboxLastUpdatedFormattedAn ISO 8601 string representing the date and time when the device's inbox was last updated.
timeZoneOffsetThe time zone difference, in hours, from the device to UTC.
importedA binary representation if a device was imported or not. This value will be 1 if a device was create via an import job.
activeA binary representation if a device is active or not. This value will be 1 if a device is active.
expiredA binary representation if a device is expired or not. This value will be 1 if a device is expired.
expireDateThe timestamp when the device was first expired.
expireDateFormattedAn ISO 8601 string representing the date and time when the device was first expired.
dndStartA string representing the hour and minute for the beginning of the Do Not Disturb of a device.
dndEndA string representing the hour and minute for the end of the Do Not Disturb of a device.
allowedUIA binary representation if a device is allowed remote messages or not. This value will be 1 if a device allowed remote messages. This value will be always 1 for Email and SMS devices.
backgroundAppRefreshA binary representation if a device supports background refresh or not. This value will be 1 if a device supports background refresh. This value will be always 1 for Email and SMS devices.
locationServicesAuthStatusA string representing the authorization status for a device. Possible values are: none, use and always. This value is only present for devices using location services.
locationServicesAccuracyAuthA string representing the accuracy authorization for a device. Possible values are: full and reduced. This value is only present for devices using location services.
bluetoothEnabledA binary representation if a device has bluetooth or not. This value will be 1 if a device has bluetooth enabled. This value is only present for iOS and Android devices using location services.
userDataA string representing the userData assigned to a device.
tagsA string representing the tags assigned to a device.

Export Users

To export the user data stored in your application, select the Export Users from the Job Type selector:

job type users

This job will generate confirmation emails throughout its processing steps. If you wish to disable that you should toggle ON the following options:

skip emails

If you would like to include users that are also inactive, toggle the following option:

export all users

If you would like to include the users' segments, toggle the following option:

include segments

If you toggle this option ON, there's two different ways of including segments, Combined will simply include all the segments of a user in one single column and Separated will include all segments in individual columns.

include segments options

If you choose Combined, you will only be able to select if you wish to export the segments' names instead of their Ids. For that toggle the following option:

show names

If you choose Separated you will also be able to select if you wish to export the segments' names instead of their Ids:

show names

Additionally, if you have the Users & Authentication add-on, you will also be able to include all the user preferences by toggling the following option:

include user preferences

Optionally, if you just want to export certain segments, you can select them in the following field:

filter segments

For that, you will need to search for existing segments like shown below:

search segments

You can select one more segments by clicking in the one you want to use:

select segments

When you are done selecting segments, simply click the Done button. The selected segments will look like this:

selected segments

If you wish to limit the export of your users, you can use the familiar Criteria selection to filter out the devices you need. You also have the option of filtering out users by last active date and/or registration date

user criteria

Learn how to setup a custom criteria by reading our guides located here.

Resulting export file

ColumnDescription
userIDA unique string assigned to a device. This value will be auto-generated if none provide by the client's application.
userNameA string assigned to the device's user profile which can be used as a placeholder in messages. This column will be assigned as anonymous if none is provided by the client's application.
accessTokenA string representing an randomly generated identifier for a user which can be used by the Mail to Push service.
pictureA string representing an URL of an image assigned to the user.
autoGeneratedA binary representation if a user was auto-generated or not. This value will be 1 if a userID was not assigned to a profile.
validatedA binary representation if a user was validated or not. This value will be 1 if the user was validated.
lastActiveThe timestamp when the user was last active.
lastActiveFormattedAn ISO 8601 string representing the date and time when the user was last active.
registrationDateThe timestamp when the user was first registered.
registrationDateFormattedAn ISO 8601 string representing the date and time when the user was first registered.
activeA binary representation if a user is active or not. This value will be 1 if the user is active.
segmentsA string representing the segment's Ids or segment's names assigned to an user.

Export User Data

To export a specific user's data stored in your application, select the Export User Data from the Job Type selector:

job type user data

This job will generate confirmation emails throughout its processing steps. If you wish to disable that you should toggle ON the following options:

skip emails

Then go ahead and search for a user in your application by using the field below:

search user

And finally click in the user you wish to export data of. It will look like the field below:

selected user

Resulting export file

This job will generate a .zip file with all the data from this user, including purchases, automation history, trigger history, replies, events, inbox items, notifications and device's data and all its media files (if applicable).

Purchases

ColumnDescription
identifierA string representing the Notificare's identifier.
transactionIdentifierA string representing the platform's transaction identifier.
dateThe timestamp when the purchase was made.
dateFormattedAn ISO 8601 string representing the date and time when the purchase was made.
deviceIDThe unique Notificare's device identifier.
typeA string representing the type of purchase. Possible values are: consumable and non-consumable.
priceA number representing the price of the purchase.
currencyA string representing the currency in which the purchase was made.
dataA string representing any additional data assigned to the purchase.

Automation History

ColumnDescription
automationA string representing the Notificare's automation connector identifier.
dateThe timestamp when the automation connector was triggered.
dateFormattedAn ISO 8601 string representing the date and time when the automation connector was triggered.
deviceIDThe unique Notificare's device identifier.
actionA binary representation if an automation connector was executed or not. This value will be 1 if the automation connector was executed.
dataA string representing any additional data assigned to the automation connector.

Trigger History

ColumnDescription
triggerA string representing the Notificare's geo-trigger identifier.
dateThe timestamp when the geo-trigger was triggered.
dateFormattedAn ISO 8601 string representing the date and time when the geo-trigger was triggered.
deviceIDThe unique Notificare's device identifier.
actionA binary representation if a geo-trigger was executed or not. This value will be 1 if the geo-trigger was executed.
sentA binary representation if a geo-trigger generated a message. This value will be 1 if the geo-trigger generated a message.
dataA string representing any additional data assigned to the geo-trigger.

Replies

ColumnDescription
timeThe timestamp when the reply was received.
timeFormattedAn ISO 8601 string representing the date and time when the reply was received.
notificationA string representing the Notificare's notification identifier.
deviceIDThe unique Notificare's device identifier.
labelA string representing the action's label.
targetA string representing the action's label (if applicable).
messageA string representing any user input assigned to the reply.
mediaA string representing the URL path to any media file assigned to the reply.

Events

ColumnDescription
typeThe type of event that was executed.
timeThe timestamp when the event was executed.
timeFormattedAn ISO 8601 string representing the date and time when the event was executed.
notificationA string representing the Notificare's notification identifier.
deviceIDThe unique Notificare's device identifier.
sessionIDA string representing a session's identifier (if applicable).
dataA string representing any additional data assigned to the event.

Inbox

ColumnDescription
notificationA string representing the Notificare's notification identifier.
deviceIDThe unique Notificare's device identifier.
timeThe timestamp when the inbox item was received.
timeFormattedAn ISO 8601 string representing the date and time when the inbox item was received.
messageA string representing the message of an inbox item.
titleA string representing the title of an inbox item.
subtitleA string representing the subtitle of an inbox item.
attachmentUriA string representing the URL of the lock screen image of an inbox item.
attachmentMimeTypeA string representing the mime type of the lock screen image of an inbox item.
extraA string representing any extra data assigned to the inbox item.
dataA string representing any additional data assigned to the inbox item.
openedA binary representation if an inbox item was opened. This value will be 1 if the inbox item was opened.

Notifications

ColumnDescription
notificationA string representing the Notificare's notification identifier.
timeThe timestamp when the notification was created.
timeFormattedAn ISO 8601 string representing the date and time when the notification was created.
scopeA string representing the target audience scope for the notification.
deviceIDThe unique Notificare's device identifier.
messageA string representing the message of a notification.

Devices

ColumnDescription
deviceIDThe unique Notificare's device identifier.
subscriptionIdThe push token, email contact or SMS number.
p256dhAn Elliptic curve Diffie–Hellman public key on the P-256 curve (that is, the NIST secp256r1 elliptic curve). The resulting key is an uncompressed point in ANSI X9.62 format. Only available for web push devices.
authAn authentication secret to use with the p256dh public key. Only available for web push devices.
userIDA unique string assigned to a device. This value will be auto-generated if none provide by the client's application.
userNameA string assigned to the device's user profile which can be used as a placeholder in messages. This column will be assigned as anonymous if none is provided by the client's application.
autoGeneratedA binary representation if a device was auto-generated or not. This value will be 1 if a userID was not assigned to a device.
platformThe platform which a device uses. Possible values are: Android, iOS, WebPush, Email and SMS.
transportThe transport technology used to deliver messages to a device. Possible values are: Notificare, Android, iOS, WebPush, Email and SMS.
originThe protocol and domain where the device was registered. Only available for web push devices.
mediumThe type of channel for a specific device. Possible values are: Android, iOS, WebPush, Email and SMS.
osVersionThe version of the device's operating system.
sdkVersionThe version of the SDK used by the device.
appVersionThe version assigned by the application, if applicable.
osStringA string identifying the version of the device's operating system.
browserNameA string describing the browser name. Only available for web push devices.
browserVersionThe version of the browser used by the device. Only available for web push devices.
deviceStringA string identifying the device model.
countryAn ISO 3166-1 alpha-2 string identifying the device's country. This value is only present for devices using location services.
languageAn ISO 639-1 or 639-2/T string identifying the device's language.
regionAn ISO 3166-1 alpha-2 string identifying the device's region.
latitudeA floating point indicating the geographic coordinate that specifies the north–south position of a point on the Earth's surface. This value is only present for devices using location services.
longitudeA floating point indicating the geographic coordinate that specifies the east–west position of a point on the Earth's surface. This value is only present for devices using location services.
locationAccuracyThe distance in meters of the accuracy of a geographic coordinate of a point on the Earth's surface. This value is only present for devices using location services.
altitudeThe altitude of a geographic coordinate. Can be positive (above sea level) or negative (below sea level). This value is only present for devices using location services.
courseThe course of the location in degrees true North. Negative if course is invalid. This value is only present for devices using location services.
speedThe speed of the location in m/s. Negative if speed is invalid. This value is only present for devices using location services.
locationLastUpdatedThe timestamp when the device's location was last collected. This value is only present for devices using location services.
locationLastUpdatedFormattedAn ISO 8601 string representing the date and time when the device's location was last collected. This value is only present for devices using location services.
lastActiveThe timestamp when the device was last active.
lastActiveFormattedAn ISO 8601 string representing the date and time when the device was last active.
registrationDateThe timestamp when the device was first registered.
registrationDateFormattedAn ISO 8601 string representing the date and time when the device was first registered.
inboxSizeThe number of inbox items in the device's local inbox.
inboxUnreadThe number of unread inbox items in the device's local inbox.
inboxLastUpdatedThe timestamp when the device was first registered
inboxLastUpdatedFormattedAn ISO 8601 string representing the date and time when the device's inbox was last updated.
timeZoneOffsetThe time zone difference, in hours, from the device to UTC.
importedA binary representation if a device was imported or not. This value will be 1 if a device was create via an import job.
activeA binary representation if a device is active or not. This value will be 1 if a device is active.
expiredA binary representation if a device is expired or not. This value will be 1 if a device is expired.
expireDateThe timestamp when the device was first expired.
expireDateFormattedAn ISO 8601 string representing the date and time when the device was first expired.
dndStartA string representing the hour and minute for the beginning of the Do Not Disturb of a device.
dndEndA string representing the hour and minute for the end of the Do Not Disturb of a device.
allowedUIA binary representation if a device is allowed remote messages or not. This value will be 1 if a device allowed remote messages. This value will be always 1 for Email and SMS devices.
backgroundAppRefreshA binary representation if a device supports background refresh or not. This value will be 1 if a device supports background refresh. This value will be always 1 for Email and SMS devices.
locationServicesAuthStatusA string representing the authorization status for a device. Possible values are: none, use and always. This value is only present for devices using location services.
locationServicesAccuracyAuthA string representing the accuracy authorization for a device. Possible values are: full and reduced. This value is only present for devices using location services.
bluetoothEnabledA binary representation if a device has bluetooth or not. This value will be 1 if a device has bluetooth enabled. This value is only present for iOS and Android devices using location services.
userDataA string representing the userData assigned to a device.
tagsA string representing the tags assigned to a device.

Export Regions

To export all the regions you've created so far, you only have to select the Export Regions option from the Job Type selector:

job type regions

This job will generate confirmation emails throughout its processing steps. If you wish to disable that you should toggle ON the following options:

skip emails

Resulting export file

ColumnDescription
regionIdA string representing the Notificare's region identifier.
referenceKeyA string representing the external's key identifier.
nameA string representing the region's name.
descriptionA string representing the region's description.
addressA string representing the region's address.
tagsA string representing the tags assigned to a region.
categoryA string representing the region's category. Possible values are: fence, poi, city, country.
timezoneThe timezone of the region.
timeZoneOffsetThe time zone difference, in hours, from the region to UTC.
countryAn ISO 3166-1 alpha-2 string identifying the region's country.
majorA number representing the Major identifier for a region.
distanceA number representing the region's radius in meters.
latitudeA floating point indicating the geographic coordinate that specifies the north–south position of a point on the Earth's surface.
longitudeA floating point indicating the geographic coordinate that specifies the east–west position of a point on the Earth's surface.
coordinatesA string representing a GeoJSON Polygon (if applicable).

Export Beacons

To export the all the beacons you've created so far, you only need to select the Export Beacons options from the Job Type selector:

job type beacons

This job will generate confirmation emails throughout its processing steps. If you wish to disable that you should toggle ON the following options:

skip emails

Resulting export file

ColumnDescription
beaconIdA string representing the Notificare's beacon identifier.
nameA string representing the beacon's name.
timezoneThe timezone of the beacon.
majorA number representing the Major identifier for a beacon.
minorA number representing the Minor identifier for a beacon.
latitudeA floating point indicating the geographic coordinate that specifies the north–south position of a point on the Earth's surface.
longitudeA floating point indicating the geographic coordinate that specifies the east–west position of a point on the Earth's surface.

Export Messages

To export all the messages you've created so far, select the Export Messages from the Job Type selector:

job type messages

This job will generate confirmation emails throughout its processing steps. If you wish to disable that you should toggle ON the following options:

skip emails

Optionally, for this export job, you can provide a date range of the messages you want to export:

date range

If you would like to use relative dates instead, you can toggle the following option ON:

use relative dates

When this option is ON, you are able to instead the values for your start and end date in seconds:

relative dates

This allows you to provide a period of time relative to the date when the job is executed. This can be extremely useful when you are using Scheduled Tasks.

If you also want to include archived messages too, make sure you toggle the following option:

include all messages

Optionally you will also be able to select if you wish to export the segments' names instead of their Ids (if applicable):

show names

Resulting export file

ColumnDescription
notificationIdA string representing the Notificare's notification identifier.
mediumA string representing the message's medium.
titleA string representing the message's title. Only applicable for push messages.
subtitleA string representing the message's subtitle. Only applicable for push messages.
messageA string representing the message's message.
subjectA string representing the message's subject. Only applicable for email messages.
timeThe timestamp when the message was created.
timeFormattedAn ISO 8601 string representing the date and time when the message was created.
typeA string representing the message's type.
scopeA string representing the target audience scope for the message.
segmentsA string representing the segments used as the target audience, if applicable. Only available for messages with scope segments.
tagsA string representing the tags used as the target audience, if applicable. Only available for messages with scope tags.
segmentsCriteriaA string representing the segments used in criteria as the target audience, if applicable. Only available for messages with scope criteria.
tagsCriteriaA string representing the tags used in criteria as the target audience, if applicable. Only available for messages with scope criteria.
locationsCriteriaA string representing the geographical points used in criteria as the target audience, if applicable. Only available for messages with scope criteria.
propertiesCriteriaA string representing the device properties used in criteria as the target audience, if applicable. Only available for messages with scope criteria.
eventCriteriaA string representing the device properties used in event criteria as the target audience, if applicable. Only available for messages with scope event.
triggeredA binary representation if a message is triggered. This value will be 1 if a message is triggered.
scheduledA binary representation if a message is scheduled. This value will be 1 if a message is scheduled.
archivedA binary representation if a message is archived. This value will be 1 if a message is archived.
statusA string representing the deliverability state for the message. Possible values are: saved, gathering, sending, error and finished.
sentA number representing the amount of devices that the message was sent to.
failsA number representing the amount of devices that the message failed to be delivered.
openedA number representing the total amount of times that the message was opened.
uniqueOpenedA number representing the unique amount of times that the message was opened.
repliedA number representing the total amount of times that the message was replied to. Only available when a message contains actions.
durationA number representing the time in seconds that the system took to deliver the message.
scheduleStatusA string representing the schedule state for the message. Possible values are: scheduled, running, cancelled and finished.
scheduleTimeAn ISO 8601 string representing the date and time when the message was scheduled.
scheduleLocalA binary representation if a message is scheduled for the device's local time. This value will be 1 if a message is scheduled for the device's local time.

Export Replies

To export replies generated by your push campaigns, select the Export Replies from the Job Type selector:

job type replies

This job will generate confirmation emails throughout its processing steps. If you wish to disable that you should toggle ON the following options:

skip emails

Then you should select which push message you want to export replies in the following field:

search notifications

When you're done selecting a message, it should look like this:

selected notification

Resulting export file

ColumnDescription
timeThe timestamp when the reply was received.
timeFormattedAn ISO 8601 string representing the date and time when the reply was received.
notificationA string representing the Notificare's notification identifier.
deviceIDThe unique Notificare's device identifier.
labelA string representing the action's label.
targetA string representing the action's label (if applicable).
messageA string representing any user input assigned to the reply.
mediaA string representing the URL path to any media file assigned to the reply.

Export Events

To export events generated by you applications, select the Export Events from the Job Type selector:

job type events

This job will generate confirmation emails throughout its processing steps. If you wish to disable that you should toggle ON the following options:

skip emails

And make sure you select which type of events you want to export. Learn more about event types here.

event type

If you have selected the Custom Event type, you also need to provide the name of your custom event:

custom event name

Optionally, for this export job, you can provide a start and end date for the events you want to export:

date range

If you would like to use relative dates instead, you can toggle the following option ON:

use relative dates

When this option is ON, you are able to use the values for your start and end date in seconds instead:

relative dates

This allows you to provide a period of time relative to the date when the job is executed. This can be extremely useful when you are using Scheduled Tasks.

Additionally, for this type of export job, you can provide an advanced filtering criteria. This is similar to what you can do when sending a notification. It will allow you to filter the results of this export job based on segments, tags, location or device properties:

event criteria

Learn more about how to setup a criteria in our guides located here.

Finally if you've selected an event of type Custom Event and you are looking to export only events with certain values (your app must register arbitrary data for this to work) you can use Custom Data Filters to get a fine-grained export job based on the data you care about:

data filters

Learn more about how to create data filters in our guides located here.

Resulting export file

ColumnDescription
eventIdA string representing the event's identifier.
typeThe type of event that was executed.
timeThe timestamp when the event was executed.
timeFormattedAn ISO 8601 string representing the date and time when the event was executed.
deviceIDThe unique Notificare's device identifier.
userIDA string representing the device's assigned user identifier.
subscriptionIdA string representing the push token, email address or SMS number.

Export Passes

To export all the passes generated by a specific pass template, select the Export Passes from the Job Type selector:

job type passes

This job will generate confirmation emails throughout its processing steps. If you wish to disable that you should toggle ON the following options:

skip emails

You should select the pass template which you would like to export passes from. To do that you need to search for an existing pass template in the following field:

search pass templates

Then simply click the desired template to select it:

selected pass template

Resulting export file

This export file will also contain all the fields of a pass where each column will be the key of a field prefixed with pass_.

ColumnDescription
pass_serialA string representing the pass serial.
pass_barcodeA string representing the pass barcode.
pass_descriptionA string representing the pass description.
pass_barcode_alt_textA binary representation if a pass should show the human-readable barcode message. This value will be 1 if a pass should show the human-readable barcode message.
pass_relevant_dateAn ISO 8601 string representing the date and time when the pass is relevant (if applicable).
pass_expiration_dateAn ISO 8601 string representing the date and time when the pass expires (if applicable).

Export Campaign Results

To export the results of a campaign, select the Export Campaign Results from the Job Type selector:

job type campaign results

This job will generate confirmation emails throughout its processing steps. If you wish to disable that you should toggle ON the following options:

skip emails

And select the campaign which you would like to export the results from. To do that you need to search for an existing campaign in the following field:

search campaign results

Then simply click the desired campaign to select it:

selected campaign results

Resulting export file

ColumnDescription
campaignA string representing the campaign's identifier.
triggerA string representing the campaign's trigger identifier.
triggerTypeA string representing the campaign's trigger type.
regionA string representing the geo-zone's identifier.
regionNameA string representing the geo-zone's name.
beaconA string representing the beacon's identifier.
beaconNameA string representing the beacon's name.
beaconMajorA string representing the beacon's Major identifier.
beaconMinorA string representing the beacon's Minor identifier.
dateThe timestamp when the campaign was created.
dateFormattedAn ISO 8601 string representing the date and time when the campaign was created.
deviceIDThe unique Notificare's device identifier.
userIDA string representing the device's assigned user identifier.
sentA boolean representing if a message was sent or not.

Export Campaign Events

To export the raw events of a campaign, select the Export Campaign Events from the Job Type selector:

job type campaign events

This job will generate confirmation emails throughout its processing steps. If you wish to disable that you should toggle ON the following options:

skip emails

You should then select the campaign which you would like to export the replies from. To do that you need to search for an existing campaign in the following field:

search campaign results

Then simply click the desired campaign to select it:

selected campaign results

Optionally, for this export job, you can provide a start and end date for the events you want to export:

date range

If you would like to use relative dates instead, you can toggle the following option ON:

use relative dates

When this option is ON, you are able to use the values for your start and end date in seconds instead:

relative dates

This allows you to provide a period of time relative to the date when the job is executed. This can be extremely useful when you are using Scheduled Tasks.

Resulting export file

ColumnDescription
campaignA string representing the automation connector's identifier.
triggerA string representing the automation connector's trigger identifier. (in Location Based Campaigns)
notificationA string representing the Notificare's notification identifier.
typeA string representing the type of the event
timeThe timestamp when the event was executed.
timeFormattedAn ISO 8601 string representing the date and time when the event was executed.
deviceIDThe unique Notificare's device identifier.
userIDA string representing the device's assigned user identifier.

Export Campaign Replies

To export the raw replies of a campaign, select the Export Campaign Replies from the Job Type selector:

job type campaign replies

This job will generate confirmation emails throughout its processing steps. If you wish to disable that you should toggle ON the following options:

skip emails

You should then select the campaign which you would like to export the replies from. To do that you need to search for an existing campaign in the following field:

search campaign results

Then simply click the desired campaign to select it:

selected campaign results

Optionally, for this export job, you can provide a start and end date for the events you want to export:

date range

If you would like to use relative dates instead, you can toggle the following option ON:

use relative dates

When this option is ON, you are able to use the values for your start and end date in seconds instead:

relative dates

This allows you to provide a period of time relative to the date when the job is executed. This can be extremely useful when you are using Scheduled Tasks.

Resulting export file

ColumnDescription
campaignA string representing the automation connector's identifier.
triggerA string representing the automation connector's trigger identifier. (in Location Based Campaigns)
notificationA string representing the Notificare's notification identifier.
labelA string representing the label of the action
targetA string representing the target (if one is provided)
messageA string with the message provided by the user (if one is provided)
mediaA URL with the media uploaded by the user (if one is provided)
timeThe timestamp when the reply was executed.
timeFormattedAn ISO 8601 string representing the date and time when the reply was executed.
deviceIDThe unique Notificare's device identifier.
userIDA string representing the device's assigned user identifier.

Export Campaigns Summary

To export the stats summary of one or more campaigns, select the Export Campaigns Summary from the Job Type selector:

job type campaigns summary

This job will generate confirmation emails throughout its processing steps. If you wish to disable that you should toggle ON the following options:

skip emails

You should then select one or more campaigns you would like to export the summary from. To do that you need to search for an existing campaign:

search campaigns summary

To select campaigns, simply click in the campaign you wish to add:

select campaigns summary

When you are done selecting campaigns, click in the Done button and this field will look like the one below:

selected campaigns summary

Resulting export file

ColumnDescription
campaignA string representing the campaign's identifier.
campaignNameA string representing the campaign's name.
infoTypeA string representing the campaign's stats type. Possible value are: notifications, triggers and automations.
sentA number representing the amount of devices that the campaign's message was sent to.
failsA number representing the amount of devices that the campaign's message failed to be delivered.
openedA number representing the total amount of devices that opened the campaign's message.
uniqueOpenedA number representing the unique amount of devices that opened the campaign's message.
repliesTotalA number representing the total amount of devices that opened an action in the campaign's message. Only applicable if message has actions.
repliesUniqueA number representing the unique amount of devices that opened an action in the campaign's message. Only applicable if message has actions.

Export Automation Connectors Summary

To export the stats summary of one or more automation connectors, select the Export Automation Connectors Summary from the Job Type selector:

Job Type

This job will generate confirmation emails throughout its processing steps. If you wish to disable that you should toggle ON the following options:

skip emails

You should then select one or more automation connectors you would like to export the summary from. To do that you need to search for an existing connector:

Search Connector

Then simply click to select one or more connectors from the resulting list as shown below:

select connectors

One you've selected the connectors you wish to export the summary from, click in the Done button. It will display something like the field shown below:

selected connectors

Resulting export file

ColumnDescription
automationA string representing the automation connector's identifier.
automationNameA string representing the automation connector's name.
notificationA string representing the Notificare's notification identifier.
sentA number representing the amount of devices that the automation connector's message was sent to.
failsA number representing the amount of devices that the automation connector's message failed to be delivered.
openedA number representing the total amount of devices that opened the automation connector's message.
uniqueOpenedA number representing the unique amount of devices that opened the automation connector's message.
repliesTotalA number representing the total amount of devices that opened an action in the automation connector's message. Only applicable if message has actions.
repliesUniqueA number representing the unique amount of devices that opened an action in the automation connector's message. Only applicable if message has actions.

Export Automation Connectors Events

To export the raw events of one or more automation connectors, select the Export Automation Connectors Events from the Job Type selector:

Job Type

This job will generate confirmation emails throughout its processing steps. If you wish to disable that you should toggle ON the following options:

skip emails

You should then select one or more automation connectors you would like to export the summary from. To do that you need to search for an existing connector:

Search Connector

Then simply click to select one or more connectors from the resulting list as shown below:

select connectors

One you've selected the connectors you wish to export the raw events from, click in the Done button. It will display something like the field shown below:

selected connectors

Optionally, for this export job, you can provide a start and end date for the events you want to export:

date range

If you would like to use relative dates instead, you can toggle the following option ON:

use relative dates

When this option is ON, you are able to use the values for your start and end date in seconds instead:

relative dates

This allows you to provide a period of time relative to the date when the job is executed. This can be extremely useful when you are using Scheduled Tasks.

Resulting export file

ColumnDescription
automationA string representing the automation connector's identifier.
automationNameA string representing the automation connector's name.
notificationA string representing the Notificare's notification identifier.
eventIdA string representing the event's identifier.
typeThe type of event that was executed.
timeThe timestamp when the event was executed.
timeFormattedAn ISO 8601 string representing the date and time when the event was executed.
deviceIDThe unique Notificare's device identifier.
userIDA string representing the device's assigned user identifier.

Export Automation Connectors Replies

To export the raw replies of one or more automation connectors, select the Export Automation Connectors Replies from the Job Type selector:

Job Type

This job will generate confirmation emails throughout its processing steps. If you wish to disable that you should toggle ON the following options:

skip emails

You should then select one or more automation connectors you would like to export the summary from. To do that you need to search for an existing connector:

Search Connector

Then simply click to select one or more connectors from the resulting list as shown below:

select connectors

One you've selected the connectors you wish to export the raw events from, click in the Done button. It will display something like the field shown below:

selected connectors

Optionally, for this export job, you can provide a start and end date for the events you want to export:

date range

If you would like to use relative dates instead, you can toggle the following option ON:

use relative dates

When this option is ON, you are able to use the values for your start and end date in seconds instead:

relative dates

This allows you to provide a period of time relative to the date when the job is executed. This can be extremely useful when you are using Scheduled Tasks.

Resulting export file

ColumnDescription
automationA string representing the automation connector's identifier.
automationNameA string representing the automation connector's name.
notificationA string representing the Notificare's notification identifier.
labelA string representing the label of the action
targetA string representing the target of the action (if one is provided)
messageA string with the message provided by the user (if one is provided)
mediaA URL with the media uploaded by the user (if one is provided)
timeThe timestamp when the reply was executed.
timeFormattedAn ISO 8601 string representing the date and time when the reply was executed.
deviceIDThe unique Notificare's device identifier.
userIDA string representing the device's assigned user identifier.

Export Automation Connector History

To export the raw trigger history of a specific automation connector, select the Export Automation Connector History from the Job Type selector:

Job Type

This job will generate confirmation emails throughout its processing steps. If you wish to disable that you should toggle ON the following options:

skip emails

You should then select one automation connector you would like to export the trigger history from. To do that you need to search for an existing connector:

Search Connector

Optionally, for this export job, you can provide a start and end date for the triggers history you want to export:

date range

If you would like to use relative dates instead, you can toggle the following option ON:

use relative dates

When this option is ON, you are able to use the values for your start and end date in seconds instead:

relative dates

This allows you to provide a period of time relative to the date when the job is executed. This can be extremely useful when you are using Scheduled Tasks.

Resulting export file

ColumnDescription
automationA string representing the automation connector's identifier.
dateThe timestamp when the reply was executed.
dateFormattedAn ISO 8601 string representing the date and time when the reply was executed.
deviceIDThe unique Notificare's device identifier.
userIDA string representing the device's assigned user identifier.
matchDataValuethe value that matched the connector data filters (if applicable).

Once you are done selecting all the options for your export job, click in the Create Job button to actually create it:

create button

Learn how to download your export job files, by reading the guides located here.