November 11, 2026 · 7 min read
Try it on your own accounts — 2,500 free credits a month, no credit card. By default every change waits for your approval.Start free
Playbooks

An AI agent for Adobe Analytics: reports, breakdowns, segments and calculated metrics

TL;DR

Adobe Analytics answers precise questions, but on its own terms: report suites, a company, product profiles and visits that are counted once across a whole period. An AI agent connected with your own OAuth Server-to-Server credential runs ranked reports, breakdowns, segments, searches and calculated metrics, and creates or edits segments and calculated metrics with your approval. This post covers what it reads, why it never adds up daily visits, how report-suite access is granted, and goals to start with.

Why Adobe Analytics needs its own playbook

Adobe Analytics is connected on its own card, with a credential you create in Adobe Developer Console — no sign-in redirect and no shared password. What the credential may read is decided in Adobe Admin Console by the product profiles it belongs to: which report suites, which metrics and dimensions. An agent that does not know this reports "no data" when the truth is "no access".

The numbers have rules too. Visits and visitors are deduplicated over the period you ask for, so a daily table and the period's total do not have to agree. A report that sums daily rows into a total quietly overstates them.

What the agent reads

ToolWhat it answers
analytics_list_report_suitesThe report suites the credential's product profile grants
analytics_list_dimensions / analytics_list_metricsA suite's dimensions and metrics, with their ids
analytics_list_segments / analytics_list_calculated_metricsSegments and calculated metrics — shared ones included by default (owned, shared or templates on request)
analytics_reportAny dimension with up to 10 metrics, ranked, sorted and paged, in the report suite's time zone
analytics_getAny other documented Analytics read
Adobe Analytics has 8 of the 28 Adobe reads; the other products are Experience Platform, Target and Launch, each connected on its own card.

Breakdowns, segments and search in one report

  • Breakdowns: the rows of one dimension inside one item of another — "pages within Paid Search", "days within the mobile channel" — up to three levels. The item is named by the id a previous report's row carries, never guessed from a name.
  • Segments: up to five applied together, your own or shared ones.
  • Search: keep only items whose name contains a word, using Adobe's own search clause.
  • Calculated metrics: a cm… id sits in a report beside ordinary metrics, so "page views per visit by channel" is one report, not a spreadsheet afterwards.
  • Paging: a ranked report says when there are more rows than one page and reads the next page on request.

Why the totals must be Adobe's

Adobe counts a visit once for the period you ask about. A visit that crosses midnight appears on two days in a daily report, and a visitor who came back three times appears on three days. So the sum of daily rows can be larger than the period's real total. In our live check on a real report suite, 30 daily rows added up to 317,464 visits while Adobe's own total for the same 30 days was 316,068. Page views, which are not deduplicated, added up exactly.

Every report therefore carries Adobe's totals for the whole period, and when visits or visitors are asked the result says to quote those totals. The agent writes "316,068 visits in the last 30 days", not a sum of rows.

Report suites come from product profiles

Adobe lists only the report suites the API credential's Analytics product profile grants. A company can be full of suites while the credential sees none: the list comes back empty and a report on any suite answers that the user does not have access to it. When that happens the agent names the suites your company has (read from its segments) and the place to grant them, instead of reporting an empty account.

  1. 1In Adobe Admin Console open Adobe Analytics → the product profile the credential belongs to → Permissions → Report Suites, and add the suites (or turn on Auto-include), with the metrics and dimensions you want read.
  2. 2Check the credential is on that profile: Developer Console → the project → OAuth Server-to-Server → Edit product profiles.
  3. 3Press Test connection on the Adobe Analytics card. The suites now appear, and reports run.

What it changes

These follow your approval setting: by default each one waits for your approval card, and auto-approve is opt-in per task, schedule or project. Deleting a segment or a calculated metric, and changing classifications, always wait for a person. Analytics data repair and users are refused — they stay in Adobe.

  • Segments: created on a report suite you can read and edited later.
  • Calculated metrics: created from a formula (page views ÷ visits, for example) and usable in the next report.
  • Anything else Adobe documents through analytics_mutate, the Analytics write gateway.
Measured on a real Adobe organization (2026-11-11): a segment created on a suite, a report run through it, the segment renamed and deleted; a calculated metric of page views ÷ visits used in a report and deleted again.

Goals to start with

GoalWhat the agent does
"Visits and orders by day for our main report suite, last 30 days."Reads the daily report in the suite's time zone and quotes Adobe's 30-day totals, not the sum of days.
"Which marketing channels lost visits this month compared with last month?"Runs the channel report for both periods and ranks the change.
"Top pages within Paid Search last week."Finds Paid Search's item id in the channel report, then breaks it down by page.
"Create a segment for visits from the mobile app and show conversion by channel."Proposes the segment for your approval, then reports through it.
"Page views per visit by channel."Uses an existing calculated metric or proposes one.

Setting it up

  1. 1In Adobe Developer Console add the Adobe Analytics API to a project with an OAuth Server-to-Server credential, and put the credential on the right product profile.
  2. 2On Integrations press Connect on the Adobe Analytics card, paste the project JSON (or type the Client ID and secret), press Test connection and pick the Analytics company if there are several.
  3. 3Pick the connection for a task and write the goal — or call the same tools from Claude, Codex or Cursor over MCP.

Frequently asked questions

Can an AI agent run Adobe Analytics reports?
Yes. With your own OAuth Server-to-Server credential it runs ranked reports on any dimension with up to 10 metrics, breakdowns up to three levels deep, segments, searches and calculated metrics.
Why don't my daily visits add up to the monthly total?
Adobe counts a visit or a visitor once for the whole period. A visit that crosses midnight appears on two days, so daily rows can add up to more than the total. Quote Adobe's own total for the period.
Why does the agent see no report suites?
The API credential's Analytics product profile grants none. Add the report suites (or Auto-include) to that profile in Adobe Admin Console, make sure the credential is on it, and press Test connection.
Can the agent create segments in Adobe Analytics?
Yes, on a report suite the credential can read. By default a new segment waits for your approval; deleting one always waits for a person.
Run your ad ops with an agent you can trust

Start free — 2,500 credits a month, no credit card. By default every write waits for your approval.

Keep reading