Export datasets to cloud storage destinations

  • This functionality is available to customers who have purchased the Real-Time CDP Prime or Ultimate package, Adobe Journey Optimizer, or Customer Journey Analytics. Contact your Adobe representative for more information.

This article explains the workflow required to export datasets from Adobe Experience Platform to your preferred cloud storage location, such as Amazon S3, SFTP locations, or Google Cloud Storage by using the Experience Platform UI.

You can also use the Experience Platform APIs to export datasets. Read the export datasets API tutorial for more information.

Datasets available for exporting datasets-to-export

The datasets that you can export vary based on the Experience Platform application (Real-Time CDP, Adobe Journey Optimizer), the tier (Prime or Ultimate), and any add-ons that you purchased (for example: Data Distiller).

Understand from the table below which dataset types you can export depending on your application, product tier, and any add-ons purchased:

Datasets available for export
Real-Time CDP
Profile and Experience Event datasets created in the Experience Platform UI after ingesting or collecting data through Sources, Web SDK, Mobile SDK, Analytics Data Connector, and Audience Manager.
  • Profile and Experience Event datasets created in the Experience Platform UI after ingesting or collecting data through Sources, Web SDK, Mobile SDK, Analytics Data Connector, and Audience Manager.
  • System-generated Profile Snapshot dataset.
Adobe Journey Optimizer
Refer to the Adobe Journey Optimizer documentation.
Refer to the Adobe Journey Optimizer documentation.
Customer Journey Analytics

Profile and Experience Event datasets created in the Experience Platform UI after ingesting or collecting data through Sources, Web SDK, Mobile SDK, Analytics Data Connector, and Audience Manager.

Note on availability: The ability to export datasets to the cloud is in the Limited Testing phase of release and might not be available yet in your environment. This note will be removed when the functionality is generally available. For information about the Customer Journey Analytics release process, see Customer Journey Analytics feature releases.

Data Distiller
Data Distiller (Add-on)
Derived datasets created through Query Service.

Video tutorial video-tutorial

Watch the video below for an end-to-end explanation of the workflow described on this page, benefits of using the export dataset functionality, and some suggested use cases.

Supported destinations supported-destinations

Currently, you can export datasets to the cloud storage destinations highlighted in the screenshot and listed below.

Destinations catalog page showing which destinations support dataset exports.

When to activate audiences or export datasets when-to-activate-audiences-or-activate-datasets

Some file-based destinations in the Experience Platform catalog support both audience activation and dataset export.

  • Consider activating audiences when you want your data structured into profiles grouped by audience interests or qualifications.
  • Alternatively, consider dataset exports when you are looking to export raw datasets, which are not grouped or structured by audience interests or qualifications. You could use this data for reporting, data science workflows, and many other use cases. For example, as an administrator, data engineer, or analyst, you can export data from Experience Platform to synchronize with your data warehouse, use in BI analysis tools, external cloud ML tools, or store in your system for long-term storage needs.

This document contains all the information necessary to export datasets. If you want to activate audiences to cloud storage or email marketing destinations, read Activate audience data to batch profile export destinations.

Prerequisites prerequisites

To export datasets to cloud storage destinations, you must have successfully connected to a destination. If you haven’t done so already, go to the destinations catalog, browse the supported destinations, and configure the destination that you want to use.

Required permissions permissions

To export datasets, you need the View Destinations, View Datasets, and Manage and Activate Dataset Destinations access control permissions. Read the access control overview or contact your product administrator to obtain the required permissions.

To ensure that you have the necessary permissions to export datasets and that the destination supports exporting datasets, browse the destinations catalog. If a destination has an Activate or an Export datasets control, then you have the appropriate permissions.

Select your destination select-destination

Follow the instructions to select a destination where you can export your datasets:

  1. Go to Connections > Destinations, and select the Catalog tab.

    Destination catalog tab with Catalog control highlighted.

  2. Select Activate or Export datasets on the card corresponding to the destination that you want to export datasets to.

    Destination catalog tab with Activate control highlighted.

  3. Select Data type Datasets and select the destination connection that you want to export datasets to, then select Next.

If you want to set up a new destination to export datasets, select Configure new destination to trigger the Connect to destination workflow.

Destination activation workflow with Datasets control highlighted.

  1. The Select datasets view appears. Proceed to the next section to select your datasets for export.

Select your datasets select-datasets

Use the check boxes to the left of the dataset names to select the datasets that you want to export to the destination, then select Next.

Dataset export workflow showing the Select datasets step where you can select which datasets to export.

Schedule dataset export scheduling

In the Scheduling step, you can set a start date and an export cadence for your dataset exports.

