Illumin Integration for Car Dealers

Journey based creative sequencing, the reach it quietly requires, and the honest state of the connection to your CRM.

Illumin is a demand side platform with an unusual organising idea. Rather than defining an audience and repeating one message at it until frequency caps out, the platform is built around a canvas where you lay out a journey: a first message, then a different message for the people who responded to it, then a third for the people who progressed again. Buying and creative sequencing live in the same tool, which is what the vendor means by journey advertising.

In dealership terms that maps onto how a vehicle purchase actually behaves. A shopper who has just started looking does not need a payment offer, and a shopper who has configured a trim three times does not need a brand awareness spot. Sequencing lets the second message assume the first one landed. It is closer to how a good salesperson works a lead over three weeks than to how most display is bought, which is why the platform reads as a natural fit for automotive and why it is worth being careful about the conditions under which that fit holds.

The argument is message relevance over time. Automotive has one of the longest research arcs in retail, and a display budget spent showing the same banner to the same household for six weeks is mostly spent teaching that household to ignore you. A journey structure lets a store spend the same money saying three different things in a sensible order, which is a better use of the same impressions without a bigger budget.

The honest objection is that sequencing needs volume to work, and a single rooftop may not have it. Every step in a journey divides the audience. If your radius contains a modest number of genuinely in market households, the second stage inherits a fraction of that and the third stage inherits a fraction of the fraction, until the deepest step is delivering to a group too small to read. The tool will still run. It will just be an expensive way to buy a first stage.

The second objection is production cost. Three sequenced messages means three sets of creative, refreshed on a cadence, and a store that struggles to produce one good banner will not produce five. Before committing, read programmatic display advertising for dealers and be honest about who is making the assets.

Available on request. The test for that status is published and it is checkable: no adapter file exists in the LeadLocate ad gateway for this platform. There is none. Illumin is not among the twenty networks registered against the gateway contract, so there is nothing partially wired, no dormant credential block and no code path that has ever addressed their API.

Access class is PARTNER, which is always the vendor's gate rather than ours. Credentials require an application the vendor reviews before issuing them. Those two facts are deliberately reported on separate lines. If the adapter were finished this month, that application would still sit between a dealership and a working connection, and it moves at a pace nobody here sets. Equally, an approved application without an adapter is a credential with nothing to use it.

None of which stops a store advertising. The managed path covers display today and does not consult this page. What this page documents is the other route, where the advertising account is yours and the CRM speaks to it directly, and for Illumin that route is unbuilt.

Design, not description. Nothing below runs. The four row shape repeats on every page here so a built platform and an unbuilt one can be compared without translation.

The step level progression counts in the return row are the interesting ones, because they are the only numbers that tell you whether the journey is a journey or an expensive first stage. That is the figure to ask any vendor for, on this platform or another.

Illumin would not be a special case in the CRM. Every advertising network answers the same contract, which is what makes a queue position meaningful.

A single library inside LeadLocate defines what any platform must do: hand us an authorization URL, exchange the returned code for a token, list the accounts the connected user controls, 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 shape is why adding a platform is scoped work with a checklist rather than an open ended project, and why turning one on leaves the others undisturbed.

The machinery around it is already built and shared. Access tokens are encrypted with AES-256-GCM before storage. Every action against a network is written to an append only event log carrying the company, the network, the user and the detail, stamped in UTC because those tables are shared across dealerships. Campaign objects record and re-resolve the credentials that created them, so disconnecting an account later does not strand the campaigns built under it. Twenty networks are registered against the contract and one is implemented, and this directory publishes that ratio rather than burying it.

Advertising through LeadLocate happens one of two ways and the choice is yours.

One is the webXintel Ads Network, included with the platform. Our team builds and operates everything from the selections you make in Leads Manager, and you receive one line rather than a stack of platform invoices and login credentials to keep track of. It is live and it does not wait on any adapter work described here.

