RichAds Integration for Car Dealers

Push subscriber traffic at low minimums, why placement filtering is mandatory, and where our ad gateway stands with it.

RichAds is a self serve network selling push notification traffic, in-page push and a native format alongside it. Its core inventory is subscriber based: people who once accepted a notification prompt on some website and now receive messages from it, delivered to a phone or a desktop where personal messages also arrive. Advertiser access is self serve, campaign moderation is quick, and minimums are low enough that a store can test without a procurement conversation.

What a dealership is buying is speed and cost per click. Approval usually lands in hours rather than days, and delivery starts as soon as it does, which makes this one of the few channels in the directory that can be stood up between a Tuesday decision and a Saturday event.

The format deserves a plain description rather than a flattering one. A push ad looks like a notification because it is one, and the person receiving it did not ask for your store specifically. That is precisely why it earns attention, and precisely why it needs handling.

The caveat leads, because in this category it is the substance rather than the fine print. This is a click volume channel, not a lead quality channel. Placement filtering is not optional here, it is the job: subscriber lists vary wildly in quality, some sources deliver far more accidental taps than genuine interest, and a campaign left unfiltered will find the cheapest supply available and spend the whole budget there. A store buying this traffic needs somebody prepared to read source level reports and cut ruthlessly, several times a week, for the life of the campaign.

Given that, the honest use case is event promotion where cost per click is the only metric anyone is claiming. A weekend sale, a clearance, a service drive push, a grand opening: things with a date, a simple message and a need to reach a very large number of people inside a defined area for very little money. On that scoreboard this network competes with anything.

What it will not do is deliver shoppers with intent. Nobody receiving a notification was looking for a vehicle at that moment, so the traffic arrives colder than any other paid channel in this directory, colder even than the other categories that sell attention rather than intent. A store that sets expectations correctly can use it well. A store that quietly hopes for something warmer will conclude the network is broken when the mismatch was in the plan. Our page on what to expect from car sales leads is the longer form of that argument.

Available on request, and the published test for that status is that work has not started. No adapter file for this platform sits in the ad gateway. No credential block, no authorization URL, no wire-up checklist, nothing partially written.

Access class is PUBLIC, which describes the vendor's gate and not ours. Advertiser API access here is self serve, so there is no application, no review and no external party whose timeline could be blamed for the status above. The only variable is our engineering time and where this network ranks in the request tally.

We would rather publish that than list a logo with no word beside it. A logo on an integrations page reads as a working connection to every dealer who sees it, and almost nobody ever asks the vendor to prove it. The index carries the same test on all one hundred entries, and exactly one of them currently describes a live connection.

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

Source level delivery is the row that makes this channel operable. Without it the exclusions cannot be built, and without exclusions the rest of the design is decoration.

Nothing here is a special case, which is the entire reason for a gateway.

One provider agnostic library inside LeadLocate defines what any advertising platform must be able to do: hand us an authorization URL, exchange the code for a token, list the accounts you own, 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. Adding a platform means filling in that file, and a network that authenticates with a token rather than a full authorization flow makes the first operations short without changing the contract.

The shared parts already exist and do not get rebuilt per network. Credentials are encrypted before storage with AES-256-GCM. Every action taken against any network lands in an append only audit log carrying the company, the network, the user and the detail, stamped in UTC deliberately, because these tables are shared across dealerships and a local timestamp is one nobody can reconcile afterwards. Campaign objects record the credentials that created them and re-resolve those same credentials later, so a store that disconnects an account does not strand the work built underneath it.

Twenty networks are registered against that contract. One is implemented. Every other adapter answers each lifecycle call with a refusal that names the network, so a stray call anywhere in the CRM fails readably rather than looking like a vendor outage.

Two ways to advertise through LeadLocate. The first is the webXintel Ads Network: included, nothing to register, our team building campaigns from the selections you make in Leads Manager, and one line on the invoice rather than a pile of platform bills. It is available today and does not depend on anything described on this page.

