Amazon Ads and Amazon DSP CRM Integration

Display and Streaming TV bought against first party shopper signal, and exactly where that connection stands with our gateway.

Most people hear Amazon and think of product listings, which is the part of the business a car store cannot use. The part a car store can use is Amazon DSP, a demand side platform that buys display and Streaming TV inventory across Fire TV, Prime Video, Twitch, IMDb, Amazon owned sites and a large pool of third party supply, aimed using what Amazon knows about shopping behaviour.

That distinction matters because a dealership is what Amazon calls a non endemic advertiser. You do not sell anything on Amazon, and Amazon supports you anyway, taking conversion events that happen somewhere other than its own storefront. Your conversion is a form on your website or a call to your store, and the platform is built to accept that.

The two formats a store would actually buy are ordinary display, which is cheap and broad, and Streaming TV, which puts a fifteen or thirty second spot in front of a household watching Prime Video with no way to skip it. It is the same argument as connected TV advertising for dealers, with a different set of screens behind it.

The case is the signal. Outside of Google, Amazon holds the strongest first party record of what a household is actually shopping for, because it is built on purchases rather than on stated interests or page visits. A person who has been pricing roof racks, tow hitches, booster seats and winter tyres is telling you something about their vehicle situation that no interest segment on a social network approaches. Layer a trade area radius over that and the audience is small, specific and reachable.

The honest objection is measurement, and it is a serious one. Amazon's own guidance for this kind of buying is that results are not reliably attributable inside twenty four hours. A household sees a Streaming TV spot on Tuesday and searches your store by name on Saturday, and the platform will not draw you a clean line between the two. If your budget is small enough that every dollar has to prove itself by the weekend, this is the wrong channel and search is the right one.

The second objection is that display and Streaming TV are upper funnel work. They fill the top of a pipeline that somebody still has to work, which is why they belong next to a CRM rather than in a standalone media plan.

Registered, not yet built. The published test for that status is that an adapter file exists in the ad gateway with a written wire-up checklist, committed and scoped rather than finished, and that is precisely what is on disk.

The adapter knows its own name, its family and its readiness gates, and it carries a seven step checklist that starts with Login with Amazon and ends with reporting. What it does not carry is the token exchange, the profile listing, the campaign creation calls, the status change calls or the verification call. Each of those lifecycle methods falls through to the shared refusal, which returns a failure naming Amazon instead of a silent success.

Access class is PARTNER, and that is Amazon's gate rather than ours. Credentials for the advertising API require an application the vendor reviews, with an onboarding step attached to it, so nobody registers themselves into this API on a Sunday afternoon the way they can with a public developer program. That review sits on Amazon's timeline. Everything after it is engineering we control, which is the honest split to understand before asking when this lands.

Stated as a design rather than a description, because none of it runs today.

Lead capture on this network is clickout. There is no form inside Amazon the way there is on a social platform, so a click lands on your website and whatever your site does next is what you get. That single fact shapes the whole page below it.

Amazon is not a bespoke project inside the CRM. It is one implementation of a contract that every advertising network answers.

There is a single library in LeadLocate that defines what any 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. Building Amazon is therefore a scoped piece of work against a checklist rather than an open ended integration project, and finishing it does not disturb the one network that already runs.

The shared machinery is already in place and does not get rebuilt per network. Access tokens are encrypted before storage with 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. Campaign objects record which credentials created them and re-resolve those same credentials later, so disconnecting an account does not strand the work built underneath it. That is the part of an Amazon connection that is finished before anyone starts on Amazon.

There are two ways to advertise through LeadLocate and you pick between them.

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. That path is available today and does not wait on this adapter or any other.

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 spend history intact. For Amazon that path is what this page describes, and it is the half that is unfinished. A store that already has an Amazon advertising profile through an agency would use this route rather than the managed one, since the profile and the history stay where they are.

One limit stated plainly, because it applies across the entire gateway and you would find out anyway: pushing, pausing and reading numbers from a network is done by our team today, not from your dashboard. It is a deliberate constraint while the connection layer is young, and it is on the list to open up.

