Technology
Four layers. One integration. No billboard. No gas pump. Read from the wire.
VideoEV is a CSMS-agnostic middleware that ingests OCPP 2.0.1 charging session events, resolves anonymous hardware identifiers to a vehicle profile when the Vehicle Identity Graph has coverage, runs a real-time ad auction, and closes the attribution loop via clean-room Amazon Marketing Cloud matching, without storing a raw vehicle identifier. That is Deterministic Physics-Based Targeting at the infrastructure level. No mobile pings. No billboard radius estimates. No Gas Station TV panel data.
End-to-End Stack
From charger plug-in to purchase attribution
CSMS Event
OCPP 1.6 · 2.0.1Charger fires an OCPP session event. VideoEV ingests it in real time across Driivz, AMPECO, ChargeLab, and EV Connect, normalized to a single payload regardless of source.
Identity Resolution
ISO 15118 · DeterministicThe EVCCID, an encrypted hardware identifier, is matched against the Vehicle Identity Graph. No VIN transmitted over OCPP. Where the graph resolves a session, it returns Make and Model plus (when the graph supports it) Trim and an MSRP proxy.
Ad Auction
OpenRTB 2.6 · Deterministic segmentsWhen the Vehicle Identity Graph resolves a session, the vehicle profile passes to the SSP as a targeting signal before the first ad slot fills. Buyers bid on resolved vehicle segments (Tesla, Porsche, luxury EV) through VideoEV's first-party auction, with a match-confidence class on every bid request. The auction uses the OpenRTB 2.6 spec for its bid protocol; today the closed VideoEV inventory network is the demand path (self-serve console + direct IO), with external DSP integrations (Amazon DSP, The Trade Desk, Vistar) on the roadmap. Unresolved sessions fall back to contextual-only inventory.
Attribution
Amazon AMC · Closed-loop · CookielessImpressions are matched to downstream Amazon purchase events via Amazon Marketing Cloud (AMC). Closed-loop attribution without a pixel, without cookies, and without third-party data sharing, from charging session OCPP event to verified Amazon cart conversion.
Universal Compatibility
One integration. Every network.
Every CSMS exposes a different API surface. VideoEV abstracts that complexity into a single normalized event stream, so your ad infrastructure never breaks when a network upgrades their platform.
Target CSMS platform · OCPP-compatible. Target bridge: OCPP 1.6 / 2.0.1 event ingest via native webhooks.
Target CSMS platform · OCPP-compatible. Target bridge: session lifecycle events via REST polling + push webhooks.
Target CSMS platform · OCPP-compatible. Target bridge: Cloud CSMS session data via OCPI-compatible event API.
Target CSMS platform · OCPP-compatible. Target bridge: direct certified network session ingest.
Vehicle Identity Graph
The charger reads the EVCCID. We resolve it.
Under ISO 15118, EV chargers never receive Make, Model, or VIN, only an encrypted hardware identifier called an EVCCID. VideoEV built the resolution layer that matches the EVCCID against the Vehicle Identity Graph before the first ad slot fills.
Resolution is deterministic where the graph has coverage. A match attaches Make and Model (Trim and Model Year where the graph supports it) plus an MSRP proxy from public trim / MSRP data, and the bid request carries a match-confidence class (High / Medium / Unresolved).
Read the full Identity Graph explainerPrivacy-First Architecture
Zero PII. Full attribution.
Raw vehicle identifiers are hashed at the point of ingestion. The original value is never written to disk, never logged, and never transmitted downstream. Attribution precision is preserved through the hashed token , without any PII leaving the origin system.
API Reference
The universal webhook schema
Every CSMS speaks a different dialect. VideoEV normalizes them into a single consistent payload, one integration for every network.
POST /v1/webhooks/session-event Authorization: Bearer <your_api_key> Content-Type: application/json { "event_type": "session_update", "session_id": "ev_sess_f7a2b4c", "hashed_vehicle_token": "sha256:a3f4b2c8d9e1f2a3...", "charger_id": "site_xyz_port_2", "current_soc_percent": 42, "estimated_dwell_time_mins": 35, "network_id": "evconnect_west", "timestamp_utc": "2026-03-08T14:22:33Z" }
{ "status": "queued", "ad_eligible": true, "matched_segment": "ev_buyer_high_intent", "recommended_creative_format": "video_15s", "estimated_inventory_window_mins": 35 }
Ad-Tech Architecture
Built to spec. Programmatic-ready.
VideoEV is built on 2026 programmatic standards (OpenRTB 2.6, VAST, IAB OMID). Today the platform is a closed inventory network: direct buys through the VideoEV console or direct IO with our media team. External DSP integrations are target paths on the roadmap.
Automated buying and selling of screen inventory, no manual IO required. VideoEV supports the OpenRTB 2.6 spec; external pDOOH buying paths are roadmap, not yet live. Current buying surface is the VideoEV self-serve console and direct IO with our media team.
VideoEV is currently a closed inventory network. Today's demand path is the VideoEV self-serve console and direct IO with media teams. External DSP integrations (Amazon DSP, The Trade Desk, Vistar Media) are target paths on the roadmap, not live production integrations.
VideoEV operates its own SSP layer, exposing charging-session inventory to its first-party auction. Sellers can set floor prices per station network, MSRP tier, or station environment.
Protocol Support
Pod bidding supported: multiple advertisers compete for individual 30-second slots within a single session. Each pod can hold up to 10 ad units, enabling layered campaigns across the session window. Full pod-bidding feature set is rolling out with pilot campaign ramp.
Video ad serving across all three surfaces. Supports interactive overlays, IAB OMID (Open Measurement) verification, third-party verification tags, and proof-of-play reporting. Individual verification-partner integrations roll out with pilot campaign ramp.
DSP Integration Roadmap
Target integration on the roadmap. Not a live production integration today. AMC clean-room attribution runs through direct VideoEV ↔ AMC plumbing, not through Amazon DSP.
Target integration via OpenRTB 2.6. Not yet integrated. VideoEV inventory is not buyable through TTD today.
Target DOOH exchange path. VideoEV inventory is not listed on Vistar today.
Additional DSPs and Direct IO available on request
Non-standard DSP onboarding handled case by case with our integrations team.
Enterprise Integrations
Built on the standards your stack already trusts.
No proprietary lock-in. Every layer of VideoEV speaks an open standard, so your DSP, ad server, and attribution platform plug straight in.
EVCCID, SoC, and session duration, direct from the charger. No API middlemen. The EVCCID feeds our Vehicle Identity Graph.
Standard OpenRTB 2.6 bid stream. Compatible DSPs can access inventory via the same spec; additional DSP paths are on the roadmap.
VAST 4.2 compliant. Drop in any video creative from any ad server. Full measurement support.
AMC-ready exposure export. Hashed impressions flow into the advertiser's own AMC instance for clean-room match against verified Amazon purchase records. Default measurement today is pixel-based; AMC surfaces once the instance is connected.
Vistar Media is a target DOOH exchange path. VideoEV inventory is not listed on Vistar today.
First-party Amazon audience sync. Retarget existing Amazon shoppers by vehicle segment and location.
Amazon Marketing Cloud · Closed-Loop Attribution
Ready to integrate?
Talk to our partnerships team about connecting your CSMS to the VideoEV middleware layer.
Platform Status
Where VideoEV is today.
VideoEV is in active pilot, not a fully productionized network. This strip is the single source of truth for the platform’s operational posture. If a page elsewhere reads as more productionized than this, trust this strip.