Resources · Claude connector

Claude Adobe Customer Journey Analytics connectorWhat Claude can do in your Adobe Customer Journey Analytics account.

The Claude Adobe Customer Journey Analytics connector lists 26 tools. 20 read your data views, components and reports, 6 create or update things, and 0 are undocumented. Here: what Claude can run, what it can build, and the Adobe permission you need first.

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What changes for an analytics team

Instead of building every freeform table by hand in Analysis Workspace, you describe what you want and Claude does the plumbing. It finds the right dimensions and metrics in your data view, runs the report and explains the result. It can also save segments, calculated metrics, audiences and whole projects back into Customer Journey Analytics, within the permissions Adobe already gives you.

An answer instead of a dashboard hunt. Ask for your top pages over a date range: Claude locates the right components with find_Dimensions and find_Metrics, then calls run_Report, which Adobe calls its primary tool for pulling analytics data.

A segment written for you. Describe the visitors you care about and upsert_Segment creates or updates the segment, after Claude has read Adobe's definition guide through describe_Cja.

A project ready to open. upsert_Project builds or updates a workspace project, and the response includes a direct link to open it in Analysis Workspace.

What the directory sheet does not say. Every user, administrators included, needs a product profile with the MCP Access permission, and Adobe enforces the same permissions as in its interface. No tool on the sheet deletes anything: the six write tools create or update. And nothing runs by itself: Claude only calls these tools while it answers you, so no report lands in your inbox on Monday morning. Scheduled delivery is the job of an automation tool, a different trade covered on the Integrations hub.

Vocabulary

Five words before you connect

The vocabulary you will meet while plugging Customer Journey Analytics into Claude.

Connector
The link you set up once between Claude and an account you already have, so Claude can work in it while it answers you.
Tool
One named thing a connector lets Claude do. Claude picks the ones it needs mid-answer, and the directory lists them by name.
Authorization
The service's own sign-in screen, here your Adobe ID, where you hand Claude the access it will use. Revocable later.
Approval
The confirmation Claude waits for before it goes through with something that changes your account, shown right in the chat.
MCP
The shared standard connectors are built on: the piece that lets an assistant like Claude talk to an outside service.
Connect

Connect Customer Journey Analytics to Claude in three steps

  1. 01

    Find the connector in Claude

    In Claude's settings, open Customize, then Connectors, and look for Adobe Customer Journey Analytics. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable it first, before any member can sign in.

  2. 02

    Start the connection

    Click Connect on its row, then sign in with your Adobe ID in the window Adobe opens. If your Adobe ID belongs to several organizations, pick the right one there. If the link breaks, use Disconnect and reconnect.

  3. 03

    Read the authorization screen

    Check the authorization screen before you accept. It belongs to Adobe, not to Claude, and it sets what the access covers. That access can also be withdrawn later from the Adobe side.

Tools

The 26 tools, sorted by what they do

Adobe Customer Journey Analytics gives Claude 26 tools: 20 that read your account, 6 that change something in it.

Two groups: what Claude reads, and what it creates or updates. Tool names stay exactly as Claude shows them, even where Adobe's own docs spell them in camelCase.

  • 20 read
  • 6 write

What Claude reads (20)

20 tools

Twenty tools that explore components and pull report data without changing anything.

describe_Cja

Acts as the starting point: it returns Adobe's reference guides on tool usage, segment and calculated metric syntax, the two-step breakdown workflow and project definitions. Claude reads them before it builds anything.

When it helps
you ask for a flow visualization and Claude first checks how Adobe expects one to be described.

Sourcedeveloper.adobe.com · October 1, 2026 ↗

describe_Dimension

Returns the metadata of one dimension: name, description, type and other properties. Claude uses it to explain what a dimension really captures before putting it in a report.

When it helps
two dimensions have similar names and you want to know which one tracks the marketing channel.

Sourcedeveloper.adobe.com · October 1, 2026 ↗

describe_Metric

Shows what a single metric measures, through its name, description, type and other properties, so the figure in your report means what you think it means.

