Run El Toro from Your Dealership CRM

Household level advertising aimed at named addresses, and the one step in it we do not perform.

El Toro sells household level display advertising matched by internet address rather than by cookie or device identifier. The mechanism is simple to describe. An advertiser supplies a list of physical street addresses. The vendor resolves each address to the internet connection serving that home. Advertising is then delivered only to devices using that connection.

The consequence is that this is not audience targeting in the sense the rest of this catalogue means it. There is no interest segment, no lookalike model and no browsing signal. There is a list of houses, and the advertising goes to those houses. That is why the product survives the decay of third party identifiers that is reshaping everything else in programmatic display, and it is also why the product is worth exactly as much as the list handed to it.

For a dealership the obvious application is the owner base. Customers approaching the end of a lease, owners of a model your used department is short of, households in a conquest zip code, service customers who have not been back. All of those are lists a store can describe, and the pitch is that advertising can be aimed at them directly rather than at people who resemble them.

The case is precision against a known target. A store already knows a great deal about who it wants to reach: the equity position of its own owner base, which lease terms mature next quarter, which trade cycle is due. Every other advertising channel in this directory asks a store to approximate that knowledge with a segment. This one asks for the addresses. When it works, the waste that comes from targeting a category instead of a person disappears, and household level delivery pairs naturally with the equity data a dealership already keeps in its CRM.

The honest objection has three parts and a store should hear all of them before it spends anything.

First, an internet connection is a household, not a person, and often not even that. Apartment buildings, shared connections and carrier level address translation mean one address can front many homes, while a home's address can change without notice. Match rates and accuracy figures in this category are produced by the vendor selling the media, and there is no independent audit a dealership can consult. Ask what the match rate was on your specific list, in writing, and treat a refusal as an answer.

Second, the outcome measurement has the same problem. A vendor that matched the households also grades whether those households later bought, which is a closed loop with nobody outside it.

Third, and most important for the rest of this page, the whole product begins with a dealership handing over a list of its own customers or a list of households it has identified. That is a decision with legal and reputational weight, it should be made deliberately with your own counsel, and it is not a step we perform on your behalf.

Available on request. The published test for that status is that the work is not started and demand decides the order, and this page does not stretch 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 behind the scenes.

Access class is PARTNER, which is the vendor's gate rather than ours. Credentials require an application the vendor reviews before issuing them. On a platform built around address level matching, a careful review of who gets programmatic access is the sane position for a vendor to take, and it is not one we would expect or want to shortcut.

So the sequence has two halves and only one is ours. We would schedule the engineering, and the request tally on this page is what decides that. Somebody else would approve a credential, on a calendar we do not see. There is also a third fact, and it does not depend on either half: even with a finished adapter and an approved credential, the audience list at the centre of this product is not something our stack produces. That is covered plainly further down, because it is the part a sales conversation would be most tempted to blur.

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

On every other page in this directory the last row is a limitation. Here it is the product. Household targeting is defined by the list, and the list is precisely what does not leave the CRM through us. A dealership that wants to run this tactic supplies that list to the vendor itself, under its own agreement and its own legal advice.

A page about an unbuilt platform can be specific because networks are not added here as bespoke projects. It is also worth noticing which of the seven operations in our contract does not include anything resembling an audience upload, because that omission is deliberate rather than pending.

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 the same way by all of them. Nothing in that list moves a customer record outward, on any network, and no eighth operation is scoped that would.

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 resembling an outage at the vendor. El Toro is not among the twenty, which is a smaller and more honest claim than registered, and the directory is built so that distinction is visible on every entry.

Underneath sits infrastructure that already exists and would not be rebuilt. 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 afterwards. Campaign objects record which credentials created them and re resolve those credentials later, 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 El Toro today, and on this platform the more useful point is about the relationship rather than the software. A store running household targeting has a direct agreement with the vendor covering how a list is supplied, what it may be used for and how long it is retained. Those are terms a dealership should own, read and be able to produce when somebody asks. An integration would put the resulting spend and delivery beside your other channels for comparison. It would not, and should not, put us in the middle of that agreement.

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 operation wired and checked against a live account. Ours is ordinary scheduled work. Theirs is not on our calendar. Neither track includes building an audience export, because that is not a thing we intend to build quietly as a side effect of connecting a network.

On measurement, this category is slower to read than it is sold as. Display delivered to a household produces no click from most of the households that see it, which is the normal behaviour of display advertising and not a fault. The instrument that works is your own traffic and your own showroom: a distinct landing destination, sessions arriving on it, and whether the specific owners you aimed at came back over the following weeks.

Decide the window before the campaign runs, because the vendor's own attribution will offer you a shorter and friendlier one. None of this forecasts how many households will respond or what any of it will close at, and on a channel this dependent on list quality nobody honest will offer that number.

This is the section that matters most on this platform, because the gap and the product are the same shape.

We do not export a customer list, and we do not upload a hashed audience. There is no code anywhere in our stack that turns your owner base, your equity records, your service history or your lead database into an audience file for any advertising platform. Household targeting depends on exactly that file. If you want this tactic, you supply the list to the vendor directly, under your own agreement. We will not describe that step as something the integration handles, now or after an adapter exists.

We do not resolve addresses, households or connections. No part of our stack performs any matching of that kind.

We do not run a server side conversions endpoint or an offline conversion upload. Those are the mechanisms a household targeting vendor would use to argue that an impression produced a sale, and we operate neither.

We do not install or manage a tracking pixel. Site side measurement is whatever you already had.

We do not retrieve leads from this platform. Lead form retrieval is implemented for exactly one network and this is not it, and a display impression collects no opt in in any case.

We do not emit a vehicle catalog. No unit level feed goes to any advertising platform from us.

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

Ask, with your store attached, and say which list you have in mind. That question is the whole conversation on this platform. A defined group of your own lease maturities is a different proposition, commercially and legally, from a purchased list of households in a zip code, and a store should know which one it is buying before the first impression is served.

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 an internal roadmap discussion. You will hear back from a person with a range or a reason.

Expect that reply to be direct about the audience limit above rather than hopeful about it, and to suggest you involve your own counsel on how a list may be used. The managed path runs today regardless, and pricing for the platform is on the pricing page.

Does LeadLocate integrate with El Toro 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 El Toro account?

Not through the CRM, because nothing exists to reach it. Stores running this tactic hold a direct agreement with the vendor covering how a list is supplied and used, and that agreement is one your group should own rather than one we should sit inside.

What happens if I request El Toro?

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 on this platform the reply will also be clear that connecting the network would not create the audience export the tactic depends on.

Can you send my customer list or equity data to this platform for me?

No. We do not export a customer list and we do not upload a hashed audience to any advertising platform. No code in our stack produces such a file. Supplying a list is something a dealership does directly with the vendor, under its own agreement and its own legal advice.

How accurate is address to household matching?

That is the right question and the honest answer is that the figures available come from the vendors selling the media, with no independent audit for a dealership to check. Connections are shared, addresses change, and one internet address can front many homes. Ask for the match rate on your specific list in writing.

How would I know a household campaign worked?

Slowly, and preferably on your own instruments. Display to a household rarely produces a click, so the workable read is a distinct landing destination, the sessions arriving on it, and whether the owners you aimed at came back over the following weeks. Set that window before the campaign runs.

The list is the whole conversation on this platform, and it is the one step we do not perform. Requests are counted against the platform they name and the tally decides build order.