> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gradial.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Adobe Journey Optimizer
> Connect Gradial to Adobe Journey Optimizer to inspect campaigns, journeys, messages, and templates — and execute supported operations across Adobe and adjacent marketing systems.
AJO gives marketing teams powerful journey orchestration, but acting on it is slow. Inspecting a live journey, understanding what an email looks like, drafting an update, and getting it through review typically means navigating multiple Adobe UIs, pulling in a developer for API work, and managing approvals in a separate tool. By the time a change is ready, the campaign moment may have passed.
Connect Adobe Journey Optimizer once and Gradial becomes your cross-platform execution layer: reading AJO context, reasoning over the marketing task, creating artifacts, and executing in AJO or any connected downstream system. Teams can inspect journeys, draft content updates, and move work through review — in the same thread where the brief was written.
***
## What You Can Do
Inspect AJO campaigns and journeys. View messages, templates, and fragments. Create or update supported objects when APIs and permissions allow.
Read templates and fragments so Gradial can reference them when drafting new messages. Generate content drafts aligned to your existing AJO assets.
Pull AJO tracking datasets and performance context. Turn campaign results into recommendations, content updates, or next-journey plans.
Use AJO context to execute or draft work in SFMC, Marketo, AEM, SMS, push, CMS, or another connected marketing system.
***
## Prerequisites
Before starting setup, confirm the following are in place:
* An active Adobe Experience Cloud organization with AJO licensed and live
* Access to the **Adobe Developer Console** to create a project and generate server-to-server OAuth credentials
* The **IMS Org ID** for your Adobe Experience Cloud organization
* The **sandbox name** (or environment) where Gradial should start — sandbox, staging, or production read-only
* Product profile membership that covers the AJO APIs in scope
* A Gradial organization **Administrator** role to complete setup
***
## How to Connect
1. Go to [Adobe Developer Console](https://developer.adobe.com/console) and sign in with your Adobe ID.
2. Select your organization from the org switcher.
3. Click **Create new project**.
4. Give the project a name (e.g., `Gradial – AJO Integration`).
1. Inside your new project, click **Add API**.
2. Filter by **Experience Cloud** and select **Adobe Journey Optimizer**.
3. Choose **OAuth Server-to-Server** as the authentication type and click **Next**.
4. Select or create a **Product Profile** that grants the API scopes needed:
| Scope | Required | Purpose |
| --------------------- | -------- | --------------------------------- |
| `ajo.campaigns.read` | Yes | Read campaigns |
| `ajo.journeys.read` | Yes | Read journeys |
| `ajo.messages.read` | Yes | Read messages and channel content |
| `ajo.templates.read` | Yes | Read templates and fragments |
| `ajo.campaigns.write` | Optional | Create or update campaigns |
| `ajo.journeys.write` | Optional | Create or update journeys |
5. Click **Save configured API**.
From the project's **OAuth Server-to-Server** credential page, copy:
* **Client ID**
* **Client Secret**
* **IMS Org ID**
* **Technical Account ID**
* **Sandbox name** (the AJO sandbox you authorized)
Keep the Client Secret secure. Anyone with this credential can act on behalf of your Adobe organization within the granted scopes.
1. In Gradial, go to **Settings → Integrations**.
2. Find **Adobe Journey Optimizer** and click **+ Add**.
3. Fill in the connection details:
| Field | Value |
| ------------------------ | ---------------------------------------------- |
| **Integration Name** | A display name (e.g., `Acme – AJO Production`) |
| **IMS Org ID** | From step 3 |
| **Client ID** | From step 3 |
| **Client Secret** | From step 3 |
| **Technical Account ID** | From step 3 |
| **Sandbox Name** | The AJO sandbox Gradial should connect to |
4. Click **Save**. Gradial validates the credentials before the integration goes live.
1. Go to **Settings → Environments** and select the Gradial Environment where AJO should be available.
2. Add the integration to that Environment.
3. Repeat for any additional Environments.
***
## How It Fits Into Broader Workflows
| Use case | How to use it |
| ---------------------------- | --------------------------------------------------------------------------------------------------------------------------- |
| **Campaign support** | Ask Gradial to inspect an AJO campaign, summarize its current state, and draft an updated message or subject line |
| **Journey planning** | Use Gradial to map an existing journey's structure, identify gaps, and draft the next phase |
| **Insight to content** | Pull AJO tracking data into a Gradial thread and have it generate a performance summary and follow-up content plan |
| **Cross-platform execution** | Use AJO audience and campaign context to execute or draft work in SFMC, Marketo, AEM, SMS, push, or CMS |
| **Migration acceleration** | Inventory source journeys and assets, classify what can be automated, and generate build packets for the destination system |
**Example — Inspect a campaign and draft updated copy:**
1. Ask Gradial to list active AJO campaigns.
2. Select a campaign and have Gradial summarize its messages and performance.
3. Ask Gradial to draft an updated subject line and body copy.
4. Review the draft and publish through AJO when ready.
**Example — Cross-platform activation:**
1. Share an AJO audience or journey with Gradial.
2. Ask Gradial to draft a matching email in Salesforce Marketing Cloud or Marketo.
3. Gradial reads the AJO context, creates the asset in the connected system, and returns a link for review.
***
## What's Not Covered Yet
* Direct send or trigger execution for live journeys — Gradial can draft and inspect, but send execution depends on API availability and your governance policy.
* Authoring new message surfaces or channel configurations — these are managed in the AJO UI.
* Private or beta AJO APIs — Gradial uses publicly available REST APIs only.
* Adobe Analytics or AEP audience context without a separate AEP integration configured.
***
## Customer Information Needed Before Setup
Use this checklist to confirm readiness before the integration meeting:
* [ ] Adobe IMS Org ID, sandbox name, and environment confirmation (sandbox, staging, or production read-only)
* [ ] Adobe Developer Console project with OAuth Server-to-Server credentials and required product profiles
* [ ] AJO context objects Gradial should read: campaigns, journeys, messages, templates, fragments, tracking datasets
* [ ] Active channels in scope: email, push, SMS, in-app, web
* [ ] Sender domains, consent policy, and suppression list configuration (required for any write operations)
* [ ] Adjacent execution systems if cross-platform activation is in scope: SFMC, Marketo, AEM, CMS, or another destination
* [ ] Governance model: who approves drafts, who can publish, who can send, and whether Gradial should start read-only
***
## Troubleshooting
| Issue | Cause | Solution |
| ---------------------- | ------------------------------ | -------------------------------------------------------------------------- |
| `401 Unauthorized` | Invalid or expired credentials | Regenerate the Client Secret in Adobe Developer Console and update Gradial |
| `403 Forbidden` | Missing API scopes | Add the required scopes to the product profile in Adobe Developer Console |
| `404 Not Found` | Incorrect sandbox name | Verify the sandbox name matches your AJO environment exactly |
| Token refresh failures | Client Secret rotated | Update the Client Secret in Gradial Settings → Integrations |
***
## Good to Know
* **Start read-only**: Gradial can deliver immediate value — inspecting campaigns, summarizing journeys, drafting content — without write permissions. Enable write scopes only when governance is confirmed.
* **Sandbox first**: Validate the integration in an AJO sandbox before pointing Gradial at a production environment.
* **Governance is explicit**: Read, draft, write, publish, and send permissions can be scoped separately so each team controls its own activation path.
***
## Support
Contact your Gradial onboarding lead or email [support@gradial.com](mailto:support@gradial.com) for help with setup.