Connect
Adobe Analytics: connect, grant report suites and run reports
TL;DR
Adobe Analytics connects on its own Integrations card with an OAuth Server-to-Server credential from your Adobe organization; the credential's product profile decides which report suites, metrics and dimensions the agent can read.
Before you start (in Adobe)
- 1Open Adobe Developer Console (developer.adobe.com/console), pick your organization, and open a project (or Create new project).
- 2Add API → Adobe Analytics, choose OAuth Server-to-Server, and tick the product profiles the agent should use.
- 3In Adobe Admin Console → Adobe Analytics → the profile → Permissions, grant Report Suites (or turn on Auto-include) and the Metrics and Dimensions to report on. Analysis Workspace projects need that permission too.
- 4On the project page press Download for Project JSON — or copy the Client ID and Retrieve client secret.
Connect
- 1Integrations → Adobe Analytics → Connect → Paste JSON (or Manual entry: name, Client ID, secret).
- 2Test connection reads
GET /discovery/me— the Analytics companies the credential reaches. - 3Pick the Analytics company (globalCompanyId) when there are several, and Save connection.
Scopes are added for you:
openid, AdobeID, additional_info.projectedProductContext. With Paste JSON your credential's own scope list is checked; a missing one is named.Which permissions unlock what
- Report Suites (or Auto-include): reports, dimensions, metrics, and segments / calculated metrics on those suites. Without it the suite list is empty and a suite's reads answer 403 — the tool names the suites your company has and the Admin Console steps.
- Metrics / Dimensions: which columns a report may use.
- Analysis Workspace: projects (403 "No access to Analysis Workspace granted" without it).
- Date ranges need no report suite.
Every Adobe Analytics tool
8 reads and 4 writes, plus get_connection and test_connection shared by the four Adobe products.
| Tool | Kind | What it does |
|---|---|---|
analytics_list_companies | Read | The Analytics companies the credential reaches (GET /discovery/me): globalCompanyId, name, data center. |
analytics_list_report_suites | Read | Report suites (GET reportsuites/collections/suites): rsid, name, currency, timezone. |
analytics_list_dimensions | Read | Dimensions of a report suite (GET dimensions?rsid=): id (variables/evar1, variables/page …), name, type. |
analytics_list_metrics | Read | Metrics of a report suite (GET metrics?rsid=): id (metrics/visits, metrics/orders, metrics/event1 …), name, type. |
analytics_list_segments | Read | Segments (GET segments): id (s…), name, rsid, owner, description; includeDefinition:true adds the definition. |
analytics_list_calculated_metrics | Read | Calculated metrics (GET calculatedmetrics): id (cm…), name, rsid, polarity, precision, type. |
analytics_report | Read | An Analytics ranked report (POST reports — a READ, changes nothing): { accountId?, rsid, startDate, endDate (YYYY-MM-DD, end inclusive, the report suite's time zone; default the last 7 complete days), dimension (varia… |
analytics_get | Read | ANY Analytics 2.0 API GET under the company (path relative to /api/{globalCompanyId}/: reportsuites/collections/suites[/{rsid}], dimensions, metrics, segments[/{id}], calculatedmetrics[/{id}], dateranges, projects, an… |
analytics_create_segment | Write | Create an Analytics segment (POST segments): { accountId?, name, rsid, definition (the segment's own JSON definition — container / func / pred as Adobe documents), description? }. |
analytics_update_segment | Write | Change a segment's name, description or definition (PUT segments/{id}; the segment is read first): { accountId?, segmentId, name?, description?, definition? }. |
analytics_create_calculated_metric | Write | Create a calculated metric (POST calculatedmetrics): { accountId?, name, rsid, definition (Adobe's formula JSON), description?, polarity? (positive | negative), precision?, type? (decimal | percent | currency | time) }. |
analytics_mutate | Write | Any other Analytics 2.0 write under the company (method POST | PUT | PATCH | DELETE, path relative to /api/{globalCompanyId}/, body = Adobe's own fields): segments, calculatedmetrics, dateranges, annotations, projects… |
Over MCP and the REST API the names are adobe__<tool> (for example
adobe__analytics_report). A workspace with no connection for this product does not list these tools over MCP; describe_tool names the card to connect. Setup for Claude, Codex or Cursor: MCP server guide.Reports and their limits
- Up to 10 metrics per report and 400 rows per page; a cut report says
truncatedand reads the next page on request. - Breakdowns: up to three chained, each naming an item by the id a previous report's row carries (a name is refused).
- Segments: up to five applied together. Search: item names containing a word (quotes and backslashes refused).
- Dates are the report suite's own time zone; the default is the last 7 complete days.
- Totals are Adobe's for the whole period — visits and visitors are counted once across rows, so daily rows can add up to more. Quote the totals.
- Segments and calculated metrics are listed own AND shared by default (
includeTypeowned | shared | templates narrows it).
Changes and approvals
- Ordinary changes follow the approval setting — by default each waits for your approval: creating or editing a segment, creating a calculated metric, date ranges, annotations through
analytics_mutate. - A person approves, every time: any DELETE and a classification import.
- Refused on every lane: data repair, users, Discovery writes and credentials paths.
Manage the connection
- Test again re-checks this product with one read-only request and stores the result.
- Configure changes this product's details; Replace credential swaps a rotated secret in place (cached tokens are dropped).
- Disconnect deletes the stored credential and its tokens here. It does not revoke the credential in Adobe — do that in Developer Console.
More on Adobe Analytics: what the agent does · setup and every tool · MCP server · AI agent guide · playbook. The other Adobe products, each its own connection: Adobe Experience Platform · Adobe Target · Adobe Launch · All four together: Adobe.
Frequently asked questions
- The card says Connected but no report suite can be read — why?
- The credential's Analytics product profile grants no report suite. Add them in Adobe Admin Console → Adobe Analytics → the profile → Permissions → Report Suites (or Auto-include), check the credential is on that profile, then press Test connection.
- Which time zone do reports use?
- The report suite's own time zone; "last 7 days" is the 7 complete days ending yesterday there.
- Can I use Adobe Analytics from Claude or Codex?
- Yes, over MCP with an Agent Planners key — see the Adobe Analytics MCP server guide.