Here is how most dealers get their stock onto Google and Meta: the vehicle lives in your dealer management system (DMS); the DMS pushes it to your website; a feed plugin or a portal reads it back off the website; and that plugin builds the file Google or Meta fetches. Four systems, three handovers, before a single ad is served.
Every one of those handovers is a place your data can go stale, get mangled, or silently stop. And when it does, the symptom is always the same: you're paying to advertise a vehicle that's wrong, mispriced, or already sold.
What breaks in the chain
Walk the usual path and count the failure points:
- DMS → website. Your site syncs on its own schedule. If that sync lags, your website — and everything downstream — is already behind your real stock.
- Website → feed plugin. The plugin reads whatever the theme renders. A template tweak, a plugin update, or a slow page and it reads the wrong number, or nothing at all.
- Feed plugin → platform. The plugin decides field mapping and formatting. Miss a required attribute and Google disapproves the vehicle; there's no one watching at 2am.
The data that finally reaches Google is a third-generation photocopy of what's actually in your DMS. Freshness and accuracy leak at every step, and when something goes wrong it's hard to even tell which step did it.
The direct link
Cut the chain. Read the stock straight from the DMS and build the ad feed from that — no website, no portal, no plugin in the middle:
Trajekt connects directly to your dealer system's stock export — for example a Navigator vehicle stock list — and turns it into the exact feed each platform needs. Because it's reading the source of truth, three whole categories of problem simply disappear:
What you get back
Freshness. A new arrival or a price change shows up on the next read — hours, not "whenever the website next syncs and the plugin next runs." Google rewards feeds that match the landing experience, and buyers don't click stale prices.
Sold stock disappears on its own. Your DMS already knows a vehicle is sold — it's in the status. Reading that directly means sold vehicles drop out of your ads automatically, so you stop paying for clicks on things you can't sell. In the website-chain model, a sold vehicle keeps advertising until the sync, the plugin, and the platform have all caught up.
Fewer things to break. No theme change can silently corrupt a feed that never touches the theme. One connection to watch instead of three, and when stock looks wrong you know exactly where to look.
Margin comes along for free
There's a bonus to reading the DMS directly: it carries data your website never exposes. Cost price sits next to retail, so you can bid harder on higher-margin stock instead of treating every vehicle the same — without publishing anything sensitive to the ad platform. That's a lever the website-scrape approach can't pull, because the website never had the cost figure in the first place.
The one honest caveat
A DMS stock list is inventory data — make, model, price, mileage, status. It usually doesn't carry your vehicle photos, and some platforms still want a landing-page URL per vehicle. Neither is a blocker: you pair images and URLs to each vehicle by its stock number, once, and the direct feed handles everything else. You're adding two fields to a clean, live feed — not rebuilding your data by hand off a web page.
Feed your ads from your dealer system, not your website
Trajekt reads your Navigator (DMS) stock list directly and builds your Google Vehicle Ads and Meta feeds — fresh, sold-stock-aware, no middleman.
See Navigator feeds →The takeaway
Every extra system between your stock and your ads is a system that can be wrong. The shortest path from "what I have on the forecourt" to "what I'm advertising" is a straight line from your dealer system to the platform. Fewer hops, fresher data, less to break — and no more paying to promote vehicles that sold last week.