ExplainerCRM & Data27 Jul 2026 · 17 min read

Amperity Customer Data Cloud: The 2026 Roadmap Bet on Real-Time Context and Identity AI

Amperity customer data cloud is betting on real-time customer context and identity resolution to solve the CDP problem.

Amperity is betting its future on real-time customer context and identity resolution AI rather than suite size. Three 2026 scorecards and a July product release now tell a more mature, but still uneven, story about whether that bet is paying off.

The customer data platform market is in an odd place right now, and for once, that's actually useful. Gartner's 2026 Market Quadrant for CDPs really shook things up.

Salesforce was the quadrant's only Leader. Tealium and Treasure Data fell into the Challenger group, while ActionIQ, Redpoint Global, mParticle, and Zeta Global disappeared from the report. Amperity held its Niche Player position. IDC then gave the company a very different verdict, naming it a Leader among AI-enabled CDPs for B2C brands. Snowflake also placed Amperity among its Data and Identity leaders.

So buyers now have three scorecards telling three slightly different stories, none of which fully answer the question of where Amperity customer data cloud, and the CDP market is really heading.

Dive deeper, and the answer looks bigger than profile unification. Amperity is pushing toward real-time customer context, agent-ready customer data, identity resolution AI, lakehouse control, predictive models, and financial measurement. July's Summer Release moved the MCP Server to general availability and added a clearer route from unified profiles into recommendations, propensity audiences, and paid media analysis. So, what's next?

TL;DR: How Strong Is Amperity's 2026 Roadmap?

TL;DR

Gartner kept Amperity in the Niche Player box, with questions around retention and consumption pricing. IDC rated it as a Leader for AI-enabled CDPs, while Snowflake praised its Data and Identity capabilities.
The core claim is identity: Stitch, per Gartner analyst Lizzy Foo Kune's January 2026 Magic Quadrant report, reportedly uses up to 45 AI models to resolve difficult identity problems, the foundation every other roadmap piece depends on.
The July shift is meaningful: Amperity's MCP Server is now generally available, while Recommended Actions, Event Propensity, and Paid Media Measurement push the platform further from profile building into action.
The honest gaps have moved: real-time Stitch is still absent, BYOC's production status needs checking by platform, and consumption pricing requires usage scenarios before anyone signs.

Why Is Amperity Both a Gartner Niche Player and an IDC MarketScape Leader?
What Is an AI-Ready Customer Data Platform, and Where Does Amperity Fit?
What Changed in Amperity's 2026 Roadmap?
How Does Real-Time Customer Context Work in the Amperity Customer Data Cloud?
Does Amperity's Lakehouse Roadmap Solve Enterprise Data-Control Concerns?
How Should Enterprises Measure Return on Customer Data?
Is Amperity a Strong Customer Data Platform Heading Into 2027?
FAQs

Why Is Amperity Both A Gartner Niche Player and an IDC MarketScape Leader?

Amperity’s Niche Player position in Gartner’s Magic Quadrant reflects its narrow focus and commercial performance, while IDC and Snowflake reward its identity and AI-readiness more directly.

Amperity's position as a niche player in the Gartner Magic Quadrant makes sense, it does have a narrow focus on identity resolution and data-engineering architecture. Still, IDC seems to see the bigger picture, viewing the underlying technology as the foundation modern enterprises need for unified data.

Gartner was strict with its Magic Quadrant this year. We only ended up with one leader, one visionary (Adobe), and a handful of Challengers and Niche Players. ActionIQ, Redpoint Global, mParticle, and Zeta Global dropped out after missing Gartner's updated inclusion bar around CDP customers and contract value.

Tealium's fall into Challenger territory says plenty about how Gartner now reads this market. Slower growth and weaker customer acquisition outweighed the comfort of an enormous connector catalog. Integration breadth can't disguise a roadmap that has lost pace.

Amperity received a warmer reading from IDC. The MarketScape report praised its identity foundation, marketer usability, and ability to support operational work across the business. Snowflake also named Amperity a Data and Identity Leader in research based on more than 11,500 customers and partners, per the fifth annual Modern Marketing Data Stack report's usage analysis (Snowflake fiscal year 2026, Feb. 2025 to Jan. 2026).

