Connect
Adobe Target: connect your tenant, permissions and tools
TL;DR
Adobe Target connects on its own Integrations card with an OAuth Server-to-Server credential and your Target tenant (the name after @ in your Target address); the credential's product profile decides which workspace and properties the agent reaches.
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 Target, choose OAuth Server-to-Server, and tick the Target product profile (its workspace) the agent should use.
- 3Find your tenant: the name after
@inhttps://experience.adobe.com/#/@tenant/target/activities. - 4Press Download for Project JSON, or copy the Client ID and Retrieve client secret.
Connect
- 1Integrations → Adobe Target → Connect → Paste JSON (or Manual entry).
- 2Test connection suggests the tenant from your organization's name (at most four probe reads) and confirms it with
GET /{tenant}/target/activities?limit=1. - 3Type or confirm the tenant and Save connection. Adobe has no API that lists tenants.
Scopes are added for you:
openid, AdobeID, target_sdk, additional_info.projectedProductContext, read_organizations, additional_info.roles. A wrong tenant answers Adobe's 403 502061, shown as "additional configuration required".Which permissions unlock what
- The product profile's workspace and properties: activities, offers (HTML and JSON), audiences, locations (mboxes), environments, properties and activity reports in that workspace.
- An approver role in that workspace is what lets an activity be made live once a person approves it here.
Every Adobe Target tool
6 reads and 3 writes, plus get_connection and test_connection shared by the four Adobe products.
| Tool | Kind | What it does |
|---|---|---|
target_list_activities | Read | Target activities (GET activities): id, name, type (ab | xt | …), state (approved = live | deactivated | saved | archived), priority, startsAt / endsAt, modifiedAt. |
target_get_activity | Read | ONE activity with its locations, options, experiences and metrics (GET activities/ab/{id} or activities/xt/{id}). |
target_list_offers | Read | Offers (GET offers): id, name, type (content | json …), modifiedAt. |
target_list_audiences | Read | Target audiences (GET audiences): id, name, description, origin, modifiedAt. |
target_activity_report | Read | An activity's performance report (GET activities/ab/{id}/report/performance or xt): visitors, visits, conversions and lift per experience. |
target_get | Read | ANY Target Admin API GET under the tenant (path relative to /{tenant}/target/: activities[/ab|xt/{id}], offers[/content|json/{id}], audiences[/{id}], properties, mboxes, environments, reports …). |
target_set_activity_state | Write — always a person | Change an activity's state (PUT activities/state with the id): { accountId?, activityId, state: approved | deactivated | saved }. ★ approved (the activity goes LIVE on the site) is PERSON-GATED on every lane. |
target_create_offer | Write | Create an offer (POST offers/content or offers/json): { accountId?, name, type: html | json, content (an HTML fragment, or a JSON object / string) }. ★ An HTML offer is code that runs on the site — PERSON-GATED. |
target_mutate | Write | Any other Target Admin API write under the tenant (method POST | PUT | DELETE, path relative to /{tenant}/target/, body = Adobe's own fields; contentType? defaults to application/vnd.adobe.target.v3+json): activities … |
Over MCP and the REST API the names are adobe__<tool> (for example
adobe__target_list_activities). 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.Formats and limits
- Each Target resource has its own media type, set per path: offers v2, activities and audiences v3, the rest v1 (a wrong one answers 415).
target_getandtarget_mutatetakeaccept/contentTypeto override. - Activities: up to 1,000 per call with
offset. Reports take areportIntervaland anenvironmentId. - State words: approved = live, saved, deactivated, archived.
Changes and approvals
- Ordinary changes follow the approval setting — by default each waits for your approval: a JSON offer, an audience, a new activity (created saved), deactivating or saving an activity.
- A person approves, every time: an activity made live (state approved, also inside a gateway body), any HTML or content offer, and any DELETE.
- Refused on every lane: the Target batch endpoint 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 Target: what the agent does · setup and every tool · MCP server · AI agent guide · playbook. The other Adobe products, each its own connection: Adobe Analytics · Adobe Experience Platform · Adobe Launch · All four together: Adobe.
Frequently asked questions
- Why does Target say Additional configuration required?
- The tenant is missing or wrong. It is the name after @ in your Target address; Adobe has no API that lists it.
- Can an activity go live without me?
- No. Making an activity live waits for a person every time, whatever the approval setting.
- Why does an offer answer 415?
- Each Target resource accepts one media type; the tools set it per path. Pass accept / contentType only when you call an endpoint the tools do not know.