The Export incremental files option is automatically selected. This triggers an export of one or multiple files representing a full snapshot of the dataset. Subsequent files are incremental additions to the dataset since the previous export.

The first incremental file export includes all existing data in the dataset, functioning as a backfill. The export can contain one or multiple files.

Dataset export workflow showing the scheduling step.

  1. Use the Frequency selector to select the export frequency:

    • Daily: Schedule incremental file exports once a day, every day, at the time you specify.
    • Hourly: Schedule incremental file exports every 3, 6, 8, or 12 hours.
  2. Use the Time selector to choose the time of day, in UTC format, when the export should take place.

  3. Use the Date selector to choose the interval when the export should take place. Note that you currently cannot set an end date for the exports. For more information, view the known limitations section.

  4. Select Next to save the schedule and proceed to the Review step.

For dataset exports, the file names have a preset, default format, which cannot be modified. See the section Verify successful dataset export for more information and examples of exported files.

Review review

On the Review page, you can see a summary of your selection. Select Cancel to break up the flow, Back to modify your settings, or Finish to confirm your selection and start exporting datasets to the destination.

Dataset export workflow showing the review step.

Verify successful dataset export verify

When exporting datasets, Experience Platform creates one or multiple .json or .parquet files in the storage location that you provided. Expect new files to be deposited in your storage location according to the export schedule you provided.

Experience Platform creates a folder structure in the storage location you specified, where it deposits the exported dataset files. A new folder is created for each export time, following the pattern below:


The default file name is randomly generated and ensures that exported file names are unique.

Sample dataset files sample-files

The presence of these files in your storage location is confirmation of a successful export. To understand how the exported files are structured, you can download a sample .parquet file or .json file.

Compressed dataset files compressed-dataset-files

In the connect to destination workflow, you can select the exported dataset files to be compressed, as shown below:

File type and compression selection when connecting to a destination to export datasets.

Note the difference in file format between the two file types, when compressed:

  • When exporting compressed JSON files, the exported file format is json.gz
  • When exporting compressed parquet files, the exported file format is gz.parquet

Remove datasets from destinations remove-dataset

To remove datasets from an existing dataflow, follow the steps below:

  1. Log in to the Experience Platform UI and select Destinations from the left navigation bar. Select Browse from the top header to view your existing destination dataflows.

    Destination browse view with a destination connection shown and the rest blurred out.

    note tip
    Select the filter icon Filter-icon on the top left to launch the sort panel. The sort panel provides a list of all your destinations. You can select more than one destination from the list to see a filtered selection of dataflows associated with the selected destination.
  2. From the Activation data column, select the datasets control to view all datasets mapped to this export dataflow.

    The available datasets navigation option highlighted in the Activation data column.

  3. [Beta]{class="badge informative"} The Activation data page for the destination appears. Use the checkboxes on the left side of the dataset list to select the datasets which you want to remove, then select Remove datasets in the right rail to trigger the remove dataset confirmation dialog.

    note note
    This feature is in beta and only available to select customers. To request access to this feature, contact your Adobe representative.

    Remove dataset dialog showing the Remove dataset control in the right rail.

  4. In the confirmation dialog, select Remove to immediately remove the dataset from exports to the destination.

    Dialog showing the Confirm dataset removal option from the dataflow.

Dataset export entitlements licensing-entitlement

Refer to the product description documents to understand how much data you are entitled to export for each Experience Platform application, per year. For example, you can view the Real-Time CDP Product Description here.

Note that the data export entitlements for different applications are not additive. For example, this means that if you purchase Real-Time CDP Ultimate and Adobe Journey Optimizer Ultimate, the profile export entitlement will be the larger of the two entitlements, as per the product descriptions. Your volume entitlements are calculated by taking your total number of licensed profiles and multiplying by 500 KB for Real-Time CDP Prime or 700 KB for Real-Time CDP Ultimate to determine how much volume of data you are entitled to.

On the other hand, if you purchased add-ons such as Data Distiller, the data export limit that you are entitled to represents the sum of the product tier and the add-on.

You can view and track your profile exports against your contractual limits in the licensing dashboard.

Known limitations known-limitations

Keep in mind the following limitations for the general availability release of dataset exports:

  • Currently, you can only export incremental files and an end date cannot be selected for your dataset exports.
  • Exported filenames are currently not customizable.
  • Datasets created via API are currently not available for export.
  • The UI does not currently block you from deleting a dataset that is being exported to a destination. Do not delete any datasets that are being exported to destinations. Remove the dataset from a destination dataflow before deleting it.
  • Monitoring metrics for dataset exports are currently mixed with numbers for profile exports so they do not reflect the true export numbers.
  • Data with a timestamp older than 365 days is excluded from dataset exports. For more information, view the guardrails for scheduled dataset exports