When it helps
a stakeholder questions whether a conversion metric counts people or sessions, and you want the official definition.

Sourcedeveloper.adobe.com · October 1, 2026 ↗

describe_Project

Describes a workspace project: its name, description, owner and data view, plus a direct link to open it in Analysis Workspace. Claude can tell you what a project is about before you open it.

When it helps
you inherit a dashboard and want to know who built it and on which data view.

Sourcedeveloper.adobe.com · October 1, 2026 ↗

describe_Audience

Gives Claude the metadata of one audience, including its definition and publishing status. It can then tell you who the audience targets and whether it is live.

When it helps
before a campaign, checking that the high-intent audience is published and built the way the brief says.

Sourcedeveloper.adobe.com · October 1, 2026 ↗

describe_Segment

Exposes how a segment is defined, along with its compatibility with a data view. Adobe suggests reading it before upsert_Segment touches that segment.

When it helps
a report looks off and you suspect the returning-customers segment filters more visitors out than intended.

Sourcedeveloper.adobe.com · October 1, 2026 ↗

describe_Calculated_Metric

Lays out the formula of a calculated metric and the base metrics it depends on. Claude can explain the math in plain words.

When it helps
finance asks how revenue per visit is computed in your reports.
Watch out
Adobe advises reading it before calling upsert_CalculatedMetric on that metric.

Sourcedeveloper.adobe.com · October 1, 2026 ↗

find_DataViews

Lists the data views your account can reach, page by page, and gives Claude the identifier it needs to set one as the session default.

When it helps
you work across a production and a staging data view and want to see both names before choosing.

Sourcedeveloper.adobe.com · October 1, 2026 ↗

find_Dimensions

Discovers the dimensions available in a data view, with semantic search on a topic such as page or user. It is how Claude checks which dimensions exist before running a report.

When it helps
you do not know the exact name of the dimension holding campaign codes.
Watch out
hidden dimensions are left out by default.

Sourcedeveloper.adobe.com · October 1, 2026 ↗

find_Metrics

Searches standard and custom metrics in the data view, by topic if you like, such as revenue or engagement. Calculated metrics are not included here; Adobe points to a separate search for those.

When it helps
a new analyst wants every engagement-related metric before building a report.

Sourcedeveloper.adobe.com · October 1, 2026 ↗

find_Segments

Returns the segments the current user has access to, in pages. Claude uses the list to pick a filter for a report or to grab the ID of a segment to inspect.

When it helps
you remember a mobile-only segment exists but not what it was called.

Sourcedeveloper.adobe.com · October 1, 2026 ↗

find_CalculatedMetrics

Browses user-made and shared calculated metrics, the counterpart of the standard metric search. Hidden ones are excluded by default, as Adobe's reference states.

When it helps
checking whether someone already built a margin metric, so you do not end up with a duplicate.

Sourcedeveloper.adobe.com · October 1, 2026 ↗

find_Audiences

Lists the audience components available to you, page by page, so Claude can find an existing audience or the ID that describe_Audience and upsert_Audience expect.

When it helps
the CRM team asks which audiences already exist for lapsed buyers before building another.

Sourcedeveloper.adobe.com · October 1, 2026 ↗

find_DateRanges

Finds saved date range components you can reuse, and their IDs for project definitions. Claude picks one up instead of rebuilding the same period.

When it helps
your team has a fiscal-quarter range and you want reports to use it, not a calendar quarter.

Sourcedeveloper.adobe.com · October 1, 2026 ↗

find_Projects

Lists the workspace projects available to you and returns their IDs, the entry point before Claude opens one with describe_Project or hands it to upsert_Project.

When it helps
locating last year's Black Friday project to compare its traffic against this year's.

Sourcedeveloper.adobe.com · October 1, 2026 ↗

run_Report

Pulls the actual numbers: a ranked report with one or several dimensions and metrics over a date range, all reported together in one request. Saved segments can serve as filters, and breakdowns rely on dimension item IDs.

When it helps
top landing pages by visits last month, split by device, in one request.
Watch out
breakdowns follow a two-step workflow described in Adobe's guide.

