Track CTV app campaigns on Roku Endemic Media
With Adjust's Roku Endemic Media integration, you can track campaigns you run on Roku inventory to measure the number of app installs on connected TV devices. This lets you see engagement data from the platform's media environments, such as on the screensaver, as well as inside channels.
Here, you can find information about how to connect Adjust to Roku Endemic Media in the Adjust dashboard, and send Adjust data server-to-server (S2S).
With Roku OneView for CTV you can promote mobile apps on connected TV:
With the Roku OneView module you can measure your mobile app attribution and event data:
Before you begin
Here's what you need to know before getting started.
Requirements
- A Roku Channel ID
- To find your Channel ID, log into
owner.roku.com
and view your channel's properties. Your ID can be found in the address bar.
- To find your Channel ID, log into
Glossary
Term | Description |
---|---|
S2S attribution | S2S attribution is an exclusive integration that cannot be used in conjunction with the Adjust SDK |
Endemic advertising | Placing adverts in a natural environment to their market |
Integration details
Adjust's S2S integration with Roku cannot be used in conjunction with the Adjust SDK.
Roku is a self-attributing network. This means that Adjust sends Roku data for all of your app's installs and Roku self-attributes using their own engagement data. Roku attributes using a 14-day lookback window for all endemic media exposures, including both clicks and impressions.
Roku reporting structure
Here's how Roku campaign data is reported in Adjust:
- Network =
Roku
- Campaign =
campaign_id
- Adgroup =
line_item_id
- Creative =
creative_id
Supported device identifiers
ID | ID Type | Format |
---|---|---|
IDFA | Raw Apple advertising ID | Uppercase, with hyphens |
GPS_ADID | Raw Google advertising ID | Lowercase, with hyphens |
FIRE_ADID | Raw Amazon Fire advertising ID | Lowercase, with hyphens |
WIN_ADID | Raw Windows advertising ID | Without hyphens |
RIDA | Raw Roku advertising ID | |
OAID | Raw Huawei advertising ID | Lowercase, with hyphens |
Roku has their own device identifier called RIDA
. Users on Roku devices can reset it at any time or disable it to avoid targeted advertising. If Roku cannot track the RIDA of a Roku device, they can still make an attribution claim using probabilistic modeling.
Dashboard setup
When you activate the Roku Endemic Media module integration, Adjust immediately begins to forward activity data to Roku for attribution.
To activate the module, follow these steps in the Adjust dashboard:
- Find your app and select your app options caret (^).
- Select Partner Setup.
- Select ADD PARTNERS and select Add (+ icon) beside Roku Endemic Media.
- Enter your Channel ID.
- Select SAVE.
Manage event linking
To link events to Roku, follow these steps.
- Find your app and select your app options caret (^).
- Select Partner Setup.
- Enter Roku Endemic Media.
- Select Event Linking.
Under each Adjust-tracked in-app event you will see a field with a drop-down menu. Use the dropdown menu to select a predefined Roku event that maps to your Adjust-tracked event. Custom events cannot be sent to Roku.
Roku Event Name | Description |
---|---|
trial | Device initiated a trial period of an app |
sign-up | Device signed up for a product or service |
subscription | The ongoing event that signifies a device’s subscription status |
QSS | Trigger QSS on Video Views exceeding 5 minutes of contiguous video playback time. A single video view of 60 minutes, for example, will result in a single QSS event. |
FQSS | The first QSS for that app |
text_search | Text Search Initiated |
voice_search | Voice Search initiated |
video_stream | Video Playback Initiation (Request for Video Stream) |
est_transaction | EST Transaction (Entertainment Sell Thru) - a one time purchase |
first_video_view | Video View (First time video view will map to Roku FTV |
video_view | Video Metadata (Detailed Content View - Content BOB Info in terms of - Network, Title, Genre, Type, Rating) |
Ad_initiated | CSAI or SSAI In-Stream Ad Initiated |
Server-to-server integration
With the Roku Endemic Media module enabled in the Adjust dashboard, you can now set up server-to server integration with Adjust. This means you only send Adjust in-app session and event data through S2S API calls.
Requirements
- For details on the requirements for your in-app solution, refer to Adjust's server-to-server attribution checklist.
- All requests to Adjust servers must be made in the same sequential order they occur on the device.
- Always include the
os_name
in your request. This can be:android
ios
fire-tv
roku
vizio
Send sessions
Sessions are the base of all attribution and tracking in Adjust. They trigger when a user resumes using an app from the background or when they open the app.
To send Adjust sessions, use our S2S sessions API.
Endpoint: https://s2s.adjust.com/session
Send in-app events
To send Adjust in-app event data, use our S2S events API.
Endpoint: https://s2s.adjust.com/event
Export your data
Placeholders
You can use the following placeholders to get specific Roku datapoints in your raw data exports.
Placeholder | Description |
---|---|
{RIDA} | Roku's device ID |
{roku_content_id} | Content or Ad Unit ID displayed |
{roku_placement_type} | Shows the value of the ad slot where the ad is being run on the Roku platform. It can include values such `mychannels` (homescreen banner) and `screensaver` (screensaver banner) |