Distribute Data To OneView
See the instructions below for distributing first-party data or Data Marketplace data to OneView (Roku's DSP).
Note
Distributing data with Connect involves activating a destination account for the destination you’re distributing to and then adding segments to distribution for that destination account. See the articles below for instructions:
Overview of the OneView Integration
LiveRamp's integration with OneView follows the guidelines listed in the table below:
Caution
The information listed below was current at the time of publication and represents our best understanding of the integration based on the information available at the time, including information given to us by the destination platform. Any sections not filled out are areas we did not have information on at the time of publication. Use this as a general guide, but check with the platform to confirm any areas that are critical to your use case.
Category | Area | Info | Notes |
|---|---|---|---|
Delivery/Matching | Identifiers that can be delivered |
| |
Lookback window | |||
Time to live | 30 days | This can be edited in the OneView UI after the segment has been created. | |
Enabled for Record Sync | No | ||
Accepts raw fields | No | ||
Duplicate segment names allowed | Yes | Duplicate segment IDs are not allowed. | |
Configuration | Account info needed | Advertiser UID: The advertiser UID where the segment will appear in OneView. | For more information, see the sections below. |
Requires OAuth authorization | No | ||
Additional data restrictions | No | ||
Requires LiveRamp action to activate destination account | No | ||
Data Marketplace | Accepts Data Marketplace data | Yes | For more information, see the “Distribute Data Marketplace Data To OneView” section below. |
Data Marketplace pricing used | |||
Additional Data Marketplace limitations or guidelines | |||
Additional Information | Can display matched reach in Connect | No | For more information, see “Destinations that Do Not Support Matched Reach Stats”. |
Limit on number of audiences per seat ID in the platform | |||
Exposure logs available | Yes | ||
LiveRamp Conversions API program available | No |
OneView Integration Options
When activating a OneView destination account, the following integration options are available:
Use | Data Type | Who It’s For | Use |
|---|---|---|---|
Distributing first-party data to OneView (Roku) | Advertisers | OneView (Roku) First-Party Data | |
Distributing Data Marketplace segments (third-party data) to OneView (Roku) | Data Marketplace data | Data Sellers | OneView (Roku) Data Marketplace |
Note
Data buyers should typically find Data Marketplace segments in OneView and do not need to distribute those themselves. Data sellers also typically do not need to distribute their segments to OneView, as OneView pulls those in themselves. For more information, see the “Distribute Data Marketplace Data To OneView” section below.
Distribute First-Party Data to OneView
To distribute first-party data to OneView, activate the “OneView (Roku) First-Party Data” integration tile by following the instructions in "Activate a New Destination Account".
Once you’ve activated the destination account, follow our instructions on "Distribute Data to a Destination".
Configure the Required Properties
When activating the destination account, the following fields are required:
Field | Description | Notes |
|---|---|---|
Advertiser UID | Enter the advertiser UID where the segment will appear in OneView. | This ID should be numeric. Click here for instructions on how to find your advertiser UID. This link requires an email login to access OneView Help. If needed, confirm your Advertiser UID with your OneView representative. |
Destination Account Name | The name you want to give to this destination account. | Enter a unique and memorable name for this destination account, or accept the default suggested name. You can use any name you want as long as it is less than 150 characters in length. |
Distribute Data Marketplace Data To OneView
Data Marketplace data can be distributed to OneView in the situations listed below:
Party Distributing | Distribution Type | Integration to Use | Notes |
|---|---|---|---|
Data buyers | Standard segments: No | OneView (Roku) First-Party Data | |
Custom segments: No | |||
Data sellers | Standard segments: No | OneView (Roku) Data Marketplace | |
Custom segments: Yes | Uses Programmatic Standard pricing |
To distribute data to OneView, follow our instructions on "Activate a New Destination Account" and select the “Data Marketplace” destination account tile listed in the table above.
Once you’ve activated the destination account, follow our instructions on "Distribute Data to a Destination".
Guidelines for Distributing Data Marketplace Data
Use the following guidelines when distributing Data Marketplace data:
LiveRamp and OneView have a unique integration. OneView's Account Managers are heavy users of the Data Marketplace Buyer UI, and use it almost exclusively as their means of acquiring both standard and custom segments.
Data buyers should typically find Data Marketplace segments in OneView and do not need to distribute those themselves. Data sellers also typically do not need to distribute their segments to Oneview, as OneView pulls those in themselves.
Configure the Required Properties
When activating the destination account, the following fields are required:
Field | Description | Notes |
|---|---|---|
Advertiser UID | Enter the OneView advertiser UID of the advertiser who will utilize your LiveRamp data. | For instructions on how an advertiser can find their advertiser UID, click here. This link requires an email login to access OneView Help. If needed, confirm your Advertiser UID with your OneView representative. |
Destination Account Name | The name you want to give to this destination account. | Enter a unique and memorable name for this destination account, or accept the default suggested name. You can use any name you want as long as it is less than 150 characters in length. |
Information for Data Sellers
Because OneView pulls Data Marketplace segments in themselves, data sellers should list their standard and custom segments for OneView and rely on OneView's team to access the data on their own.
OneView typically acquires data on a campaign-specific basis. Their account teams will browse the Data Marketplace UI to locate relevant segments for particular campaigns.
Note
Following best practices for segment naming will be particularly helpful with OneView so your segments will appear properly in searches.
OneView also brings in segments from certain data sellers to to OneView so that data buyers can view and buy those Data Marketplace segments within OneView. This process is usually referred to as “syndication”, but is sometimes also referred to as “stocking the shelves”. To request that OneView syndicate your Data Marketplace segments, review the guidelines below.
For information on distributing your Data Marketplace segments to OneView, review the guidelines below.
Pricing information: Uses Programmatic Standard pricing.
Editing segment metadata: Most segment metadata can be updated.
Segment removal process: Contact your OneView rep.
Syndication allowed: Yes.
Syndication pre-approval required: Yes.
Syndication approval process steps and timeline: Contact the OneView CSM. The approval process timeline varies.
Syndication distribution process: Once you've been approved, segment share the intended data to the OneView account.
If you have any additional questions, contact your OneView representative or your LiveRamp representative.
Distribute Custom Segments to a Data Buyer on OneView
If a brand or agency customer requests a custom segment from you for a campaign on OneView, follow the instructions listed below:
By default, data sellers do not have access to OneView’s Data Marketplace tile and access needs to be approved by OneView's data ops team. Email the OneView data ops team at dldataops@roku.com for approval.
Create a case in the LiveRamp Community portal confirming that OneView's data ops teams has approved giving you access to the Data Marketplace tile and that the tile will only be used for custom segments.
When naming each segment, make sure to include the advertiser or agency name in the segment name.
To ensure that each segment you distribute to OneView has a unique segment ID, perform one of the following actions:
Caution
OneView cannot accept duplicate segment IDs in their system. If a custom segment that has already been sent to OneView is resent, that new segment will be blocked from appearing in OneView's systems. Make sure to follow the instructions below to avoid sending duplicate segment IDs to OneView.
Upload the segment as a new segment.
Create a derived segment using a previously uploaded segment (see "Create a Derived Segment" for more information).
Once the LiveRamp support team has provided access to the OneView (Roku) Data Marketplace tile, "Activate a New Destination Account "and "Distribute Data to a Destination".