All docs
Connect

Adobe: connect Analytics, Target, Platform and Launch

TL;DR

Adobe connects with a credential you create in your own Adobe organization (client credentials — no sign-in redirect, no refresh token). Each product — Adobe Analytics, Adobe Experience Platform, Adobe Target and Adobe Launch — is its OWN integration on Integrations: connect them one by one, each with only that product's permissions and its own detail.

Each product's own setup page

This page covers what the four products share. Each product's own page has its card, scopes, permissions and every tool:

Before you start (in Adobe)

You need a person who is a System Administrator or Developer in your Adobe organization (Adobe Admin Console → Users shows the role). Everything below happens in your own Adobe organization; Agent Planners never creates or changes the credential.

  1. 1Open Adobe Developer Console (developer.adobe.com/console) and pick your organization in the top-right switcher.
  2. 2Create new project (or open an existing one) → Add API. Add each product you want, choosing OAuth Server-to-Server when asked: Adobe Analytics, Experience Platform API, Adobe Target, Experience Platform Launch API (this is Tags). Several APIs share ONE credential.
  3. 3When each API asks for product profiles, tick the ones the agent should use. They decide what it may read and change: report suites (Analytics), sandboxes and datasets / audiences (Experience Platform), workspaces (Target), properties and publishing rights (Launch). You can change them later in Adobe Admin Console → Products → the product → the profile → API credentials.
  4. 4On the project page press Download for Project JSON (top right) — or open OAuth Server-to-Server and copy the Client ID, press Retrieve client secret, and copy the Organization ID.

Where to find each value

  • Project JSON: Developer Console → your project → Download for Project JSON. It holds everything below except, sometimes, the secret.
  • Client ID: Developer Console → project → OAuth Server-to-Server → Client ID (32 letters and digits).
  • Client Secret: the same page → Retrieve client secret. If you rotated it, the newest one is the active one; an old one stops working when you delete it.
  • IMS Organization ID: the same page → Organization ID, ending in @AdobeOrg (needed for Experience Platform and Launch).
  • Scopes: nothing to type — they are added for you. To see them: the credential → Scopes tab.
  • Analytics company (globalCompanyId): found by the test. Several companies → pick one. You can see it in Analytics → Admin → Company Settings → API.
  • Report suite (rsid): Analytics → Admin → Report Suites, the Report Suite ID column. The agent lists the ones the credential can see; an empty list means none is in its product profile.
  • Experience Platform sandbox: found by the test (prod, or a development sandbox). In Platform the sandbox switcher at the top shows the name.
  • Target tenant: the name after @ in your Target address — https://experience.adobe.com/#/@yourtenant/target/activities. We suggest it from your organization's name and confirm it with Target; Adobe has no API that lists it.
  • Launch company and property: found by the test. A property's id (PR…) is in Data Collection → Tags → the property → its URL.

Which product-profile permissions unlock what

Checked against a live Adobe organization (2026-11-11). Each tool tells you the exact permission when one is missing; nothing else needs changing on our side.

  • Analytics — Report Suites (or Auto-include): reports, dimensions, metrics, and segments / calculated metrics on those suites. Date ranges need no suite.
  • Experience Platform — Data Modeling: schemas and field groups (read and write). Identity Management: identity namespaces. Data Management: datasets (403 without it). Profile Management: audiences and merge policies (401 "RBAC Unauthorized" without it). Query Service: queries. Sandboxes: the sandboxes the profile includes.
  • Target — the product profile's workspace and properties: activities, offers (HTML and JSON), audiences, locations (mboxes), environments, properties and activity reports.
  • Launch — Property Rights / Company Rights: rules, data elements, extensions, libraries; building a library needs Develop / Publish rights on that property.

Analytics reports the agent can run

  • Any dimension (variables/daterangeday, variables/page, variables/marketingchannel …) with up to 10 metrics, including your calculated metrics (cm… ids).
  • Breakdowns: the rows of a dimension within one item of another — e.g. "Paid Search by day" — up to three chained. The item is named by the id a previous report's row carries.
  • Segments: up to five applied together. Search: keep only items whose name contains a word.
  • Totals: each report returns Adobe's own totals for the whole period. Visits and visitors are counted once across rows (a visit that crosses midnight appears in two days), so daily rows can add up to slightly more than the total — the agent quotes the total.

What the project JSON looks like (redacted)

The part the import reads — every other field is ignored, and nothing in the file is followed or run. Values below are placeholders.

