Export files on-demand to batch destinations using the Experience Platform UI
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
-
Go to Connections > Destinations, select the Browse tab and the filter symbol to show existing connections to your desired batch destinations.
-
Select your desired destination connection to inspect the existing dataflow to the destination.
-
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.
-
Select Yes to confirm and trigger the file export.
-
A confirmation message appears, letting you know that the file export has started.
-
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.
segment ID
for order dataflow ID
with run id flow run ID
<segment name>
are not part of this dataflow or out of schedule range!