Roku Ads Manager Integration for Dealerships

Self serve streaming television with genuinely local targeting, and exactly how far the adapter has got.

Roku sells advertising on the television screen itself, across its home screen, its own channel and the streaming apps running on its devices. Ads Manager is the self serve console for that, which is the part that matters to a dealership, because streaming television has historically been sold by a salesperson with a rate card and a quarterly commitment.

Two products change the shape of the buy for a store. Targeting goes genuinely hyperlocal, so a campaign can be drawn around a trade area rather than a metropolitan region, which is the difference between a buy a single rooftop can justify and one only a regional association can. And Action Ads let a viewer request information using the television remote, which is a real opt in event happening on the platform rather than a click that has to survive a jump to a phone.

Roku also opened a public advertising API, so a developer can register an application and obtain credentials directly. That single fact is why this platform sits at registered rather than on the request list with most of its category. It is the same category covered on our connected TV advertising page, bought through the most accessible door in it.

The case is reach at a price television has not historically offered a single store. Roku publishes a case study in which an Arizona dealer group reached more than 1.7 million households at roughly nineteen cents per household. Treat that as one advertiser's published result rather than a rate you should expect, but it does illustrate the shape of the channel: television level coverage of a trade area for a sum a store can actually approve.

The honest objection is that a television screen is a poor place to ask somebody to do something. A viewer half watching a show with a remote in their hand is not in a buying posture, and the Action Ad opt in, real as it is, is a low friction expression of curiosity from a sofa. That is not the same intent as somebody typing a trim and a city into a search box, and a store that treats the two identically in the follow up will misprice both.

The second objection is measurement, and it is the one that sinks most dealership streaming buys. Results here are not reliably attributable inside twenty four hours. Household level reach numbers describe households, not people, and the person who saw your spot will not identify themselves the same evening. Buy this for coverage and conquest across a trade area, hold your search and social spend responsible for the immediate scoreboard, and set the expectation before the campaign starts rather than defending it afterwards.

Registered, not yet built, and the published test for that status is that an adapter file exists in the ad gateway with a written wire up checklist, committed and scoped. That is precisely what is there. The checklist is seven steps, it is ordered, and every lifecycle method in the adapter currently falls through to the shared refusal, which returns a failure naming Roku rather than pretending to succeed.

That refusal behaviour is deliberate and worth a sentence. A stray call from anywhere in the CRM fails loudly and readably instead of looking like an outage at the network, which is the difference between a bug somebody fixes in an hour and a support ticket about streaming being down.

The access class is PUBLIC, and here that word means what it says. Authentication is an API key generated in the Events tab of Ads Manager, not an application, not a partner review and not a signed minimum. There is no approval queue standing between this integration and a working credential, which is the single largest reason Roku is registered while most of its category sits on the request list. Compare that with the other streaming platforms in this directory, where a vendor review usually comes first.

Written as a design, because the adapter is scoped rather than running.

Lead capture on this platform works both ways, which is unusual for streaming. A viewer can opt in on the platform through an Action Ad, or a spot can drive to a landing page in the ordinary manner. Both are real. Only one of them lands somewhere we can read today, and the section on what we will not claim is specific about which.

Roku is not a special case in the CRM. It is one implementation of a contract that every network answers. A single provider agnostic library defines what any advertising platform must be able to do: hand us an authorization URL, exchange the code for a token, list the accounts a credential can reach, deploy a campaign, pause or resume it, return spend and results, and prove on demand that the connection still works.

Seven operations, one adapter file per network. That is why finishing Roku is a scoped piece of work with a checklist rather than an open ended project, and why completing it does not disturb the network already running. Twenty networks are registered against the contract and one is implemented, which is a ratio worth publishing rather than hiding, because a directory that only listed the finished network would be one entry long.

The shared plumbing is already built and Roku inherits all of it. Credentials are encrypted before storage using AES-256-GCM. Every action against a network is written to an append only audit log carrying the company, the network, the user and the detail, stamped in UTC on purpose, because these tables are shared across dealerships and a timezone relative timestamp is one nobody can reconcile later. Campaign objects record which credentials created them and re resolve those same credentials afterwards, so disconnecting an account next month does not strand the campaigns built under it this month.

Two ways to advertise through LeadLocate, and the dealership chooses. The first is the webXintel Ads Network. It is included, our team builds and operates the campaigns from the selections you make in Leads Manager, and it arrives as one line rather than a stack of platform invoices. That path is live and independent of this adapter.

The second is your own account. Connect the advertising account your store already holds and campaigns route through it instead, on your billing, in your name, with your spend history intact. Disconnect whenever you like and delivery falls back to the managed path without you doing anything. For Roku that is the half this page is about, and it is the half that is unfinished.

