Get your Auto Dealers tracking to 95%+ accuracy guaranteed in writing.
Dealer websites are vendor-built and vendor-controlled, the highest-intent tools on them are iframes, and the sale closes in the DMS weeks after the click. We rebuild the chain from VDP to lead to delivered unit with real gross, on a container the store owns, so a vendor template push can't wipe it out.
Free30 minutesNo obligation
Auto Dealers · what breaks
What breaks on a vendor-hosted dealer site
- 01
Your website vendor owns the head tag
On Dealer.com, Dealer Inspire, DealerOn or Sincro you get a tag slot, not the container. A platform release can drop your tags without telling anyone, and the vendor's own GTM is usually firing a second GA4 and a second pixel next to yours.
- 02
Trade-in and credit tools are iframes
Kelley Blue Book Instant Cash Offer, TradePending, the payment calculator and the credit application all live on another domain. The submit fires inside a frame the parent never hears, GA4 opens a new session, and the highest-intent action on the site gets credited to a referral.
- 03
"Check availability" and a credit app are one event
A single generate_lead means a price shopper on a ten-year-old trade counts the same as a pre-qualified buyer on a new truck. Bidding buys the cheaper one, because the cheaper one is easier to get.
- 04
The deal closes in the DMS, weeks later
CDK, Reynolds or Tekion knows the unit was delivered and what the front and back gross were. Your CRM knows which lead it came from. Neither tells Google Ads, and by the time anyone checks, the click is near the edge of the import window.
Auto Dealers · the fix
What changes when the delivered unit is the conversion — Auto Dealers
VDP signals that mean something
VDP views carry new versus used, body style, price band, days on lot and stock number, so you can bid toward the inventory that's aging instead of the inventory that sells itself.
Iframe tools report into your own container
Trade-in, payment and credit-app completions get bridged back with the session intact, so they're credited to the campaign that produced them rather than to kbb.com.
Gross, not lead count, drives the bidding
Delivered units go back with front and back gross as the value, matched on hashed contact from the CRM. A store selling fewer, better deals stops looking worse than one farming lead volume.
A matchback the GM already understands
Monthly: clicks, leads, delivered units and gross side by side against the DMS. It's the Source-of-Truth Reconciliation Method applied to a sales log the store already trusts.
Auto Dealers · architecture
SRP to VDP to lead to delivered unit — Auto Dealers
The dealer funnel spans a vendor-controlled website, third-party iframes, a sales CRM and a DMS. We instrument each hop and rejoin them on a click ID or a hashed contact.
- 1
The vendor tag slot, used carefully
Dealer.com, Dealer Inspire, DealerOn or Sincro keeps its own container; we deploy through the slot they give you and route everything to a container the store owns.
- 2
VDP and SRP events carry vehicle attributes
Every vehicle detail page view sends condition, body style, price band, days on lot and stock number, so bidding can chase the inventory that's aging.
- 3
Iframe tools bridged back to the parent
KBB Instant Cash Offer, TradePending, payment calculators and credit applications report completions over postMessage or a vendor callback with the session intact.
- 4
CRM owns the lead, the DMS owns the sale
VinSolutions, Elead, DealerSocket or DriveCentric holds the stored click ID, while CDK, Reynolds or Tekion holds the delivered unit and the gross.
- 5
Matchback returns gross to the platforms
Delivered units go back as offline conversions matched on hashed contact, with front plus back gross as the value rather than a lead count.
Auto Dealers · events
Dealer events, from SRP filter to delivered unit
Website events exist for reporting; the DMS-sourced sale is what bidding is actually asked to chase.
| Event | Fires when | Key parameters | Sent from / role |
|---|---|---|---|
| srp_filtered | Shopper applies an inventory filter on a search results page | make, model, condition, price_band, results_count | Browser · reporting only |
| vdp_view | A vehicle detail page renders | vin, stock_number, condition, body_style, price, days_on_lot | Browser + server · reporting only |
| trade_in_completed | KBB ICO or TradePending returns an offer inside the iframe | gclid, em (hashed), ph (hashed), vin, event_id | Server via postMessage bridge · optimization (secondary) |
| lead_submitted | Check availability, ePrice or test-drive form posts | gclid, em (hashed), ph (hashed), vin, lead_type, event_id | Browser + server, deduped by event_id · reporting only |
| credit_app_submitted | Finance application submits, usually on the vendor's domain | gclid or hashed contact, value (tier), currency, event_id | Server · optimization (primary) |
| appointment_set | The CRM logs a confirmed showroom appointment | gclid or hashed contact, conversion_date_time, event_id | Server · optimization (secondary) |
| unit_delivered | The DMS records the deal as delivered | gclid or hashed contact, value (front + back gross), currency, transaction_id, vin | Server offline import · optimization by value |
| service_appointment | Xtime or myKaarma booking confirms | gclid or ph (hashed), ro_type, value (average RO), currency | Server · separate conversion action, kept out of sales bidding |
Auto Dealers · prove
The monthly matchback against the DMS sold report — Auto Dealers
The store already trusts its own sold log, so that's what we reconcile to, rooftop by rooftop rather than group-wide.
Source of truth
Delivered units and front/back gross in CDK, Reynolds & Reynolds or Tekion, taken from the DMS sold report
- Export delivered units for the month with deal number, VIN, gross, and the CRM lead ID that produced each one.
- Join to CRM leads and label each deal site-originated, marketplace ADF, phone, walk-in or unknown before any credit is claimed.
- Match site-originated deals to a click ID; where the click aged out, match on hashed email or phone instead.
- Compare unit count and total gross to what Google Ads and Meta report by conversion date, per rooftop.
- Confirm marketplace and OEM-referred leads stayed excluded, so paid search isn't quietly claiming Autotrader or Cars.com volume.
- Name the remaining gap as window, cross-device or view-through difference, then fix only the events that never fired.
Auto Dealers · free audit
What we check in the free audit
- Your website vendor owns the head tag
- Trade-in and credit tools are iframes
- "Check availability" and a credit app are one event
- The deal closes in the DMS, weeks later
Checked against
Delivered units and front/back gross in CDK, Reynolds & Reynolds or Tekion, taken from the DMS sold report
Free30 minutesNo obligation
Auto Dealers · when not to buy
When a rooftop shouldn't buy this yet — Auto Dealers
Four cases where a dealer's money goes further somewhere else.
- Most of your volume is marketplace listings and walk-ins and paid search is a small line item. Fix the VDP form and get a tracking number.
- Your website vendor won't implement a dataLayer change and won't give you the tag slot. Solve the vendor relationship before buying a build.
- The store doesn't reliably close CRM leads to a deal record. Without that link there's no matchback to build, only one to invent.
- You run only OEM-controlled tier-3 campaigns where the manufacturer owns the creative, the budget and the landing pages.
Auto Dealers · what we deliver
What we build for a store whose website isn't its own — Auto Dealers
A first-party container the vendor can't overwrite
A GTM server container on a subdomain of the dealer's own domain, in the dealer's cloud project. A vendor template push stops being an outage.
A vendor tag-slot audit
Everything the site vendor is already firing, listed out: duplicate GA4 properties, stray pixels from the last agency, OEM-mandated tags, and which of them are double counting the same lead.
A VDP and SRP dataLayer spec
Vehicle attributes on every VDP view and SRP filter, plus phone, chat and form events from Gubagoo, ActivEngage or Podium. Written as a spec your vendor can implement, or we deploy it through the tag slot.
An iframe bridge for the high-intent tools
postMessage or vendor callback handling for trade-in, payment calculator and credit application, with cross-domain linking so the session survives the hop.
A CRM and DMS matchback pipeline
VinSolutions, Elead, DealerSocket or DriveCentric leads joined to delivered units from CDK, Reynolds or Tekion, then returned to Google and Meta with hashed contact and gross as the value.
A rollout that repeats across rooftops
One build, deployed store by store with its own container and reporting, and co-op documentation showing the OEM what fired without disturbing their required tags.
Written guarantee
95%+ tracking accuracy
Measured against Delivered units and front/back gross in CDK, Reynolds & Reynolds or Tekion, taken from the DMS sold report. Miss it and we keep working at no cost.
FAQ
Auto Dealers questions, answered
We've never needed full access. The vendor keeps their container, we use the tag slot they do give you, and everything else runs in a server container on your domain. Where the vendor has to implement a dataLayer change, we hand them a written spec instead of a support ticket, which tends to move faster.
No, and be careful with anyone who says they do. Those leads arrive as ADF into your CRM without ever touching your site, so there's no click to match them to. What we can do is keep them clearly separated from your own site's leads, so your paid search numbers aren't quietly taking credit for marketplace volume.
It's built with that in mind. We document what fires, leave the OEM's required tags alone, and keep reporting in a form co-op administrators accept. We can't promise a particular claim gets approved, since that's between you and the manufacturer, but we won't be the reason it gets kicked back.
Usually, because most delivered units close inside Google's 90-day click import window. For the ones that don't, we send the lead-stage event while the click is still in window and attribute the sale through hashed contact matching, which doesn't depend on a click ID at all.
That's the easy case. The build gets done once against the shared template, then deployed per store with its own container, its own CRM connection and its own reporting. One rooftop's mess stays in that rooftop instead of polluting group numbers.
Xtime and myKaarma scheduling can be tracked the same way, and service is usually the faster win because appointments close in days rather than weeks. We keep it in its own conversion action so service volume doesn't get mixed into sales bidding and flatten the value signal.
If most of your volume comes from marketplace listings and walk-ins, and paid search is a small line item, this is premature. Fix the VDP form and get a tracking number first. It starts paying when you're spending enough on your own site's traffic that the difference between lead count and gross would change a decision.
More on Auto Dealers
- GuideOffline Conversion Tracking: Send Closed Deals Back to Google Ads and Meta
- Auto RepairGoogle Ads for auto repair shops: the build order
- Auto repair shopsLocal Services Ads for auto repair shops: no badge, status calls and cost per ap…
- Auto glass companiesLocal Services Ads for auto glass companies: no badge, chip-price calls and cost…
Free · 30 min
Match your ad spend to the deals that actually delivered
WhatsAppFree30 minutesNo obligation
