Yahoo DSP Integration for Car Dealers

Native placements, connected TV and a logged in identity graph, with a plain answer about where it sits in our ad gateway.

Yahoo DSP is a buying platform sitting on top of one of the last large logged in audiences on the open internet. Mail, Finance, Sports and News still draw a signed in readership at scale, and that sign in is what makes the platform interesting: the audience is identified by a real account rather than inferred from a cookie that may not survive the week.

Three formats matter to a store. Native placements, which render inside an article or a mail feed and read as content rather than as a banner. Connected TV, bought against the same identity rather than as a separate silo. And ordinary display, which is the cheap volume underneath both.

The audience skew is worth saying rather than dancing around. This is an older, more settled readership than a short video app reaches, and in automotive that is frequently the point. Households in the market for a full size truck, a three row crossover or a certified pre owned sedan are not the same households a teenager scrolls next to, and a platform whose logged in base is weighted that way is a targeting advantage rather than an apology.

The case is identity plus local reach at a price that is not being bid up by every other advertiser in the country. Because the audience is signed in, a household can be reached across desktop, mobile and a television screen with the frequency understood as one person rather than three cookies, and mid size groups covering several rooftops in one metro get useful coverage without buying national scale they cannot use.

The honest objection is native inventory quality and what a click on it is worth. A native placement earns attention by resembling the page it sits on, which means some of the traffic it produces is a mis click and some of it is idle curiosity rather than intent. A store measuring this channel by raw clicks will be pleased and then confused. Measured by contactable shoppers arriving on the website, it is a more ordinary channel that has to be worked like any other.

The second objection is commercial. This platform's account structure tilts toward managed service and negotiated commitments, so a store cannot simply put down a card and start, and the layer of service between you and the buy is a cost you should price before you compare it against a self serve network like Meta.

Available on request, and that phrase carries a published test rather than a hint: not started, with demand deciding the order. No adapter file exists in the ad gateway for this platform, so there is nothing partial to describe and nothing to overstate.

Access class is CERTIFIED, which is the vendor's gate and not ours. API access here follows a contract, a certification or an agreed spend commitment, which means credentials are the end of a commercial conversation rather than the beginning of a technical one. That step is outside our control entirely, and a store that already has a relationship with this vendor is holding the part we cannot supply.

It is worth separating the two axes deliberately, because vendors blur them. Status describes what is in our code. Access class describes what the platform requires of anyone at all. A network can be wide open and unbuilt, or contract gated and unbuilt, and those are different sentences with different fixes. This one is the second kind.

Written as a design. None of it exists yet.

Lead capture would be a clickout. There is no form living inside the placement, so the shopper reaches your website and your website decides whether a contactable person exists at the end of it.

Not started means one file has not been written. It does not mean the surrounding work is unclear.

LeadLocate carries one library defining 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. Because every network answers the same seven, adding one is bounded work rather than a discovery project, and turning one on cannot disturb the network already running.

What surrounds that file is already built. 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 same credentials later, so an account disconnected next quarter does not leave campaigns nobody can reach. On a page about a platform we have not touched, that is the part worth knowing: the expensive foundations are not what would be missing.

Two ways to advertise through LeadLocate, and you choose which.

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 contract to negotiate with a third party and no certification to clear.

The second is your own account, which is what this directory is about. Connect the advertising account your store already holds and campaigns route through it instead, on your billing, in your name, with your spend history intact. Most vendors will not offer that second option because it costs them the margin on your media. On a certified platform the option still depends on you holding the contract, which is why an honest page says so rather than implying the choice is free.

One limit applies across the whole gateway and is stated here rather than discovered later: pushing, pausing and reading numbers from a network is done by our team today, not from your dashboard. That constraint is deliberate while the connection layer is young.

Two commercial steps first, then seven engineering ones. Reach an agreement with the vendor, since a certified platform issues keys against a contract or a spend commitment. Obtain credentials under that agreement. Then the adapter file, the credential exchange, seat listing, campaign creation, status changes, reporting and verification.

Nothing in the second list is unusual. Everything in the first list is out of our hands, and it is the reason a request for a certified platform gets a different answer from a request for a public one. We would rather set that expectation now than let it arrive as a surprise after somebody has budgeted for a launch date.

On proof, native and connected TV are patient channels. The value shows up as more people arriving at your website and more people walking in already knowing the name of the store, which is real and is not visible by Friday. Judge it across a flight, keep the follow up on whatever it does produce immediate, and do not let a slow reading channel sit next to a fast one in the same weekly report without a note explaining why the numbers cannot be compared. The wider version of that argument is on car dealership advertising.

The identity story on this platform is exactly the place a vendor page would overreach, so here is the boundary.

We do not onboard your customer list to any identity graph, and we export no hashed audience of any kind. Matching your database against a logged in audience is a real capability of this platform and nothing in our product produces the file it would require.

We do not place or manage a tracking tag on your website. Conversion measurement for a clickout buy depends on tagging that we neither install nor maintain.

We do not run a server side conversions API and we do not upload offline conversions, so sold units and showroom visits are not returned to the platform for optimisation by us.

We do not emit a vehicle catalog, so dynamic creative showing your actual units is not something we deliver on this platform or any other in the gateway.

No campaign has ever been deployed to this platform from the CRM, because no adapter exists that could deploy one. Everything above describes a design, and the page says so on purpose.

Ask for it with your store attached. Requests are recorded against the platform they name and counted, and the tally is what decides build order, because a dealership ready to spend on a channel is a better input than an internal roadmap meeting.

One detail is worth including. Say whether you already work with this vendor, directly or through an agency, because a certified platform is gated by that relationship and a request backed by existing access is a materially shorter project than one that is not. If several stores in a group ask together, say that too, since a group is the unit that usually clears a spend commitment.

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

Does LeadLocate integrate with Yahoo DSP today?

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

Can I use my own Yahoo DSP seat?

Not through the CRM, since there is nothing to connect it to yet. Holding a seat already does change the queue maths, because it removes the commercial step that usually takes longer than the code.

What happens if I request Yahoo DSP?

It is recorded against this platform by name and counted, and the tally decides build order. A person replies with a range or a reason, and if the blocker is the vendor contract rather than our engineering, that is what you will be told.

Can you target my existing customers using their email addresses?

No. We do not onboard a customer list to this platform's identity graph and we produce no hashed audience file for any network. That capability does not exist in the product.

Is native traffic worth paying for at a car store?

It is cheap and it is not all intent. Some of a native click through is curiosity and some is a mis tap, so judge the channel by contactable shoppers rather than by click volume, and expect to work them like any other cold arrival.

Does a certified access class mean it will never be built?

No. It means the vendor requires a contract, certification or spend commitment before issuing API access, so the request queue and the commercial gate move on separate tracks. Demand still decides our order of work.

Requests are counted against the platform they name and the count decides what gets built next. Tell us whether you already work with this vendor and what you would run first.