Roku OneView campaign configuration

The Integration tab includes a number of sections, as described below.

Activate partner

On your first visit, you must activate the partner to enable the setup, by turning on Activate partner.

Advanced Privacy

For iOS apps only, when Advanced Privacy (for iOS 14.5+ and later) is turned on, you can control what data is shared with Roku OneView via postbacks and reports.

General settings

• Enter the Roku ID: Roku Pixel-ID (Install) 
• Turn on View-Through attribution if you want to attribute view-through installs from Roku OneView. The view-through lookback slider is available on the Attribution link tab (described below).

Default postbacks

Send automatic postbacks to Roku OneView following installs and rejected installs. Use this section to define the source of the users for the postbacks:

• Select This partner only for installs coming only from users attributed to Roku OneView.
• Select All sources, including organic to have your entire user base available to be reported to Roku OneView.

Note: Rejected installs can be sent for This partner only.

In-app event postbacks

Configure in-app event postbacks sent to Roku OneView:

1. Turn on In-app event postbacks.
2. Set the In-app events postback window.
3. Click Add event to add an SDK or server-to-server event to the list.
   

   Parameter name	Description
   AppsFlyer event	The name of the event, as received by AppsFlyer either from the SDK integrated into your app or from server-to-server events. Tip: Don't see the event you are looking for? Make sure to activate the event on a device with a non-organic installation and recheck. Type it in AppsFlyer event, then click Create custom. Read more about custom event mapping.
   mapped to partner event	The unique name or ID of each event, as defined on the partner's side. Possible mapping configurations are: Text field: Get the corresponding event ID from the partner. Drop-down box: Select the most suitable pre-defined AppsFlyer event. As is: Send the events as they are, without name mapping.
   for users from	Select the sending option for the event: This partner only: Send postbacks only when this event is attributed to this partner. All media sources including organic: Send postbacks for events attributed to any partner, as well as organic events.
   including	No data (default): Send only the event itself without the event value. Values and revenue: Send all the event parameters, including the revenue value (if exists in the event). Values without revenue: Send all the parameters excluding the revenue value.

4. [Optional] Clickto set conditions for sending certain in-app events to the partner.
5. Click Save integration.

Generate and save attribution links and send them to the partner for attributing specific campaigns, ad sets, or single ads.

Learn more about attribution link structure and parameters.

To generate an attribution link, follow the CTV-to-mobile app attribution setup instructions.

Cost integration is not available for Roku OneView.

Ad revenue is not available for Roku OneView.

In this tab, you can select the permissions to grant Roku OneView, whether the partner acts as an ad network, agency, or even both. Note that even if attribution is disabled for Roku OneView, the permissions tab can be active and you can grant control to Roku OneView.

After you enable granting permissions to Roku OneView, you can add team members to grant them access to the data, according to the selected permissions.
Permissions can be granted only to Roku OneView employees that have an ad network team member account on AppsFlyer.
To grant permission to ad network team members:

1. Click Add team member.
2. Enter the ad network team member's email. 
3. Click Add.

Permission types that advertisers can grant Roku OneView