Sourcedeveloper.adobe.com · October 1, 2026 ↗

search_Dimension_Items

Retrieves the top values of a dimension, such as US, UK or Canada for a country dimension, with keyword search to find a specific one. It supplies the item IDs breakdown reports need.

When it helps
drilling into a single campaign code inside a channel report.

Sourcedeveloper.adobe.com · October 1, 2026 ↗

list_Component_Usage

Ranks the components of a given type by how often they appear in reports across your organization, so Claude knows which dimensions, metrics or segments people rely on.

When it helps
designing a new executive project and wanting it built on what teams already use.

Sourcedeveloper.adobe.com · October 1, 2026 ↗

list_FrequentlyUsedWith

Shows which components tend to appear together with one you name, a natural pairing Claude can suggest when building a report.

When it helps
you picked a product dimension and want to know which metrics colleagues usually put next to it.

Sourcedeveloper.adobe.com · October 1, 2026 ↗

list_SimilarTo

Suggests dimensions, metrics or segments that serve a similar purpose to a given one, useful to spot alternatives or near-duplicates in a crowded library.

When it helps
tidying up a component list where three slightly different bounce metrics coexist and nobody knows which to trust.

Sourcedeveloper.adobe.com · October 1, 2026 ↗

What Claude creates or updates (6)

6 tools

Six tools that save something, in your account or in your session. No source gives them a confirmation of their own: the general rule further down applies.

upsert_Segment

Approval: see the rule

Saves a segment in your account: with an existing ID it updates that segment, without one it creates a new one. Claude first reads Adobe's segment definition guide.

What Claude asks for
no source describes a confirmation for this tool; the general approval rule below applies.
When it helps
turning "visitors from paid search who viewed pricing" into a reusable filter.

Sourcedeveloper.adobe.com · October 1, 2026 ↗

upsert_CalculatedMetric

Approval: see the rule

Writes a calculated metric into Customer Journey Analytics, as a new one or as an update when an ID is given. Adobe asks for its metric definition guide to be read first.

What Claude asks for
nothing specific is documented; refer to the general rule further down.
When it helps
adding a revenue-per-visitor metric your team keeps recomputing by hand.

Sourcedeveloper.adobe.com · October 1, 2026 ↗

upsert_Audience

Approval: see the rule

Creates an audience, or updates an existing one when its ID is passed. The change lands in your audience components.

What Claude asks for
no confirmation specific to this tool appears in any source, so the default approval rule covers it.
When it helps
refining a lapsed-buyer audience after the CRM team changes its definition.

Sourcedeveloper.adobe.com · October 1, 2026 ↗

upsert_Project

Approval: see the rule

Builds a new Analysis Workspace project or updates one: with a project ID it updates that one, without it creates a new one. Adobe asks for its project structure guide to be read first.

What Claude asks for
see the general approval rule below.
When it helps
getting a first version of a weekly traffic project you then polish yourself.

Sourcedeveloper.adobe.com · October 1, 2026 ↗

create_DateRange

Approval: see the rule

Adds a new reusable date range component that can be shared and used across projects. Unlike the upsert tools, Adobe describes it as creation only.

What Claude asks for
the general approval rule further down is the one that applies.
When it helps
setting up a campaign window once so every report uses the same dates.

Sourcedeveloper.adobe.com · October 1, 2026 ↗

set_Default_Session_DataViewId

Approval: see the rule

Sets which data view the session uses by default, so later calls can skip it. It changes a session setting, not your reports or components, and Adobe says it persists for up to 8 hours.

What Claude asks for
no tool-specific confirmation is documented; the default rule applies.
When it helps
a long working session on one production data view.

Sourcedeveloper.adobe.com · October 1, 2026 ↗

Approvals

What Claude asks before acting

By default, Claude stops and asks for your go-ahead before every action it takes on an account on your behalf. The request shows up in the conversation, at the moment it matters.

