Vehicle Identity Graph
The charger doesn't know what car just plugged in. We do.
Under ISO 15118, EV chargers never receive Make, Model, or VIN — only an encrypted hardware identifier. VideoEV built the resolution layer that matches it to a real vehicle profile and runs an ad auction against the result.
The gap every CPO is sitting on
A CPO running 500 stalls processes thousands of charging sessions a day. Each one contains an EVCCID. Without a resolution layer, that identifier is useless — the CPO has no idea if they just charged a Porsche Taycan or a Chevy Bolt.
That gap is why high-CPM vehicle-targeted advertising hasn't existed at EV charging networks until now. The hardware was always there. The identity layer wasn't.
How Resolution Works
How a hardware ID becomes a vehicle profile
Charger receives an anonymous identifier
When an EV connects, the charger receives an EVCCID — an encrypted hardware identifier derived from the vehicle's MAC address. ISO 15118 automotive privacy standards mean Make, Model, and VIN are never transmitted to public infrastructure.
OCPP 2.0.1 · ISO 15118VideoEV ingests the session record
The full OCPP session record — EVCCID, station ID, connector type, session timestamp, and energy delivered — is pushed to VideoEV in real time. The identifier alone tells you nothing. That's the gap every CPO is sitting on.
Real-time ingestionDeterministic matching against the identity graph
The EVCCID is matched against our Vehicle Identity Graph — a cross-reference of hardware identifiers, CPO session histories, and OEM data. No inference. No probabilistic modelling. A confirmed match attaches a vehicle profile to the session.
Deterministic · No panelsSession-resolved vehicle profile attached
The resolved profile includes Make, Model, Trim, Model Year, and MSRP proxy. This becomes the targeting signal for the ad auction running on that session — passed to the SSP in real time before the first ad slot is filled.
Make · Model · MSRP proxyWhat Gets Resolved
Six signals. One OCPP identifier.
One confirmed match. One vehicle profile in the SSP bid request — before the first ad slot fills.
Technical Questions
How it actually works
Why don't chargers just read the VIN?
They can't. ISO 15118 — the protocol that governs EV-to-charger communication — does not expose VIN, Make, or Model to charging infrastructure. What passes over the wire is a cryptographic identifier. This is intentional: automotive OEMs treat vehicle identity as proprietary.
What's an EVCCID?
Electric Vehicle Communication Controller ID. It's a hardware-level identifier derived from the onboard communication chip's MAC address. It's consistent across sessions for the same vehicle, which is what makes deterministic matching possible.
Is this probabilistic matching?
No. Probabilistic models infer identity from behavioural signals — browser history, app data, lookalike modelling. Our matching is deterministic: the EVCCID is a stable hardware identifier that maps to one vehicle. When a match is found, it's confirmed, not estimated.
What happens when there's no match?
The session still runs. Unresolved sessions are served contextual inventory — station type, location, time of day — without vehicle-level targeting. Match confidence is passed with every bid request so buyers can set floor prices accordingly.
The first Vehicle Identity Graph built for programmatic media.
If you run a charging network and want to understand what identity data you're currently leaving on the table, talk to us.