Automated exports

When a regular export is required, usually for processes such as exporting of user profiles to a third-party platform, then Xtremepush Automations is the place to go.

This feature allows users to set up hourly (only available for some export types), daily, weekly or monthly export schedules via SFTP or email.


Navigate to Data > Automations and select the Exports tab.

This menu shows the full list of exports for the project and specifically their Target, Frequency and Status. It is also possible to see when they last ran and whether that export was successful.

Clicking on the last run timestamp shows details and any errors for that export.

Actions that can be performed on an existing automation can be found under > more.
Exports can be activated/de-activated and run now if an immediate export is required.

Create export

Click the Create Export button to be taken to the wizard-driven setup process.

Export Type

After giving the new export a name, the first step is to set up where you would like the export to go and the type of data you would like it to contain.

  1. Target Settings.
    Set where the data should be sent at the time of export. There are several options available:
  • Export to an email. Type out an email address and press enter. Multiple addresses can be added so the export will be sent to multiple people. When the export is complete, a message will be sent to the list of emails provided containing a link to a secure page where the export can be downloaded.
  • Export to client SFTP. Select an SFTP account that has been set up beforehand via the project's Integrations Marketplace.
  • Export an audience to a retargeting platform. This option will only show up if you have integrated ad retargeting from the Integrations Marketplace. Review our dedicated Ad Retargeting page for more details.
  1. Data Type.
    Select whether you want to export profile, device, or campaign engagement data.
  • Profiles generates a report where each line item contains the profile record along with any associated attribute data.
  • Devices exports a report where each row is a single device. Available fields:
idDevice ID (Xtremepush identifier)
profile_idProfile ID (Xtremepush identifier)
user_idUser ID (if provided)
subscriptionPush subscription status (1, 0)
last_subscription_changeTimestamp in Unix format for when this status was last updated
addressablePush addressable status (1, 0)
last_addressable_changeTimestamp in Unix format for when this status was last updated
  • Campaign engagement produces a report where each row is an engagement action in relation to a campaign. Available fields:
campaign_idCampaign ID
campaign_nameCampaign name
category_idEngagement category ID (if applicable)
category_nameEngagement category name (if applicable)
user_idUser ID (if available)
profile_idProfile ID (XP identifier)
device_idDevice ID (XP identifier)
message_typeMessage channel (email, journey, SMS, push, etc)
message_variantSplit test variant (if applicable)
message_variant_nameSplit test variant name (if applicable)
language_variantLanguage variant (if applicable)
campaign_schedule_typeCampaign schedule type (recurring, triggered, time)
emailEmail address of the profile (if available)
mobile_numberMobile number of the profile (if available)
interaction_typeInteraction type (sent, delivered, open, click, close, failed, etc)
interaction_valueAdditional info about the interaction (reason for failure, redirect URL of the click, bounce reason, etc)
workflow_action_idWorkflow node ID (only applicable for workflow campaigns)
workflow_action_nameWorkflow node name (only applicable for workflow campaigns)
timestampUnix timestamp of the interaction (in UTC)
interaction_idMessage action ID (only applicable for workflow campaigns)
trigger_idID that identifies each batch of users entering a workflow. If users enter the same workflow campaign more than once, a different trigger ID will show up against them


Can't see this option?

Automating a campaign engagement report is a new feature. Contact us if you would like to use it.

Selecting the Delta Report option will make sure the export only contains records that have been created or changed since the last time it ran, rather than being an export of the entire data in the project. For campaign engagement reports, the delta report option is compulsory.


First export of Delta engagement report

The first run of the delta engagement report provides the records from the point when export is first set up on the project until the time of run. Subsequent exports will generate records created or changed since the last time the report ran.

Data Structure

  1. Segment Settings
    The export will only include data for user profiles or devices which match the given Segment.

  2. Export Attributes
    Select which attributes should be included with the list of user profiles in the export.
    You can rearrange the selected attributes to order them in the CSV file. This might be useful if the export is being picked up by an external platform which requires them in a specific order.

It is only possible to add attributes to the exported file for profile exports.

This step doesn't apply to campaign engagement exports.


Finally, a frequency for export can be set on the scheduling step. After saving the schedule it will run at the next available time closest to the current time. Note the timezone set in your project and account for any adjustment needed in your process to avoid issues such as a file being updated in the SFTP by a system running in a timezone different to the one set in the automation schedule.