Connect Google Ads to Your Dealership CRM

Search, Performance Max, YouTube and VIN-level Vehicle Listing Ads, and where that connection actually stands.

Google Ads is the only advertising account a dealership can open that covers the entire funnel in one place. Search captures somebody typing the exact thing they want to buy. Performance Max spreads a single budget across Search, Display, YouTube, Gmail and Maps. Demand Gen works the upper funnel. Vehicle Listing Ads render actual VIN level inventory directly in results, with the price and the mileage on the unit.

For a store the practical consequence is that Google is where the highest-intent demand in automotive lives. A person searching for a specific trim within twenty miles of your lot is closer to a purchase than anyone you will reach anywhere else in this catalogue, and they cost accordingly.

Two details are worth knowing because they change how the account is structured. Waze inventory now runs inside Performance Max under store visit goals rather than as a separate buy, so a dealership asking about Waze is really asking about a PMax setting. And lead form assets capture an opt-in inside the search result itself, without the shopper ever reaching a landing page, which is the same mechanic that makes social lead forms cheap.

The argument for Google is intent, and it is the strongest argument in paid media. Nobody types a model and a trim and a city by accident. Compared with every social and programmatic channel in this directory, the person arriving from a search result has already done the work of deciding roughly what they want.

The honest objection is cost and competition. Automotive search is one of the most contested categories there is, you are bidding against franchise stores, national aggregators and the listing sites, and a poorly structured account will spend a real budget on searches that were never going to buy from you. Google rewards structure and punishes carelessness more than any other platform here.

The second objection, less often said out loud, is that Google is where most dealership agencies already are. If a store is unhappy with its advertising, there is a decent chance the problem is not the channel but the account. That is worth diagnosing before moving money, and it is a reason to read how Google Ads works for car dealerships before deciding what to change.

Registered, not yet built. The published test for that status is that an adapter file exists in the ad gateway with a written wire-up checklist, committed and scoped. That is exactly what is there.

Concretely, the adapter carries a real authorization URL pointing at Google's OAuth endpoint with the correct advertising scope and offline access, and readiness gates that read the actual credential keys rather than returning a hardcoded answer. What it does not carry is the token exchange, the campaign mutation calls, the reporting calls or the verification call. Those six lifecycle methods fall through to the shared refusal, which returns a failure naming Google rather than pretending to succeed.

Access class is PUBLIC, but read that precisely: anyone can register a Google developer application without an approval queue. A developer token still has to be applied for through a manager account, and that application is Google's process rather than ours. It is the one remaining step in this integration that is not ours to clear.

Stated as a design rather than a description, because none of it runs yet.

That last row is the one that decides whether Vehicle Listing Ads are possible, and the section below is blunt about it.

Google is not a special case in the CRM. It is one implementation of a contract that every network answers.

There is a single library inside LeadLocate defining what any advertising platform must be able to do: hand us an authorization URL, exchange the 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 file per network. That is why building Google is a scoped piece of work with a checklist rather than an open ended project, and why finishing it does not disturb the network that is already running.

Access tokens are encrypted before storage using AES-256-GCM, and every action against a network is written to an append only audit log carrying the company, the network, the user and the detail. When campaign objects are created the system records which credentials created them and re-resolves those same credentials later, so disconnecting an account does not strand the work built under it. None of that has to be reinvented for Google; it already exists and it is the reason the remaining work is measured in a checklist.

There are two ways to advertise through LeadLocate and you pick. The first is the webXintel Ads Network: included, always on, built and run by our team from the selections you make in Leads Manager, arriving as one line rather than a stack of platform invoices. That path is live today and does not wait on this adapter.

The second is your own account. Connect the advertising account your store already has and campaigns route through it instead, on your billing, in your name, with your history intact. For Google that path is what this page is about, and it is the half that is not finished.

One limit stated plainly, because it applies across the whole gateway: 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 it is on the list to open up.

The checklist in the adapter is eight steps and it is ordered. Register a developer application and obtain a developer token through a manager account. Fill the Google block in the credential file and enable it. Implement the token exchange. Implement account listing. Implement campaign deployment against the mutate endpoints. Implement status changes. Implement reporting. Implement verification.

The dependency worth understanding is that the developer token application is Google's timeline, not ours. Everything after it is engineering we control. That is why this platform sits at registered rather than available on request: the work is scoped and written down, and a dealership asking for it is asking us to schedule it rather than to go and think about it.

Once live, Google produces readable data faster than most channels here, generally inside a day of a campaign going live, because search volume in a dealership trade area is immediate. That is a statement about how quickly the channel produces information, not a promise about lead counts or what those leads close at. Nobody can promise that.

This is the section that matters most on a page about something we have not built.

We do not emit a Merchant Center vehicle feed. Vehicle Listing Ads render VIN level inventory from a product feed, and there is no code anywhere in our stack that generates one for Google. Inventory Link ingests your feed and merchandises your units, which is a different thing. Until a feed exists, VIN level Google inventory advertising is not something we deliver, and no part of the adapter checklist changes that.

We do not run conversion uploads or server side conversions. No offline conversion import, no enhanced conversions, no pixel installation or management.

We do not upload Customer Match lists. Audience targeting built from a dealership's own customer list is a real Google capability and we have no export that produces one.

We have never deployed a campaign to Google from the CRM, because the code that would do it is not written. Anyone describing this integration as working today is describing the plan, not the product.

Say so, and say it with your store attached. Requests are recorded against the platform they name, and the count is the input to build order, because a request from a dealership ready to spend on a channel is a better signal than any roadmap meeting.

Google carries an unusual amount of leverage in that queue for a reason that has nothing to do with Google. Microsoft Advertising imports campaigns wholesale from a Google Ads account, so the second platform becomes close to one click once the first exists. Two of the twenty registered networks move together, which is why the Microsoft page tells the same story from the other side.

In the meantime the managed path runs today and does not wait on any of this. Pricing for the platform is on the pricing page and does not change based on which networks you turn on.

Does LeadLocate integrate with Google Ads today?

No. Google Ads is registered in the ad gateway, which means an adapter file exists with a real authorization URL and an eight step wire-up checklist, and it is not built. Every lifecycle call it receives returns a refusal naming the network rather than failing silently.

Can I use my own Google Ads account?

Not yet through the CRM. The self connect path for Google is the half that is unfinished. The managed path runs today and does not depend on it.

What happens if I request Google Ads?

It is recorded against Google specifically and counted. That tally decides build order. You will hear back from a person with a range or a reason rather than silence.

Can you run Vehicle Listing Ads with my inventory?

No. Those render from a Merchant Center vehicle feed and we do not generate one. That gap is separate from the adapter work and finishing the adapter would not close it.

What is a developer token and why does it matter here?

It is the credential Google requires before an application may call the Ads API, applied for through a manager account and reviewed by Google. It is the one step in this integration that runs on somebody else's timeline.

Does connecting Google also give me Waze?

Effectively yes, but not as a separate buy. Waze inventory now runs inside Performance Max under store visit goals, so it is a campaign setting rather than a distinct integration.

Requests are counted against the platform they name, and the count decides what gets built next. Tell us your store and what you would run first.