Creating custom audiences for Amazon DSP — such as viewers or purchasers of specific ASINs — can be time-consuming, especially when building many variations with different lookback windows.
Adbrew’s Bulk Audience Creation feature streamlines this process by allowing you to upload a CSV file with all your audience requirements. Adbrew then automatically creates these audiences, which will be visible in your Amazon DSP console for targeting.
Types of Audiences You Can Create
You can use the bulk upload feature to create the following types of audiences:
Audience Type | Description |
PRODUCT_VIEWS | Shoppers who viewed specific products |
PRODUCT_PURCHASES | Shoppers who purchased specific products |
PRODUCT_SEARCH | Shoppers who searched for specific products |
PRODUCT_SIMS | Shoppers who viewed similar products |
WHOLE_FOODS_MARKET_PURCHASES | Shoppers who purchased specific products at Whole Foods Market |
Where to Find This Feature
1. Open Adbrew
2. Go to DSP > Audience Explorer in the Adbrew app.
3. Click the three-dot menu in the top-right corner.
4. Select Bulk Create Audiences from the dropdown.
How to Use the Bulk Audience Creation Tool
Step 1: Download the Template
In the modal window, click "Download and edit this sample CSV" to get the correct file structure.
Step 2: Fill in the CSV
Each row in your CSV represents one audience. You must include the following columns:
Column | Description | Example |
| Comma-separated list of ASINs |
|
| A name for your custom audience |
|
| Number of days to look back (max for view - 90 & purchase - 365) |
|
| One of the supported audience types |
|
Step 3: Upload Your CSV
Click "Choose file" and select your edited CSV file.
Click "Upload" to start the audience creation process.
Step 4: Review Status
After processing, the modal will show:
Successful audience creations
Errors for failed rows (with reasons)
Important Notes & Best Practices
Processing Time: Audiences are created one at a time in the backend due to Amazon DSP API limitations. Each audience may take 5–10 minutes to appear in your DSP console.
Best Practice: Upload no more than 30 audiences per batch to reduce the risk of errors or API timeouts.
Edit Carefully: Ensure ASINs are valid and
audience_typevalues are spelled exactly as required.