Send campaigns to Azure Blob Storage

Azure Blob Storage is an object storage solution for the cloud that is optimized for storing massive amounts of unstructured data.

Build campaign

Use the campaign editor to build campaigns that send data to Azure Blob Storage. Add a segment, define exclusions and sub-audiences, and then configure Amperity to send campaign data to Azure Blob Storage.

To build a campaign

  1. From the Campaigns tab, click Create Campaign. This opens the New Campaign page.

  2. Give your campaign a name.

  3. Choose the segment that represents the audience to use for this campaign.

  4. Optional. Choose a segment that contains a list of customers to exclude from this campaign.

  5. Configure at least one control group/recipient group set for this campaign. Rename these groups as necessary.


    A campaign may have many control group/recipient group sets and each set may have more than one recipient group. Click Add recipient group to add another recipient group. Click Add Sub-audience to add more sets to this campaign, and then use the Audience Builder to define the criteria for each sub-audience.

  6. For each control group/recipient group set, configure the percentages for each group, and then select a destination that is configured to send campaigns from Amperity to Azure Blob Storage.

  7. Click Edit attributes to review the attributes that Amperity will send to Azure Blob Storage.

    You must select the set of attributes that are sent to Azure Blob Storage. Review your downstream requirements, open the Edits attributes page, and then select the attributes you want to send to Azure Blob Storage for this campaign.

    Amperity pre-selects the list of attributes that may be sent to Azure Blob Storage. When you open the Edit attributes page for Azure Blob Storage, it will be similar to:

    Attributes for campaigns that send data to SFTP, Amazon S3, Azure Blob Storage, and Google Cloud Storage.


    The Merged_Customers table is the default table from which data is sent to Azure Blob Storage, even though your segments were built against the Customer_360 table. This is by design. The Merged_Customers table is the underlying table for customer profile data and is the source for customer profile data that exists in the Customer_360 table.

  8. Specify if this campaign is a one-time or recurring campaign, define the delivery schedule, and then define the campaign launch date. (Amperity uses the campaign launch date internally to improve results tracking for campaigns.)

  9. Click Schedule.


    Amperity will begin processing the segments that define audiences, exclusions, and sub-audiences, and will then send the results to configured destinations. Please allow for enough time for Amperity to complete this process before kicking off a campaign in your downstream systems.