MNTN Integration for Dealerships

Television held to digital standards, and the site side dependency that argument quietly rests on.

MNTN sells connected television as a direct response channel. Same screens, same streaming apps, same living rooms as any other television buy, presented and measured as though it were a digital campaign: self serve setup, automated optimization on the platform's side, and reporting built around actions rather than gross rating points.

The pitch to an advertiser is that television no longer has to be the one line on the marketing budget that nobody can defend. Instead of a reach estimate and a hope, the platform reports what happened after the impression and adjusts delivery towards whatever is performing.

For a dealership the appeal is obvious. Most stores have a general manager who will approve anything with a defensible number attached and nothing without one. This category is the same media described on our connected TV advertising page, sold in the vocabulary a dealership already uses for search.

The case is that television becomes arguable. A store can run a streaming campaign, see a report that speaks in visits and actions, and hold the channel to a standard rather than accepting it as brand spend that pays off invisibly. Automated optimization also removes a real operational cost, since most dealerships have nobody whose job is tuning a media buy daily.

The honest objection is that performance connected television rests on a view through window, and a view through window is a policy decision rather than a fact. If somebody sees a spot on Tuesday, visits your website on Friday after a search, and the platform claims the visit inside a multi day window, the report will look excellent and the search campaign will look worse than it is. Nothing dishonest has occurred. Two systems have both counted the same person and only one of them prompted the visit.

The second objection is that the optimization is a black box on the vendor's side. You do not see what it decided or why, which is fine when performance is good and unanswerable when it is not. A dealership should therefore run this the way it would run any channel it cannot inspect: with a fixed budget, a defined test window, and an agreement in advance about which numbers count. That discipline matters more here than on channels where the mechanics are visible, and it applies equally to programmatic display.

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

The access class is PARTNER, which is the vendor's gate and not ours. Credentials require an application the vendor reviews before they are issued. That gate sits in front of everybody, including us, and it is a queue we cannot shorten by writing code faster.

Keeping those two axes separate is deliberate and it is the reason this directory is worth reading. A platform can be entirely open to developers and unbuilt by us, or fully specified in our code and blocked behind a vendor review. Folding the two into a single badge is how integration pages across this industry end up implying connections that do not exist. MNTN is unbuilt and gated, which is stated here rather than smoothed over.

A design rather than a description, because nothing below exists.

The final row carries the whole measurement story on this platform. Performance connected television depends on a site side signal to close the loop, and that signal is not ours. Whatever exists on your website is what the reporting would be built on.

Adding a network here is an adapter file rather than a project, which is the only reason a page about something unbuilt can be specific. 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, answered identically by every network. Twenty are registered against that contract and one is implemented. The nineteen that are not each return a refusal naming themselves, so a stray call anywhere in the CRM fails loudly and readably instead of resembling an outage at the vendor. MNTN is not among the twenty at all.

The plumbing beneath the adapters already exists and no new network rebuilds it. 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 on purpose, because the tables are shared across dealerships and a timezone relative timestamp is one you cannot reconcile later. Campaign objects record which credentials created them and re resolve those same credentials afterwards, so disconnecting an account does not orphan the campaigns built under it. That is unglamorous work and it is what makes an audit question answerable.

Two ways to advertise through LeadLocate, and the dealership picks. The first is the webXintel Ads Network: included, built and operated by our team from the selections you make in Leads Manager, delivered as one line rather than a stack of platform invoices. It is live today and independent of every adapter question raised here.

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 whenever you like and delivery falls back to the managed path.

Neither route reaches MNTN today, and the self connect route waits on a vendor review as well as on our engineering. If your group already holds an approved relationship with the vendor, say so, because that is the half of the sequence we cannot influence.

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

Two tracks and they run in order. 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 verified against a live account. The second track is predictable. The first is not on our calendar.

On measurement, hold the caveat that governs the whole category. Results from streaming television are not reliably attributable inside twenty four hours. A performance report that appears the next morning is showing you an attribution model's opinion, not a settled fact, and the honest way to read it is alongside what your direct channels did over a longer window.

The practical advice for a dealership evaluating a platform like this is to fix three things before spending anything: the length of the view through window, what counts as an action, and whether the campaign will be judged against a period when nothing else changed. A channel judged against a moving baseline will always look like whatever the person reading the report already believed. None of this is a forecast of lead volume or closing rate, and nobody can honestly provide one for television.

The gaps below are the ones that apply to this platform in particular, and on a performance television product the first one is not a detail.

We do not install or manage a pixel. The entire measurement argument for performance connected television depends on a site side tag observing what happened after an impression, and we do not place one, maintain one or verify one. Whatever is on your website came from somewhere else.

We do not run a server side conversions endpoint and we do not upload offline conversions. The showroom outcome never reaches the platform from our side, so nothing the optimizer chases is confirmed by your actual sales.

We do not reconcile attributed visits against CRM records. A reported action would arrive uncontested, because there is no process that matches it to a customer.

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

We do not upload hashed audiences. No customer list becomes a targeting or suppression segment anywhere.

No campaign has ever been deployed to this platform from the CRM, because the code that would do it has not been written.

Ask, with the store attached and with the budget you would commit to a defined test window. Requests are recorded against the platform they name and the tally is what decides build order, because a request from a dealership ready to spend on a channel is a better signal than a roadmap discussion nobody outside the building attended.

Expect the reply to ask about measurement rather than creative. On a performance television product the report is the product, and a store that has agreed in advance what counts as a result will get a straight answer from the channel. A store that has not will get an argument.

The managed path is live today and does not wait on any of this. Pricing for the platform is on the pricing page and does not change based on which networks you turn on.

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

Not through the CRM, because nothing has been built to reach it. The access class is PARTNER, so a credential also depends on an application the vendor reviews. If your group is already approved, tell us, since that clears the step outside our control.

What happens if I request MNTN?

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 ask how you intend to judge the campaign.

Does performance connected TV really work like search?

Commercially it is presented that way. Mechanically it is not. Television reporting depends on a view through window rather than a click, so the same shopper can be claimed by both the streaming campaign and the search campaign that actually prompted the visit.

What does the measurement depend on?

A site side tag observing behaviour after an impression. We do not install, manage or verify one, so the reporting on this platform would be built on whatever your website already carries rather than on anything supplied by us.

How long before a television test can be judged?

Longer than a day. Results are not reliably attributable inside twenty four hours, so fix the test window, the definition of an action and the baseline period in advance, and read the channel against what your direct channels did over the same stretch.

Requests are counted against the platform they name and the tally decides build order. Send your store, a test budget and how you would judge the result.