The technology wins praise from IDC and Snowflake. Gartner is less convinced by the business around it. Amperity has a solid product case, though cost and commercial resilience still need scrutiny.

Scorecard / Verdict on Amperity / What Buyers Should Press On

Scorecard	Verdict on Amperity	What Buyers Should Press On
Gartner Magic Quadrant (26 Jan 2026)	Niche Player, held from last cycle	Net revenue retention and consumption-pricing risk before signing
IDC MarketScape	Leader among AI-enabled CDPs for B2C brands	Validates the technology; says nothing about commercial risk
Snowflake Modern Marketing Data Stack Report	Named a Data and Identity Leader	Drawn from Snowflake's own partner ecosystem, not an independent audit

Key Takeaways

Gartner scores far more than the product itself. Amperity's Niche Player label also reflects its market reach and commercial performance.
IDC and Snowflake reward Amperity's identity, AI-readiness, and data architecture more directly than Gartner's broader market lens.
Weaker net revenue retention and consumption-pricing uncertainty remain the commercial questions buyers should press hardest.

What Is An AI-Ready Customer Data Platform and Where Does Amperity Fit?

An AI-ready CDP needs current, governed identity data, and Amperity is betting on a governed context layer that multiple AI tools can query rather than one enterprise suite.

An AI-ready CDP gives the business a trusted answer to a basic question: "Who are we dealing with?" That answer has to reflect the latest data and the customer's permissions, rather than whatever record happens to be easiest to retrieve.

Identity data has to be current, governed, and traceable wherever it lands, whether that's an AI assistant, loyalty platform, service workflow, or campaign tool. Stitch is Amperity's strongest answer.

Gartner's January 26, 2026 CDP Magic Quadrant, led by analyst Lizzy Foo Kune, says the technology uses up to 45 AI models for tough identity resolution. That gives buyers a clear test across shared households, changing devices, patchy identifiers, and split online and in-store behavior.

The wider market is splitting in two directions. Platformization favors an enterprise suite such as Salesforce, Adobe, or Oracle, where the CDP becomes another service inside a larger application estate. Agentification treats the CDP as a governed customer-context layer that several AI tools and operating teams can query.

Amperity is pursuing the second route. It wants to give AI systems access to identity, behavior, predictions, audiences, and activation without forcing the entire business into one front-office suite. That position will appeal to enterprises with a mixed technology estate, although it leaves Amperity with more to prove around interoperability and commercial value.

Databricks makes the contest harder, though. CustomerLake pushes an AI-native CDP model from inside the lakehouse, forcing Amperity to prove its identity layer and action tools justify a distinct customer intelligence platform.

Key Takeaways

Platformization favors suite consolidation; agentification favors a governed context layer that can serve several AI tools and operating teams.
An AI-ready CDP needs current identity, permissions, lineage, and cost controls before the assistant or agent layer becomes useful.
Databricks CustomerLake increases the pressure on Amperity to prove why a separate customer intelligence layer is worth buying.

Learn more about how to fix the data gaps in your analytics model here.

CX Awards 2026 Categories Announced

CX Today has announced all 25 categories for the CX Awards 2026, recognizing excellence across customer engagement, contact center, analytics, and AI-powered CX platforms.

Explore the full CX Awards 2026 category list

What Changed in Amperity's 2026 Roadmap

Amperity’s 2026 roadmap has moved from building a cleaner Customer 360 into making that context usable in the moment, with its MCP Server now generally available.

Amperity's roadmap has moved beyond building a cleaner Customer 360 into making customer context usable when a decision needs to happen, then feeding the result back into the platform.

The May 2026 launch set out that operating model. Identity, history, and live behavior sit in a shared context layer. Recommended Actions, now in public preview, identifies an opportunity, a user or AI client chooses what to do, and Real-Time Activation executes the response.

