Creatopy Integration for Car Dealers

Template driven banner production at volume, and a clear line between making an advertisement and buying one.

Creatopy makes advertisements. It does not buy them, place them, or decide who sees them. A designer builds one master layout, marks which pieces are variable, points the layout at a data source, and the tool produces every size and every variation the placement standards call for. What used to be an afternoon of resizing becomes a job that runs while nobody watches.

That distinction matters more on this page than almost any other in the catalogue, because a dealership reading a list of advertising platforms will reasonably assume every entry is somewhere to spend media money. This one is not. Whatever comes out of it still has to be uploaded into a network that sells impressions, and the network is a separate decision with a separate invoice.

For a store the use case is straightforward once that is clear. Twenty units you want merchandised, three offers, four sizes each, refreshed when the stock turns. Done by hand that is a standing weekly task somebody resents. Done from a template and a data source it is a job that runs on a schedule, and the output is consistent because the layout is the same every time.

The case is production capacity. Most rooftops do not employ a designer, and the ones that do have that person doing six other things. Creative volume is the quiet constraint behind a lot of underperforming display and social spend: the store runs one tired image for a quarter because making a new one is a chore, and the campaign fatigues long before the budget does. A tool that makes fifty variants from one layout removes that constraint entirely.

The first honest objection is that automation multiplies whatever you give it. Feed a weak template and a bad offer into this and you get four hundred weak advertisements instead of one, faster and at greater expense. Feed it a stale data source and you have just published a price on a unit that sold on Tuesday, in every size, across every placement. The tool has no opinion about whether the input was right.

The second objection is scale. A store running two campaigns a month with a handful of creatives does not have a volume problem worth paying a platform to solve, and the honest recommendation there is to make four good images and rotate them. The value curve here climbs steeply with the number of rooftops, the number of offers and the frequency of change, which is why this is usually a group conversation rather than a single point one.

The third is the destination. Banners have to run somewhere, and display is not the strongest dollar in a dealership's plan in most trade areas. Before buying a machine that produces display creative faster, it is worth being sure display is where the money should go at all, which is the argument our page on programmatic display for dealers takes apart in more detail.

Not started, and the published test for that status is one you can check: no adapter file exists in the ad gateway for this platform. No authorization URL, no credential block, no wire-up checklist, and no partially written code sitting behind a status word.

Access class is PUBLIC, which describes the vendor's gate and nothing else. The vendor documents an interface for automated creative generation openly, so no approval queue and no contract stands between a developer and the ability to build against it. Every obstacle remaining on this entry is on our side, which is unusual in a catalogue where most entries wait on somebody else's review.

There is a second thing the status word cannot express, and it belongs here rather than buried further down. The gateway is built around seven operations that assume a network selling impressions. A creative tool answers perhaps two of them naturally. Connecting it would either mean stretching the contract or treating it as a different class of integration altogether, and that design question is genuine work rather than paperwork. It is not a reason to refuse the request. It is a reason the request should be specific about what a store actually wants to happen.

Written as a design for something nobody has built, and the shape here differs from every media platform in this catalogue.

Read the first and last rows together, because they are the honest heart of this page. Creative could be built from vehicle data we already hold in the CRM. It would not be built from a live catalog handed to an advertising network, because we emit no such feed to any network. That is a real difference in freshness and it changes what a store should expect.

An unbuilt integration can be described precisely because the frame it would join already exists and already carries a live network.

One library inside LeadLocate defines what any advertising platform must be able to do: hand us an authorization URL, exchange the credential for a usable token, list the accounts that credential reaches, 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 contract is why a catalogue this size is maintainable at all.

A creative tool fits it awkwardly and that is worth being straight about. Authorization and verification map over cleanly. There is no campaign to deploy, no spend to read and nothing to pause, so an adapter here would implement the operations that apply and return a refusal naming the reason for the ones that do not, in the same way every unimplemented network already does rather than quietly returning an empty success.

The parts that would carry over without change are the ones that matter for a franchise review. Credentials are encrypted with AES-256-GCM before storage. Every action against any connected service is written to an append only audit log carrying the company, the service, the user and the detail, stamped in UTC because the table is shared across dealerships and a company local timestamp cannot be reconciled later. Objects created record which credentials created them and re-resolve those credentials afterwards, so a disconnected account does not strand the assets built beneath it.

Two ways to advertise through LeadLocate, and the store chooses which.

