Run Brave Ads from Your Dealership CRM

The one audience that cannot be retargeted, reached inside the browser that stops everyone else from trying.

Brave is a web browser whose selling point is that it blocks advertising and tracking by default. Its own advertising product is the exception it carves out for itself: users choose to see ads in exchange for a rewards balance, and those ads appear as notifications, as sponsored placements on the new tab page, and inside the browser's news feed. Nobody sees them who did not agree to.

The mechanism underneath is the part worth understanding. Matching happens on the device rather than on a server, so the browser decides locally which ad to show and the advertiser is never handed the browsing history that produced the decision. That is a genuinely different architecture from the rest of this catalogue, and it produces a genuinely different kind of reporting.

For a dealership the value is access rather than volume. This is the audience that has removed itself from ordinary display advertising entirely, deliberately and by installing software to do it, and this is the only door into that group that the group itself opened.

The case is reach that money cannot otherwise buy. The people using this browser tend to be higher income, technically literate and in the earlier part of their careers, which is a good description of a new vehicle buyer with a strong credit profile. They are also the people your display and retargeting budget never touches, because they blocked it before you bought it. If your campaigns are quietly missing a slice of your market's best buyers, this is where that slice went.

There is a second, smaller argument about goodwill. Advertising that the viewer agreed to receive lands differently from advertising that ambushed them, and a local business showing up politely in that context is not the intrusion it would be elsewhere.

The honest objection is measurement, and it is unusually blunt on this platform. The entire product is designed so that the advertiser learns less. There is no per user path to follow, the matching happens where you cannot see it, and reporting is aggregate by design rather than by omission. A dealership used to reading a click through to a specific shopper will find that instrument simply absent, and no amount of budget or configuration restores it.

The second objection is scale. The audience is small next to any mainstream browser, so even complete coverage of your trade area here is a modest number of people. This is a supplement to a media plan and not a channel a store can build one on.

The third is intent. When users receive a rewards balance for viewing advertising, some share of the attention you buy is attention paid to the reward rather than to your offer. Judge the traffic that arrives on your site, not the interaction counts reported upstream.

Available on request. The published test for that status is that the work is not started and demand decides the order, and nothing on this page stretches it. No adapter file exists in the ad gateway for this platform, and there is no credential block, no authorization URL and no wire up checklist waiting to be finished.

Access class is PARTNER, which is the vendor's gate and not ours. Credentials require an application the vendor reviews before issuing them. On a platform whose whole proposition is restraint about data, that review is not a formality, and it would be a reasonable thing for a vendor in this position to be careful about.

The sequence therefore has two halves and only one of them is ours. We would schedule the engineering, which the request tally on this page decides. Somebody at another company would approve a credential, on a calendar we cannot see. Publishing a date would mean inventing that second half, which is precisely the habit this directory was built to avoid.

A design rather than a description, because none of it runs.

The second row is deliberately thin, and on this platform that thinness is the product working as intended rather than an integration falling short. What comes back is aggregate. A store that needs shopper level reporting from a channel should read that row twice before funding a test here.

A page about an unbuilt platform can still be concrete because networks are not added here as bespoke projects. On a platform that returns aggregate numbers, the operations that carry the weight are deployment and verification: you need to know the campaign went out as specified and that the connection is alive, precisely because the reporting will not tell you much afterwards.

One provider agnostic library inside the CRM 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, answered identically by every one of them.

Twenty networks are registered against that contract and exactly one is implemented. The nineteen that are not return a refusal naming themselves, so a stray call fails readably instead of looking like an outage at the vendor. Brave is not among the twenty, which is a smaller and more honest claim than registered, and it is the claim the directory makes about eighty of the hundred platforms it lists.

Underneath the adapters is infrastructure that already exists and would not be rebuilt for a new network. Credentials are encrypted before storage with 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 deliberately, because those tables are shared across dealerships and a timezone relative timestamp cannot be reconciled later. Campaign objects record which credentials created them and re resolve those credentials afterwards, so a disconnected account does not orphan the work built under it.

Two routes, and the store picks. The first is the webXintel Ads Network: included, built and operated by our team from the selections you make in Leads Manager, arriving as one line rather than a stack of platform invoices. That path is live and nothing on this page gates it.

The second is your own account. Where a network is built, you connect the account your store already holds, campaigns route through it, and the billing, the naming and the spend history stay yours. Disconnect and delivery falls back to the managed path.

