Smartly.io Integration for Car Dealers

Creative and campaign orchestration above the major social platforms, and why the certified gate matters most here.

Smartly.io sits above the advertising platforms rather than beside them. An advertiser connects its accounts on the major social networks, and the platform then handles creative production, campaign structure, budget shifting and reporting across all of them from one place, rather than the advertiser opening four separate consoles and reconciling four separate exports by hand.

The creative half generates variants from templates and data, in the way a production tool does. The campaign half builds and edits the objects inside each network according to rules the advertiser sets. The reporting half pulls everything back into one view. Its whole value proposition is that a large advertiser running many campaigns across many networks does that work once instead of many times.

For a dealership the useful mental model is a control room. It does not sell impressions and it does not own inventory. Every dollar still goes to the underlying network, on accounts you hold, and the vendor charges for the orchestration on top. That framing decides whether it is worth anything to a given store, and the next section is blunt about which stores those are.

The case is coordination at scale. A group running paid social across dozens of rooftops in dozens of markets, with different offers and different inventory, faces real operational cost in keeping campaign structure consistent and creative current. Doing that natively means a large team clicking through consoles, and mistakes made that way are invisible until a month end report shows a market that quietly stopped delivering. An orchestration layer is a genuine answer to that problem.

The first honest objection is that the layer is priced against the spend it manages, and a store spending a few thousand a month across one or two networks is buying coordination it does not need. Two campaigns do not need a control room. They need somebody to look at them on a Tuesday.

The second objection is that a layer is another place things break. When something is wrong, you now have three parties: the network, the orchestration vendor, and whoever built the rules. Migration away is also real work, because campaign structure created through a layer tends to be shaped by that layer. Adding a middle tier is a decision to be made deliberately rather than because a demonstration looked impressive.

The third is the honest overlap. What we have built inside the CRM is a narrow version of the same idea: one contract that many networks answer, so a campaign is described once. Ours is much smaller and one network is live against it. Theirs is broad, mature and expensive. A group that genuinely needs breadth today should buy breadth today, and a store weighing the trade off will get more from social media lead ads for dealers than from any orchestration pitch.

Not started, and the test attached to that status is stated so a dealer can check it: no adapter file exists in the ad gateway for this platform. No authorization URL, no credential block, no wire-up checklist, and nothing partially written waiting behind a status word.

Access class is CERTIFIED, which is the strictest of the three and this is the page where it bites hardest. A contract, a certification or a minimum spend commitment is required before interface access is granted at all. That is not a form to fill in. It is a commercial relationship with thresholds, and it belongs to the vendor rather than to us. No amount of demand in our queue moves it.

There is a second dependency stacked behind the first, and it is unusual enough to name. This platform's own access to the social networks depends on partner status it holds with each of them. So a connection here would run through two gates in series: theirs to us, and the networks' to them. A store should read that as the reason this entry sits far down any realistic build order, not as a reason nobody wants to build it.

A design for a connection nobody has built, written as a design so nothing here is read as current behaviour.

Note that this is the only entry in the catalogue where the return column describes objects living inside other networks. That indirection is the product, and it is also why an audit trail matters more here rather than less. Everything created still has to be traceable back to a person and a credential inside the CRM.

An unbuilt integration can be described precisely because the structure it would join is already running, and on this entry the structure is worth comparing rather than just describing.

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. Twenty networks are registered against that contract and one is implemented, which is the plain state of it.

Connecting an orchestration platform to that gateway produces an odd shape, and saying so is more useful than glossing it. Our contract expects an adapter to reach a network. An orchestration vendor is itself a layer that reaches networks. Routing through it would mean a campaign object crossing two abstractions before it reaches the place that sells the impression, with an extra party in every failure and an extra party in every audit. There are arguments for it, mostly about breadth arriving sooner, and it is not the obvious architecture. A dealer asking for this should know the question is real.

What does not change either way: credentials are encrypted with AES-256-GCM before storage, every action 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 created objects re-resolve the credentials that made them so a disconnection does not strand them.

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

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. Nothing to file, nothing to certify, no credential for you to hold.

