Most OEMs collect connected vehicle data, but only 40% of OEMs and suppliers run an automated pipeline from that data to a deployed update, according to the Capgemini Research Institute. Its July 2026 survey of 800 automotive executives found that 81% of OEM and supplier executives collect vehicle telemetry, and 64% say what they learn mainly informs the next vehicle programme.
Explore3, the connected vehicle analytics product from Cubic3, gives OEMs early adoption signals and usage behaviour from vehicles in service. This post sets out where the data stalls, according to Capgemini, and what OEM teams can measure to close the gap.
What connected vehicle data reaches vehicles in service
Collection is widespread
Among OEM and supplier executives in the Capgemini survey, 81% collect connected vehicle telemetry, 76% use dealer service network data and 72% capture insights from over-the-air update interactions. 68% say the data they capture after launch is enough to reflect real-world customer experience patterns, but only 54% have built the capabilities to turn it into action.
Over-the-air updates mostly deliver content
The delivery channel is broad, and what travels over it is narrow. 84% of OEM and supplier executives deliver updates for vehicle data security and 78% for navigation and traffic services. Updates that change driving functions such as braking or suspension reach 36%, and updates for assisted or autonomous driving reach 30%. Capgemini sums it up this way: “Vehicles receive content. They do not yet receive behavior.”
Udo Lange, Global Head of Digital Engineering and R&D Transformation at Capgemini Invent, says connected products and over-the-air updates “create a real-time feedback loop between engineering, product performance, and customer experience.” The survey shows that loop is only partly closed.
Analysis still leans on history
For vehicle performance and usage data, 39% of organisations run advanced analytics on historical data and 30% analyse it in real time, while 11% collect it without analysing it. Connected services and cockpit data is further along: 40% use real-time analysis and 15% collect it without analysing it. Only 53% have clear decision processes for which insights from vehicles in the field require action.
Explore3 data from [OEM programme and reporting period] shows that [METRIC: approved source required] of vehicles that used a connected service in their first 30 days were still using one at day 90.
How OEMs can close the feedback loop
Capgemini proposes one test for progress: the share of what is learned from vehicles in use that reaches vehicles in use. Today 40% of OEM and supplier executives run an automated pipeline from vehicle data to deployment, and 35% have governed or fully embedded field learning in the backlog for the current fleet.
Baseline three lifecycle measures
The report recommends baselining three times for each programme within a quarter. Feedback-to-decision time is how long it takes to turn insights from testing, telemetry, customer feedback or warranty data into an approved engineering decision. Decision-to-release time is how long it takes to deploy that decision as a software update, design change or product release. Release-to-value time is how long a released feature takes to deliver a measurable benefit in the field. Capgemini puts feedback-to-decision first, because nothing downstream of an undecided insight can be fast.
WEBINAR
How to Stop Fleet Spend Leakage & Regain Cost Control
Fleet spend leakage is eroding your margins across freight and logistics operations. Learn how to regain control of your fleet spend with this free on-demand webinar now.
Start with how drivers use connected services
Connected services show release-to-value within weeks, because adoption and repeat use show whether a feature reached drivers and stayed in use. Explore3 gives OEM teams that view of adoption signals and usage behaviour, so decisions about what to change or retire rest on what drivers did. A connected vehicle only produces usage data once its services are activated, which we cover in how activation at delivery affects connected car revenue.
Questions OEMs ask about connected vehicle data
What counts as connected vehicle data?
Connected vehicle data is information that vehicles in service send back to the OEM. Capgemini lists telemetry, battery health, software diagnostics, over-the-air update data, feature usage patterns and charging patterns. Explore3 covers adoption signals and usage behaviour from connected services.
Why do OEMs struggle to act on connected vehicle data?
The gap sits in the process behind the data. Capgemini found that only 55% of OEM and supplier executives consolidate customer feedback and vehicle data into a unified view, and only 53% have clear decision processes for which insights require action.
How can an OEM tell whether a connected service reaches drivers?
Activation and repeat use are the two signals: whether a driver switches a service on, and whether they keep using it. Explore3 shows OEM teams which connected services drivers activate and keep using, so the next change rests on observed behaviour.
