Adform Integration for Car Dealers

Buying and ad serving in one independent stack, and an unvarnished account of where the CRM connection stands.

Adform is an independent advertising stack, European in origin, that combines two things most companies sell separately. One is a demand side platform, the software that buys display, video and streaming inventory across the exchanges. The other is an ad server, the system that stores creative, decides which version renders in a given slot, counts the impression and holds the tracking. Owning both means the creative library and the buying live in one place rather than being stitched together with third party tags.

Independence is the second characteristic worth knowing. The company is not owned by a publisher or a search platform, so it has no inventory of its own to favour, which is a genuine structural difference from the large integrated stacks. For a dealership the practical relevance is narrow but real: if you are a group running creative across several rooftops and several markets, having the ad serving and the buying under one roof removes a class of trafficking work that otherwise gets billed to you by an agency.

The case is creative operations, not media access. Any platform in this family can buy a banner in your market. What a combined stack changes is what happens to fifty creative variants across eight rooftops, each with its own offer, running for six weeks and needing a mid flight swap when the manufacturer changes an incentive. Doing that with a separate ad server and a separate buying platform is a trafficking job. Doing it in one system is an afternoon, and for a dealer group with real creative volume that is where the money actually goes.

The honest objection is fit. This is a stack built around European supply, European clients and European regulatory habits, and while it operates far beyond that, a store buying a twenty mile radius in a domestic market is unlikely to find advantages there that a domestic platform lacks. Support hours, supply depth in your specific market and the availability of people who know the platform locally all matter more than a feature comparison.

The second objection is simpler. A single rooftop with four banners does not need an ad server. If that is you, the argument on programmatic display advertising for dealers is the whole of what you need.

Available on request. The test behind that status is published so it can be checked: no adapter file exists in the LeadLocate ad gateway for the platform. There is none. Adform is not among the twenty networks registered against the gateway contract, so there is no partial implementation to describe, no dormant credential block and no code that has ever spoken to their API.

Access class is PARTNER, and that axis is always the vendor's gate rather than ours. Credentials require an application the vendor reviews before issuing them. Keeping the two apart is not pedantry. If the adapter were finished this month, that review would still stand between a dealership and a working connection and it runs on a clock we do not control. An approved application with no adapter behind it is equally inert.

None of that stops a store advertising this week, because the managed path covers display and does not consult this page. What this page documents is the other route, the one where the advertising account belongs to you and the CRM speaks to it directly, and for Adform that route has not been started.

Design rather than description, because none of it exists. Every page in this directory uses the same four rows so a connected platform and an unconnected one can be compared without translation.

The creative level delivery in the return row is the row a group should care about, because it is the only figure that tells you which of your fifty variants is carrying the campaign. Ask any vendor for it by name.

Underneath every platform in this directory sits one library, and it is worth understanding because it is what makes a request answerable rather than aspirational.

The library defines seven operations that any advertising network must answer: produce an authorization URL, exchange the returned code for an access token, list the accounts the connected user controls, deploy a campaign, change its status, report spend and results, and verify on demand that the credentials still work. A network is added by writing one adapter file against those seven. Nothing else in the CRM changes, and nothing already running is affected.

Access tokens are encrypted with AES-256-GCM before they are stored. Every action taken against a network is written to an append only event log carrying the company, the network, the user and the detail, stamped in UTC on purpose, because those tables are shared across dealerships and a local timestamp is one nobody can reconcile afterwards. Campaign objects record which credentials created them and re-resolve those same credentials later, so an account disconnected next quarter does not strand the work built under it. None of that would need reinventing for Adform. What is missing is the adapter file, and the directory says so rather than implying otherwise with an icon.

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 operates the campaigns from the selections you make in Leads Manager, and it arrives as one line rather than a stack of platform invoices to reconcile. Nothing to set up, no vendor application to file, and no dependency at all on what this page says.

The second is your own account, connected to the CRM so campaigns sit on your billing, in your name, with your spend history and your creative library intact. That is the path documented here, and for Adform it does not exist. An account or an ad server instance you already hold with them stays exactly where it is, untouched and unread by anything in the CRM.

One limit stated plainly, because it holds across the whole gateway even where a network is fully built: pushing, pausing and reading numbers from a network is done by our team today rather than by you from a dashboard. That is a deliberate constraint while the connection layer is young, and opening it up is queued work rather than a promise.

The vendor application comes first, because credentials are reviewed rather than issued on registration, and that review is not something we can compress. The adapter follows: the seven operations written against their endpoints, a credential block added to the gateway configuration, and a verification call that proves the connection instead of assuming it. Your own setup comes third, and on a combined stack that step is larger than usual because an ad server has to be populated before a buy has anything to serve.

On measurement, display delivery reads inside a day or two because impressions accumulate fast. Creative learning is slower and is the actual reason to be on a platform like this, since telling which variant works needs enough delivery per variant to be a comparison rather than a coincidence. Splitting a modest budget across fifty creatives produces fifty results you cannot trust, so plan the rotation before the flight rather than after.

None of this is a promise about volume or about what any of it closes at. Nobody can promise that, and this directory would rather publish a checklist than a forecast.

These gaps are true whether or not the adapter is ever written, and on a stack that includes ad serving the first two are sharper than usual.

We do not emit a vehicle catalog or an inventory feed to any advertising platform. That matters more here than on a pure buying platform, because dynamic creative rendering a specific unit with its price and mileage is exactly what an ad server is for, and we generate nothing that could drive it. Inventory Link ingests your feed and merchandises your units on your own properties, which is a different job.

We do not install or manage pixels or tracking tags, including the ones an ad server ordinarily places for conversion counting and retargeting pools.

We do not run a server side conversions API and we do not upload offline conversions, so joining a served impression to a signed deal is not something this integration would deliver.

We do not export a hashed audience built from your customer records.

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

Ask for it by name with the 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 internal roadmap meeting.

On this platform, say how many rooftops and how many live creative variants you are running. Those two numbers decide whether a combined buying and serving stack is solving a real problem for you or adding a system to administer, and they change the reply from a shrug into a recommendation. If the honest answer is that a platform already registered in the gateway gets you further sooner, you will be told that plainly.

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

Does LeadLocate integrate with Adform 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. Adform is not among the twenty networks registered against the gateway contract.

Can I use my own Adform 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 or ad server instance you already hold stays entirely separate from LeadLocate.

What happens if I request Adform?

It is recorded against Adform specifically rather than against display buying in general, and counted. The count is the input to build order, and you will get a range or a reason back from a person rather than silence.

Could the ad server render my live inventory in the creative?

Not from anything we supply. Dynamic creative showing a specific unit with its price and mileage runs from a product feed, and we do not generate one for any advertising platform. That gap sits outside the adapter work entirely.

Does a single rooftop need an ad server?

Almost certainly not. The combined stack argument is about managing many creative variants across many stores and markets. A store running a handful of banners is buying administration it will not use.

Why does the PARTNER gate matter if nothing is built?

Because the two gates are independent and clearing one leaves the other. PARTNER means the vendor reviews an application before issuing credentials, on their timeline. The missing adapter is ours on ours, and publishing both stops either from hiding behind the other.

A combined buying and serving stack solves a problem only some stores have. Tell us how many rooftops and how many live creative variants you run, and the Adform request comes back with a real recommendation.