diff --git a/help/destinations/assets/catalog/advertising/magnite/destination-batch-active-audience-field-mapping.png b/help/destinations/assets/catalog/advertising/magnite/destination-batch-active-audience-field-mapping.png index 8cdfff5248..3ed384198b 100644 Binary files a/help/destinations/assets/catalog/advertising/magnite/destination-batch-active-audience-field-mapping.png and b/help/destinations/assets/catalog/advertising/magnite/destination-batch-active-audience-field-mapping.png differ diff --git a/help/destinations/assets/catalog/advertising/magnite/destination-batch-active-audience-select-device-type.png b/help/destinations/assets/catalog/advertising/magnite/destination-batch-active-audience-select-device-type.png index aa18a1a32e..ee4327cd91 100644 Binary files a/help/destinations/assets/catalog/advertising/magnite/destination-batch-active-audience-select-device-type.png and b/help/destinations/assets/catalog/advertising/magnite/destination-batch-active-audience-select-device-type.png differ diff --git a/help/destinations/assets/catalog/advertising/magnite/destination-batch-existing-mapping-id.png b/help/destinations/assets/catalog/advertising/magnite/destination-batch-existing-mapping-id.png new file mode 100644 index 0000000000..8b1eb8b2b3 Binary files /dev/null and b/help/destinations/assets/catalog/advertising/magnite/destination-batch-existing-mapping-id.png differ diff --git a/help/destinations/assets/catalog/advertising/magnite/destination-batch-mapping-id-NONE.png b/help/destinations/assets/catalog/advertising/magnite/destination-batch-mapping-id-NONE.png new file mode 100644 index 0000000000..2b42c5f1fe Binary files /dev/null and b/help/destinations/assets/catalog/advertising/magnite/destination-batch-mapping-id-NONE.png differ diff --git a/help/destinations/assets/catalog/advertising/magnite/destination-realtime-active-audience-field-mapping.png b/help/destinations/assets/catalog/advertising/magnite/destination-realtime-active-audience-field-mapping.png index c5b7d9e84b..6d004ffda8 100644 Binary files a/help/destinations/assets/catalog/advertising/magnite/destination-realtime-active-audience-field-mapping.png and b/help/destinations/assets/catalog/advertising/magnite/destination-realtime-active-audience-field-mapping.png differ diff --git a/help/destinations/assets/catalog/advertising/magnite/destination-realtime-active-audience-target-popout.png b/help/destinations/assets/catalog/advertising/magnite/destination-realtime-active-audience-target-popout.png new file mode 100644 index 0000000000..0a530e39a2 Binary files /dev/null and b/help/destinations/assets/catalog/advertising/magnite/destination-realtime-active-audience-target-popout.png differ diff --git a/help/destinations/catalog/advertising/magnite-batch.md b/help/destinations/catalog/advertising/magnite-batch.md index 4a126363c2..06297b1f06 100644 --- a/help/destinations/catalog/advertising/magnite-batch.md +++ b/help/destinations/catalog/advertising/magnite-batch.md @@ -1,25 +1,29 @@ --- -title: Magnite Batch Destination -description: Use this destination to deliver Adobe CDP audiences to the Magnite Streaming platform in batch. +title: Magnite Batch destination +description: Use this destination to deliver Adobe Real-Time CDP audiences to the Magnite platform in batch. last-substantial-update: 2024-11-18 exl-id: 8cc3890f-84f8-49d1-a329-322c13f9e5af --- -# Magnite: Batch connection {#magnite-streaming-batch} +# Magnite: Batch destination {#magnite-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. +This document describes the [!DNL 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: +>[!NOTE] +> +>The [!DNL Magnite] destinations can be used for ingestion into any [!DNL Magnite] platform: Streaming, DV+, SpringServe, etc. -1. 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. +Adobe Real-Time CDP audiences can be delivered to the [!DNL Magnite] platform in two ways - they can be delivered once per day, or they can be delivered in real-time: -2. However, if you want or need to deliver audiences more frequently, you will need to use the [Magnite Real-Time](/help/destinations/catalog/advertising/magnite-streaming.md) 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. +1. If you only want and/or need to deliver audiences once per day, you can use the [!DNL Magnite: Batch] destination, which delivers audiences to [!DNL Magnite] via a daily S3 batch file delivery. These batch audiences are stored more persistently in the [!DNL Magnite] platform, unlike real-time audiences, which are only stored for a couple days. -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. +2. However, if you want or need to deliver audiences more frequently, you will need to use the [Magnite: Real-Time destination](/help/destinations/catalog/advertising/magnite-streaming.md). When using the real-time destination, [!DNL Magnite] will receive audiences in real-time, but [!DNL 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 [!DNL Magnite: Real-Time] destination, you will *also* need to use the [!DNL 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 [!DNL 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 [!DNL Magnite: Batch] destination, and the[!DNL Magnite: Real-Time] destination. For more information, reach out to [!DNL Magnite]. -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. + +Continue reading below for more information about the [!DNL 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](magnite-streaming.md) instead. >[!IMPORTANT] @@ -28,46 +32,34 @@ For more information about the Real-Time destination, See [this documentation pa ## 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. +To help you better understand how and when you should use the [!DNL Magnite: Batch] destination, here are sample use cases that [!DNL 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. +You have activated an audience on the [!DNL 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. +Any audiences activated via the [!DNL Magnite: Real-Time] destination must also use the [!DNL Magnite: Batch] destination, as the batch delivery's data is meant to replace/persist the real-time delivery's data within the [!DNL Magnite] platform. ### Use case #2 {#use-case-2} -You want to activate an audience only in a batch/daily cadence to the Magnite Streaming platform. +You want to activate an audience only in a batch/daily cadence to the [!DNL Magnite] 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. +Any audience(s) activated via the [!DNL Magnite: Batch] destination will be delivered in a batch/daily cadence and will then be available for targeting in the [!DNL Magnite] platform. ## Prerequisites {#prerequisites} -To use the [!DNL Magnite] destinations in Adobe Experience Platform, you must first have a Magnite Streaming account. If you have a [!DNL Magnite Streaming] account, please reach out to your [!DNL Magnite] account manager to be provided credentials to access [!DNL Magnite's] destinations. If you do not have a [!DNL Magnite Streaming] account, please reach out to adobe-tech@magnite.com +To use the [!DNL Magnite] destinations in [!DNL Adobe Experience Platform], you must first have a [!DNL Magnite] account. If you already have a [!DNL Magnite] account, please reach out to your [!DNL Magnite] account manager to be provided credentials to access [!DNL Magnite's] destinations. If you do not have a [!DNL Magnite] 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. - ->[!NOTE] -> ->*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 | - -{style="table-layout:auto"} +The [!DNL Magnite: Real-Time] destination supports the activation of any attributes and/or identities stored in [!DNL Adobe Experience Platform], which will need to be mapped to a [!DNL Magnite] supported device type. The list of supported device types is managed by [!DNL Magnite], and may change and/or grow over time. The current list of supported device types will be available from a 'Select target field' popout window, during the Mapping step of Audience Activation (described below). Learn more about [identities](/help/identity-service/features/namespaces.md). ## Supported audiences {#supported-audiences} | Audience origin | Supported | Description | |-----------------------------|----------|----------| -| [!DNL Segmentation Service] | ✓ | Audiences generated through the Experience Platform [Segmentation Service](../../../segmentation/home.md).| -| Custom uploads | ✓ | Audiences [imported](../../../segmentation/ui/audience-portal.md#import-audience) into Experience Platform from CSV files. | +| [!DNL Segmentation Service] | ✓ | Audiences generated through the [!DNL Adobe Experience Platform] [Segmentation Service](../../../segmentation/home.md).| +| Custom uploads | ✓ | Audiences [imported](../../../segmentation/ui/audience-portal.md#import-audience) into [!DNL Adobe Experience Platform] from CSV files. | {style="table-layout:auto"} @@ -75,18 +67,18 @@ The Magnite: Batch destination can receive *any* identity sources from the Adobe | 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 type | Audience export | You are exporting all members of an audience with the identifiers (name, phone number, or others) used in the [!DNL 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](/help/destinations/destination-types.md). | {style="table-layout:auto"} ## 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. +Once your destination usage has been approved and [!DNL Magnite] 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. +Locate the [!DNL Magnite: Batch] destination in the [!DNL Adobe Experience Platform] 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: @@ -96,7 +88,7 @@ To create a new account, and authenticate it to the destination for the first ti >[!NOTE] > ->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. +>[!DNL Magnite'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. ### Fill in destination details {#destination-details} @@ -106,21 +98,21 @@ To configure details for the destination, fill in the required and optional fiel future. * **[!UICONTROL Description]**: A description that will help you identify this destination connection/instance in the future. -* **[!UICONTROL Your company name]**: Your customer/company name. Only supported [!DNL Magnite Streaming] clients are available for selection. +* **[!UICONTROL Your company name]**: Your customer/company name. Only supported [!DNL Magnite] clients are available for selection. >[!NOTE] > ->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](#authenticate) step. The supported characters include 'a-z', 'A-Z', '0-9', '-'(dash), or '_'(underscore). +>The company name must be a string which matches the name of the Amazon S3 delivery bucket you have configured with [!DNL Magnite] and set up in the [authenticate to destination](#authenticate) step. The supported characters include 'a-z', 'A-Z', '0-9', '-'(dash), or '_'(underscore). ![destination configuration auth fields filled](../../assets/catalog/advertising/magnite/destination-batch-config-auth-filled.png) >[!NOTE] > ->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. +>If you plan to map an Audience to multiple device types (GAID, IDFA, etc.) using the Batch destination, a new destination connection/instance is required for each mapping. Please contact your [!DNL Magnite] account representative for more information. You can then proceed by selecting **[!UICONTROL 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. +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 [!DNL Magnite: Batch] destination. ![Optional governance policy and enforcement actions](../../assets/catalog/advertising/magnite/destination-batch-config-grouping-policy.png) @@ -147,12 +139,23 @@ In the **[!UICONTROL Source field]**, you can select any attribute or identity f ![map desired data fields to the device_id field](../../assets/catalog/advertising/magnite/destination-batch-active-audience-field-mapping.png) In the **[!UICONTROL Target field]**: -![select the appropriate device type target identity](../../assets/catalog/advertising/magnite/destination-batch-active-audience-select-device-type.png) See [Supported Identities](#supported-identities) for more information. -In this example, we've selected the **[!UICONTROL Target field]**: magnite_deviceId_CUSTOM, because our **[!UICONTROL Source field]** was defined as a custom IdentityMap: DeviceID. +The next step is mapping Source Field identifiers to the [!DNL Magnite] Device Type identifier of your choice, located in the Target Field. + +The current list of [!DNL Magnite] supported device types will be available via a 'Select target field' popout window, by clicking the Target Field's target attribute button. + +In order to support a dynamic list of device types, the 'Select target field' popout window will provide a list of integers (from 0-50), each of which represents a specific device type in [!DNL Magnite]'s system. To understand which device type id in the list of integers corresponds to which [!DNL Magnite] device type, reach out to your [!DNL Magnite] account representative. + +![Choose desired device type integer attribute from 'Select target field' popout window](../../assets/catalog/advertising/magnite/destination-batch-active-audience-select-device-type.png) + +See [Supported Identities](#supported-identities) for more information. +In this example, we've selected the **[!UICONTROL Target field]**: Attribute: "00". +!["Attribute: 00" was selected](../../assets/catalog/advertising/magnite/destination-batch-active-audience-field-mapping.png) + +* You can add as many mappings as you want/need by selecting **[!UICONTROL Add new mapping]**. >[!NOTE] > ->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. +>If you plan to map an audience to multiple device types (GAID, IDFA, etc.) using the Batch destination, a new destination connection/instance is required for each mapping. Please contact your [!DNL 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. @@ -161,19 +164,21 @@ On the "Configure a filename and export schedule for each audience" screen, you > > 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. +> Provide a Mapping ID when your audience has a pre-existing Segment ID previously known to [!DNL Magnite]. Otherwise, enter "NONE" 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\]`. +> 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 [!DNL Magnite], 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\]`. +!["ExistingMappingId" was entered](../../assets/catalog/advertising/magnite/destination-batch-existing-mapping-id.png) +!["NONE" was entered for MappingId](../../assets/catalog/advertising/magnite/destination-batch-mapping-id-NONE.png) ## 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. +* The [!DNL Magnite: Batch] destination delivers S3 files to [!DNL Magnite] at a daily cadence. After delivery and ingestion, audiences/segments are expected to appear in [!DNL Magnite], 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 [!DNL Adobe Experience Platform]. >[!NOTE] > ->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. +>Audiences activated/delivered to the [!DNL Magnite: Batch] destination will *replace* the same audiences that were activated/delivered via the [!DNL 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 [!DNL Magnite] platform. ## Data usage and governance {#data-usage-governance} diff --git a/help/destinations/catalog/advertising/magnite-streaming.md b/help/destinations/catalog/advertising/magnite-streaming.md index 4f8a89fbd4..5eb09d3305 100644 --- a/help/destinations/catalog/advertising/magnite-streaming.md +++ b/help/destinations/catalog/advertising/magnite-streaming.md @@ -1,23 +1,27 @@ --- -title: Magnite Real-Time destination connection -description: Use this destination to deliver Adobe CDP audiences to the Magnite Streaming platform in real-time. +title: Magnite Real-Time destination +description: Use this destination to deliver Adobe Real-Time CDP audiences to the Magnite platform in real-time. last-substantial-update: 2024-11-18 exl-id: 4e08a14b-6800-41e1-95a5-826a6241144d --- -# Magnite: Real-Time destination connection +# Magnite: Real-Time destination {#magnite-real-time-destination} ## Overview {#overview} -The [!DNL Magnite: Real-Time] and the [Magnite: Batch](/help/destinations/catalog/advertising/magnite-batch.md) destinations in Adobe Experience Platform help you map and export audiences for targeting and activation on the Magnite Streaming platform. +The [!DNL Magnite: Real-Time] and the [Magnite: Batch](/help/destinations/catalog/advertising/magnite-batch.md) destinations in [!DNL Adobe Experience Platform] help you map and export audiences for targeting and activation on the [!DNL Magnite] platform. -Activating audiences to the [!DNL Magnite Streaming] platform is a two step process which requires you to use both the Magnite: Real-Time and the Magnite: Batch destinations. +>[!NOTE] +> +>The [!DNL Magnite] destinations can be used for ingestion into any [!DNL Magnite] platform: Streaming, DV+, SpringServe, etc. + +Activating audiences to the [!DNL Magnite] platform is a two-step process which requires you to use both the [!DNL Magnite: Real-Time] destination and the [!DNL Magnite: Batch] destination. -To activate your audiences to [!DNL Magnite Streaming], you must: +To activate your audiences to [!DNL Magnite], you must: * Activate the audiences on the [!DNL Magnite: Real-Time] destination, as shown in this page. -* Activate the same audience on the Magnite: Batch destination. The [!DNL Magnite: Batch] destination is a mandatory component. Failing to activate the audience on the [!DNL Magnite Streaming] Batch destination will result in a failed integration, and your audiences will not be activated. +* Activate the same audience on the [!DNL Magnite: Batch] destination. The [!DNL Magnite: Batch] destination is a mandatory component. Failing to activate the audience on the [!DNL Magnite: Batch] destination will result in a failed integration, and your audiences will not be activated. -Note: When using the Real-Time destination, [!DNL 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. +Note: When using the real-time destination, [!DNL Magnite] will receive audiences in real-time, but [!DNL 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 [!DNL Magnite: Real-Time] destination, you will *also* need to use the [!DNL Magnite: Batch] destination - each audience that you activate to the real-time destination, you also need to activate to the batch destination. >[!IMPORTANT] > @@ -25,26 +29,20 @@ Note: When using the Real-Time destination, [!DNL Magnite Streaming] will receiv ## Use cases {#use-cases} -To help you better understand how and when you should use the [!DNL Magnite: Real-Time] destination, here is a sample use case that Adobe Experience Platform customers can solve by using this destination. +To help you better understand how and when you should use the [!DNL Magnite: Real-Time] destination, here is a sample use case that [!DNL Adobe Experience Platform] customers can solve by using this destination. ### Activation and targeting {#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). +This integration with [!DNL Magnite] allows customers to pass their Real-Time CDP audiences from [!DNL Adobe Experience Platform] to [!DNL Magnite], and any [!DNL Magnite] platforms, for advertising targeting. Audiences may be selected within [!DNL Magnite] for positive targeting as well as negative targeting (suppression). ## Prerequisites {#prerequisites} -To use the [!DNL Magnite] destinations in Adobe Experience Platform, you must first have a [!DNL Magnite Streaming] account. If you have a [!DNL Magnite Streaming] account, please reach out to your [!DNL Magnite] account manager to be provided credentials to access [!DNL Magnite's] destinations. -If you do not have a [!DNL Magnite Streaming] account, please reach out to adobe-tech@magnite.com +To use the [!DNL Magnite] destinations in [!DNL Adobe Experience Platform], you must first have a [!DNL Magnite] account. If you already have a [!DNL Magnite] account, please reach out to your [!DNL Magnite] account manager to be provided credentials to access [!DNL Magnite's] destinations. +If you do not have a [!DNL Magnite] account, please reach out to adobe-tech@magnite.com ## Supported identities {#supported-identities} -The [!DNL Magnite: Real-Time] destination supports the activation of identities described in the table below. Learn more about [identities](/help/identity-service/features/namespaces.md). - -| 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. | - -{style="table-layout:auto"} +The [!DNL Magnite: Real-Time] destination supports the activation of any attributes and/or identities stored in [!DNL Adobe Experience Platform], which will need to be mapped to a [!DNL Magnite] supported device type. The list of supported device types is managed by [!DNL Magnite], and may change and/or grow over time. The current list of supported device types will be available from the 'Select target field' popout window, during the Mapping step of Audience Activation (described below). Learn more about [identities](/help/identity-service/features/namespaces.md). ## Supported audiences {#supported-audiences} @@ -52,8 +50,8 @@ This section describes which type of audiences you can export to this destinatio | Audience origin | Supported | Description | |-----------------------------|----------|----------| -| [!DNL Segmentation Service] | ✓ | Audiences generated through the Experience Platform [Segmentation Service](../../../segmentation/home.md).| -| Custom uploads | ✓ | Audiences [imported](../../../segmentation/ui/audience-portal.md#import-audience) into Experience Platform from CSV files. | +| [!DNL Segmentation Service] | ✓ | Audiences generated through the [!DNL Adobe Experience Platform] [Segmentation Service](../../../segmentation/home.md).| +| Custom uploads | ✓ | Audiences [imported](../../../segmentation/ui/audience-portal.md#import-audience) into [!DNL Adobe Experience Platform] from CSV files. | {style="table-layout:auto"} @@ -64,7 +62,7 @@ Refer to the table below for information about the destination export type and f | Item | Type | Notes | |------------------|---------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Export type | **[!UICONTROL Segment export]** | You are exporting all members of a segment (audience) with the identifiers (name, phone number, or others) used in the [!DNL Magnite: Real-Time] destination. | -| Export frequency | **[!UICONTROL 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](/help/destinations/destination-types.md#streaming-destinations). | +| Export frequency | **[!UICONTROL Streaming]** | Streaming destinations are "always on" API-based connections. As soon as a profile is updated in [!DNL Adobe Experience Platform] based on segment evaluation, the connector sends the update downstream to the destination platform. Read more about [streaming destinations](/help/destinations/destination-types.md#streaming-destinations). | {style="table-layout:auto"} @@ -91,11 +89,11 @@ To configure details for the destination, fill in the required and optional fiel * **[!UICONTROL Name]**: A name by which you will recognize this destination in the future. * **[!UICONTROL Description]**: A description that will help you identify this destination in the future. -* **[!UICONTROL Your company name]**: Your customer/company name. Only supported [!DNL Magnite Streaming] clients are available for selection. +* **[!UICONTROL Your company name]**: Your customer/company name. Only supported [!DNL Magnite] clients are available for selection. >[!NOTE] > ->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](#authenticate) step. The supported characters include 'a-z', 'A-Z', '0-9', '-'(dash), or '_'(underscore). +>The company name must be a string which matches the name of the Amazon S3 delivery bucket you have configured with [!DNL Magnite] and set up in the [authenticate to destination](#authenticate) step. The supported characters include 'a-z', 'A-Z', '0-9', '-'(dash), or '_'(underscore). ![destination configuration auth fields filled](../../assets/catalog/advertising/magnite/destination-realtime-config-auth-filled.png) @@ -122,23 +120,33 @@ Once the destination connection has been created, you can proceed to the audienc ### Map attributes and identities {#map} -The next step is mapping source identifiers to the Magnite device_id identifier. +The next step is mapping Source Field identifiers to the [!DNL Magnite] Device Type identifier of your choice, located in the Target Field. -* You can add as many mappings as you need by selecting **[!UICONTROL Add new mapping]**. +The current list of [!DNL Magnite] supported device types will be available via the 'Select target field' popout window, by clicking the Target Field's target attribute button. -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 [!UICONTROL Next]. +In order to support a dynamic list of device types, the popout window will provide a list of integers (from 0-50), each of which represents a specific device type in [!DNL Magnite]'s system. To understand which device type id in the list of integers corresponds to which [!DNL Magnite] device type, reach out to your [!DNL Magnite] account representative. If you are still unsure, you should select 0 (zero). -![Map desired data fields to the device_ID field](../../assets/catalog/advertising/magnite/destination-realtime-active-audience-field-mapping.png) +![Choose desired device type integer from 'Select target field' popout window](../../assets/catalog/advertising/magnite/destination-realtime-active-audience-target-popout.png) + +This example using the Real-Time destination shows a row that contains a generic deviceId source identifier mapped to the [!DNL Magnite] device type with integer id: "1". When you are satisfied with the mappings, select [!UICONTROL Next]. + +![Map desired data fields to the target field](../../assets/catalog/advertising/magnite/destination-realtime-active-audience-field-mapping.png) + +* You can add as many mappings as you want/need by selecting **[!UICONTROL Add new mapping]**. + +>[!NOTE] +> +>If you plan to map an audience to multiple device types (GAID, IDFA, etc.) using the Real-Time destination, a new destination connection/instance is required for each mapping. Please contact your [!DNL Magnite] account representative for more information. -Be sure to set Mapping IDs to all activated audiences, or set NONE if no Mapping ID is present. +Be sure to set Mapping IDs for all activated audiences, or set NONE if no Mapping ID is present. -![Be sure to set Mapping IDs to all activated audiences, or set NONE if no Mapping ID is present](../../assets/catalog/advertising/magnite/destination-realtime-active-audience-mappingid.png) +![Be sure to set Mapping IDs for all activated audiences, or set NONE if no Mapping ID is present](../../assets/catalog/advertising/magnite/destination-realtime-active-audience-mappingid.png) You must now configure a Start date (mandatory), an End date (optional), and a Mapping ID for each audience. **Mapping ID** -* Use the **[!UICONTROL Mapping ID]** field when an audience has a pre-existing Segment ID previously known to Magnite. +* Use the **[!UICONTROL Mapping ID]** field when an audience has a pre-existing Segment ID previously known to [!DNL Magnite]. * To add a **[!UICONTROL 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. @@ -152,17 +160,17 @@ Once your audiences have been uploaded, you may validate your audiences have bee -* Post-ingest, audiences are expected to appear in [!DNL Magnite Streaming] within a few minutes and can be applied to a deal. You can confirm this by looking up the segment ID that was shared during the activation steps in the Adobe Experience Platform. +* Post-ingest, audiences are expected to appear in [!DNL Magnite] within a few minutes and can be applied to a deal. You can confirm this by looking up the segment ID that was shared during the activation steps in the [!DNL Adobe Experience Platform]. -## Activate the same audiences through the [!DNL Magnite: Batch ]destination +## Activate the same audiences through the [!DNL Magnite: Batch] destination -Audiences shared with [!DNL Magnite Streaming] using the Real-Time destination will also need to be shared using the Magnite: Batch destination. When configured correctly, segment names in the [!DNL Magnite Streaming] UI are updated to reflect those used in the Adobe Experience Platform post-daily update. +Audiences shared with [!DNL Magnite] using the Real-Time destination will also need to be shared using the [!DNL Magnite: Batch] destination. When configured correctly, segment names in the [!DNL Magnite] UI are updated to reflect those used in the [!DNL Adobe Experience Platform] post-daily update. -Finally, if a Batch destination has not been configured for your integration, set it up now via the Magnite: Batch destination document. +Finally, if a Batch destination has not been configured for your integration, set it up now via the [!DNL Magnite: Batch] destination document. ## Data usage and governance {#data-usage-governance}