Run LiveIntent from Your Dealership CRM

Newsletter placements decided at open time, and why the capability they lean on is the one we have never built.

LiveIntent puts advertising inside the body of email newsletters. The unusual part is when the decision happens. A newsletter is written and sent once, but the ad slot inside it is filled at the moment the reader opens the message, which can be minutes or days later. That turns a static send into live inventory.

The second unusual part is how it is targeted. Because the reader identified themselves when they subscribed, the placement is addressed through an identity graph keyed on the email address rather than through a browser cookie. Nothing depends on a third party cookie surviving in the reader's browser, and nothing depends on the reader visiting a website first.

For a dealership the mental model is closer to a local newspaper insert than to a display banner. You are buying a slot in something the reader chose to receive, next to editorial they trust, in an inbox they clear on purpose. The trade is attention in exchange for a format that does very little.

The case is attention and the absence of competition. Open rates on a newsletter somebody subscribed to are far higher than the engagement rate of any feed, the reader is not being interrupted mid task, and almost no dealer group in the country is buying this inventory. That last point is worth more than it sounds, because auction pressure in automotive is what makes the obvious channels expensive.

The honest objection is that an email ad is a very limited unit. It renders inside a mail client, which means restricted markup, no interactivity worth the name, and image blocking on a share of opens. Click rates are correspondingly low. Measurement is coarse for the same reason, because view through in email is not reliable and the click is essentially all you get. A store that judges this channel on the same yardstick as a search click will be disappointed by the numbers and will be measuring the wrong thing.

The deeper objection belongs to this page specifically. The reason identity based newsletter buying is interesting is that an advertiser can bring its own customer records and address them directly. That capability is exactly what we do not have, which is covered plainly further down and which changes what a connection would actually be worth. Before spending here, it is worth reading what to expect from any paid lead source.

Not started. The published test for that status is that no adapter file exists in the LeadLocate ad gateway for this platform, and none does. No authorization URL, no wire-up checklist, no partially written token exchange. A dealer can hold us to that wording, which is the point of publishing it.

Access class is PARTNER, and that is the vendor's gate rather than ours. Credentials here require an application the vendor reviews before it issues them. Whatever we build, and however quickly we build it, that review sits in front of a live connection and it runs on somebody else's calendar. It is the step that is not ours to clear, and any vendor telling you otherwise is describing a relationship they have rather than one you would get.

The practical consequence of a reviewed gate on an unstarted platform is that the honest timeline has two unknowns in it rather than one. That is why the request queue matters more here than on a platform with open credentials: demand is what buys the engineering time, and the application is only worth filing once the engineering is scheduled.

Written as a design sketch rather than a description of anything running, because nothing here is built.

On most pages in this directory the last row is a footnote. Here it is the headline, because the identity based targeting that makes this platform distinctive is built to consume exactly the thing that row says never leaves.

This platform would not be a bespoke piece of work. It would be one more implementation of a contract every network answers.

Inside LeadLocate there is a single 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. That is why a new network is a scoped piece of work with a checklist rather than an open ended project, and why finishing one does not disturb the network already running.

Twenty networks are registered against that contract. One of them is implemented. The rest return a refusal that names themselves, so a stray call anywhere in the CRM fails loudly and readably rather than looking like an outage at the vendor. This platform is not among the twenty, which is a further step back again.

Underneath the contract, credentials are encrypted with AES-256-GCM before storage, every action is written to an append only audit log carrying the company, the network, the user and the detail, stamped in UTC because the tables are shared across dealerships and a local timestamp is one nobody can reconcile afterwards. Campaign objects record the credentials that created them and re-resolve those same credentials later, so a disconnected account does not orphan the work built under it.

There are two ways to advertise through LeadLocate and you pick. 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 configure and no application to file with anybody.

The second is your own account. Connect the advertising account your store already has and campaigns route through it instead, on your billing, in your name, with your spend history intact. Disconnect whenever you like and delivery falls back to the managed path.