json
{
  "project": {
    "org": { "name": "Your Company", "ims_org_id": "XXXXXXXXXXXXXXXXXXXXXXXX@AdobeOrg" },
    "workspace": {
      "details": {
        "credentials": [
          {
            "id": "1234567",
            "name": "Agent Planners",
            "integration_type": "oauth_server_to_server",
            "oauth_server_to_server": {
              "client_id": "0123456789abcdef0123456789abcdef",
              "client_secrets": ["p8e-••••••••••••••••••••••••"],
              "scopes": ["openid", "AdobeID", "additional_info.projectedProductContext", "read_organizations", "session", "target_sdk", "additional_info.roles", "additional_info.job_function"]
            }
          }
        ],
        "services": [
          { "code": "AdobeAnalyticsSDK", "name": "Adobe Analytics" },
          { "code": "McDataServicesSdk", "name": "Experience Platform API" },
          { "code": "AdobeTargetSDK", "name": "Adobe Target" },
          { "code": "McDtmSDK", "name": "Experience Platform Launch API" }
        ]
      }
    }
  }
}
Treat the file like a password: it contains the client secret. Paste it, then delete the downloaded file; rotate the secret in Developer Console if it was shared.

If a product does not connect

  • Invalid credentials: the Client ID and secret do not match — copy them again, or retrieve the secret again (a deleted secret stops working).
  • Missing permissions: the credential works but its product profile does not allow that read — add the credential to a profile with the permission (Admin Console → Products → profile → API credentials), then press Test again. Example: an Experience Platform profile without dataset or segmentation permissions.
  • Additional configuration required: a detail is missing or wrong (the Target tenant, a company, a sandbox), or the API is not added to the credential's project — add it in Developer Console, download the JSON again and use Replace credential.
  • Temporarily unavailable: Adobe did not answer — try again in a minute.

Connect

  1. 1Integrations → the card of the product you want (Adobe Analytics, Adobe Experience Platform, Adobe Target or Adobe Launch) → Connect. Repeat on each card you need — the same project JSON works on every card; each card takes only its product's permissions.
  2. 2Paste JSON (or choose the .json file) and press Import — or Manual entry: connection name, Client ID, Client Secret and, for Experience Platform or Launch, the IMS Organization ID.
  3. 3If the project has several OAuth Server-to-Server credentials, choose one; if a credential holds several client secrets, choose the one that is active; if the export left the secret out, type it.
  4. 4Press Test connection. Each product shows Connected, Additional configuration required, Missing permissions, Invalid credentials or Temporarily unavailable, with what to do.
  5. 5Set what it asks for — the Analytics company, the Experience Platform sandbox, the Target tenant (the name after @ in your Target address; we suggest and confirm it), the Launch company — and Save connection.

What is kept, and what is not

  • Kept, encrypted: the client secret. Kept: the Client ID, IMS Organization ID, the scope list, the chosen products and details, and each product's last check.
  • Never kept: the pasted JSON (cleared from the page after import, never stored or logged) and access tokens in your browser. Tokens live only on our server, cached until shortly before they expire.
  • Scopes: from Adobe Developer Console's per-API list. With Paste JSON your credential's own list is used; a scope a product needs that the credential lacks is named, and that product is not called connected.

Changes and approvals

  • Ordinary changes wait for your approval unless auto-approve is on.
  • A person approves, every time: a Target activity turned live, an HTML offer, building or publishing a Launch library, Launch custom code and extensions, Experience Platform data ingestion and dataflows, and every delete.
  • Refused: sandboxes, access control, privacy jobs, Analytics data repair and users.
Over MCP and the REST API the names are adobe__<tool> (for example adobe__target_list_activities). Setup for Claude, Codex or Cursor: Adobe MCP server · Walkthroughs: Adobe Analytics reports · Adobe Target and Launch.

Manage the connection

  • Test again re-checks every product (read-only) and stores the result.
  • Configure changes this product's details (company, sandbox, tenant or Launch company / property). Another product is connected on its own card.
  • Replace credential swaps a rotated secret or a new credential of the same Adobe organization in place (every cached token is dropped).
  • Disconnect deletes the stored credential and its tokens. It does not revoke the credential in Adobe — do that in Developer Console.

Frequently asked questions

Why does a product say Missing permissions?
The credential is valid but its product profile in Adobe Admin Console does not allow that read (for example a sandbox's datasets). Add the permission there and press Test again.
Adobe Analytics says it is connected but no report suite can be read — why?
Adobe lists only the report suites the API credential's Analytics product profile grants. The card names the suites your company has (read from its segments). In Adobe Admin Console → Adobe Analytics → the product profile the credential belongs to → Permissions → Report Suites, add them (and Metrics / Dimensions, or turn on Auto-include), check the credential is on that profile (Developer Console → the project → OAuth Server-to-Server → Edit product profiles), then press Test connection. Until then reports, dimensions, metrics and new segments on those suites answer that the suite is not granted.
Why does Target say Additional configuration required?
The Target tenant is missing or wrong. It is the name after @ in your Target address (https://experience.adobe.com/#/@<tenant>/target); Adobe has no API that lists it.
Do tokens expire?
Yes, Adobe's tokens last about 24 hours. A new one is requested on our server shortly before the old one expires — nothing to do on your side.
Can I use Adobe from Claude or Codex?
Yes, over MCP with an Agent Planners key: the Adobe MCP server guide at /resources/adobe-mcp-server has the setup.

Related