With the July 2023 Experience Platform release, the Azure Blob destination provides new functionality, as listed below:
Azure Blob (hereinafter referred to as Blob) is Microsoft’s object storage solution for the cloud. This tutorial provides steps for creating a Blob destination using the Platform user interface.
This tutorial requires a working understanding of the following components of Adobe Experience Platform:
If you already have a valid Blob destination, you may skip the remainder of this document and proceed to the tutorial on activating audiences to your destination.
This section describes which types of audiences you can export to this destination.
|Audiences generated through the Experience Platform Segmentation Service.
|Audiences imported into Experience Platform from CSV files.
Refer to the table below for information about the destination export type and frequency.
|You are exporting all members of a segment, together with the desired schema fields (for example: email address, phone number, last name), as chosen in the select profile attributes screen of the destination activation workflow.
|Batch destinations export files to downstream platforms in increments of three, six, eight, twelve, or twenty-four hours. Read more about batch file-based destinations.
Experience Platform supports the following file format to be exported to Azure Blob:
To connect to this destination, follow the steps described in the destination configuration tutorial. In the destination configuration workflow, fill in the fields listed in the two sections below.
To authenticate to the destination, fill in the required fields and select Connect to destination.
Connection string: the connection string is required to access data in your Blob storage. The Blob connection string pattern starts with:
Encryption key: Optionally, you can attach your RSA-formatted public key to add encryption to your exported files. View an example of a correctly formatted encryption key in the image below.
To configure details for the destination, fill in the required and optional fields below. An asterisk next to a field in the UI indicates that the field is required.
manifest-<<destinationId>>-<<dataflowRunId>>.json. View a sample manifest file. The manifest file includes the following fields:
flowRunId: The dataflow run which generated the exported file.
scheduledTime: The time in UTC when the file was exported.
exportResults.sinkPath: The path in your storage location where the exported file is deposited.
exportResults.name: The name of the exported file.
size: The size of the exported file, in bytes.
You can enable alerts to receive notifications on the status of the dataflow to your destination. Select an alert from the list to subscribe to receive notifications on the status of your dataflow. For more information on alerts, see the guide on subscribing to destinations alerts using the UI.
When you are finished providing details for your destination connection, select Next.
See Activate audience data to batch profile export destinations for instructions on activating audiences to this destination.
This destination supports dataset exports. For complete information on how to set up dataset exports, read the tutorials:
For Azure Blob Storage destinations, Platform creates a
.csv file in the storage location that you provided. For more information about the files, see Activate audience data to batch profile export destinations in the audience activation tutorial.