The checklist in the adapter is ordered and it is short. Apply for advertising API access and clear the onboarding review. Register a Login with Amazon security profile and record the client credentials. Implement the OAuth2 token exchange and refresh. Implement profile listing so a dealer can choose which advertiser to run under. Implement campaign and line item creation. Implement status changes. Implement reporting.

The first step is the one that is not ours. Amazon reviews applicants before issuing credentials, and a review does not run on a schedule we publish. That is exactly why this platform sits at registered rather than at available on request: the engineering is written down and scoped, so a dealership asking for it is asking us to schedule work rather than to go away and think about the problem.

On spend, the useful correction is that self service Amazon DSP carries no Amazon imposed minimum. The fifty thousand dollar figure that circulates in dealer groups is the old managed service commitment and it does not describe the self service product. On proof, set the expectation before you start: results here are not reliably attributable inside twenty four hours, and a store that judges a Streaming TV flight after two days will reach a conclusion the data cannot support.

Amazon supports several capabilities we have not built, and a page about an unbuilt adapter is the worst possible place to blur that line.

We do not run a server side conversions API. Amazon offers one, it is the mechanism that makes a non endemic advertiser measurable, and we have written no part of it. No conversion events are posted from our stack to Amazon, and no offline conversion upload exists anywhere in the product.

We do not install or manage an advertising tag on your website. Because lead capture on this network is a clickout, the entire measurement path depends on tagging that we neither place nor maintain. If a vendor tells you an Amazon buy is measurable through their CRM, ask them who owns the tag.

We do not emit a vehicle catalog. No feed of your inventory is generated for Amazon or for any other advertising platform, so dynamic vehicle level creative is not something we deliver.

We do not export a hashed audience. Building an Amazon audience from your customer list is a real capability of the platform and there is no export in our product that produces one.

No campaign has ever been deployed to Amazon from the CRM, because the code that would do it is not written. Anyone describing this integration as working is describing a plan.

Say so, and say it with your store attached. Requests are recorded against the platform they name, and the tally is the input to build order, because a dealership ready to spend on a channel is a better signal than any roadmap meeting.

Two things are worth telling us at the same time. Whether you already hold an Amazon advertiser profile, since that changes which half of the work matters to you, and whether you want display, Streaming TV or both, since the line item work differs. If your interest is really the screens rather than the marketplace, compare the note on programmatic display for dealers before you decide.

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

Does LeadLocate integrate with Amazon Ads today?

No. Amazon is registered in the ad gateway, which means an adapter file exists with a seven step wire-up checklist and readiness gates, and it is not built. Every lifecycle call it receives returns a refusal naming Amazon rather than a quiet failure.

Can I use my own Amazon advertising account?

Not through the CRM yet. The self connect path for Amazon is the unfinished half, and it also depends on advertising API credentials that Amazon reviews before issuing. The managed path runs today and does not depend on either.

What happens if I request Amazon Ads?

It is recorded against Amazon specifically and counted, and that tally decides build order. You will hear back from a person with a range or a reason rather than silence, and if the honest answer is that the vendor review is the blocker, that is what you will be told.

Is there a fifty thousand dollar minimum on Amazon DSP?

Not on the self service product. That figure describes Amazon's managed service commitment. Self service DSP carries no Amazon imposed minimum, so the practical floor is whatever buys enough impressions inside your trade area to be worth reading.

How fast would I know whether it is working?

Slower than search or social, and the platform's own guidance says results are not reliably attributable inside twenty four hours. Display and Streaming TV influence a shopper days before the visit, so judge a flight over weeks rather than over a weekend.

Can you send my conversions back to Amazon so it optimises?

No. Amazon supports a server side conversions API and we have built no part of it, nor any offline conversion upload. That gap is separate from the adapter work and finishing the adapter would not close it.

Requests are counted against the platform they name and the count decides what gets built next. Tell us your store, whether you already hold an Amazon advertiser profile, and what you would run first.