Adobe's Claude guide adds a per-tool control: once connected, you can open the connector's Tool permissions and choose, tool by tool, whether Claude may use it, must ask first, or is blocked. You only see the tools your organization granted. On Team and Enterprise, workspace owners decide whether members can skip some prompts and can cap a connector for everyone. Claude also inherits your Adobe permissions and nothing more.

Plans

Which plans it works on

Out of 819 sheets in the official directory, not one shows availability by plan. That answer, connector by connector, is published nowhere: it is a real gap in the catalog.

The general rule is public: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner enables the connector for the organization before each member can connect. On the Adobe side, access also depends on the MCP Access permission. For this connector's current state, check its sheet in the official directory.

Limits

Where this connector stops

A connector is not an automation. Claude calls these tools while it answers you: no report goes out on a schedule and nothing fires when a metric drops.

The tool list is an observed floor, not a promise: an admin can open actions that appear on no public sheet, and Adobe says you only see the tools your organization granted. The partner badge is not a security audit either, and Anthropic says so on every sheet: it does not choose the tools a publisher exposes and does not guarantee they behave as described. This connector is documented only by Adobe; Claude's help center has no page for it. For another Adobe connector, see the Claude adobe-workfront connector.

Need help

Need help connecting Adobe Customer Journey Analytics to Claude?

A person reads every message.

FAQ

Claude Adobe Customer Journey Analytics connector: common questions

01What can Claude do with the Adobe Customer Journey Analytics connector?
Claude can explore your Customer Journey Analytics setup and pull data from it. Twenty documented read tools cover finding and describing data views, dimensions, metrics, calculated metrics, segments, audiences, date ranges and projects, running ranked and breakdown reports, listing dimension items, and spotting popular or related components. Six more tools save work: segments, calculated metrics, audiences and projects through create-or-update tools, new date ranges, and a default data view for the session.
02Can Claude create, change or delete things in Customer Journey Analytics?
It can create and update, not delete. Four tools create or update segments, calculated metrics, audiences and workspace projects, one creates reusable date ranges, and one changes the default data view of your session. Neither the directory sheet nor Adobe's reference lists any delete tool, so removing a component still happens in Adobe itself. Everything stays within your Adobe permissions, since the servers enforce the same rights as the interface.
03Does Claude ask before it saves a segment or a project?
By default, Claude asks for confirmation before every action it takes on an account on your behalf. No source describes a confirmation specific to these tools, but Adobe's guide points to the connector's Tool permissions, where you set each tool to allow, require approval or block. Choosing require approval for the six write tools keeps every save under your control. On Team and Enterprise, owners can also limit what the connector may do for the whole organization.
04Which Claude plans is it available on?
No official source publishes plan availability connector by connector, and none of the 819 directory sheets displays it. The general rule says remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, with an Owner or Primary Owner enabling them first on Team and Enterprise. Adobe adds its own gate, the MCP Access permission in a product profile. The connector's sheet in the official directory is the place to check its current state.
05Does Claude see all of our Customer Journey Analytics data?
No. Claude signs in with your Adobe ID and inherits your rights: Adobe states its servers enforce the same permissions as the interface, and you only see the tools your organization granted. Searches also skip hidden dimensions and metrics by default. If your Adobe ID belongs to several organizations, you choose one when you sign in. On Team and Enterprise, a Claude workspace owner can restrict the connector further for everybody.
06Why can't I connect Customer Journey Analytics to Claude?
The most likely reason is a missing Adobe permission. Adobe requires every account, product administrators included, to belong to a product profile that contains the MCP Access permission item. Adobe's servers enforce the same permissions as its interface, so your account also needs the Customer Journey Analytics rights for the actions you want. Check as well that you picked the right organization when signing in with an Adobe ID linked to several.
07Claude or an automation tool for Customer Journey Analytics?
They do different jobs. Claude answers when you ask: explain a drop, build a segment from a description, draft a project you then refine. An automation tool runs in the background on a schedule or an event, which this connector does not do, since nothing fires on its own when a metric moves. For a report emailed every Monday, look at an automation platform; for analysis and building in conversation, the connector is the right fit.