Basis Technologies Integration for Car Dealers

The planning, buying and billing console agencies run dealer media through, and where it stands with our ad gateway.

Most platforms in this family buy media. This one runs an advertising business. Basis combines programmatic buying with the work that surrounds it: media planning, insertion orders, direct publisher buys, reconciliation, billing and the internal workflow that keeps a team of buyers from losing track of what was promised to whom.

That is why a dealership rarely encounters the name directly. It is an operating system for agencies, and the agencies that use it tend to put everything through it, including the search, social and direct site buys that were never programmatic in the first place. If a regional agency handles your store's media, this may well be where your plan lives, where your invoice is generated and where somebody reconciles what was ordered against what actually delivered.

The practical consequence for a store is that the platform's most valuable output is not an impression. It is a defensible record of what was bought, at what price, on whose authority. That is a different thing from a buying console, and it changes what an integration would even be for.

The honest case is not that a store should buy this platform. Very few dealerships should. The case is that a store benefiting from it is usually doing so through an agency, and the benefit is discipline: a plan that exists as a document, orders that match the plan, delivery reconciled against the orders and an invoice that can be traced back to all three. Anyone who has argued with a media vendor about an under delivering month understands why that record matters.

The honest objection is ownership of the value. The workflow serves the buyer, not the advertiser. A single rooftop paying for a seat in an agency operating system is paying for a system designed around managing many clients, and the store is one of them. The reporting a dealership actually wants, which is what happened to the money and did it produce anybody worth calling, is a small slice of what the platform does.

The second objection is duplication. If your agency runs this and you run a CRM, the interesting gap is between the media record and the lead record, and that gap is not closed by adding a second console. It is closed by the follow up discipline described on what to expect from car sales leads, which is where most of the leaked value in dealer media actually goes.

Available on request, and the test published beside that status is that nothing has been started and demand decides the order. There is no adapter file for this platform in the ad gateway. No authorization URL, no checklist, no partial implementation to characterise generously.

Access class is CERTIFIED, which is the vendor's requirement and not ours. API access follows a contract, a certification or a spend commitment, which on a platform sold to agencies means the credential belongs to an agency relationship rather than to a store. A dealership asking for this connection is usually asking us to reach into a system somebody else pays for, and that is a permissions conversation before it is an engineering one.

Saying that plainly costs us nothing and saves a dealer a wasted month. The alternative, which is the industry norm, is a logo on an integrations page that lets everyone assume a connection exists. Every entry in this directory carries a status with a stated test precisely so that assumption is never available.

Design only. None of this exists in code.

The invoice row is specific to this platform and it is deliberate. The most requested thing a billing aware system suggests is financial reconciliation, and that is not what an advertising adapter does.

Every network in the gateway answers one contract, which is what makes a not started platform a bounded question rather than an open one.

LeadLocate carries a single library defining what an advertising platform must 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. Notice what is absent from that list. There is no operation for a media plan, an insertion order or an invoice, because the contract was written for buying platforms. A workflow system exposes far more than seven things, and only some of them map.

The shared machinery around the file is finished and is not rebuilt per 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. Campaign objects record which credentials created them and re-resolve those credentials afterwards, so disconnecting an account does not strand what was built under it. Our own record of who did what is strong. It is simply not an accounting system.

Two ways to advertise through LeadLocate, and the store picks.

The first is the webXintel Ads Network. It is included, our team builds and runs the campaigns from the selections you make in Leads Manager, and it arrives as one line rather than a stack of platform invoices. No agency seat, no contract with a third party, no certification to clear.

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 history intact. For an agency operating system that route is unusual, because the account is normally the agency's rather than the store's. If your goal is to see what your agency is doing rather than to buy media yourself, tell us that in those words, because it is a different request and it deserves a different answer instead of a queue position.

One limit stated plainly, true across the gateway: pushing, pausing and reading numbers from a network is done by our team today, not from your dashboard. That is deliberate while the connection layer is young.

Commercial steps first. Establish the relationship that entitles someone to API credentials, and settle whose relationship it is, since on this platform that is the genuinely hard part. Obtain credentials under it. Then the engineering: the adapter file, the credential exchange, account listing, campaign creation, status changes, reporting and verification.

The middle question is the one most likely to stop this project before code is written. If the credential belongs to an agency, then every campaign created through it is created inside their business record, and the agency has legitimate reasons to control that. We would rather surface that on a public page than discover it in week three.

On measurement, the media bought through a platform like this is mostly display and video, which influence a shopper before the visit rather than in the hour after the impression. Judge it over a flight. The faster reading channels are the ones with a form inside the app, which is why the connected network in this directory is usually the first thing a store turns on and the last thing it turns off.

The gaps that matter here are different from the rest of the family, because the platform does more than buy.

We do not sync media plans, insertion orders or invoices, and we are not an accounting integration. Nothing in our product reconciles ordered against delivered spend or produces a billing record for media bought elsewhere. This is the single most likely thing to be assumed about a connection to a billing aware system, and it is not true.

We do not install or manage a tracking tag on your website, so conversion measurement for anything bought through this platform depends on tagging we neither place nor maintain.

We do not export a hashed audience or onboard your customer list to this or any platform in the gateway.

We do not emit a vehicle catalog, so no dynamic creative renders your live inventory through this route.

We do not run a server side conversions API or upload offline conversions, so sold units are not returned to any platform by us to train bidding.

No campaign has ever been deployed to this platform from the CRM. There is no adapter that could deploy one, and no part of this page describes work in progress.

Ask, with the store attached. 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 better signal than an internal meeting.

Be specific about the outcome you want, because on this platform the name and the goal often diverge. If you want media bought, a buying platform is the shorter path. If you want to see what an agency is doing with your money, say that, since visibility into somebody else's seat is a permissions problem rather than an adapter. If you want your media spend and your lead record in one place, say that too, and read the case for programmatic sitting next to the CRM on programmatic display advertising for dealers first.

The managed path runs today and none of this blocks it. Pricing is on the pricing page and does not change based on which networks you turn on.

Does LeadLocate integrate with Basis Technologies today?

No. There is no adapter file for this platform in the ad gateway, so nothing partial exists. It sits at available on request, which means not started, with demand deciding the order.

Can I use my own Basis account?

Not through the CRM, because there is nothing to connect it to yet. On this platform the account usually belongs to an agency rather than to a store, which is a permissions question before it is an engineering one.

What happens if I request Basis Technologies?

It is recorded against this platform by name and counted, and the tally decides build order. A person answers with a range or a reason, and will say plainly if what you described is better solved another way.

Would this reconcile my media invoices?

No. We do not sync plans, insertion orders or invoices, and nothing in the product compares ordered spend against delivered spend. An advertising adapter is not an accounting integration and we will not describe it as one.

My agency uses it. Can you show me what they are running?

Not today, and even with an adapter it would depend on the agency granting access to their own account. That is their decision to make. Tell us if visibility is the real goal, because it changes what we would build.

Why is this listed at all if a store would rarely buy it?

Because dealers ask, and a directory that only lists the platforms we like is a sales page. Every platform a dealership names gets an entry with the same published test, whether the honest answer flatters us or not.

Requests are counted against the platform they name and the count decides what gets built next. Tell us whether you want media bought, media reconciled, or an agency's work made visible.