> ## 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 Target Integration

> Connect Gradial to Adobe Target for experimentation and personalization — browse, create, preview, and activate activities without leaving the platform.

Teams can work with Adobe Target activities, audiences, offers, mboxes, properties, and environments directly from Gradial, then preview and launch personalized experiences without switching tools.

***

## What You Can Do

<CardGroup cols={2}>
  <Card title="Activity management" icon="list-check">
    Browse, filter, create, rename, schedule, prioritize, activate, and deactivate Adobe Target activities — including A/B tests and experience targeting — without leaving Gradial.
  </Card>

  <Card title="In-context previews" icon="eye">
    Preview each experience before launch. When a Default Preview URL is configured, Gradial generates in-context previews directly inside the workflow so PMs and marketers can review outcomes earlier.
  </Card>

  <Card title="Audiences, offers & mboxes" icon="users">
    Work with audiences, offers, mboxes, properties, and environments. Use the dedicated Adobe Target authoring assistant to shape experiences end to end.
  </Card>

  <Card title="Performance reporting" icon="chart-bar">
    Review performance and order reporting to support optimization decisions, and combine Adobe Analytics insights with Adobe Target execution in a tighter loop.
  </Card>
</CardGroup>

***

## Prerequisites

Before connecting Adobe Target to Gradial, make sure you have:

* An active **Adobe Experience Cloud** organization
* Access to **Adobe Developer Console** to create or open a project for the correct organization
* **Tenant ID** for your Adobe Target instance (found in the Target URL subdomain after signing in to Adobe Experience Cloud)
* **IMS Organization ID** from your Adobe credential details
* A Gradial organization **Administrator** role to complete setup

<Info>
  The setup pattern is the same as Adobe Analytics. If you have already configured that integration, you can reuse the same Developer Console project and credentials.
</Info>

***

## How to Connect

<Steps>
  <Step title="Create credentials in Adobe Developer Console">
    1. Go to [Adobe Developer Console](https://developer.adobe.com/console/) and sign in for the correct Experience Cloud organization.
    2. Create or open the project you want to use for this integration.
    3. Click **Add API** and select **Adobe Target**.
    4. Choose **OAuth Server-to-Server** as the credential type.
    5. Select the product profiles or workspaces the integration should be allowed to use.
    6. From the credential details screen, copy the **Client ID**, **Client Secret**, and **Organization ID**.
  </Step>

  <Step title="Find your Tenant ID">
    Sign in to Adobe Experience Cloud and open Adobe Target. Your Tenant ID appears in the URL after `#/@` (e.g., `https://experience.adobe.com/#/@yourcompany/target` → Tenant ID is `yourcompany`).

    <Warning>
      The Tenant ID is different from the Target client code. Use the subdomain from the Target URL, not the client code shown in Target's admin settings.
    </Warning>
  </Step>

  <Step title="Add the integration in Gradial">
    1. In Gradial, go to **Settings → Integrations**.
    2. Find **Adobe Target** and click **+ Add**.
    3. Fill in the connection details:

    | Field                                | Value                                                                                                                                        |
    | ------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------- |
    | **Integration Name**                 | A display name (e.g., `My Adobe Target Connection`)                                                                                          |
    | **Adobe Target API URL**             | Pre-filled as `https://mc.adobe.io` — leave as-is                                                                                            |
    | **Authentication Type**              | Fixed to **OAuth 2.0 Client Credentials**                                                                                                    |
    | **Client ID**                        | From your Adobe Developer Console project                                                                                                    |
    | **Client Secret**                    | From your Adobe Developer Console project                                                                                                    |
    | **Token URL**                        | Use Adobe's standard token URL unless your Adobe team has specified a different approved value                                               |
    | **Scope**                            | Use Adobe's standard Target scope unless otherwise directed                                                                                  |
    | **Tenant ID**                        | Your Target tenant slug, used in API request paths (e.g., `clientcode123`)                                                                   |
    | **IMS Org ID**                       | Your Adobe Organization ID ending in `@AdobeOrg` — sent as the IMS organization header on Target API requests                                |
    | **Default Preview URL** *(optional)* | A base URL for your live or preview site. When set, experiment previews auto-load against this URL. Leave blank to be prompted per activity. |

    4. Click **Save**.
  </Step>

  <Step title="Assign to an Environment">
    1. Go to **Settings → Environments** and select the Environment where Adobe Target should be available.
    2. Add the Adobe Target integration to that Environment.
    3. Repeat for any additional Environments.
  </Step>
</Steps>

***

## How It Fits Into Broader Workflows

| Use case                          | How to use it                                                                                                                                                                                   |
| --------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Analytics → Target loop**       | Combine Adobe Analytics insights with Adobe Target execution. Use CX Optimizer to identify where performance is under target, define the next audience, and move straight into a new experiment |
| **Faster personalization cycles** | Preview the experience in context before launch, then activate — cutting the time between identifying an opportunity and going live                                                             |
| **End-to-end in Gradial**         | Draft offers, shape audiences, preview experiences, and activate activities all from the same workflow without context-switching                                                                |

**Example flow:**

1. Start with a performance insight from Adobe Analytics or CX Optimizer.
2. Identify the audience that should receive a different experience.
3. Draft or refine the offer in Gradial using the Adobe Target authoring assistant.
4. Preview each experience variant before launch.
5. Activate the activity and begin learning from results.

***

## Troubleshooting

**"Invalid client" error when saving**
Double-check that the Client ID and Client Secret are copied exactly from Adobe Developer Console with no extra spaces.

**Tenant ID not recognized**
Confirm you are using the subdomain from the Adobe Target URL, not the client code. These are different values and the API requires the subdomain form.

**IMS Org ID error**
The IMS Org ID should end in `@AdobeOrg`. Copy it directly from the Adobe Developer Console credential details screen.

**Previews not loading automatically**
Set a **Default Preview URL** in the integration settings. Without it, Gradial will prompt you for a URL each time you preview an activity.

**Integration not available in a Workspace**
Assign the integration to the correct Environment under **Settings → Environments**.

***

## Support

Contact your Gradial onboarding lead or email [support@gradial.com](mailto:support@gradial.com) for help with setup.