For this platform neither path exists yet. The managed path runs today on the networks our team already works with, and the self connect path is the half this page is about. A dealership that already holds credentials with this vendor keeps using them exactly as it does now, in the vendor's own console, entirely outside the CRM.

One limit that holds across the whole gateway: pushing, pausing and reading numbers from any network is done by our team today, not from your dashboard. That is a deliberate constraint while the connection layer is young and it is on the list to open up.

Four things, in order, and the first is the slow one. File the vendor application and pass its review. Write the adapter file against the seven operations. Fill and enable a credential block. Prove a verification call against a real account before anybody spends a dollar.

The review is the part with no engineering answer. On a platform with open credentials, we control the whole timeline. Here we control three quarters of it, and saying so is more useful than a confident estimate that quietly depends on somebody else's inbox.

On measurement, set expectations to the format rather than to the channel you are used to. Email inventory fills as readers open their mail, so delivery arrives in waves across a day rather than smoothly across an hour, and a small budget in a single trade area can take several sends before it has produced enough impressions to read at all. Every response is a click through to a page you control, so your landing page and your follow up speed decide the outcome more than the media buy does. That is a statement about how the format behaves, not a promise about lead counts, which nobody can make honestly.

This page has a sharper gap list than most, because the platform's headline capability sits on the wrong side of it.

We do not export a hashed audience. Addressing a newsletter reader from a customer file is the mechanic that makes identity based email advertising worth buying, and there is no export anywhere in our product that produces such a file for any platform. That is not a scheduling problem, it is an absence.

We do not install or manage pixels and we do not run a server side conversions endpoint of any kind. Nor do we upload offline conversions. Measurement of anything that happens after the click is your own analytics, not something we hand back.

We do not emit a vehicle catalog. Nothing in our stack generates a product feed for any advertising system, so an inventory driven creative on this platform is not something we could produce.

No campaign has ever been deployed here from the CRM, because there is no code that could do it. Anyone describing this as an integration is describing a logo on a page.

A dealer cannot push, activate, pause or read spend on any network without our team. That is true across the gateway today.

Say so with your store attached, and say what you would run first. Requests are recorded against the platform they name and the count is the input to build order, because a dealership ready to spend on a channel is a better signal than any roadmap meeting. You will hear back from a person with a range or a reason rather than silence.

Be aware of what you are asking for on this one. The engineering is ordinary. The vendor review in front of it is not ours, and the capability that makes the platform special is a gap we have named above rather than a switch we can throw. A request here is most useful if it comes with the thing you actually want to achieve, because the answer may be a different channel entirely. Compare it against the platform we have actually connected on the Meta page.

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

Does LeadLocate integrate with LiveIntent today?

No. The published test for that status is that no adapter file exists in the ad gateway for this platform, and none does. There is no authorization URL, no checklist and no code in the CRM that reaches this vendor.

Can I use my own LiveIntent ad account?

Not through the CRM, because there is nothing to attach an account to. If your store already holds credentials with this vendor, keep running them in the vendor's own console. Nothing about LeadLocate interferes with that.

What happens if I request LiveIntent?

It is recorded against this platform specifically and counted, and the tally decides build order. Because credentials here need a vendor review, the reply will separate the part we control from the part we do not rather than quoting one date for both.

Can you target my own customer list inside these newsletters?

No, and this is the most important line on the page. We have no export that produces a hashed audience file for any platform. Identity based addressing from an owned customer file is the platform's strongest feature and it is a capability we do not have.

Why does the access class say PARTNER?

Because credentials require an application the vendor reviews before issuing them. That is the vendor's gate, not ours, and it is kept on a separate axis from our build status so both answers stay mechanical rather than blended into one vague sentence.

Would leads from a newsletter placement land in my CRM by themselves?

No. Placements here send the reader to a page you control, so capture happens on your own landing page and routing onward is handled by our team rather than by an automatic processor. We will not describe that path as hands free while a person is in it.

Requests are counted against the platform they name and the count decides what gets built next. Tell us your store, your radius and what you would run first.