In July 2026, Amperity turned the heat up, making its MCP Server generally available. It runs as a hosted, multi-user service and connects Amperity with MCP-compatible clients including ChatGPT, Claude, and Microsoft Copilot Studio. As of the July 2026 Summer Release, over 200 tools were already available, covering work such as querying data, inspecting identity resolution, building segments, and running activations or journeys.

There's still risk, of course. An external AI client may receive customer data or trigger actions through Amperity, so buyers still have to decide which clients are approved, which tools users can access, and whether write operations should be permitted. Amperity's public documentation doesn't state what a connected AI client retains or logs after a query, or for how long. That's a term buyers will need to negotiate directly rather than find published anywhere today.

Plus, Amperity's Event Propensity model now estimates whether a customer will complete a chosen revenue-generating event within the next 30 days, such as joining a loyalty program or making another booking. It can recommend an audience size or rank customers so marketers can select the highest-propensity group.

Propensity scoring itself isn't new to the category: Salesforce's Einstein Engagement Scoring and Adobe's Customer AI have both offered predictive-audience creation from propensity scores for several release cycles, so this reads less like Amperity pulling ahead and more like it closing a table-stakes gap against suite competitors.

We've also seen updates to Paid Media Measurement & Optimization features. Meta and Google performance data can sit beside customer information in Amperity's Customer 360 database, with daily refreshes and roughly a year of history loaded during the initial setup.

Marketers can ask AmpAI about ROAS, CPA, CTR, CPM, and CPC in plain language rather than writing SQL. That gets customer data closer to budget decisions, with two catches. The daily refresh won't suit teams moving spend within hours, and Amperity hasn't disclosed enough about the attribution model behind its answers.

Key Takeaways

Customer Data Agent cuts the analyst wait by letting marketers explore data and build audiences in ordinary language.
The generally available MCP Server connects governed customer context with AI clients such as ChatGPT, Claude, and Microsoft Copilot Studio.
Amperity's pCLV and product-affinity models can send results into Databricks, Snowflake, or BigQuery.

How Does Real-Time Customer Context Work in Amperity Customer Data Cloud?

Amperity can recognize activity against an identity-resolved profile and trigger a response in sub-second time, but Stitch still rebuilds the underlying identity graph in batch.

Amperity combines an established Customer 360 profile with behavior arriving during the live session. A browse, login, abandoned cart, or completed purchase can change what the customer sees while the interaction is still underway.

There is an important limit. Amperity can recognize activity against an identity-resolved profile and trigger a response in sub-second time. Stitch still rebuilds the underlying identity graph in batch.

There's a difference between identity resolution and identity recognition. Stitch works out which records belong to the same person and creates the durable profile. The real-time layer then matches a current visit, transaction, or app session to that existing profile and uses the latest behavior to trigger a response.

A customer can browse, abandon a cart, make a purchase, or change loyalty tier, with that event added to the live profile while the intent is still useful. The platform can then adapt a journey or suppress an irrelevant offer after conversion.

What it can't do yet is rebuild the full identity graph in the same live window. A deeper change involving a new identifier, household relationship, or conflicting record may wait for the next Stitch process. That limitation doesn't collapse the real-time proposition. It defines the boundary buyers need to test. Ask which events update immediately, how anonymous behavior becomes attached to a known profile, when identity changes are reconciled, and how quickly each destination can act.

That both the May and July 2026 releases advanced activation and action layers while leaving Stitch's batch cadence untouched is itself a priority signal. Amperity appears to be spending its engineering effort on making existing identity output more usable rather than on re-architecting resolution itself, likely because the multi-model matching approach depends on the reconciliation window batch processing provides. Buyers should treat a move to real-time Stitch as an unscheduled, distinct roadmap item rather than an assumed extension of current momentum.

Real-time personalization still depends on the destination. A web page may respond instantly while email and paid-media tools lag behind. The customer feels the delay at the slowest handoff.

Key Takeaways

Personalization can happen in real time, while Stitch continues resolving the full identity graph in batch.
Amperity supports real-time recognition and sub-second responses, while Stitch remains a batch identity-resolution process. Buyers need to test the entire path from signal to destination.

