Connect X Ads to Your Dealership CRM

Enthusiast and truck audiences, pay per use API pricing, and a channel we would argue against making your primary buy.

X sells promoted posts, video and takeover placements against a feed that moves faster than any other consumer surface in this catalogue. The advertising account is ordinary enough: campaigns, ad groups, targeting by interest, keyword and follower lookalike, with billing by impression or by engagement.

What a dealership needs to know is the shape of the audience rather than the shape of the account. X communities cluster hard around specific interests, and several of those clusters are automotive in a way no general purpose feed replicates. Truck owners, tuner and enthusiast circles, motorsport, overlanding, work vehicle upfitting. Those are real conversations with real participants, and reaching them is a genuinely different buy from reaching everyone inside a radius.

Lead capture on this platform is clickout, not native. There is no in feed form prefilled from a profile, so every campaign sends the shopper to a landing page and the form on that page does the work. That single fact governs almost everything about how a store would run it, because the cost of a click is not the cost of a lead and the gap between them is your website's problem, not the platform's.

The most honest case for X is not the audience, it is the economics of building against it. The platform retired the expensive flat monthly developer tier that used to gate its advertising API and moved to credit based pay per use pricing. That changes the calculation for us rather than for you: an integration that used to carry a standing cost before a single dealership benefited now costs roughly what it is used for. Cheap to build is a legitimate reason a platform moves up a queue, and pretending otherwise would be dishonest about how this list gets ordered.

The case for you is narrower and it is worth stating narrowly. If your store moves trucks, performance inventory or anything with an enthusiast following, X reaches those people in a context where they are already talking about vehicles. That is a real thing. It is also a small thing next to search or a general feed.

The honest objection is blunt enough that we would rather say it here than let you discover it: lead quality from this platform is inconsistent, and it should never be a dealership's primary channel. Clickout traffic from a fast feed converts unevenly, the same targeting that finds enthusiasts finds a great many people who will never buy a vehicle in your trade area, and month to month results move around more than they do anywhere else in this directory. Our position is that it belongs in a dealer mix switched off by default, turned on for a specific reason, and read against what to expect from car sales leads rather than against your best channel.

Registered, not yet built. The published test for that status is that an adapter file exists in the LeadLocate ad gateway with a written wire-up checklist, committed and scoped. That is exactly what is there and nothing beyond it. The checklist runs to five ordered steps, shorter than most entries in this directory because the campaign model on this platform is simpler than the ones underneath the larger networks.

Every lifecycle method on the adapter falls through to a shared refusal that names X. A stray call from anywhere in the CRM fails loudly with the network in the error text, so an unbuilt adapter can never be mistaken for an outage at the vendor. We would rather ship a refusal a person can read than a green light nobody can trust.

Access class is PUBLIC, which is the vendor's gate rather than ours, and it needs reading carefully on this platform. Anyone can open an X developer account without an approval queue. Ads API access is a separate grant on top of that developer account, and it is the reason authentication here is described as a developer account plus separate advertising access rather than plain OAuth2. Neither step involves a contract, a certification or a minimum spend, so the gate is procedural rather than commercial.

Stated as a design rather than a description, because none of it runs. The same four row shape appears on every page in this directory, so a platform we have built and one we have not can be compared line for line.

Note what is absent from the second row. Because lead capture is clickout, there are no form submissions to return. Whatever arrives from this platform arrives through your own landing page, which is a materially different integration from the one people picture when they hear the word.

X would not be a special case in the CRM, and that is the entire reason a five step checklist is a credible statement rather than an optimistic one.

A single library inside LeadLocate defines what any advertising platform must be able to do: hand us an authorization URL, exchange the returned 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. Adding a platform is a scoped piece of work rather than an open ended project, and turning one on does not disturb the ones already running.

Access tokens are encrypted before storage using AES-256-GCM, and every action taken against a network lands in an append only event log carrying the company, the network, the user and the detail, stamped in UTC because these tables are shared across dealerships and a timezone relative timestamp is one nobody can reconcile later. Campaign objects record which credentials created them and re-resolve those same credentials afterwards, so an account disconnected next month does not orphan the work built under it. Twenty networks are registered against that contract and one of them is implemented, which is the fact this directory exists to publish rather than hide.

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. Nothing to set up, no developer application to file, and no dependency on the state of this page.

