Magnite: Batch connection magnite-streaming-batch
Overview overview
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.
adobe-tech@magnite.com.Use cases use-cases
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.
Use case #1 use-case-1
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.
Use case #2 use-case-2
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.
Prerequisites prerequisites
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
Supported identities supported-identities
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.
magnite_deviceId target identities.Supported audiences supported-audiences
Export type and frequency export-type-frequency
Connect to the destination connect
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.
Authenticate to destination authenticate
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
Fill in destination details destination-details
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.
- Name: A name by which you will recognize this destination connection/instance in the
future. - Description: A description that will help you identify this
destination connection/instance in the future. - Your company name: Your customer/company name. Only supported Magnite Streaming clients are available for selection.
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
Enable alerts enable-alerts
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.
Activate segments to this destination activate
-
To activate data, you need the View Destinations, Activate Destinations, View Profiles, and View Segments access control permissions. Read the access control overview or contact your product administrator to obtain the required permissions.
-
To export identities, you need the View Identity Graph access control permission.
Read Activate audience data to batch profile export destinations for instructions on activating audience segments to this destination.
Map attributes and identities map
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:
In this example, we’ve selected the Target field: magnite_deviceId_CUSTOM, because our Source field was defined as a custom IdentityMap: DeviceID.
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.
{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\].Exported data / Validate data export exported-data
Once your audiences have been uploaded, you may validate your audiences have been created and uploaded correctly.
- The Magnite: Batch destination delivers S3 files to Magnite Streaming at a daily cadence. After delivery and ingestion, audiences/segments are expected to appear in Magnite Streaming, and can be applied to a deal. You can confirm this by looking-up the segment ID or segment name that was shared during the activation steps in the Adobe Experience Platform.
Data usage and governance data-usage-governance
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.
Additional resources additional-resources
For additional help documentation, visit the Magnite Help Center.