Does Amperity's Lakehouse Roadmap Solve Enterprise Data-Control Concerns?

Amperity’s Bridge, Bring Your Own Storage, and Bring Your Own Compute reduce data-movement concerns, but BYOC remains preview-stage for Databricks.

Partly. And that "partly" is doing a lot of work. Amperity Bridge allows enterprises to share data with Databricks, Google BigQuery, and Snowflake without maintaining another set of copied tables. Bring Your Own Storage keeps persisted customer data in the enterprise's own AWS or Azure environment.

Bring Your Own Compute goes further by running selected Amperity workloads on the customer's Databricks compute, keeping the data inside the enterprise environment.

BYOC is only in preview for Databricks for now, but Snowflake remains part of Amperity Bridge and secure data sharing.

Data teams keep tighter control over where sensitive information lives and where it is processed, while Amperity handles work such as identity resolution and segmentation. Companies with committed Databricks spend may also be able to use capacity they're already paying for.

The tradeoff is maturity. The concrete test isn't a question list, it's a single scenario: pick one workload already running on committed Databricks spend, and ask Amperity to show it executing there today, in production, not on a roadmap slide. Preview status means the honest answer may still be "not yet," and that gap between committed spend and current capability is exactly what support terms during preview need to cover.

Don't assume one lakehouse integration proves the rest. Amperity may work smoothly with Databricks while another warehouse brings different limits or extra setup.

Key Takeaways

Bridge supports zero-copy data sharing across Databricks, BigQuery, and Snowflake, while Databricks BYOC is still in preview.
The lakehouse roadmap reduces data-movement concerns, but buyers still need workload-level answers on availability, governance, performance, and platform coverage.

How Should Enterprises Measure Return on Customer Data?

Enterprises should test identity resolution against difficult production scenarios and treat Amperity’s own ROI figures as a starting hypothesis, not a promised return.

Start with what happens when the data's wrong. Ask Amperity to resolve identities without a reliable shared key. Use households where two people share an address, customers who switch devices, and records where consent differs across source systems. Buyers should be able to inspect why records matched, what changed during Stitch, and how false matches can be corrected.

Then test the real-time claim as a sequence. Which events are processed live? Which attributes depend on the next batch run? How quickly does recognition happen, and how long does the chosen destination take to respond?

MCP requires its own governance review, too. Decide which AI clients can access Amperity, which tools they can call, and whether users should be allowed to create or change operational assets. More than 200 tools create considerable scope for useful work, along with a larger permission surface to manage.

The connected AI provider also sits outside Amperity's direct control. Its data handling, retention policy, and model-governance terms belong in the same assessment as Amperity's authentication and role-based permissions.

The financial conversation should run beside the technical one. Amperity's Return on Customer Data framework scores maturity from 0 to 100 across eight dimensions covering business outcomes, technical capabilities, and cross-cutting enablers.

Its internal model, published in Amperity's "How to Measure ROI on Customer Data" report (May 20, 2026), estimates that a representative enterprise could add $14.7 million in annual revenue moving from Marginal to Stable maturity, another $24.3 million moving to Best in Class, and a further $34.6 million on reaching Transformational status. Amperity says roughly ten enterprises had completed full ROCD assessments as of mid-2026, with five to eight more queued. Those figures illustrate Amperity's methodology. They aren't promised customer returns.

Key Takeaways

Evaluate identity, real-time performance, MCP governance, and destination latency using difficult production scenarios rather than controlled demonstrations.
Treat Amperity's ROCD figures as a starting hypothesis. The buying case should be rebuilt around the enterprise's own costs, margins, usage volumes, and measurable results.

Is Amperity a Strong CDP Pick Heading into 2027?

The verdict: Yes, but position it carefully. Amperity's case rests on resolving identity well and proving that better customer context changes revenue or cost, not on suite gravity or lakehouse control.

Amperity's strongest argument is its attempt to become the trusted customer-context layer behind enterprise CRM, marketing, service, analytics, and AI. Stitch gives it a serious identity foundation. Real-Time Profiles and Activation make that foundation usable during live customer moments.

