Update documentation #478
Update documentation #478
Conversation
- Updated magnite-streaming.md - Updated audience-field-mapping image - Added new audience-target-dropdown image
- Updated doc wording
- Updated page title
- Updated doc
- Fixed 'magnite-streaming' typos
- Change 'Magnite Streaming' to 'Magnite'
- Updated doc and images
- Updated 'Magnite Streaming' to 'Magnite'
- Added missing DNL
- Updated wording
- Updated 'Adobe Real-Time CDP audeinces' to 'Adobe CDP audeinces'
- Updated magnite.streaming.md doc - Updated the screenshots for audience-field-mapping and audience-target-dropdown
- Updated magnite-batch.md doc - Updated the screenshots for audience-field-mapping and audience-select-device-type
There was a problem hiding this comment.
@jakeseawell please see my comments. Let's add some more clarity before rolling this update out.
| | 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 a dropdown in the Target Field, during the Mapping step of Audience Activation (described below). Learn more about [identities](/help/identity-service/features/namespaces.md). |
There was a problem hiding this comment.
"The current list of supported device types will be available from a dropdown in the Target Field,".
There is no dropdown when you configure mapping. Please rephrase this part so it reflects the UI.
There was a problem hiding this comment.
Will update dropdown to 'Select target field' popout window
| 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 a dropdown list, by clicking the Target Field's target attribute button. |
There was a problem hiding this comment.
"The current list of [!DNL Magnite] supported device types will be available via a dropdown list, by clicking the Target Field's target attribute button.".
There is no dropdown when you configure mapping. Please rephrase this part so it reflects the UI.
There was a problem hiding this comment.
Will update dropdown to 'Select target field' popout window
There was a problem hiding this comment.
Don't forget about this update please.
| The current list of [!DNL Magnite] supported device types will be available via a dropdown list, 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 dropdown 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. |
There was a problem hiding this comment.
Multiple issues here:
- he dropdown will provide a list of integers (from 0-50): there is no dropdown in any of the mapping configuration steps. Please rephrase so it reflects the UI.
- Is there some Magnite documentation where these integers are explained? Or is this a custom implementation with no public info? Having to reach out to Magnite whenever a user doesn't know what to select is not a great experience.
There was a problem hiding this comment.
- Will update
dropdownto'Select target field' popout window - Yes, the former: There is a custom implementation with no public info. If the client does not know which device type to use for this stage, they should be reaching out to Magnite for more information
- I have added that 0 (zero) should be considered the "default"
| >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 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: |
There was a problem hiding this comment.
Please update all "Adobe CDP" occurences to "Adobe Real-Time CDP". Same for "CDP".
There was a problem hiding this comment.
Can you clarify - is this an update to the naming of the Adobe CDP product -> Adobe Real-Time CDP? The reason I ask, is because Magnite has 2 Adobe-CDP destinations - 1 Real-Time destination, and 1 Batch destination. This file represents the document for the Magnite: Batch destination, so I worry about the use of the term "Real-Time" in this context. However, if the name change is required because the Adobe-CDP is now named Adobe Real-Time CDP, then I can make that change 👍
There was a problem hiding this comment.
@jakeseawell Any time you refer to Adobe's CDP, the official branding is "Real-Time CDP". It has nothing to do with the type of destination platform. Please update all occurrences accordingly.
- Updated magnite-batch.md and magnite-streaming.md based on code-review comments/requests - Added 2 new screenshots for MappingId examples (batch)
|
@vfalon Thank you for the review. I have pushed up the requested changes to the PR. Can you please re-review, when you get a chance? Thanks! |
| > 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\]`.   |
There was a problem hiding this comment.
please space out the images. One per row.
- updated Adobe CDP -> Adobe Real-Time CDP - updated dropdown -> 'Select target field' popout window - renamed asset drowdown -> popout - Spaced out screenshots/assest to their own lines
|
@vfalon Added those updates. Thanks! |
3 participants
No description provided.