Roku

Prev Next

Overview

For marketers utilizing Branch and Roku, this article details how to integrate Branch's robust deep linking and attribution features within your Roku ad campaigns.

Learn how this integration can improve the user journey and provide clearer insights into your advertising effectiveness on the Roku platform

Roku Ad Manager
Roku's Self-Attributing Ad Network, provides access for its third-party Measurement Partners to request attribution for install and event attribution for clients utilizing Roku’s Endemic(i.e. streaming) Media to help drive distribution and re-engagement of their apps. Similar to other Self-Attributing Networks (SANs), Roku will be able to receive conversion events tracked via Branch SDK and use it for performance optimization, audience segmenting, and re-targeting.

Roku Data Sharing

Roku last-attributed data will be wiped at the log-level (via Custom Exports and Daily Exports) and this data will appear as null/blank in exports but you can still export it via aggregated data (Aggregate API or Query API)

Prerequisites

In order to enable Roku, you need to have completed the following:

  1. Created a Branch Dashboard.

  2. Enable Household Measurement for your Branch account. Contact your Branch account manager or visit the Pricing page.

  3. (Optional) Implemented the Branch SDK into your OTT/CTV app:

  4. Admin access to your Roku Account.

Enable Roku

To enable Roku, complete the steps below:

1. Sign in to Roku Ads Manager

2. Navigate to Events page

  1. Identify an existing Event Group or create a new Event Group

    1. Copy the Event Group ID
      A screenshot of a web page

AI-generated content may be incorrect.

3. Send Roku ([email protected]) the following information:

  1. Your MMP name (Branch)

  2. Your Event Group ID

4. Connect Roku in Branch

  1. In the Branch Dashboard in Ads Partner page, find and search for “Roku SAN”. Do not use the “Roku”

  2. Enter your Roku Ads Manager Event Group ID and click Save.

  3. Switch to the Events Config tab and map your Branch app events to Roku Ads Manager events.

    1. Events will appear in Roku Ads Manager attribution reporting based on this mapping configuration.

    2. Click Save.

  4. (Optional) After configuring your events, navigate to the Attribution Windows tab to set windows by attribution type.

    1. Here are Roku’s recommended attribution window settings:

      Attribution Type

      Window

      click to session start

      1 day

      click to install

      7 days

      click to conversion event

      1 day

      impression to session start

      1 day

      impression to install

      1 day

      impression to conversion event

      1 day

Please note that events can take up to 4 hours to appear in Roku Ads Manager

Data mapping between Roku & Branch

Branch maps the following data fields from Roku to Branch.

Roku Data

Branch Data

Possible Values

Touch Type

last_attributed_touch_type

CLICK or IMPRESSION

Campaign ID

last_attributed_touch_data_tilde_campaign_id

The ID of your Roku Campaign

Creative ID

last_attributed_touch_data_tilde_creative_id

The ID of your Roku Creative

Line Item ID

last_attributed_touch_data_tilde_ad_set_id

The ID of the Roku Line Item

Content ID

last_attributed_touch_data_tilde_content_id

The ID of the Roku Content

Placement Type

last_attributed_touch_data_tilde_placement

"mychannels" or “screensaver”

Timestamp

last_attributed_touch_timestamp

Timestamp of the ad impression or click

Forwarding events to Roku

Once you begin tracking events through the Branch SDK, we will start sending them to Roku. Roku has pre-defined events that map to pre-defined Branch events, listed below.

Branch will forward in-app events to Roku for campaign optimization. In addition, Branch will receive attribution data for rich analysis in the Branch dashboard.

Branch Event Name

Roku Event Name

Description

INSTALL

first_open

Initial App Open (First time app open will map to Roku Install)

OPEN

session_start

App Session (First time app session should be sent as First App Session)

START_TRIAL

trial

Device initiated a trial period of an app

COMPLETE_REGISTRATION

sign_up

Device signed up for a product or service

SUBSCRIBE

subscription

The ongoing event that signifies a device’s subscription status

COMPLETE_STREAM

qss

(“Qualified Streaming Session”) Trigger QSS on Video Views exceeding 5M of contiguous video playback time. A single video view of 60M, for example, will result in a single QSS event.