> ## 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 Customer Journey Analytics
> Connect Gradial to Adobe Customer Journey Analytics to turn cross-channel performance data into campaign recommendations, content updates, and activation plans.
Cross-channel performance data lives in CJA, but turning that data into a decision — a new audience, a content change, a follow-up campaign — requires analysts to translate reports into briefs, then hand those briefs to a separate team to act on them. The gap between insight and execution is where momentum dies.
Connect Adobe Customer Journey Analytics (CJA) and Gradial can read your data views, Workspace projects, filters, and calculated metrics — then turn that analysis into a concrete next action: updated content, a new campaign brief, a page change, or an activation step in a connected system. The analyst and the marketer can work in the same thread, moving from report to recommendation to execution without a handoff.
***
## What You Can Do
List data views and explore their dimensions, metrics, and date ranges. Pull the schema context Gradial needs to interpret your cross-channel data correctly.
Read Analysis Workspace projects, panels, and visualizations. Use project context to generate summaries, highlight trends, and draft recommendations.
List and inspect filters (segments) and calculated metrics. Reference audience definitions and custom KPIs when drafting briefs or activation plans.
Turn funnel analysis, behavior data, and segment performance into campaign briefs, content updates, journey plans, or execution steps in a connected system.
***
## Prerequisites
* An active Adobe Experience Cloud organization with Customer Journey Analytics licensed and live
* Access to the **Adobe Developer Console** to create a project and generate server-to-server OAuth credentials
* Your **IMS Org ID** and the **data view IDs** Gradial should have access to
* A product profile with CJA API access granted in Adobe Admin Console
* 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** and give it a name (e.g., `Gradial – CJA Integration`).
1. Inside your new project, click **Add API**.
2. Filter by **Experience Cloud** and select **Customer Journey Analytics**.
3. Choose **OAuth Server-to-Server** as the authentication type and click **Next**.
4. Select or create a **Product Profile** that grants CJA API access. The profile must be configured in Adobe Admin Console under Customer Journey Analytics.
| Scope | Required | Purpose |
| ----------------------------------------- | -------- | -------------------------------------------------- |
| `adobeanalytics.read` | Yes | Read data views, dimensions, metrics, and projects |
| `adobeio.appregistry.read` | Yes | Required for OAuth token exchange |
| `read_organizations` | Yes | Resolve IMS org context |
| `additional_info.projectedProductContext` | Yes | Confirm CJA product entitlement |
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**
Keep the Client Secret secure. It grants API access to your CJA data views and should be treated as a sensitive credential. Regenerate it in Adobe Developer Console if it is ever exposed.
Gradial reads CJA data using data view IDs. To find them:
1. In CJA, go to **Data Management → Data Views**.
2. Open each data view you want Gradial to access.
3. Copy the **Data View ID** from the URL or the data view settings panel (format: `dv_xxxxxxxxxxxxxxxxxx`).
Provide these IDs during Gradial setup so Gradial knows which data views are in scope.
1. In Gradial, go to **Settings → Integrations**.
2. Find **Adobe Customer Journey Analytics** and click **+ Add**.
3. Fill in the connection details:
| Field | Value |
| ------------------------ | ------------------------------------------------- |
| **Integration Name** | A display name (e.g., `Acme – CJA Production`) |
| **IMS Org ID** | From step 3 |
| **Client ID** | From step 3 |
| **Client Secret** | From step 3 |
| **Technical Account ID** | From step 3 |
| **Data View IDs** | Comma-separated list of data view IDs from step 4 |
4. Click **Save**. Gradial validates the credentials and confirms access to the specified data views.
1. Go to **Settings → Environments** and select the Gradial Environment where CJA 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 |
| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------- |
| **Performance to brief** | Ask Gradial to summarize a Workspace project or data view trend, then draft a campaign brief based on what the data shows |
| **Funnel gap analysis** | Pull funnel metrics into a Gradial thread and ask it to identify drop-off points and recommend content or journey changes |
| **Segment-driven content** | Reference a CJA filter to have Gradial tailor copy, subject lines, or page content for a specific audience |
| **Cross-channel activation** | Use CJA insight to execute or draft a follow-up in AJO, SFMC, Marketo, AEM, or another connected system |
| **Reporting summaries** | Ask Gradial to translate a complex Workspace project into an executive summary or stakeholder brief |
**Example — Turn a funnel report into a campaign plan:**
1. Ask Gradial to list your CJA data views and pick the relevant one.
2. Have Gradial pull the funnel visualization from a Workspace project.
3. Ask Gradial to identify the biggest drop-off step and draft a re-engagement email.
4. Execute the draft in a connected system — AJO, SFMC, or Marketo — in the same thread.
**Example — Segment-specific content update:**
1. Ask Gradial to list the filters defined in a data view.
2. Select a high-value segment and ask Gradial to draft a tailored landing page headline and body copy.
3. Have Gradial push the update to AEM or your connected CMS.
***
## What's Not Covered Yet
* Writing back to CJA — the integration is read-only; Gradial cannot create or modify data views, projects, or filters through the API.
* Raw event-level data queries — Gradial reads aggregated project and dimension data, not individual event streams.
* Report Suite data from legacy Adobe Analytics — use the Adobe Analytics integration for that context.
* Real-time streaming data — CJA's API returns processed batch data, not live event streams.
***
## Troubleshooting
| Issue | Cause | Solution |
| ---------------------------- | --------------------------------------- | ------------------------------------------------------------------------------------------------------- |
| `401 Unauthorized` | Invalid or expired credentials | Regenerate the Client Secret in Adobe Developer Console and update Gradial |
| `403 Forbidden` | Product profile lacks CJA API access | Confirm the profile has CJA API permission in Adobe Admin Console |
| `404 Not Found` on data view | Data view ID is incorrect or not shared | Verify the data view ID and confirm the technical account has been added to the data view's access list |
| No data views returned | IMS Org ID mismatch | Confirm the IMS Org ID matches the organization where CJA is provisioned |
| Token exchange fails | Missing required OAuth scopes | Re-add the API in Adobe Developer Console and confirm all required scopes are selected |
***
## Good to Know
* **Data view access is explicit**: The technical account created by the Adobe Developer project must be added to each CJA data view individually under **Data Views → Access**. If Gradial returns an empty data view list, this is the most common cause.
* **Workspace projects are read via the Projects API**: Only projects saved in Analysis Workspace are accessible. Auto-saved or unsaved drafts are not returned.
* **Calculated metrics are org-scoped**: Gradial can read calculated metrics defined at the org level. Data-view-scoped calculated metrics require the matching data view ID to be in scope.
* **Rate limits apply**: The CJA API enforces rate limits per org. For high-volume analysis threads, Gradial batches requests automatically.
***
## Support
Contact your Gradial onboarding lead or email [support@gradial.com](mailto:support@gradial.com) for help with setup.