The first is the webXintel Ads Network: included, built and operated by our team from the selections you make in Leads Manager, and billed as one line rather than a stack of platform statements. Creative for that path is handled by our team as part of it, so a store on the managed path is not the store that needs this tool.

The second is your own account. Connect the accounts your group already holds and work routes through them, on your billing, in your name. For this platform that path does not exist today because no adapter has been written, and it is the only reason.

One constraint applies across the gateway and belongs on the page: deploying, activating, pausing and reading spend is done by our team rather than from a control on your dashboard. That is deliberate while the connection layer is young, and it is on the list to open up. A creative tool would sit alongside that constraint rather than inside it, since nothing it produces spends money on its own.

Three steps, and no vendor review among them, which is what a public access class buys. A request from a store or a group that would actually use the output at volume. A queue position earned against the rest of the catalogue. And an adapter written against the operations that apply, with a credential block, a verification path and a defined mapping from the vehicle attributes we hold to the variable fields in a template.

That mapping is the real work and it is worth understanding before asking. Somebody has to decide which field becomes the headline, what happens when a photograph is missing, how a payment figure is expressed, and what the layout does when a trim name runs long. Those are design decisions with legal implications on a price, not a switch to flip, and a template built without them produces four hundred embarrassing advertisements very efficiently.

On measurement, the thing to measure is production rather than performance. How long it took to get a new offer live across every size, and whether the creative in market matches the stock actually on the ground. Whether the advertising works is a question about the network you bought, the offer you made and the follow up behind it, and no creative tool can answer it. Nobody can promise a result from a better banner.

Nothing is connected, and this page has an extra gap that the media platforms do not, so both get stated.

We have never made a call to this platform. No adapter file, no credential, no verification, no generation job, and nothing partially written.

Connecting a creative tool does not buy media. It produces files. Those files still have to be placed into a network that sells impressions, on a separate account with a separate invoice, and any proposal blurring those two things is worth reading twice.

We do not emit a vehicle catalog or an inventory feed to any advertising platform. That is the honest limitation on this entire idea. Creative could be generated from vehicle data we hold on our side, which is a real capability, but it is not a live catalog handed to a network, so freshness depends on when the generation job last ran rather than on a continuous handoff. A sold unit can survive in a rendered banner until somebody regenerates it.

We do not run a server side conversions API, we do not upload offline conversions, and we do not install or manage pixels.

We do not export a hashed customer list for audience matching or suppression, and dynamic creative decided per viewer at serve time is not something we do.

Ask by name and say what you want generated, not just which vendor you want connected. Requests are recorded against the platform they name and the tally decides build order, because a dealer describing a concrete production job is a far better brief than a logo on a wish list.

Two things make a request here much stronger. Say how many rooftops and how many offers a month you would run through it, since the value of creative automation is almost entirely a volume argument. And say where the finished files would go, because a store without a display or social budget to put them into is asking for a machine with nowhere to point it.

There is no vendor approval to wait on here, so this request competes purely on demand against everything else in the queue. In the meantime the managed path runs today, creative included, and depends on none of this. Platform pricing is on the pricing page.

Does LeadLocate integrate with Creatopy today?

No. The status is not started, and its test is that no adapter file exists in the ad gateway for this platform. Nothing partial is written. The vendor documents its interface openly, so the only remaining obstacle is our own build queue.

Can I use my own Creatopy account?

Not through the CRM. Nothing has been written on our side. Access here is public, meaning no vendor approval stands in the way, so the missing piece is the adapter rather than anybody's permission.

What happens if I request Creatopy?

It is recorded against this platform by name and counted, and the count feeds build order across the catalogue. A person replies with a range or a reason. A request describing a concrete production job carries much more weight than one naming only the vendor.

Would it pull my live inventory into the banners?

Not as a live handoff. Creative could be generated from vehicle data we already hold on our side, but we emit no catalog feed to any advertising platform, so freshness depends on when the generation job last ran. A sold unit can persist in a rendered file until it is regenerated.

Is this a place to spend advertising money?

No. It makes the advertisements. The impressions are bought somewhere else, on a different account with a different invoice, and keeping those two ideas apart is the single most useful thing to take from this page.

Is creative automation worth it for one rooftop?

Usually not. The economics improve with the number of stores, offers and refreshes. A single point running two campaigns a month is better served by making four good images and rotating them properly than by paying for a production system it cannot fill.

Requests are recorded against the platform they name and the tally sets build order. Send your rooftop count, how many offers a month you would run, and where the files would go.