Neither route reaches Brave today. There is a further point worth making on this platform, because it cuts against our own interest. If your reason for wanting this channel is that you suspect a segment of your market is invisible to your current advertising, the cheapest way to test that suspicion is not an integration at all. It is a small direct buy and a look at what arrives on your website. An integration would make the spend easier to compare against everything else you run. It would not make the channel work better.

The limit that applies across the entire gateway, stated on every page here: pushing, pausing and reading numbers from a network is done by our team, not from your dashboard. That is a deliberate constraint while the connection layer is young, and it is on the list to open up.

Two tracks. The vendor track is an application and a review before a credential exists. Our track is an adapter file against the seven operation contract, a credential block, and each of the seven operations wired and checked against a live account. Ours is ordinary scheduled work. Theirs runs on a calendar we do not control.

The design question worth resolving before any of that is what the reporting operation should even return here. Every other network in the gateway hands back numbers detailed enough to compare campaigns. This one hands back aggregate delivery, and an honest implementation surfaces exactly that rather than dressing it up to match the others. A dashboard that made this channel look as measurable as search would be lying by layout.

On measurement in practice, use your own website as the instrument. A distinct landing destination and a count of the sessions that arrive on it, watched against the cost of the buy, is the workable method here. Decide before the campaign runs what such a session is worth. That is a statement about how to read this channel, not a forecast of traffic or of anything it closes at, and on a privacy first platform nobody can honestly offer one.

The gaps below are the ones that bite here specifically, and on this platform several of them are the vendor's design rather than our shortfall.

We do not install or manage a tracking pixel. This is worth stating twice on a page about a browser built to block them. Site side measurement on your website is whatever you already had, and a large share of this audience will block it anyway.

We do not run a server side conversions endpoint or an offline conversion upload. Neither exists anywhere in our stack, so any claim that a campaign here produced a sale would rest on a mechanism we do not operate.

We do not upload a hashed audience or a customer list. No export turns your database into a targeting segment on this or any network, and retargeting your own visitors here is not something we enable.

We do not retrieve leads from this platform. Lead form retrieval is implemented for exactly one network and this is not it. Traffic here lands on your own site and your own forms.

We do not emit a vehicle catalog. No unit level feed goes to any advertising platform from us, so creative here is your store rather than individual stock.

No campaign has ever been deployed to Brave from the CRM, because there is no code that could do it.

Ask, with your store attached, and say what you expect this channel to prove. The useful version of that sentence is usually a suspicion: that a professional, higher income slice of your market never sees your advertising, and that you would like to find out cheaply whether that is true. That is a good reason to test a channel and it is a better brief than a budget with no question attached.

Requests are recorded against the platform they name, and the tally is what decides build order, because a request from a store ready to spend is a better input than any internal roadmap discussion. You will hear back from a person with a range or a reason.

Expect the reply to warn you about reporting before anything else, since a store that needs shopper level attribution will not enjoy this platform whatever we build. The managed path runs today regardless, and pricing for the platform is on the pricing page.

Does LeadLocate integrate with Brave Ads today?

No. The status is available on request, whose published test is that the work is not started and demand decides the order. There is no adapter file, credential block or wire up checklist for this platform in the ad gateway.

Can I use my own Brave advertising account?

Not through the CRM, because nothing exists to reach it. You can buy directly from the vendor, and on this platform that is a reasonable way to test the channel cheaply. An integration would put the spend beside your other channels rather than in a separate login.

What happens if I request Brave Ads?

It is recorded against this platform specifically and counted, and the tally is the input to build order. A person replies with a range or a reason, and the reason will note that credentials need a vendor reviewed application, which is a step outside our control.

Why would a dealership advertise in a browser that blocks ads?

Because the people using it are unreachable everywhere else and they tend to be good buyers: higher income, technically literate, early in strong careers. The ads they see are ones they agreed to receive, which is a different reception from an interruption they did not.

How well can this channel be measured?

Less well than anything else in the directory, and that is the product working as designed rather than a gap in our stack. Matching happens on the device and reporting comes back aggregate. Use a distinct landing destination on your own site and judge the sessions that arrive.

Can I retarget people who visited my website here?

No. We do not upload audiences or customer lists to any advertising platform, and this particular audience blocks the conventional mechanisms in any case. Targeting here is contextual and geographic rather than built from your own visitors.

Requests are counted against the platform they name and the tally decides build order. Tell us your store and what you suspect your current channels are missing.