This document describes the Magnite: Batch destination and provides sample use cases to help you better understand how to activate and export audiences to it.
Adobe Real-Time CDP audiences can be delivered to the Magnite Streaming platform in two ways - they can be delivered once per day, or they can be delivered in real-time:
If you only want and/or need to deliver audiences once per day, you can use the Magnite: Batch destination, which delivers audiences to Magnite Streaming via a daily S3 batch file delivery. These Batch audiences are stored indefinitely in the Magnite platform, unlike real-time audiences, which are only stored for a couple days.
However, if you want or need to deliver audiences more frequently, you will need to use the Magnite Real-Time destination. When using the Real-Time destination, Magnite Streaming will receive audiences in real-time, but Magnite can only store real-time audiences temporarily in their platform, and they will be removed from the system within a couple days. For this reason, if you want to use the Magnite Real-Time destination, you will also need to use the Magnite: Batch destination - each audience that you activate to the Real-Time destination, you also need to activate to the Batch destination.
To recap: If you only want to deliver Adobe Real-Time CDP audiences once per day, you will use the Magnite: Batch destination only, and audiences will be delivered once per day. If you want to deliver Adobe Real-Time CDP audiences in Real-Time, you will use both the Magnite: Batch destination, and the Magnite Real-Time destination. For more information, reach out to Magnite: Streaming.
Continue reading below for more information about the Magnite: Batch destination, how to connect to it, and how to activate Adobe Real-Time CDP audiences to it.
For more information about the Real-Time destination, See this documentation page instead.
The destination connector and documentation page are created and maintained by the Magnite team. For any inquiries or update requests, please contact them directly at adobe-tech@magnite.com
.
To help you better understand how and when you should use the Magnite: Batch destination, here are sample use cases that Adobe Experience Platform customers can solve using this destination.
You have activated an audience on the Magnite Real-Time destination.
Any audiences activated via the Magnite Real-Time destination must also use the Magnite: Batch destination, as the Batch delivery’s data is meant to replace/persist the Real-Time delivery’s data within the Magnite Streaming platform.
You want to activate an audience only in a batch/daily cadence to the Magnite Streaming platform.
Any audience(s) activated via the Magnite: Batch destination will be delivered in a batch/daily cadence and will then be available for targeting in the Magnite Streaming platform.
To use the Magnite destinations in Adobe Experience Platform, you must first have a Magnite Streaming account. If you have a Magnite Streaming account, please reach out to your Magnite account manager to be provided credentials to access Magnite’s destinations. If you do not have a Magnite Streaming account, please reach out to adobe-tech@magnite.com
The Magnite: Batch destination can receive any identity sources from the Adobe CDP. Currently, this destination has three Target Identity fields for you to map to.
Any identity sources can map to any of the magnite_deviceId
target identities.
Target Identity | Description | Considerations |
---|---|---|
magnite_deviceId_GAID | Google Advertising ID | Select this Target Identity when your source identity is a GAID |
magnite_deviceId_IDFA | Apple ID for Advertisers | Select this target identity when your source identity is an IDFA |
magnite_deviceId_CUSTOM | Custom/user-defined ID | Select this target identity when your source identity is not a GAID or IDFA, or if it is a custom or user-defined ID |
Audience origin | Supported | Description |
---|---|---|
Segmentation Service | ✓ | Audiences generated through the Experience Platform Segmentation Service. |
Custom uploads | ✓ | Audiences imported into Experience Platform from CSV files. |
Item | Type | Notes |
---|---|---|
Export type | Audience export | You are exporting all members of an audience with the identifiers (name, phone number, or others) used in the Magnite: Batch destination. |
Export frequency | Batch | 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. |
Once your destination usage has been approved and Magnite Streaming has shared your credentials, please follow the below steps to authenticate, map, and share data.
Locate the Magnite: Batch destination in the Adobe Experience catalog. Click the additional options button (…) and then configure the destination connection/instance.
If you already have an existing account, you can locate it by changing the Account type option to “Existing account”. Otherwise, you will create an account below:
To create a new account, and authenticate it to the destination for the first time, fill in the required “S3 access key” and “S3 secret key” fields (provided to you via your account manager), and select Connect to destination
Magnite Streaming’s security policy requires a regular rotation of S3 keys. You should expect to update your account in the future with new S3 access and S3 secret keys. You only need to update the account itself - destinations using that account will automatically use the updated keys. Failure to upload the new keys will result in the data failing to send to this destination.
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.
The company name must be a string which matches the name of the Amazon S3 delivery bucket you have configured with Magnite and set up in the authenticate to destination step. The supported characters include ‘a-z’, ‘A-Z’, ‘0-9’, ‘-’(dash), or ‘_’(underscore).
If you plan to send multiple ID types (GAID, IDFA, etc.) using the Batch destination, a new destination connection/instance is required for each. Please contact your Magnite Account representative for more information.
You can then proceed by selecting Next
On the next screen, titled “Governance Policy and Enforcement Actions (Optional)”, you can optionally select any relevant data governance policies. “Data Export” is generally selected for the Magnite: Batch destination.
Once selected, or if you wish to skip this optional screen, select Create
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.
Read Activate audience data to batch profile export destinations for instructions on activating audience segments to this destination.
In the Source field, you can select any attribute or identity for your devices. In this example, we’ve selected a custom IdentityMap called “DeviceId”
In the Target field:
See Supported Identities for more information.
In this example, we’ve selected the Target field: magnite_deviceId_CUSTOM, because our Source field was defined as a custom IdentityMap: DeviceID.
If you plan to send/map multiple ID types (GAID, IDFA, etc.) using the Batch destination, a new destination connection/instance is required for each. Please contact your Magnite Account representative for more information.
On the “Configure a filename and export schedule for each audience” screen, you must now configure a Start date (mandatory), End date (optional), and a Mapping ID (mandatory) for each audience.
A Mapping ID or “NONE” is required for this destination.
A Mapping ID should be provided when an audience has a pre-existing Segment ID previously known to Magnite Streaming. Otherwise, “NONE” should be used as the Mapping ID.
When configuring the filename for each audience, please include the Mapping ID via the “Custom Text” field to add. The Mapping ID will be appended as: {previous_filename}\_\[MAPPING_ID\].
If this audience is new to Magnite Streaming, and you will not be providing a Mapping ID, “NONE” should be entered into the “Custom Text” field. The new filename in this case should be: {previous_filename}\_\[NONE\]
.
Once your audiences have been uploaded, you may validate your audiences have been created and uploaded correctly.
Audiences activated/delivered to the Magnite: Batch destination will replace the same audiences that were activated/delivered via the Magnite Real-Time destination. If you are looking-up a segment using the segment name, you may not find the segment in real-time, until the batch has been ingested and processed by the Magnite Streaming platform.
All Adobe Experience Platform destinations are compliant with data usage policies when handling your data. For detailed information on how Adobe Experience Platform enforces data governance, read the Data Governance overview.
For additional help documentation, visit the Magnite Help Center.