The authentication story here is unusually friendly, which is worth knowing in advance. There is no developer application to file and no token exchange dance to survive. An API key is generated inside the Events tab of Ads Manager by somebody with access to the account, and that is the credential. When the adapter is finished, connecting will be a paste rather than a project.

One limit applies across the whole gateway and this page states it like every other: pushing, pausing and reading numbers from a network is done by our team, not from your dashboard. It is a deliberate constraint while the connection layer is young, and it is on the list to open up.

The checklist is seven steps and the order is fixed. Register an application and generate the API key. Fill and enable the Roku block in the credential file. Implement credential storage and verification. Implement account listing. Implement campaign deployment. Implement status changes so a campaign can be paused and resumed. Implement reporting so spend and delivery come back.

Nothing on that list waits on somebody else's approval queue, which is the meaningful difference between this platform and the rest of its category. There is also no published minimum spend on Roku's side, so the practical floor is whatever buys enough impressions inside a trade area to be worth reading. A streaming campaign too small to reach a household more than once teaches you nothing, which is a worse outcome than not running it.

On timing, the caveat from earlier is a design constraint rather than a disclaimer, and when this is built the expectation will be set in the interface itself. Results on this platform are not reliably attributable inside twenty four hours. Delivery data is quick, outcome data is slow, and the honest way to hold a streaming buy to account is coverage of the trade area, completion rate and movement in your direct channels over a longer window. None of that is a promise about volume or closing rate, and nobody can offer one.

Roku supports several things we have not built, and on a page carrying our second strongest status word the gaps deserve naming rather than implying.

Action Ad opt ins are not retrieved by us. Our lead form retrieval is implemented for one network only, and Roku is not it. The opt in is real and it happens on the platform, and today it lives in the vendor's console rather than arriving in your CRM. That is the most important sentence on this page, because it is the exact spot where a reader would otherwise assume too much.

We do not run a server side conversions endpoint. Roku exposes conversion event ingestion and we operate no server side conversions API of any kind, for this network or any other. No offline conversion upload either.

We do not install or manage a pixel. Site side measurement remains whatever your website already has.

We do not emit a vehicle catalog. No feed of individual units goes to any advertising platform from our stack.

We do not upload hashed audiences. No customer list is exported to build a targeting segment.

No campaign has ever been deployed to Roku from the CRM. Every lifecycle call still returns a refusal naming the network, and that will remain true until the checklist above is finished.

Ask, with your store attached, and say what you would run first. Requests are recorded against the platform they name and the tally is what decides build order, because a request from a dealership ready to spend on a channel is a better signal than any roadmap meeting.

Roku carries more leverage in that queue than most streaming entries for a reason that has nothing to do with Roku's audience. It is the only platform in its category with an open credential path, so the vendor side of the work is already solved and the remaining distance is entirely ours. A request here buys scheduling rather than negotiation.

In the meantime the managed path runs today and does not wait on any of this. If what you want is television reach across a trade area this month, that is the conversation to have. Pricing for the platform is on the pricing page and does not change based on which networks you turn on.

Does LeadLocate integrate with Roku Ads Manager today?

No. Roku is registered in the ad gateway, which means an adapter file exists with a seven step wire up checklist, and it is not built. Every lifecycle call it receives returns a refusal naming the network rather than failing silently.

Can I use my own Roku Ads Manager account?

Not yet through the CRM, because the self connect half is the unfinished half. When it is done the credential is an API key generated in the Events tab of Ads Manager, so connecting will be a paste rather than a developer application. The managed path runs today and does not depend on it.

What happens if I request Roku?

It is recorded against Roku specifically and counted, and that tally decides build order. This platform sits unusually well in the queue because its credential path is open, so a request buys scheduling rather than a negotiation with a vendor.

Would Action Ad opt ins arrive in my CRM?

Not today, and this is the gap worth reading twice. Action Ads produce a genuine opt in on the platform, but our lead form retrieval is built for one network and Roku is not that network. Those opt ins currently live in the vendor's console.

How fast would I know whether a Roku campaign worked?

Delivery and spend read quickly. Outcomes do not. Results on this platform are not reliably attributable inside twenty four hours, which is a property of television viewing rather than a flaw in the reporting, and the expectation belongs at the start of the campaign.

Is there a minimum spend?

None is published by the vendor. The practical floor is whatever buys enough impressions inside your trade area for the data to mean something, and a campaign too small to reach a household more than once is worse than no campaign because it teaches you nothing.

Can you advertise specific vehicles on Roku?

No. Unit level creative from a feed requires a vehicle catalog and we do not emit one to any advertising platform. Streaming creative here is video about your store and your offers rather than individual stock.

The adapter is written and the credential path is open, so the remaining distance is ours. Tell us your store and the trade area you would cover first.