Magnite: Real-Time destination connection
Overview
The Magnite: Real-Time and the Magnite: Batch destinations in Adobe Experience Platform help you map and export audiences for targeting and activation on the Magnite Streaming platform.
Activating audiences to the Magnite Streaming platform is a two step process which requires you to use both the Magnite: Real-Time and the Magnite: Batch destinations.
To activate your audiences to Magnite Streaming, you must:
- Activate the audiences on the Magnite: Real-Time destination, as shown in this page.
- Activate the same audience on the Magnite: Batch destination. The Magnite: Batch destination is a mandatory component. Failing to activate the audience on the Magnite Streaming Batch destination will result in a failed integration, and your audiences will not be activated.
Note: 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.
IMPORTANTadobe-tech@magnite.com.Use cases
To help you better understand how and when you should use the Magnite: Real-Time destination, here is a sample use case that Adobe Experience Platform customers can solve by using this destination.
Activation and targeting
This integration with Magnite allows customers to pass their CDP audiences from Adobe Experience Platform to Magnite for advertising targeting. Audiences may be selected within Magnite for positive targeting as well as negative targeting (suppression).
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
The Magnite: Real-Time destination supports the activation of identities described in the table below. Learn more about identities.
| Target Identity | Description | Considerations |
|---|---|---|
| device_id | A unique identifier for a device or identity. We accept any device ID and first-party ID regardless of type. | Identity types supported by Magnite include but are not limited to PPUID, GAID, IDFA, and TV Device IDs. |
Supported audiences
This section describes which type of audiences you can export to this destination.
| Audience origin | Supported | Description |
|---|---|---|
| Segmentation Service | ✓ | Audiences generated through the Experience Platform Segmentation Service. |
| Custom uploads | ✓ | Audiences imported into Experience Platform from CSV files. |
Export type and frequency
Refer to the table below for information about the destination export type and frequency.
| Item | Type | Notes |
|---|---|---|
| Export type | Segment export | You are exporting all members of a segment (audience) with the identifiers (name, phone number, or others) used in the Magnite: Real-Time destination. |
| Export frequency | Streaming | Streaming destinations are “always on” API-based connections. As soon as a profile is updated in Experience Platform based on segment evaluation, the connector sends the update downstream to the destination platform. Read more about streaming destinations. |
Connect to the destination
IMPORTANTTo connect to this destination, follow the steps described in the destination configuration tutorial. In the configure destination workflow, fill in the fields listed in the two sections below.
Authenticate to destination
To authenticate to the destination, fill in the required fields and select Connect to destination.
- Username: The username supplied to you by Magnite.
- Password: The password supplied to you by Magnite.
Fill in 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 in the future.
- Description: A description that will help you identify this destination in the future.
- Your company name: Your customer/company name. Only supported Magnite Streaming clients are available for selection.
NOTE
Once done, select the Create button.
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
IMPORTANT-
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 profiles and segments to streaming segment export destinations for instructions on activating audience segments to this destination.
Once the destination connection has been created, you can proceed to the audience activation flow. The following section walks through how to activate audiences using the Real-Time destination.
Map attributes and identities
The next step is mapping source identifiers to the Magnite device_id identifier.
- You can add as many mappings as you need by selecting Add new mapping.
This example using the Real-Time destination shows a row that contains a generic deviceId source identifier mapped to the Magnite device_id target field. When you’re with the mappings, select Next.
Be sure to set Mapping IDs to all activated audiences, or set NONE if no Mapping ID is present.
You must now configure a Start date (mandatory), an End date (optional), and a Mapping ID for each audience.
Mapping ID
-
Use the Mapping ID field when an audience has a pre-existing Segment ID previously known to Magnite.
-
To add a Mapping ID to an audience, select each audience row individually, and enter data in the right-hand column (see image above). If you do not want to add a Mapping ID, please enter NONE into the Mapping ID field.
Select Next and finalize the activation flow.
