AI agent for Adobe Analytics, Target and Experience Platform
Adobe connects with a credential you create in your own Adobe organization: in Adobe Developer Console, a project with the APIs you want (Adobe Analytics, Experience Platform API, Adobe Target, Experience Platform Launch API) and an OAuth Server-to-Server credential. Each product is its own integration — connect them one by one: paste the project's JSON (or type the Client ID, secret and IMS organization ID) on that product's card, and it is checked with a read-only request before you save, using only that product's permissions. Access tokens are requested on our server, cached and renewed before they expire; the secret is stored encrypted and never shown again.
Connecting it
- 1In Adobe Developer Console create a project (or open one) and add the APIs you want — Adobe Analytics, Experience Platform API, Adobe Target, Experience Platform Launch API — each with an OAuth Server-to-Server credential.
- 2In Adobe Admin Console add that credential to the product profiles it should use: they decide what it may read and change (report suites, sandboxes, Target workspaces, Launch properties).
- 3Open Integrations: each Adobe product has its own card (Adobe Analytics, Adobe Experience Platform, Adobe Target, Adobe Launch). Press Connect on the ones you want, then Paste JSON (Project → Download for Project JSON) or Manual entry. You never type scopes.
- 4Press Test connection — each product is checked on its own — set the details it asks for (an Analytics company, a sandbox, the Target tenant, a Launch company), then Save connection.
What the agent reads
- Adobe Analytics: report suites, dimensions and metrics, segments, calculated metrics, and ranked reports (visits, orders, revenue … by day, page, channel or any dimension) in the report suite's time zone.
- Experience Platform: sandboxes, XDM schemas, datasets and audiences (segment definitions) in the chosen sandbox.
- Adobe Target: activities and their state (live, paused, draft), offers, audiences and each activity's performance by experience (visitors, conversions, lift).
- Launch: properties, rules, data elements, extensions and libraries with their publishing state.
What it can change — and what always waits for you
- Ordinary changes wait for your approval unless you turn on auto-approve: an Analytics segment or calculated metric, an Experience Platform audience or schema, a Target JSON offer, a Launch development library or a rule's enabled switch.
- Always a person: turning a Target activity live, an HTML offer (code on your site), building or publishing a Launch library, Launch custom code and extensions, Experience Platform data ingestion and dataflows, and every delete.
- Never: sandboxes, access control, privacy (data deletion) jobs, Analytics data repair and users — those stay in Adobe Admin Console.
Things to ask
- "Which Target activities are live, and which experience is winning in each?"
- "Show visits and orders by day for my main report suite for the last 30 days."
- "List the Launch rules on our website property that changed since the last published library."
- "Which Experience Platform schemas use the Profile class in our prod sandbox?"
Each Adobe product's own page
Each product is its own connection, with its own card, scopes, tools and MCP offering — pick the one you use:
- Adobe Analytics — reports, breakdowns, segments and calculated metrics.
- Adobe Experience Platform — schemas, datasets and audiences in a sandbox.
- Adobe Target — activities, offers, audiences and lift.
- Adobe Launch — properties, rules, data elements and libraries.
Frequently asked questions
- Does Agent Planners support Adobe Analytics, Target, Experience Platform and Launch?
- Yes. Each is its own integration: connect the ones you use, one by one, with your own Adobe OAuth Server-to-Server credential; each is checked with a read-only request, and the agent then reads and makes approval-gated changes in it.
- Do I need to type scopes?
- No. The scopes each product needs are added for you (from Adobe Developer Console's per-API list); with Paste JSON your credential's own scope list is used and checked.
- Is the client secret safe?
- It is used only on our server, stored encrypted and never shown again; the pasted JSON is not stored or logged. Access tokens stay on the server too.
- Can the agent make a Target activity live or publish Launch?
- Only with a person's approval, every time — auto-approve never applies those.
- What does Disconnect do?
- It deletes the stored credential and its tokens here, so no task, schedule or agent can reach your Adobe organization. The credential itself stays in Adobe Developer Console until you delete or rotate it there.