Roku Ads Conversions API Destination
Send server-side conversion events to Roku Ads Manager to measure how your CTV campaigns drive purchases, sign-ups, and other conversions.
Use this page to connect Ours Privacy to Roku Ads Manager. Each conversion you forward is attributed against your Roku campaigns, so you can measure how your CTV ads drive purchases, sign-ups, checkouts, and other outcomes — and keep that attribution working when the browser pixel can't fire.
Before you start
- A Roku Ads Manager account with Organization Admin or Account Admin access.
- An Event Group created in Roku Ads Manager for the property you want to track.
Setup
- Sign in to Roku Ads Manager with an admin account.
- Open Assets → Events and select or create an Event Group for your property.
- Copy the Event Group ID — it starts with
eg-. - In the same Events tab, click Generate API Key and copy the key right away — Roku shows it once.
- In Ours Privacy, add the Roku Ads Conversions API destination and paste in your API Key and Event Group ID.
- Configure your event mappings, and connect at least one identity field (such as email, phone, or IP address) so Roku can match conversions to ad views.
Event types
Map each of your events to one of Roku's conversion types — PURCHASE, ADD_TO_CART, PAGE_VIEW, SIGN_UP, LEAD, and more. The full list is shown in the mapping UI. Roku only accepts its defined event names, so any unmapped event name is rejected.
Limited Data Use (LDU)
Roku calls its version Limited Data Use (LDU). When it is set, Roku limits how it uses the event data, which helps you honor opt-outs under US state privacy laws such as the CCPA and its CPRA amendments. Roku makes the restriction available to people in California, Colorado, Connecticut, Florida, Montana, Oregon, Texas, Utah, and Virginia.
One field in the destination mapping controls it:
- Limited Data Use (LDU): set to true and the event is restricted at Roku. Map it to the opt-out signal you already collect, such as a consent choice or a Global Privacy Control signal.
The Conversions API does not accept a country or state with this flag. You are responsible for determining the person’s location and whether the flag should be sent.
Unlike the Roku pixel, where the flag sticks to a visitor once applied, the flag has to accompany every event you send through the Conversions API. Map it to a signal that stays true for that visitor rather than one that fires once.
Setting the flag restricts what Roku may do with the event; it does not stop the event from being sent. To withhold events entirely, use Global Data Governance rules or your consent configuration.
Expect reduced retargeting and measurement for flagged events. Leave the field unmapped and your events go out with no restriction requested, which is the default.
See Limited Data Use for every destination that supports a flag like this and what each platform calls it.
Next steps
Need help? Contact support@oursprivacy.com.
How is this guide?