The second is your own account, connected to the CRM so campaigns sit on your billing, in your name, with your spend history intact. That is the path this page documents, and for X it is the half that is unfinished. Any advertising account your store holds with them stays where it is and operates independently of 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, not from your dashboard. That is a deliberate constraint while the connection layer is young, and opening it up is queued work rather than a promise.

Five steps, in order. Obtain a developer account and the separate advertising access grant, then fill the credential block in the gateway configuration. Implement the token exchange. Implement account listing. Implement campaign deployment, status changes and reporting against their endpoints. Implement the verification call that proves a stored credential still works rather than assuming it.

The pay per use pricing model matters at step one and nowhere else. It means a credential can be held and exercised without a standing monthly cost, which is why this platform is cheap to keep current once built rather than an obligation that has to justify itself every month.

On measurement, the two halves separate. Click and engagement data would read within hours of a campaign going live, because a fast feed delivers impressions fast. Meaningful lead counts take two to five days, because a clickout campaign has to move enough people through a landing page for the numbers to mean anything, and the early hours of any campaign on this platform are noise dressed as a trend. Read it on a week, not on an afternoon. None of that is a promise about volume or about what any of it closes at, and nobody can promise those.

The gaps here differ from the ones on a catalog capable network, and the differences are worth naming precisely rather than mail merging a list.

There is no vehicle catalog on either side. X does not carry an automotive inventory format, and we do not emit a vehicle feed or an inventory catalog to any advertising platform anyway. Both halves are missing, so VIN level advertising is not a conversation this platform supports at all. Inventory Link merchandises your units on your own properties, which is a different job.

We do not run a server side conversions API and we do not upload offline conversions. X offers a conversion endpoint. We have no code that speaks to it, so connecting a delivered impression to a signed deal is outside what this integration would produce.

We do not install or manage pixels. On a clickout platform that gap has teeth, because conversion measurement here depends entirely on a tag living on your website. Placing it, maintaining it and keeping consent handling correct are not things we do.

We do not export a hashed audience. Tailored audiences built from your own customer records are a real capability on their side and we have no export that produces one.

There are no native lead forms to retrieve. Lead capture on this platform is clickout, so nothing arrives by webhook and the real time lead path built for one network does not apply here.

No campaign has ever been deployed to X from LeadLocate, because the code that would deploy one does not exist.

Say so, and say it with your store attached and a reason. 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 the reason matters more than usual. A request that says your store moves lifted trucks and you want to reach the people already posting about them is a request we can scope and argue for. A request that says you want another lead source will get a straight answer instead: this is not the channel for that, and pointing you at the one network already connected or at the managed path costs us less than selling you a disappointment.

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

Does LeadLocate integrate with X Ads today?

No. X is registered in the ad gateway, meaning an adapter file exists with a five step wire-up checklist, and it is not built. Every lifecycle call it receives returns a refusal naming the network rather than a quiet failure.

Can I use my own X ad account?

Not yet through the CRM. The self connect path is the unfinished half here. Your advertising account stays where it is and runs independently of LeadLocate, and the managed path does not depend on any of it.

What happens if I request X Ads?

It is recorded against X specifically and counted, and the tally decides build order. Because we would not recommend it as a primary channel, expect a conversation about what you are trying to achieve rather than a straight yes.

Why does the pricing change at the platform matter to a dealership?

Indirectly. Retiring the expensive flat monthly developer tier for credit based pay per use removed a standing cost that had to be justified before any store benefited. It makes the build cheap, which is a real input to queue order even though it changes nothing about your media cost.

Do leads from this platform arrive in the CRM automatically?

There are no native forms to arrive. Lead capture is clickout, so a shopper lands on your website and the form there does the work. Nothing about the adapter changes that, and any lead handling depends on your own landing page.

Would you recommend this as a dealership's main advertising channel?

No, and we would say so before taking the money. Lead quality is inconsistent and results move around more than anywhere else in this catalogue. It belongs switched off by default and turned on for a specific enthusiast or truck audience reason.

Requests are counted against the platform they name. Bring a specific enthusiast or truck audience and we can scope it. Bring a volume target and you will get an honest redirection instead.