(Beta) Export files on-demand to batch destinations using the Experience Platform UI

IMPORTANT
The Export file now option in Adobe Experience Platform is currently in Beta. The documentation and functionality are subject to change.
Contact your Adobe representative for access to this functionality.
IMPORTANT
To activate data, you need the View Destinations, Activate Destinations, View Profiles, and View Segments access control permissions. Read the access control overview or contact your product administrator to obtain the required permissions.

Export file now overview overview

This article explains how to use the Experience Platform UI to export files on-demand to batch destinations such as cloud storage and email marketing destinations.

The Export file now control allows you to export a full file without interrupting the current export schedule of a previously scheduled audience. This export happens in addition to previously scheduled exports and does not change the export frequency of the audience. The file export is triggered immediately and it picks up the latest results from Experience Platform segmentation runs.

You can also use the Experience Platform APIs for this purpose. Read how to activate audiences on-demand to batch destinations via the ad-hoc activation API.

Prerequisites prerequisites

To export files on-demand to batch 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.

How to export files on-demand how-to-export-files-on-demand

  1. Go to Connections > Destinations, select the Browse tab and the filter symbol to show existing connections to your desired batch destinations.

    Image highlighting how to get to the browse tab and filter existing dataflows.

  2. Select your desired destination connection to inspect the existing dataflow to the destination.

    Image highlighting a filtered dataflow.

  3. Select the Activation data tab and select the audiences for which you want to export files on-demand and select the Export file now control to trigger a one-time export which will deliver a file for each selected audience to your batch destination.

    Image highlighting the Export file now button.

  4. Select Yes to confirm and trigger the file export.

    Image showing the Export file now confirmation dialog.

  5. A confirmation message appears, letting you know that the file export has started.

    Image showing confirmation of successful ad-hoc activation.

  6. You can also switch to the Dataflow runs tab to confirm that the file export has kicked off.

Considerations considerations

Keep in mind the following considerations when using the Export file now control:

  • Export file now works only for audiences whose schedule in the batch activation dataflow overlaps with the present date. This includes audiences with schedules that have no end date (export frequency of Once), or where the end date has not yet passed.
  • When adding an audience to an existing dataflow, wait for at least 15 minutes until using the Export file now control.
  • If you change an audience’s merge policy, or if you create an audience which uses a new merge policy, wait 24 hours until using the Export file now control.

UI error messages ui-error-messages

When using the Export file now control, you might encounter any of the error messages listed below. Review the table to understand how to address them when they do appear.

Error message
Resolution
Run already going on for audience segment ID for order dataflow ID with run id flow run ID
This error message indicates that an ad-hoc activation flow is currently ongoing for an audience. Wait for the job to finish before triggering the activation job again.
Audiences <segment name> are not part of this dataflow or out of schedule range!
This error message indicates that the audiences you selected to activate are not mapped to the dataflow or that the activation schedule set up for the audiences has either expired or not yet started. Check if the audience is indeed mapped to the dataflow and verify that the audience activation schedule overlaps with the present date.
recommendation-more-help
7f4d1967-bf93-4dba-9789-bb6b505339d6