StackAdapt Integration for Car Dealers

Native, display, connected TV and audio from one console, and a plain account of where that sits with our ad gateway.

StackAdapt is a buying platform that put four things a store would otherwise buy from four vendors into one console: native placements, ordinary display, connected TV and streaming audio. The pitch is consolidation. One audience definition, one budget, one set of reports, and a frequency view across all of it rather than four platforms each certain they showed the household one impression.

What sets it apart from the enterprise platforms in the same family is the interface. It was built to be operated by a marketer rather than by a trained programmatic buyer, which is why it spread through mid market agencies quickly, including the ones that serve dealer groups. If your marketing is handled by a regional agency with a handful of automotive clients, this is one of the platforms most likely to be sitting behind the display line on your invoice.

For a dealership the practical read is that it is a plausible single home for everything above search and social: the awareness layer, the retargeting layer and the video layer, without three separate contracts.

The case is operational rather than exotic. Running native, display, video and audio through one platform means one pacing decision, one creative library and one place to answer the question of how often a household in your trade area saw anything at all. For a store spending steadily every month, the reporting coherence is worth more than a marginal difference in media cost, because it is the difference between managing a budget and receiving reports about one.

The honest objection is that breadth invites dilution. Four channels available in one console tempts a store into running all four on a budget that would only have read clearly in one. Split a modest monthly spend across native, display, connected TV and audio in a single metro and every line is too thin to interpret, so the platform ends up proving nothing and getting blamed for it. Consolidation is a good reason to buy a platform and a bad reason to buy four channels.

The second objection is access. This is a seat product with a commercial arrangement behind it, so most single rooftops reach it through an agency and pay a management layer for the privilege. That layer may be worth it, but it should be priced honestly against running one channel well inside a system that already works your leads, which is the argument for keeping media next to the CRM.

Available on request. The published test for that status is not started, with demand deciding the order, and it applies here without qualification: there is no adapter file for this platform in the ad gateway, no authorization URL and no checklist.

Access class is CERTIFIED, which describes the vendor's requirement rather than ours. API access follows a contract, a certification or an agreed spend commitment, so credentials arrive at the end of a commercial process. That is not a criticism of the platform. It is normal for buying tools whose customers are agencies, and it is the reason a store cannot simply sign up on a Sunday the way it can with a public network.

Publishing both facts side by side is the point of the directory. Plenty of vendors show a logo for this platform on an integrations page and let a dealer assume the rest. We would rather write that we have not built it, name what would have to happen, and let the request tally decide whether it moves. A page that says less than the truth is worth less than no page.

A design, written down so it can be argued with. None of it is running.

Lead capture would be a clickout on every one of those four channels. Nothing collects a form inside the placement, so the shopper lands on your website and your website is what decides whether you have a contactable person.

The reason a not started platform can be estimated at all is that every network in the gateway answers the same contract.

There is one library inside LeadLocate defining what an 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. A platform at not started is a platform whose file has not been written, which is a smaller statement than it sounds and an honest one.

The surrounding machinery is shared and finished. Credentials are encrypted before storage using AES-256-GCM. Every action taken against a network is written to an append only audit log carrying the company, the network, the user and the detail, stamped in UTC because the table is shared across dealerships and a local timestamp cannot be reconciled afterwards. Campaign objects record which credentials created them and re-resolve those credentials later, so disconnecting an account does not orphan what was built under it. None of that would be rebuilt for a multichannel platform.

Two ways to advertise through LeadLocate, and the choice belongs to the store.

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. Nothing to contract for, nothing to certify.

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. On a seat based platform that route depends on somebody holding the seat, and if that somebody is your agency then what you are really asking for is visibility into a buy you do not control. That is a fair thing to want and it is a different project from an adapter.

One limit stated plainly, because it is true across the gateway: pushing, pausing and reading numbers from a network is done by our team today rather than from your dashboard. It is a deliberate constraint while the connection layer is young, and it is on the list to open up.

The order runs commercial first, engineering second. Agree the seat or the certification with the vendor. Obtain API credentials under it. Then write the adapter, implement the credential exchange, implement account listing, implement campaign creation across the channel types, implement status changes, implement reporting and implement verification.

Only the second half is ours to schedule, and pretending otherwise is how integration timelines become fiction. A request for this platform is most useful when it tells us which half you are already holding.

On measurement, the four channels do not read at the same speed and that catches stores out. Display retargeting produces visible traffic quickly. Native produces cheap clicks that need qualifying. Connected TV and audio influence a household days before the visit and cannot be judged against next day form fills at all. A single report averaging all four is a report that hides its own best channel. If audio is the part you actually want, the standalone case is on streaming audio ads for dealers, and it is worth reading before spreading a budget across everything at once.

A multichannel platform makes a long list of tempting claims available. Here is what is not true of us.

We do not install or manage a conversion pixel on your website. Retargeting and conversion reporting on this platform run from a tag, and we neither place nor maintain one for any network.

We do not export a hashed audience or match your customer database against the platform's users. No file of that kind is produced anywhere in the product.

We do not emit a vehicle catalog, so dynamic retargeting creative rendering the exact unit a shopper viewed is not something we deliver. That is a feed capability and no feed is generated to any advertising platform.

We do not run a server side conversions API or upload offline conversions. Sold units do not travel back to the platform from us to train its bidding.

No campaign has ever been deployed to this platform from the CRM, because no adapter exists that could deploy one. If a competitor's logo grid suggests otherwise about their own product, the fair question is which of the seven operations they have implemented and when the last verified call ran.

Ask, with the store named. Requests are recorded against the platform they name and counted, and the count is the input to build order, because a dealership ready to spend on a channel is a stronger signal than a roadmap discussion nobody outside the building can see.

Two things sharpen a request here. Say which of the four channels you actually want, since a request for connected TV and a request for native retargeting are different pieces of work behind the same logo. And say whether you or your agency holds the seat, because on a certified platform that relationship is the gate, and a request that already clears it counts for more than one that would need us to solve the commercial side as well.

The managed path runs today regardless. Pricing for the platform is on the pricing page and does not change based on which networks you turn on.

Does LeadLocate integrate with StackAdapt today?

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

Can I use my own StackAdapt seat?

Not through the CRM, because there is nothing yet to connect it to. If you or your agency already holds a seat, say so when you request, since that removes the slowest step from the project.

What happens if I request StackAdapt?

It is recorded against this platform by name and counted, and the tally decides build order. You will get an answer from a person with a range or a reason, and a note on which channel you should start with.

Should I run all four channels at once?

Usually not at a single rooftop budget. Four thin lines in one metro produce four unreadable results. Pick the channel that matches the job, prove it, then widen with money the first channel earned.

Can you retarget my website visitors with the exact vehicle they viewed?

No. That requires both a tag we do not manage and a product feed we do not emit. Neither exists in our stack for this platform or any other, and finishing an adapter would not create them.

My agency already buys through it. What would an integration add?

Record keeping and a single place where campaign actions are logged, not cheaper media. If the real problem is that you cannot see what the agency is doing, say that when you request, because it is a different problem with a different fix.

Requests are counted against the platform they name and the count decides what gets built next. Tell us which channel you want first and whether a seat already exists.