Connections
Three things from you. Nothing that runs the store.
Your public domain, your published inventory feed, and one pixel on your vehicle pages. Zero DMS or CRM passwords.
What Zumbay needs
Your domain, your feed, one pixel.
01 · DOMAIN
Public website address
Every vehicle link is verified against your domain so shoppers always land on your own site, never a marketplace.
02 · FEED
Published inventory feed
A scheduled CSV/XML URL re-checks every VIN daily. A one-time CSV, XML, or vAuto-style export works to start.
03 · PIXEL
One line on vehicle pages
Placed once on your VDP template to record the referring assistant, the VIN, and organic vs. paid.
What Zumbay never asks for
Counting ends at the vehicle page, so store systems stay closed.
- No DMS login: CDK and Reynolds are never connected; inventory comes from your published feed.
- No CRM login: Zumbay never reads customer records or lead logs.
- No sold reports: Attribution closes on the vehicle page by VIN.
- No vAuto API: Export files are read directly without API credentials.
- No website admin login: Your web provider places the single pixel snippet once.
3 THINGS CONNECTED
- Public website domain
- Published CSV / XML feed
- 1 pixel on vehicle pages
NEVER TOUCHED
- No DMS login or API
- No CRM or customer list
- No sold reports or deal files
- No site admin password
How assistants connect
Assistants reach Zumbay, not your systems.
- Published four ways: machine-readable vehicle pages, structured data,
/llms.txt, and MCP/actions endpoints. - Scoped read-only keys can be rotated or revoked by your team at any time.
- Every match returns the tagged vehicle-page URL on your own domain.
