AI agent for Adobe Launch: properties, rules, data elements and libraries
Adobe Launch connects on its own card with an OAuth Server-to-Server credential from your Adobe organization. The agent reads properties, rules, data elements, extensions and libraries with their publishing state, makes approval-gated changes, and holds builds, publishing, custom code, extensions and deletes for a person.
Connecting Adobe Launch
- 1In Adobe Developer Console open a project (or create one), add the Experience Platform Launch API API and choose OAuth Server-to-Server. In Adobe Admin Console add that credential to the Launch product profile it should use — the profile decides what it may read and change.
- 2Give that profile Property Rights on the properties the agent should read; building a library also needs Develop / Publish rights there.
- 3Open Integrations → the Adobe Launch card → Connect. Paste the project JSON or type the Client ID, secret and IMS Organization ID.
- 4Press Test connection (the companies the credential reaches), pick the Launch company and, if you like, a default property, then Save connection.
AdobeID, openid, read_organizations, additional_info.job_function, additional_info.projectedProductContext, additional_info.roles.What the agent does in Adobe Launch
- Properties: web, mobile and edge properties with their domains and state.
- Rules and data elements: each with enabled, published and dirty (changed since the last publish) state and revision.
- Extensions and libraries: installed extensions and versions; libraries with their state (development, submitted, approved, published) and environment.
- Changes: switch a rule on or off (a new revision — it reaches the site only when a library with it is built and published), create a development library with the rules, data elements and extensions you name.
What it changes — and what waits for a person
- Ordinary changes follow your approval setting (by default each waits for your approval card): a development library, a rule switched on or off, a rule or data element whose settings are not code.
- Always a person: building a library (it deploys), submitting, approving or publishing a library, custom code (and any rule component or data element settings change that could rewrite it), extensions, environments, hosts, and every delete.
- Refused: creating or removing a Launch company, and anything under a credentials or users path.
What we measured with a real Adobe organization
- 13 properties read on the owner's Launch company, with their rules, data elements and libraries.
- A library add needs the resource's current revision. A resource changed since its revision answered 409 "needs to be revised"; the tool revises it and adds the new revision.
- In a throwaway property (created and deleted by the run): a data element created, renamed and deleted; an Adobe-managed host; a development environment; a library with the Core extension; and a build that succeeded (2026-11-11). Nothing was published to a site.
Things to ask
- "List the rules on our website property that changed since the last published library."
- "Which data elements are not used by any enabled rule?"
- "Turn off the old promo rule and put it in a new development library."
- "Which extensions are out of date on each property?"
Frequently asked questions
- Does Agent Planners support Adobe Launch?
- Yes. Adobe Launch is its own integration: connect it with your own Adobe OAuth Server-to-Server credential, and the agent audits properties, rules, data elements, extensions and libraries and makes approval-gated changes.
- Can the agent publish Launch changes to my site?
- Not on its own. A rule switch and a new development library follow your approval setting; building, submitting, approving or publishing a library waits for a person every time.
- Can it add custom code?
- Only with a person's approval — custom code runs on your site, and a settings change that could rewrite it is held too.
- Is Adobe Launch the same as Adobe Launch?
- Yes. Adobe renamed Launch to Tags (part of Experience Platform Data Collection); the API is still the Reactor API. We call it Adobe Launch.