The second is your own advertiser account. Where an adapter exists, you authorize once and campaigns route through your account, on your billing, in your name, with your spend history intact. RichAds has no adapter, so that path is closed here and anything a store buys on this network today happens outside our stack, with no entry in your audit log.

One constraint said plainly: pushing, pausing and reading spend from a network is done by our team rather than from your dashboard. It is a deliberate limit while the connection layer is young, and on a channel that approves quickly and delivers immediately, a human confirmation before anything spends is worth more than the convenience it costs.

Four steps and no waiting room. Register the advertiser account and generate an API token. Add the credential block and write the adapter against the seven operations. Implement campaign creation, source level reporting and exclusion management, which is the part with real design in it, because on subscriber traffic the exclusion list is the campaign. Then verification.

Because access is self serve, an estimate here would be honest engineering time rather than a guess about somebody else's review queue. Whether that time gets scheduled is a demand question, and the request tally is how demand gets expressed.

Measurement is fast at the top and slow underneath. Clicks arrive within hours of approval and prove that delivery is working. Everything worth knowing comes later: which sources produced visits that lasted, which creative earned a second page, and whether any of it produced a conversation at the store. Give that a week at minimum, keep the same day numbers in their proper place, and treat any vendor who quotes you a same day click count as a result with appropriate suspicion.

The gaps, by name, including the ones peculiar to a subscriber traffic network.

We do not emit a vehicle catalog to any advertising platform. No inventory feed leaves our stack toward an ad network. Inventory Link ingests your feed and merchandises your units on properties you own, which is a different job with a similar sounding name.

We do not install or manage pixels and we operate no server side conversions API. On push traffic the conversion signal is what separates a source worth keeping from a source that produces reflex taps, and we do not supply that signal. No offline conversion upload either, so a closed deal never travels back.

We export no hashed audience, and we build no subscriber or retargeting pool from your customer list.

There is no on platform lead form to retrieve, so every lead would arrive through a page you control, and our form retrieval was written for a single network. We have automated no part of placement filtering, which on this network is the difference between a defensible campaign and an embarrassing one. No campaign has ever been deployed from the CRM to RichAds.

Ask, and say what you are promoting. Requests are recorded against the platform they name and counted, and the tally decides build order, because a dealership ready to spend on a channel is a stronger signal than any internal ranking of which network looks interesting.

The reply will probably ask two things back. What is the date you are driving toward, and who at the store is going to read the source reports. If the answer to the second is nobody, the honest recommendation is a channel that does not require that discipline, and a tighter geofenced buy around your trade area usually fits better. Meanwhile the managed path is available now and waits on none of this.

Platform pricing is on the pricing page and does not vary with which networks are enabled.

Does LeadLocate integrate with RichAds today?

No. It is available on request, which here means work has not started: no adapter file, no credential block, no checklist. Vendor access is self serve, so the only obstacle is queue position.

Can I use my own RichAds advertiser account?

Not through the CRM, because there is nothing to authorize against. Registering directly is quick, and anything run that way sits outside our stack with no entry in your audit log.

What happens if I request RichAds?

It is logged against this network by name and counted, and the count feeds build order. With no vendor application to clear, the answer is about scheduling rather than about somebody else's approval.

Why is placement filtering described as mandatory?

Because subscriber list quality varies enormously and an unfiltered campaign drifts toward the cheapest sources, which are cheap for a reason. Somebody has to read source reports and cut, repeatedly, for the life of the campaign.

What should a store realistically expect from push traffic?

Cheap clicks quickly, and cold ones. Nobody receiving a notification was shopping for a vehicle at that moment, so buy it for event awareness and click volume and judge it on cost per click alone.

Could this be set up before a weekend sale?

On the network itself, yes, since approval is fast and minimums are low. Not through us, because no adapter exists. That distinction matters, and blurring it is exactly what this directory was built to stop.

Requests are counted against the platform they name. Tell us the event, the radius and who will watch the source reports, and you will get a straight answer about whether this is the right buy.