The other is bringing your own account, so campaigns sit where you control them, on your billing, with the history and the audience work you have already paid for. That is the half of the product this directory documents platform by platform, and for Illumin that half is empty. Nothing in the CRM reaches an Illumin account, including one you already hold.

Worth repeating because vendors are vague about it: the push, the pause and the spend read are performed by our team today rather than by you from a dashboard inside the CRM. Every page here says so, including the page for the one platform that is fully connected.

Vendor application first, because credentials are reviewed rather than issued on sign up, and that review runs on the vendor's schedule. Adapter second: the seven operations written against their endpoints, a credential block added to the gateway configuration, and a verification call that proves a connection instead of assuming one. Store setup third, which here is heavier than usual because a journey needs its creative built before the first impression rather than after.

On measurement, the first stage of a journey reads quickly, usually inside a day or two, because it behaves like ordinary display. The later stages do not, and cannot, because a person has to move through stage one before stage two has anyone to serve. Plan on several weeks before the sequence itself can be judged, and insist on step level numbers rather than a blended campaign total, which will always flatter the structure by hiding how few people reached the end of it.

None of that is a promise about volume or about what any of it closes at. Nobody can promise that, and a plan that depends on such a promise is not a plan.

The gaps below apply whether or not an adapter is ever written, and a journey platform makes two of them sharper than usual.

We do not install or manage pixels. That is the important one here. Journey progression is normally measured with site side signals, so the branch conditions that make sequencing work depend on tags we neither place nor maintain. A journey built without them is a schedule, not a sequence.

We do not emit a vehicle catalog or an inventory feed to any advertising platform, so a step that renders a specific unit with price and mileage is not something we could supply creative for.

We do not run a server side conversions API and we do not upload offline conversions, so the end of the journey cannot be joined to a signed deal by anything we operate.

We do not export a hashed audience built from your customer list, which rules out seeding a journey from your own records.

No campaign has ever been deployed to Illumin from LeadLocate, because no code exists that could deploy one.

Ask by name and attach the store. 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 internal roadmap meeting.

On this platform, include the size of your trade area in the request. Journey sequencing is the one idea in this family that fails quietly rather than loudly when the audience is too small, and knowing your radius changes whether the honest answer is a queue position or a suggestion to spend the same money on a simpler structure. If a network with a working connection would get you there sooner, you will be told that, and the one platform already connected is documented in the same detail so you can judge for yourself.

The managed path is live and none of this delays it. Platform pricing is on the pricing page and does not change based on which networks you turn on.

Does LeadLocate integrate with Illumin today?

No. The published test for available on request is that no adapter file exists in the ad gateway for the platform, and none does. Illumin is not among the twenty networks registered against the gateway contract.

Can I use my own Illumin ad account?

Not through the CRM. Routing campaigns through an account you own requires an adapter and there is none for this platform. An account you already hold with the vendor is unaffected and unconnected.

What happens if I request Illumin?

It is recorded against Illumin specifically rather than against display generally, and counted. The count is the input to build order, and the reply comes from a person with either a range or a reason.

Is journey sequencing worth it for a single rooftop?

It depends entirely on reach. Each step divides the audience, so a small trade area can leave the later stages delivering to a group too small to read. Ask for step level progression numbers before you judge the structure, not a blended campaign total.

Could you build the journey branches from CRM activity?

No. Branch conditions on a platform like this are normally driven by site side signals, and we neither install nor manage the tags that produce them. We also do not export any audience built from your customer records to seed a journey.

Why does the vendor gate matter if the adapter is missing anyway?

Because clearing one does not clear the other. PARTNER means the vendor reviews an application before issuing credentials, on their timeline. The missing adapter is our work on ours. This directory publishes them separately so a dealer can tell which conversation is actually holding things up.

Sequencing lives or dies on reach, so tell us the trade area and how many creative assets you can realistically produce. You will get a queue position or a straight recommendation to run something simpler.