Adobe

Adobe Customer Journey Analytics

Curated anchor platform in customer journey analytics with material relevance to the Marcom operating stack and a first-party developer surface.

Analytics, SEO & experimentationSystem of intelligenceAgent-accessible SaaS
System roleSystem of intelligence
Access maturityAgent-accessible SaaS
Agent postureFirst-party provider
Reference updatedNot stated by publisher
BYO-UI reviewedJul 10, 2026

Concrete capability record

Data, retrieval, actions, identity, and operating limits

A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.

01 · Records and state owned

Data views, dimensions, metrics, segments/audiences, reports, date ranges, workspace projects

02 · Data you can retrieve

Data views, dimensions, metrics, segments/audiences, reports, date ranges, workspace projects

03 · Actions and write paths

Manage supported segments, audiences and date ranges and create/run ranked or trended reports. Do not infer permission to reconfigure connections, data views or unrelated CJA administration.

04 · Authentication and permissions

Adobe identity and the connected CJA product, data-view and component permissions control access to dimensions, metrics, segments/audiences, projects and reports.

05 · Monitoring, approval, and recovery

Preserve data-view boundaries, metric and audience definitions, consent and identity assumptions, date ranges, component ownership and report provenance.

06 · Gaps and implementation limits

The public MCP overview lists data-view/component discovery, reporting, segment/audience/date-range management and workspace exploration; use the current tool reference for exact parameters and availability.

Agent access

MCP and adjacent posture

Verified first-party provider MCPAdobe-hosted remote MCPGenerally documented service

Role: provider

Read scope: Data views, dimensions, metrics, segments/audiences, reports, date ranges, workspace projects

Write scope: The hosted server can manage segments, audiences and date ranges and can create/run ranked or trended reports; no broader CJA administration write scope is inferred.

Authentication: Authentication model is documented by the vendor; inspect the cited source before implementation.

Approval boundary: Require explicit human confirmation for costly, externally visible, destructive, or hard-to-reverse actions.

Protocol does not erase product boundaries.

Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.

Editorial assessment

Access-maturity dimensions

A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.

Data access4
Action access4
Event access1
Identity4
Governance4
Agent access4
UI extensibility3
Portability4
Observability3
Documentation4

Proposed interfaces

What customers could build on top.

These are design proposals derived from documented access—not claims that Adobe ships these experiences.

Single-platform patterns

  • Cross-channel journey analysis room
  • Executive insight brief
  • Experiment review board
  • Anomaly investigation room
Use in the brief composer →

Multi-platform compositions

  • Adobe Customer Journey Analytics + warehouse or semantic layer: executive insight brief
  • Adobe Customer Journey Analytics + CRM or lifecycle platform + work-management system: cross-system decision workspace
Explore composition recipes →

Evidence and dates

First-party references, with publisher and review dates separated

“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.

4 recorded sources
MCP / agent-role validationRepresentative source
https://developer.adobe.com/analytics-mcp/docs/cja/ ↗

Official Adobe documentation provides hosted endpoint and tool scope.

Publisher updated
Not stated by publisher
BYO-UI reviewed
Jul 10, 2026

Targeted first-party MCP/agent-role review; broader API inventory retained

APISource inventory
https://developer.adobe.com/cja-apis/docs/ ↗

First-party API reference or API overview recorded for this platform.

Publisher updated
Not stated by publisher
BYO-UI reviewed
Jul 10, 2026

Inventory source: structurally normalized; content was not individually reopened in this pass.

Verified fact

Tied to the representative first-party source or targeted access review.

Source inventory

Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.

Editorial assessment

System role, maturity interpretation, and architectural boundary.

Proposed design

Interface patterns and compositions—not vendor product claims.