Adobe Analytics Is Live in Cogny: Report Suites, Dimensions and Ad-Hoc Reports for Your Agent
Adobe Analytics runs reporting for a lot of enterprise marketing and e-commerce teams that Google Analytics 4 doesn't reach. Until today none of that data was reachable from a Cogny agent. Now it is. Adobe Analytics is a live MCP integration, joining Google Analytics 4 as a second analytics platform your agent can query directly.
No developer app to register on Cogny's side, no redirect flow to click through: one OAuth Server-to-Server credential created in the Adobe Developer Console, pasted once into Settings → Cogny Managed MCPs as a Client ID and Client Secret. Adobe's older JWT / Service Account auth is deprecated and deliberately not implemented here — only the current Server-to-Server flow is supported.
TL;DR
- Adobe Analytics is live now. Connect it with an OAuth Server-to-Server Client ID and Client Secret from your warehouse Settings → Cogny Managed MCPs.
- 7 tools covering account info, report suites, dimensions, metrics, segments, calculated metrics and ad-hoc reports. All of them are reads — this release writes nothing to Adobe Analytics;
run_reportonly runs a report against existing data. - You never have to find or paste a Global Company ID. Cogny discovers it automatically from your organization's Adobe IMS account the first time a tool runs, and caches it.
- Tokens are handled the same way: each call exchanges your Client ID/Secret for a short-lived bearer token with the OAuth2 client-credentials grant against Adobe IMS, cached until shortly before it expires, and refreshed once automatically if a call comes back
401. - The
data-quality,conversion-optimizationandcroscheduled templates now recommend themselves for Adobe Analytics workspaces, same as they already do for Google Analytics 4. - Works from any MCP client on
app.cogny.com/mcp. - Included in Cogny Solo ($9/mo); bring your own agent and the standard MCP tools run under fair use.
What you can do with it
| Area | What Claude can do |
|---|---|
| Account | Confirm the credential is wired up and see the resolved Global Company ID |
| Report suites | List the report suites (data views) a credential can see, with pagination |
| Dimensions & metrics | List the dimensions and metrics available on a report suite, filtered by whether they're segmentable or reportable |
| Segments & calculated metrics | List shared segments and calculated metrics, optionally filtered to specific report suites |
| Reports | Break one dimension down by one or more metrics over a date range — e.g. page by visits, or campaign by orders and revenue |
In plain terms: "Which report suites can this credential see?" "What dimensions does the main report suite expose?" "Break down visits by page for the last 30 days." "Run orders and revenue by marketing channel for last month." The answers come straight from the Adobe Analytics 2.0 Reporting API, not an exported CSV.
Why discovery matters
Every Adobe Analytics API call needs a Global Company ID in its URL path, and most integrations make a customer dig it out of a support ticket or a browser network tab before they can connect anything. Cogny skips that: the first tool call resolves it from GET /discovery/me against the connected credential's own Adobe IMS organization, and caches it for every call after. The same credential that authenticates you is the one that tells Cogny which company to talk to.
Two ways in: chat or scheduled
Ask interactively from any MCP client, or enable the data-quality, conversion-optimization or cro templates as scheduled prompts — each now recognizes Adobe Analytics as an alternative to Google Analytics 4 and will use whichever one your workspace has connected.
How to connect it
- In the Adobe Developer Console, sign in with a System Administrator or Developer role, create a project (or open an existing one), click Add API, and choose Adobe Analytics. Select OAuth Server-to-Server as the credential type — not the older JWT/Service Account option.
- In the Adobe Admin Console, attach the credential's product profile to the report suites you want Cogny to read, with reporting access to the metrics and dimensions you use.
- Back in the Developer Console, copy the Client ID and Client Secret from the credential.
- In your warehouse Settings → Cogny Managed MCPs, click Connect on the Adobe Analytics card and paste them in.
The credentials are stored encrypted and scoped to the single workspace. Each call exchanges them for a short-lived bearer token with the OAuth2 client-credentials grant against Adobe IMS — no redirect, nothing to approve on Adobe's side beyond the product profile you already set up. Disconnect any time with one click, and revoke the credential in the Developer Console if you ever stop using Cogny.
On trust
Every tool carries MCP behavior annotations, so Cogny's UI and Claude.ai connectors know that all of them read and none of them write. There are no segment, calculated-metric or annotation writes in this release — run_report is a POST under Adobe's own Reporting API wire format, but it only runs a report against existing data; it creates nothing in Adobe Analytics. A 403 on a report suite, metric or dimension means the product profile attached to the credential needs that access added in the Adobe Admin Console — not that the credential itself is wrong.
If your organization reports through Adobe Analytics, this connector puts that data on the same footing as Google Analytics 4 in your agent's toolbox. Connect it from your Cogny dashboard and ask your first question.