Skip to main content

Distribute Data To OneView (Roku's DSP)

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

See the table below for an overview of LiveRamp's integration for OneView.

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 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.

Note

For detailed information on the distribution options, see the additional sections below.

Category

Area

Info

Notes

Delivery/Matching

Identifiers that can be delivered

  • Cookies: Yes

  • Mobile device IDs: Yes

  • RampIDs: Yes

  • CTV IDs: No

  • CIDs/Platform IDs: No

Lookback window

Time to live

30 days

This can be edited in the OneView UI after the segment has been created.

Precision levels allowed

  • Individual: Yes

  • Household: Yes

  • Neighborhood: Yes

For more information, see "Precision Levels".

OneView never directly expands the segment membership. But they do allow cross-device targeting at bid time, which is controlled by the Identity Targeting settings that you configured for your campaign in the OneView UI. If you opt to disable cross-device, they’ll only use the data in the segment. If you choose a cross-device policy (deterministic, high precision, household) they’ll use different graph data at bid time to determine if a particular device is associated with the segment.

Allowed input data types

  • Offline (PII): Yes

  • Online (cookies, MAIDs, etc.): Yes

Enabled for Record Sync

No

For more information, see "Keep Destination Data Fresh with Record Sync".

Accepts raw fields

No

For more information, see “Platforms that Do Not Accept Raw Fields”.

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

For information on LiveRamp’s standard data restrictions, see “LiveRamp Data Restrictions” and “Data Marketplace Segment Review and Approval”.

Requires LiveRamp action to activate destination account

No

Data Marketplace

Accepts Data Marketplace data

  • Standard segments: No

  • Custom segments: Yes

  • Syndication: Yes (with approval)

For more information, see the “Distribute Data Marketplace Data To OneView” section below.

Data Marketplace pricing used

Programmatic Standard

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

OneView has the integration options listed in the table below.

Integration Name

Data Type

Who It’s For

Use

Distributing first-party data to OneView (Roku's DSP)

First-party data 

  • Advertisers

OneView (Roku) First-Party Data

Distributing custom segments to OneView on behalf of a data buyer

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, follow our instructions on activating a destination account and select the “OneView (Roku) First-Party Data” integration tile.

When activating the destination account, the following fields are required:

  • Advertiser UID: Enter the advertiser UID where the segment will appear in OneView. Click here for instructions on how to find your advertiser UID. If needed, confirm your Advertiser UID with your OneView representative.

  • Destination Account Name: 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.

Once you’ve activated the destination account, follow our instructions on distributing data to a destination.

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

Custom segments: No

Data sellers

Standard segments: No

Custom segments: Yes

OneView (Roku) Data Marketplace

Uses Programmatic Standard pricing

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.

To distribute Data Marketplace custom segments to OneView, data sellers should follow our instructions on activating a destination account and select the "OneView (Roku) Data Marketplace" destination account tile.

When activating the destination account, the following fields are required:

  • 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.

  • Destination Account Name: 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.

Once you’ve activated the destination account, follow our instructions on distributing data to a destination.

Information for Data Sellers

Because OneView pulls Data Marketplace segments in themselves, data sellers should allowlist 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:

  1. 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.

  2. Create a case in the LiveRamp Community portal confirming that the tile to gain access to the Data Marketplace tile, confirming that OneView's data ops teams has approved this, and that the tile will only be used for custom segments.

  3. When naming each segment, make sure to include the advertiser or agency name in the segment name.

  4. 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).

  5. Once the LiveRamp support team has provided access to the OneView (Roku) Data Marketplace tile, activate a new destination account and distribute the desired custom segment(s).

In this section:
Lookback windowTime to livePrecision levelsecord Sync

A field in a given file that has over 250 distinct values, and so cannot be separated out and managed individually in the UI.

OAuth (Open Authorization) is an open standard for token-based authentication and authorization.

The number of records and devices that have been matched at a distribution destination for your distributed fields and segments. Also referred to as "actual reach".

Data that a company has collected themselves, as opposed to second-party data or third-party data.