Verified identity on anonymous traffic. No form fill, no phone call, no chat — while the buyer is still in-market.
This is a service we operate for the store — not a piece of software a dealer logs into and runs alone.
Match rate on Google & Meta audience uploads
Verified individuals in the identity graph WebID resolves against.
A pixel on the dealer site de-anonymizes the people visiting it — without a form fill, a phone call, or a chat.
Website visitor identification (also called anonymous visitor identification) is the process of recognizing who is on your website when they don't identify themselves. The vast majority of dealership site traffic is anonymous — people research for days or weeks across multiple visits and never submit a lead. Identification closes part of that gap by resolving a portion of those anonymous sessions to a real person or household, then making that record actionable in your CRM and ad platforms.
Verified identity — who the shopper is, what they’re shopping, and how to reach them — pulled from real-person records, not modeled signal. Resolved audiences upload to Google and Meta at 95%+ match rates for deterministic targeting on the buyer, not a lookalike of one.
WebID sits underneath every other surface DSRPTV operates — paid media, communications, data and identity. It is the layer that makes those services deterministic instead of probabilistic — and it ties the spend back to the DMS.
Two distinctions matter up front, because vendors blur them:
Company-level ID (the classic B2B use case) maps an office IP to a business. It's close to useless for a dealer — you don't sell to "Acme Corp," you sell to the person browsing your F-150 inventory from their couch. Person-level (or household-level) resolution is what auto retail needs.
Some tools identify net-new anonymous visitors; others enrich the contacts already in your CRM. They're different jobs and you should know which one a vendor is actually selling.
One shopper, six moments, one week. Today most dealers find out at the very end — if the shopper calls this store at all. WebID resolves them on the first visit.
A form fill. A phone call. A walk-in. By the time the dealer has identity, the shopping window has closed — and the conversation that mattered already happened somewhere else.
WebID resolves the visitor on the lot — digitally — before the next move is made. The dealer reaches out while the buyer is still in-market, not after a competitor has already closed. Real-time triggers on the moment of intent — not lagging, modeled, or conversion-dependent signals.
Illustrative shopper. Timing and actions show how the program works, not a specific dealer's results.
The mechanism is the same across credible platforms, and understanding it is how you see through a sales pitch.
A lightweight first-party JavaScript tag sits on your site. When a visitor loads a page, it captures the signals available in that session — a first-party cookie ID, device characteristics, IP, and on-page behavior (which VDPs, how long, payment calculator, trade-in tool). The shopper never sees it and never interacts with it.
Those signals get matched against an identity graph — a large database that links cookies, device fingerprints, and hashed identifiers to verified person records. If the match clears a confidence threshold, the graph returns an identity.
A resolved shopper — with contact data and the behavioral context of what they looked at — pushes into your CRM and/or builds an ad audience, so the BDC can follow up and retargeting can serve the exact inventory they viewed.
This is the hard part, and it's where platforms diverge:
DMS records, CRM contacts, and first-party data enriched with verified fields and current in-market signal — then activated across email, SMS, paid audience uploads, direct mail, and outbound. The dealer's own book, sharpened.
First-party, deterministicMost site visitors leave without converting. WebID gives the dealer verified identity on the people who browsed inventory without filling out a form — referencing the exact vehicles, trims, and price points they were shopping, across email, SMS, Google, Meta, and direct mail.
In-market, not in-memoryCustom audiences built from verified identity — not probabilistic signal. Segment by vehicle interest, price range, equity status, geography, or buying cycle. Uploaded to Google and Meta at 95%+ match rates for deterministic targeting — and conquest audiences ordered on demand.
Verified, not modeledAcross the industry, probabilistic tools on narrow graphs land roughly in the 5–15% range, while deterministic tools with a strong owned graph reach 30–40%+ on favorable traffic — and consumer (B2C) traffic, ad-blocker-heavy traffic, and mobile-first traffic generally sit toward the lower end. The 95%+ figure measures something different: of the shoppers already resolved, the share Google and Meta recognize when the audience uploads.
This is where most of the industry oversells, so here's the straight version. Match rate is the share of anonymous visitors a tool can resolve, and it varies widely with traffic and method.
Any vendor should give you a match rate on your own traffic, in writing, and should be able to talk about accuracy and false-positive rate, not just coverage.
DSRPTV runs visitor identification as a managed capability inside the data and identity layer of a dealer's program.
You can buy a visitor-ID tool, or you can have the capability run for you. The distinction matters more in auto retail than most places.
You license a pixel and a dashboard. You're responsible for installing it, tuning match thresholds, integrating the CRM, building the follow-up cadences, and — critically — keeping the whole thing compliant. The tool is only as good as the operation around it, and a resolved shopper sitting unworked in a dashboard sells exactly zero cars. (More on what to look for in website visitor identification software.)
The capability is run as part of your marketing program: identification deployed and tuned, records routed into your CRM with the behavioral context attached, retargeting audiences built, and follow-up wired to your BDC — with compliance handled deliberately rather than left to chance. For most stores, the constraint was never access to a tool; it was the operational lift of turning resolved visitors into worked opportunities.
Website visitor identification reveals the in-market shoppers behind anonymous sessions on your dealership's site — the ones browsing VDPs, building payments, and checking trade values who never call and never fill out a form. A first-party pixel matches those sessions against an identity graph; the resolved shoppers sync to your CRM so your team and your ad campaigns can act on them. For a dealer, the point isn't generic lead-gen. It's recognizing high-intent buyers you were already paying to attract, and reaching them on real buying signals — lease-end, warranty expiration, service defection — before they buy somewhere else.
Generic visitor-ID tools are built for B2B software companies trying to name the account behind an office IP. Auto retail is a different problem: you're identifying individual consumers, on consumer devices, acting on consumer buying cycles. This page explains how the technology actually works, where it's honest and where it over-promises, how dealers use it, and the compliance terrain you have to respect.
Generic B2B visitor-ID is about naming an account so a rep can prospect. Dealer visitor-ID is about catching a consumer mid-purchase. The value lives in the buying signals auto retail uniquely has:
Which VINs and trims they viewed, whether they ran payments, whether they used the trade tool. That tells your team what to lead with — not "someone visited," but "this person is shopping a loaded Highlander and checked their trade twice."
A shopper coming off a lease is the single most winnable repeat customer you have. Identification surfaces them while they're researching, before the competing store's conquest offer lands.
Identity data tied to your service base helps you spot customers drifting to the aftermarket and pull them back into the drive with the right offer — fixed-ops revenue you're otherwise leaking.
Resolved in-market shoppers who looked but didn't buy become a retargeting audience served the exact inventory they viewed.
This is why a generic tool underperforms for a dealer: it's optimized to identify businesses, not to read the buying signals that decide whether a person buys a car this month. The automotive application is the whole point.
See how identification feeds retargeting and paid media → Back to the dealership marketing program
The practical takeaway: a credible visitor-ID program is built around consent, clear privacy disclosures, honored opt-outs, vetted data sources, and contracts that bind your vendors — not around blasting every resolved record.
A program that ignores this doesn't just risk penalties; it burns your domain reputation and your customers' trust. We build the identification layer to be defensible, and we expect your compliance team to review it.
Because a dealership arranges or facilitates financing (or leases for more than 90 days), the FTC treats it as a financial institution subject to the GLBA Safeguards Rule and Privacy Rule. The Safeguards Rule requires administrative, technical, and physical protections for customers' nonpublic personal information (NPI); the Privacy Rule governs notice and the sharing of NPI with third parties. The FTC issued auto-dealer-specific FAQs in 2025 reaffirming this, and the amended Safeguards Rule also carries a breach-notification obligation. Any data program touching customer information has to live inside that framework, including diligence and contracts with the vendors that handle the data.
Resolving a shopper's identity is one thing; calling, texting, or emailing them is another, and each channel has its own rules:
Autodialed or prerecorded telemarketing calls and texts require prior express written consent. Note a recent shift here: the FCC's "one-to-one consent" rule was vacated by the 11th Circuit in January 2025, and the FCC reinstated the prior prior-express-written-consent standard in 2025 — so the heightened one-to-one requirement is not in effect, but the underlying consent obligation very much is. A separate rule also strengthened consumers' ability to revoke consent.
Commercial email carries its own requirements — accurate headers, a clear opt-out, and honoring it.
A growing list of state laws (California's CPRA among them) add obligations like honoring the Global Privacy Control signal and offering opt-outs of certain data sharing. GLBA-covered data is often carved out, but marketing data frequently isn't — so the state-law layer can still apply.
This is the part responsible operators lead with, not bury. Identifying shoppers and contacting them sits on top of real regulation, and the rules differ by how you reach out. None of this is legal advice — your dealership's compliance and legal team should sign off on any program — but here's the terrain.
It's the process of recognizing in-market shoppers behind anonymous website sessions — visitors who browse but never submit a lead. A first-party pixel captures session signals, an identity graph resolves a portion of them to real people, and the resolved records sync to your CRM and ad platforms so you can follow up and retarget.
A first-party JavaScript pixel captures signals from each session (cookie ID, device, IP, on-page behavior). Those signals are matched against an identity graph that links identifiers to verified person records. If a match clears a confidence threshold, the system returns an identity and pushes it — with the shopper's behavioral context — into your CRM or a retargeting audience.
It can be, when run responsibly — but it sits on top of real regulation. Dealers are financial institutions under the GLBA (Safeguards and Privacy Rules), outreach by call or text is governed by the TCPA's consent rules, email is governed by CAN-SPAM, and state privacy laws may apply. This isn't legal advice; a compliant program is built around consent, disclosures, honored opt-outs, and vetted vendors, and your legal team should review it.
It varies with your traffic and the method. Probabilistic tools on narrow data sit roughly in the 5–15% range; deterministic tools with a strong owned graph reach 30–40%+ on favorable traffic, with consumer and mobile-heavy traffic trending lower. More important than the headline number is accuracy — a high match rate full of false positives wastes BDC time and pollutes your database. Ask any vendor for a match rate on your own traffic, in writing.
To catch high-intent shoppers mid-purchase and act on buying signals: surfacing lease-end customers before a competitor's offer lands, pulling service-defecting customers back into the drive, retargeting shoppers with the exact inventory they viewed, and giving the BDC context-rich records to follow up instead of cold lists.
Software gives you a pixel and a dashboard but leaves installation, tuning, CRM integration, follow-up, and compliance to you — and a resolved visitor nobody works sells nothing. A managed service runs the capability as part of your marketing program: deployed, tuned, routed to your CRM with context, wired to retargeting, and kept compliant. For most stores the constraint was operational, not access to a tool.
Resolved records push into your CRM through an integration, carrying the shopper's contact data plus behavioral context — the VINs and trims viewed, payment or trade-tool activity — so follow-up is informed rather than generic. The same data can build retargeting audiences in your ad platforms.
