AI agent for Adobe Target: A/B tests, offers, audiences and lift
Adobe Target connects on its own card with an OAuth Server-to-Server credential and your Target tenant. The agent reads activities, offers, audiences, locations and each activity's performance by experience, makes approval-gated changes, and holds turning an activity live, HTML offers and deletes for a person.
Connecting Adobe Target
- 1In Adobe Developer Console open a project (or create one), add the Adobe Target API and choose OAuth Server-to-Server. In Adobe Admin Console add that credential to the Adobe Target product profile it should use — the profile decides what it may read and change.
- 2Note your Target tenant: the name after
@in your Target address (https://experience.adobe.com/#/@tenant/target). Adobe has no API that lists it; the card suggests it from your organization's name and confirms it with Target. - 3Open Integrations → the Adobe Target card → Connect. Paste the project JSON or type the Client ID and secret.
- 4Press Test connection (one read of the activities), confirm the tenant, and Save connection.
openid, AdobeID, target_sdk, additional_info.projectedProductContext, read_organizations, additional_info.roles. A wrong tenant answers Adobe's 403 502061, which the card names as "additional configuration required".What the agent does in Adobe Target
- Activities: A/B and Experience Targeting activities with their state (live, saved, deactivated, archived), priority and dates; one activity with its locations, experiences and metrics.
- Performance: each activity's report by experience — visitors, visits, conversions and lift.
- Offers and audiences: HTML and JSON offers, audiences, locations (mboxes), environments and properties.
- Changes: a JSON offer, an audience, an activity created as saved, an activity deactivated or saved — and, with a person, an activity made live.
What it changes — and what waits for a person
- Ordinary changes follow your approval setting (by default each waits for your approval card): a JSON offer, an audience, a new activity (created saved, never live), deactivating or saving an activity.
- Always a person: turning an activity live (state approved — directly or inside a gateway body), any HTML or content offer (code that runs on your site), and every delete.
- Refused: the Target batch endpoint — each change is sent and judged on its own.
What we measured with a real Adobe organization
- Each Target resource has its own media type: offers v2 only, activities and audiences v3, mboxes, environments and properties v1. A wrong one answered 415; the tools set the right one per path.
- The tenant was found from the organization's name with at most four probe reads, then confirmed.
- An HTML offer was created, changed, read back and deleted; an audience created and deleted; an A/B activity created saved, deactivated and deleted (2026-11-11) — it was never made live.
Things to ask
- "Which Target activities are live, and which experience is winning in each?"
- "Show visitors, conversions and lift by experience for the homepage hero test."
- "Deactivate the activities that ended last month."
- "Create a JSON offer for the spring banner and a saved A/B activity that uses it."
Frequently asked questions
- Does Agent Planners support Adobe Target?
- Yes. Adobe Target is its own integration: connect it with your own Adobe OAuth Server-to-Server credential and your tenant, and the agent reads activities and their lift and makes approval-gated changes.
- Can the agent make a Target activity live?
- Only with a person's approval, every time — making an activity live changes what visitors see on your site, so auto-approve never applies it.
- Where do I find the Target tenant?
- It is the name after @ in your Target address: https://experience.adobe.com/#/@<tenant>/target. Adobe has no API that lists it; the card suggests it and confirms it with Target.
- Can it create offers?
- A JSON offer follows your approval setting; an HTML offer is code that runs on your site, so a person approves it every time.