The second is your own account. Connect the advertiser accounts your group already holds and campaigns route through them, on your billing, in your name, with your history intact. For this platform neither path exists today, because no adapter has been written and the certified gate has not been approached.

One constraint applies across the entire gateway and belongs in plain sight: 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 rather than something already in the product.

Four steps, and only two are ours. A request from a group whose spend across several networks would justify an orchestration layer. A queue position earned against every other request in the catalogue. An adapter written against the operations that apply, with a credential block and a verification path. And a certified level commercial arrangement with the vendor, which is a contract with thresholds rather than an application form.

Order matters more here than on any other entry. On most platforms the vendor gate and the engineering can proceed in parallel. Here the commercial arrangement realistically comes first, because certification governs whether an interface exists to build against at all. A store should read that as a long timeline honestly stated rather than as a soft refusal.

Measurement, if it ever existed, would be about operations rather than about advertising outcomes: how quickly a new offer reaches every market, how consistent structure stays across rooftops, and how much manual console work disappears. Campaign results would still be produced by the underlying networks, the offer and the follow up, none of which an orchestration layer improves by itself. Nobody can promise that a control room sells more cars.

Nothing is connected, and there are two gaps specific to this entry, so all of it gets said.

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

We hold no marketing partner certification with any social network. Certification of that kind is what this vendor's own access depends on, and we do not have it, which is a second gate stacked behind the first.

We do not emit a vehicle catalog or an inventory feed to any advertising platform. Creative could be produced from vehicle data we already hold on our side, and that is a real capability, but it is not a live catalog handed to a network. Currency depends on when a job last ran rather than on a continuous handoff, and dynamic vehicle level campaigns are out of reach either way.

We do not run a server side conversions API, we do not upload offline conversions, and we do not install or manage pixels. An orchestration layer does not create those capabilities for us.

We do not export a hashed customer list for audience matching, lookalike seeding or suppression.

Connecting an orchestration platform would not, on its own, connect the networks beneath it. Each one still has to be reachable, and today one network in this catalogue is live.

Ask by name, attach the group, and be specific about spend and breadth, because those are the two things the certified gate actually weighs. Requests are recorded against the platform they name and the tally decides build order, but this entry is the clearest example of demand not being sufficient on its own.

The most valuable thing you can tell us is whether you already hold an agreement with the vendor. A certified relationship you have cleared removes the step neither we nor the queue can influence, and turns a distant entry into a scheduling conversation. Absent that, a request here is still worth making, because it tells us something about what a large group actually needs and it may argue for building the underlying networks sooner instead.

Meanwhile the managed path runs today and depends on none of it. Platform pricing is on the pricing page and does not change with the services you connect.

Does LeadLocate integrate with Smartly.io today?

No. The status is not started, and its test is that no adapter file exists in the ad gateway for this platform. There is no credential, no certification and no partial code, and the request count is only one of the inputs to whether that changes.

Can I use my own Smartly.io account?

Not through the CRM. Nothing has been written on our side, and access is certified, meaning a contract, certification or minimum spend is required before an interface opens at all. An agreement you already hold would remove the hardest part of that answer.

What happens if I request Smartly.io?

It is recorded against this platform by name and counted, and the count feeds build order. Because the vendor gate here is commercial rather than procedural, a request may also be answered by building the underlying networks sooner, which usually serves the same goal faster.

Why is this harder to reach than the other creative platforms?

Two gates in series. The vendor requires a certified commercial arrangement before granting access, and the vendor's own reach into the social networks depends on partner status it holds with each of them. Neither gate responds to demand in our queue.

Does LeadLocate already do some of this?

A narrow version. The ad gateway defines seven operations that every network answers, so a campaign is described once rather than per platform. Twenty networks are registered against that contract and one is implemented, which is a far smaller thing than a mature orchestration product.

Would connecting it give me all the networks at once?

No. Each underlying network still has to be reachable in its own right, on accounts you hold, subject to its own approvals. An orchestration layer coordinates connections that exist. It does not create them.

Requests are recorded against the platform they name and the tally sets build order. Tell us your group, your spend across networks, and whether an agreement already exists.