First-party automotive identity, without the records changing hands.
Nexus Motive holds resolved first-party identity built from real dealer touchpoints: website, chat, phone, lead, deal and repair order. Partners work with it through hashed matching and aggregate measurement rather than through a file transfer.
Automotive data is plentiful and mostly secondhand
Most automotive audience data available to buy is inferred: a browsing signal from a third-party site, a stale registration record, a modeled in-market score with no transaction behind it. It is abundant, it is cheap, and it degrades quietly because nothing in the chain observes an actual purchase.
The signals worth having sit in systems that rarely connect: the deal in the DMS, the repair order in the service lane, the trade appraisal, the conversation in the showroom. Those are first-party, transactional, and owned by retailers who have every reason not to hand them to anyone. How those sources resolve into one record is described on the platform page.
So the useful data exists but the usual commercial model for reaching it, which is a file moving from one party to another, is exactly the model the owner will refuse.
How a partnership actually works
Match without moving records
Identifiers are SHA-256 hashed before they leave the edge. Matching happens on hashes, so a partner can find overlap without either side handing over a plaintext customer file.
Outcomes, not individuals
Measurement is returned at the level of a segment, a campaign or a store. There is no export of individual customer records as part of a partnership.
Signals tied to a closed deal
Equity position, lease maturity, service lapse and lost-purchase status are facts derived from deals and repair orders, not modeled scores inferred from browsing.
No cross-tenant pool to buy
Each dealer tenant is encrypted under its own key and there is no combined graph sold back to the market. Any partnership works within that constraint, which is stated up front rather than discovered in diligence.
Governed before anything activates
Consent state, contact frequency and deletion requests are enforced across the graph. Suppression is applied before an audience is pushed, not reconciled afterwards.
Every figure traceable to its events
The record is event-sourced and append-only, so any number can be replayed back to the events that produced it. That is what a serious diligence process asks for.
Where Nexus Motive sits in the value chain
Nexus Motive is the first-party data source in these conversations, not the buyer. The identity graph is built from the dealer own touchpoints and connected into a single record with full-chain revenue attribution, which is a position very few participants in automotive occupy.
That shapes what a partnership can look like. We are not seeking enrichment to fill gaps in a thin file, and we do not resell customer records. The useful arrangements are measurement, verification and activation that respect tenant isolation, where the value moves without the records moving. The security posture behind that is documented on the technology page.
If a proposal requires a raw customer file to change hands, it is not something the architecture can do, and we would rather say that in the first meeting than the fifth.
How an evaluation runs
Scope on the constraint
We start from what cannot move: raw records, cross-tenant views, unconsented contact. Most designs get simpler once that is agreed in the first conversation.
Security review before commercials
Send the questionnaire early. Isolation model, key management, audit schema and deletion handling are answered before any commercial discussion, not after.
Bounded match test
A hashed overlap test on a defined scope establishes match rate and quality without either party exposing a customer file.
Measured pilot
A limited pilot with aggregate reporting on both sides, so the value is observed rather than modeled before anything scales.
What this role asks first.
Can we license or purchase the underlying customer records?
No. Dealer tenants are cryptographically isolated and the records belong to the dealer. Partnerships are built on hashed matching and aggregate measurement, which is a deliberate architectural constraint rather than a pricing tier.
What identifiers do you match on?
Deterministic keys first: hashed email, hashed phone, VIN and deal number. Inference fills gaps only under a confidence floor, and every merge is versioned and reversible.
How is consent handled across a partnership?
Consent state travels with the record and is enforced before activation. Deletion requests are honored across the graph within 30 days, including anything derived from the deleted record.
What does diligence look like?
Isolation model, per-tenant key management, the append-only audit schema, retention and deletion, and third-party penetration testing. We answer the security questionnaire before the first commercial call rather than after a contract.
Send the security questionnaire first.
We would rather establish what the architecture can and cannot do in the first meeting than the fifth. If a raw file has to move, we will tell you straight away.
No slidewareBook a walkthrough