Connected Services Subscription Revenue Isn’t Following Engagement

The auto industry has a monetization problem hiding inside its own metrics: Nissan‘s connected services subscription revenue, and that of most OEMs, is not keeping pace with rising customer engagement. Zheng Xu, Senior Connected Services App Product Owner at Nissan Motor Corporation, argues in a new analysis that engagement and willingness to pay are measuring different things entirely, and that conflating them is costing the industry real revenue.

The argument is structural, not tactical. OEMs have spent years optimizing for usage metrics, assuming that more interaction signals more perceived value. The data is increasingly pushing back on that assumption.

The Subscription Revenue Problem Engagement Can’t Solve

According to the JD Power 2026 U.S. OEM EV App Report, 64% of EV owners say they would not pay a fee for app access, even though 55% say the app had a major or moderate impact on their vehicle purchase decision. Customers value the app enough to let it influence a six-figure purchase, then refuse to pay separately for it. That is the gap Xu is describing.

His framework identifies three behavioral modes: discover, execute, and commit. In discover mode, customers browse and evaluate what is available. In execute mode, they perform a specific task: starting the climate control, checking vehicle status, finding a charging point. In commit mode, they recognize ongoing value and choose to keep paying.

The catch is that most connected ecosystems are optimized for the first two modes and largely neglect the third. Heavy usage of a remote-start or charging function can actually work against monetization: the more reliable the feature becomes, the more the customer perceives it as part of the car rather than a separate digital service. Familiarity breeds entitlement, not loyalty.

Xu introduces a second concept he calls the “decision compressor.” For most of a subscription period, customers use features without consciously evaluating their worth. In the final days before renewal, that latent judgment is forced into a single binary decision. The product experience may have spent weeks encouraging discovery. The renewal decision demands commitment. When no layer of the experience has helped the customer answer the question “is this worth paying for,” the default answer tends to be no.

Perceived Value Sits Below the Engagement Layer

The deeper problem is classification. Before a customer discovers, executes, or commits, they form a prior judgment: is this feature part of the car I already paid for, or is it a distinct service delivering ongoing value? If a customer categorizes remote climate control as a standard vehicle utility, increasing engagement reinforces that belief rather than correcting it. The monetization problem stops being a conversion problem and becomes a framing problem.

The JD Power data adds a layer of complexity here. 51% of EV owners who said the app influenced their purchase decision were first-time OEM app users, per the same report. As EV adoption widens the customer base, more buyers are arriving with no prior expectation of paying separately for connected features. The window to frame these services as premium and discrete is narrowing.

Nissan is simultaneously deepening its software investment. A partnership with AWS announced in December 2025 cut vehicle software test execution time by 75% and created a unified development environment for more than 5,000 developers globally. The company’s “Mobility Intelligence for Everyday Life” vision targets AI Drive technology adoption across 90% of future models, with the US, Japan, and China as lead markets. More capable software infrastructure does not automatically translate into more compelling subscription economics, but it does remove the excuse that the product cannot deliver.

Xu’s prescriptions follow from the diagnosis. OEMs should design for commitment rather than engagement: making the distinct value of a service visible at every interaction, not just at renewal. Feature frequency should not be treated as a proxy for willingness to pay; the behavioral signal that matters is whether the customer perceives the service as genuinely separate from the vehicle. And connected services should be managed as ongoing value relationships, not feature catalogs.

The strategic read is that the industry’s software buildout is solving the wrong problem at scale. Faster development cycles and broader model coverage increase the supply of connected features. What the JD Power data and Xu’s framework both point to is a demand-side failure: customers are not being helped to perceive connected features as worth paying for. Until the experience is explicitly designed to create that perception before the renewal window compresses the decision, rising engagement numbers will keep flattering dashboards while subscription revenue stays stuck.