Integration
DriveCentric integration for dealer websites
Zoomshop routes leads generated on your VDPs, contact forms, and inventory pages directly to DriveCentric as standard ADF/XML — the same format DriveCentric accepts from AutoTrader, Cars.com, and every other lead source. Leads land in DriveCentric within seconds with vehicle-of-interest details, referring URL, and UTM parameters intact, ready for DriveCentric's AI engagement to take over.
What this integration does
DriveCentric is your customer engagement layer — the CRM where every conversation lives, the AI agents that respond in seconds, the texting workflow your team runs from mobile. Zoomshop’s job is to feed that layer with clean, well-attributed leads and stay out of the way.
The integration is intentionally minimal. Zoomshop doesn’t try to be a lead management system. DriveCentric doesn’t try to be a website. Each system does what it’s best at, connected through the automotive industry’s oldest and most reliable interface — ADF/XML over email intake — the same plumbing that has moved lead data between systems for over two decades.
For independent dealers who chose DriveCentric because it treats them like a first-class customer (unlike legacy CRMs built for franchise scale), this pairing preserves that. Zoomshop is a website platform built with the same independent-dealer respect: your domain, your data, your leads, no contract lock-in.
What data moves
| Field | Direction | Cadence |
|---|---|---|
| Lead submissions — all form fills on Zoomshop VDPs and pages | Zoomshop → DriveCentric | On submit, within seconds |
| Shopper name, email, phone, additional form fields | Zoomshop → DriveCentric | Per lead |
| Vehicle-of-interest (VIN, year, make, model, trim, stock number) | Zoomshop → DriveCentric | Per lead |
| Referring URL (the exact VDP or page they submitted from) | Zoomshop → DriveCentric | Per lead |
| UTM parameters (source, medium, campaign, term, content) | Zoomshop → DriveCentric | Per lead |
| Source attribution (labeled as your dealership website) | Zoomshop → DriveCentric | Per lead |
| Timestamp | Zoomshop → DriveCentric | Per lead |
Note the direction: it’s one-way. Zoomshop sends leads to DriveCentric; DriveCentric doesn’t need to send anything back to Zoomshop for the integration to work correctly. Your DriveCentric account remains the source of truth for lead management, communication history, and sales workflow — Zoomshop just puts leads in the door.
Setup requirements
From your side:
- Your dealership’s ADF intake email address from DriveCentric (available in your DriveCentric account settings, or ask your DriveCentric rep)
- 15 minutes for setup and verification
From Zoomshop’s side:
- Configure the ADF endpoint in your Zoomshop admin (paste the DriveCentric intake address into the CRM configuration field)
- Send a test lead
- Confirm receipt in DriveCentric with correct source labeling and vehicle context
Typical timeline:
- Minute 0-5: Get the ADF intake address from DriveCentric
- Minute 5-10: Configure in Zoomshop admin
- Minute 10-15: Send test lead, verify appearance in DriveCentric
The variable is usually how quickly you can reach your DriveCentric account rep to confirm the intake address if it’s not already visible in your account settings. Most dealers have the integration live inside an hour.
How lead attribution works
The most common way dealer platforms break attribution is with source labeling. A shopper clicks your Google Ad → lands on your website → submits a form. That lead should be labeled with source = your website, campaign = your Google campaign, medium = paid search. Some website platforms strip UTM parameters between the landing page and the form submission. Some CRMs default to labeling every website lead as the platform’s own name instead of the dealership’s site. Result: attribution is broken by the time you look at reports.
Zoomshop preserves attribution end-to-end:
- Shopper lands on
yourdealership.com/inventory/vehicle-detail/2023-honda-crv-ex/?utm_source=google&utm_campaign=fall-sales - UTM parameters attach to the shopper’s session on your Zoomshop-powered site
- Shopper browses your inventory (UTMs preserved across page loads)
- Shopper submits a form on a specific vehicle page
- Zoomshop generates ADF/XML with: source = your dealership website, referring URL = the exact VDP, UTM parameters attached to source/campaign fields, vehicle context populated
- Lead lands in DriveCentric labeled as coming from your website, with the campaign that drove them
- Your DriveCentric AI agent engages via text; your DriveCentric reports show the lead attributed correctly to the Google campaign
This is what “closed-loop attribution” is supposed to mean. Most dealer platforms handwave this. Zoomshop makes it a first-class capability.
Questions dealers ask
Does Zoomshop work with DriveCentric?
Yes. Zoomshop routes leads generated on your VDPs, contact forms, and inventory pages directly to DriveCentric as standard ADF/XML — the same format DriveCentric accepts from AutoTrader, Cars.com, CarGurus, and every other lead source. No custom integration needed on the DriveCentric side; they parse the XML automatically and create a lead record with all fields populated.
What data lands in DriveCentric when a shopper submits a form?
Every ADF lead from Zoomshop includes: the shopper's name, email, phone, and any additional fields they filled in; the specific VIN and vehicle details (year, make, model, trim, stock number) they were viewing; the exact page URL that generated the lead; the timestamp; UTM parameters preserved from wherever the shopper originally arrived (Google Ads, Meta, direct, referral); and the lead source labeled as your dealership website. DriveCentric's CRM then creates the lead record with all of that context ready for your team.
How fast does the lead show up in DriveCentric?
Seconds. Zoomshop sends the ADF/XML to DriveCentric's intake address the moment the shopper hits submit. DriveCentric parses it and creates the lead record on their side within a few seconds. DriveCentric's AI response workflows (built-in texting, auto-follow-up) then fire immediately per your account's configuration — usually before the shopper has closed the browser tab.
Do UTM parameters and referring page make it into the DriveCentric lead record?
Yes. This is where a lot of dealer platforms silently break attribution. Zoomshop preserves UTM parameters through the shopper's full session — captured on the initial landing page, held across every internal navigation, and attached to the ADF/XML payload when they submit a form. DriveCentric ingests them into the lead record where they show up as source and campaign fields. You can trace a specific closed sale back to the specific campaign, ad set, and creative that generated it — the attribution loop your paid media reports depend on.
Does Zoomshop use DriveCentric's API or ADF/XML?
ADF/XML by default. DriveCentric supports both ADF (the automotive industry's standard email-based intake) and direct API pushes for enrichment partners. For website leads, ADF is more reliable — it's the same path that's been battle-tested for two decades and works with DriveCentric's existing routing, scoring, and workflow rules without any custom configuration. If your setup has specific reasons to prefer API (real-time enrichment, non-standard fields), that's available too.
What about DriveCentric's chat widget and AI agent — how do those work alongside Zoomshop?
DriveCentric's chat widget is a JavaScript snippet you paste into your site. Zoomshop supports drop-in scripts like DriveCentric's chat and AI agent as first-class integrations — they load correctly, don't conflict with the page's performance budget, and their conversations feed into the same lead record ADF creates. Your DriveCentric AI agent can engage a shopper via chat and have that conversation stitched to any subsequent form submission from the same visitor.
Can we run Zoomshop and our current website in parallel during a switch to DriveCentric?
Yes. DriveCentric's ADF intake accepts leads from multiple sources concurrently — your existing website, Zoomshop, and third-party marketplaces can all feed the same DriveCentric instance simultaneously. Common pattern for dealers switching website providers while also adopting DriveCentric: run both sites in parallel for a week or two, verify DriveCentric is receiving clean leads from Zoomshop, then cut over the domain.
What's the setup process?
Simple: (1) In DriveCentric, get your dealership's ADF intake email address (available from your DriveCentric account settings or your account rep). (2) In Zoomshop admin, paste the address into the CRM configuration for your dealership. (3) Zoomshop sends a test lead. (4) You verify it appeared in DriveCentric with the correct fields, source, and vehicle context. Total time: about 15 minutes end-to-end.
Ready to see how this works on your site?
Run the free grader to see how your current site scores on the criteria that matter for AI visibility, Core Web Vitals, structured data, and Google search fundamentals — or book a call to talk through your specific setup.