Connect Branch and Roku to unlock a more holistic picture of the customer journey for your app on OTT/CTV.
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's non Self-Attributing Ad Network(non-SAN) is for all other Roku media advertising. We have a separate guide to setup Oneview here. OneView was formerly known as DataXu before Roku purchased them in 2019 and renamed it.
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)
Engagement and Install Ads
Understand which ad impressions and clicks drove installs.
Measure app installs from apps packaged with your partner platforms
Measure daily installs, opens, and session length
Attribute subscription events, logins, views, opens, etc. back to the last ad seen or Branch Link clicked
Forward activity from partners directly to Branch
Route users directly to content in your app from the Roku Ad
Measure user journeys to and from your various OTT apps
Supported Attribution Methods
- You, as an advertiser, serve an ad for your streaming media app on a CTV platform (ex. Roku, FireTV, Samsung, etc).
- User downloads your streaming media app on their CTV device.
- Your streaming media app will have the Branch SDK installed.
- Branch connects with the Ad Partner and attributes the install & downstream streaming media app events to them.
In order to enable Roku, you need to have completed the following:
- Created a Branch Dashboard.
- Enabled Universal Ads for your Branch account.
- Contact your Branch account manager or visit https://branch.io/pricing
- Implemented the Branch SDK into your OTT/CTV app:
- Admin access to your Roku Account.
1. Set up Roku Exposure Pixel & Channel ID
If you have a Roku Account Manager, send a request to them to set up the Roku Exposure Pixel on all of your eligible Roku display and video media. This ensures that all impressions and clicks are properly being attributed.
They will also be able to provide you with your Channel ID from your channel's properties. (Channel ID will be used later)
If you do not have a Roku Account Manager, you need to select Branch as the approved measurement provider when are uploading a creative:
Afterward, you can locate your Channel ID by searching by channel name and it will populate including the 6-digit ID:
2. Connect Roku in Branch
In the Branch Dashboard in Ads → Partner Management page, find and search for Roku. If you're already logged into the Branch Dashboard, you can also click here to go there directly.
Roku Channel ID
Obtained from your channel properties.
Choose attribution based on clicks, impressions, or considering both equally (Best Match Attribution)
Attribution methods to be considered for attribution
Key/value pairs to be used for advanced attribution methods
3. Configure Events
After authenticating your Roku account to Branch, navigate to the Events Config tab to configure your events.
It's important to add your event mappings here for Branch to properly send event metadata to Roku for attribution. You should see the events you are tracking with the Branch SDK here when you Add Event Mappings.
Events from mParticle or Segment
If you are using mParticle or Segment to track events, you can import them through Branch's integration. View the guides below to enable event importing:
More details on the Roku event mapping can be found here.
4. Configure Attribution Windows
After configuring your events, navigate to the Attribution Windows tab to set windows by attribution type.
You have full freedom to choose your attribution windows; however, it may cause discrepancies between the Branch and Roku when comparing.
Recommended Attribution Windows:
click to session start
click to install
click to conversion event
impression to session start
impression to install
impression to conversion event
5. Cross-Device Attribution
OTT/CTV Cross-Device Attribution with Branch is currently in beta. Please be aware that there may be unexpected bugs/behaviors until the full release. Please reach out to your Branch account manager to get access to OTT/CTV Cross-Device Attribution.
Typically, you do not need Branch Ad Links in order to attribute your Roku campaigns because attribution works through a server-to-server connection between Branch and Roku. For cross-device attribution, however, you will need to use a Branch Ad Link and include the
$cross_device=true parameter to your Branch Click & Impression tracking links to be used in your Roku campaigns.
Roku 和 Branch 之间的数据映射
Branch 将以下数据字段从 Roku 映射到 Branch。
您的 Roku 广告活动的 ID
您的 Roku 广告素材的 ID
Roku 订单项的 ID
Roku 内容的 ID
一旦您开始通过 Branch SDK 追踪事件，我们将开始将其发送到 Roku。Roku 具有映射到预定义 Branch 事件的预定义事件，如下所示。
Branch 会将应用内事件转发给 Roku 进行广告活动优化。此外，Branch 将在 Branch 操作后台 (Dashboard)中接收归因数据以进行丰富的分析。
Branch Event Name
Roku Event Name
首次打开应用（首次打开应用将映射到 Roku 安装）
（“Qualified Streaming Session”）在连续视频播放时间超过5M的视频视图上触发 QSS。例如，单个视频观看60M，将导致单个 QSS 事件。
FQSS (custom event)
voice_search (custom event)
first_video_view (custom event)
视频视图（首次视频视图将映射到 Roku FTV）
视频 metadata（详细的内容视图-内容 BOB 信息，包括-网络，标题，流派，类型，等级）
CSAI 或 SSAI 插播广告已启动
Updated about 1 month ago