Roku provides access for its third-party Measurement Partners to request attribution for install and event attribution for clients utilizing Roku’s Endemic Media to help drive distribution and re-engagement of their apps. Similar to other Self-Attributing Networks (SAN), Roku functions will be able to take conversions where they claim attribution for and use it for audience targeting.
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
- You, as an advertiser, serve an ad for your app on a CTV platform (ex. Roku, FireTV).
- User downloads your app on their Roku TV.
- Your app will have the Branch SDK installed.
- Branch connects with Roku and attributes the install & downstream app events to the ad partner.
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.
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:
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
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.
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
Branch maps the following data fields from Roku to Branch.
CLICK or IMPRESSION
The ID of your Roku Campaign
The ID of your Roku Creative
Line Item ID
The ID of the Roku Line Item
The ID of the Roku Content
"mychannels" or “screensaver”
Timestamp of the ad impression or click
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
Initial App Open (First time app open will map to Roku Install)
App Session (First time app session should be sent as First App Session)
Device initiated a trial period of an app
Device signed up for a product or service
The ongoing event that signifies a device’s subscription status
(“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.
FQSS (custom event)
The first QSS for that app.
Text Search Initiated
voice_search (custom event)
Voice Search Initiated
Video Playback Initiation (Request for Video Stream)
EST Transaction (Entertainment Sell Thru) - a one time purchase
first_video_view (custom event)
Video View (First time video view will map to Roku FTV)
Video Metadata (Detailed Content View - Content BOB Info in terms of - Network, Title, Genre, Type, Rating)
CSAI or SSAI In-Stream Ad Initiated
Updated about 1 month ago