- Home
- Resources
- Integrations
- Adobe Customer Journey Analytics
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
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.
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 Customer Journey Analytics to Claude in three steps
- 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.
- 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.
- 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.
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
Tools index
- describe_Cja
- describe_Dimension
- describe_Metric
- describe_Project
- describe_Audience
- describe_Segment
- describe_Calculated_Metric
- find_DataViews
- find_Dimensions
- find_Metrics
- find_Segments
- find_CalculatedMetrics
- find_Audiences
- find_DateRanges
- find_Projects
- run_Report
- search_Dimension_Items
- list_Component_Usage
- list_FrequentlyUsedWith
- list_SimilarTo
What Claude reads (20)
20 toolsTwenty 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.
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.
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.
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.
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.
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.
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.
upsert_CalculatedMetric on that metric.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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
list_FrequentlyUsedWith
Shows which components tend to appear together with one you name, a natural pairing Claude can suggest when building a report.
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.
What Claude creates or updates (6)
6 toolsSix 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 ruleSaves 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.
upsert_CalculatedMetric
Approval: see the ruleWrites 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.
upsert_Audience
Approval: see the ruleCreates an audience, or updates an existing one when its ID is passed. The change lands in your audience components.
upsert_Project
Approval: see the ruleBuilds 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.
create_DateRange
Approval: see the ruleAdds a new reusable date range component that can be shared and used across projects. Unlike the upsert tools, Adobe describes it as creation only.
set_Default_Session_DataViewId
Approval: see the ruleSets 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 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.
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.
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 connecting Adobe Customer Journey Analytics to Claude?
A person reads every message.