The Customer Data Agent, MCP Server, Recommended Actions, and predictive models push the platform closer to decision-making and execution. The July release improves the maturity story because MCP is generally available, while Event Propensity and paid-media measurement address genuine functional gaps.

Recommended Actions is promising, though its retail public-preview status limits how much weight it should carry in a current product score. BYOC is also still preview-stage for Databricks. There are other reasons to press hard. Stitch remains batch. Real-time performance depends on the signal and destination involved. MCP creates fresh governance questions once customer information reaches an external AI client.

Amperity doesn't have Salesforce's suite gravity or Databricks' control over the lakehouse. Its case rests on resolving identity well, making that identity usable across a mixed enterprise stack, and proving that better customer context changes revenue or cost.

Explore the Best CRM and Customer Data Platform Award

The CX Awards 2026 will recognize the CRM, CDP, and customer data management vendors powering personalization and insight.

Learn more about the Best CRM and Customer Data Platform Award

Frequently Asked Questions

FAQs

Which teams need to be in the Amperity buying room?

Marketing alone shouldn't own this decision. Bring in CRM, data engineering, analytics, privacy, finance, and service leaders early. The Amperity customer data cloud touches identity rules, customer permissions, live activation, media spend, and AI access. If those teams arrive late, the roadmap review becomes procurement theater rather than a real evaluation.

What's the biggest Amperity risk buyers might miss?

The biggest risk is assuming every 'real-time' claim means the same thing. Amperity has a credible real-time customer context story, but buyers still need to separate live activation from real-time identity resolution. Stitch remains batch, and that distinction matters for service, loyalty, fraud, and high-value personalization, especially in regulated industries.

How does consumption pricing change the CDP business case?

Consumption pricing can make sense when usage tracks value, but it needs careful modeling. More profiles, agent queries, live calls, activations, and predictive runs can change the bill fast. Any CRM customer data platform contract should include usage scenarios tied to real campaign, loyalty, and service volumes, not just launch-day estimates.

Why does Amperity's identity layer deserve so much attention?

Because bad identity poisons everything downstream. Segments inflate. Suppression fails. AI agents read the wrong record. Service teams miss context. Amperity's identity resolution AI is one of its best claims, especially for brands with loyalty, ecommerce, store, and call-center data scattered across different systems and vendors.

What would make Amperity's roadmap more convincing?

Clearer GA timelines would help. Buyers need firmer answers on MCP availability, AMP Agent maturity, real-time connector coverage, BigQuery, Fabric, BYOM, and real-time architecture. The roadmap is pointed at the right buyer problems. The proof has to come from production usage, not a polished launch slide.

Amperity Customer Data Cloud: The 2026 Roadmap Bet on Real-Time Context and Identity AI

TL;DR: How Strong Is Amperity's 2026 Roadmap?

In This Article

Why Is Amperity Both A Gartner Niche Player and an IDC MarketScape Leader?

What Is An AI-Ready Customer Data Platform and Where Does Amperity Fit?

What Changed in Amperity's 2026 Roadmap

How Does Real-Time Customer Context Work in Amperity Customer Data Cloud?

Does Amperity's Lakehouse Roadmap Solve Enterprise Data-Control Concerns?

How Should Enterprises Measure Return on Customer Data?

Is Amperity a Strong CDP Pick Heading into 2027?

Frequently Asked Questions

FAQs

Which teams need to be in the Amperity buying room?

What's the biggest Amperity risk buyers might miss?

How does consumption pricing change the CDP business case?

Why does Amperity's identity layer deserve so much attention?

What would make Amperity's roadmap more convincing?

Why Claudeforce Indicates CRM Complexity Is Breaking Customer Experience

Why Claudeforce Indicates CRM Complexity Is Breaking Customer Experience

Optimove AI Is Betting Big on Agentic Marketing. Most CRM Teams Aren’t Ready

CRM’s Great Escape: Salesforce, HubSpot, Zeotap, and Zendesk Redraw the Data Battle