What You Can Do
Audience Creation
Describe an audience in plain language and Gradial drafts the segment definition using available AEP datasets. Review the definition before anything is created.
Audience Retrieval
Retrieve existing audiences by name or ID. Inspect audience metadata including namespace, status, evaluation time, profile count, and segment definition.
Cross-System Activation
Use AEP audience context to feed AJO journeys, inform CJA analysis, or activate through Marketo, SFMC, or another connected marketing system.
Dataset Exploration
Query available datasets and schemas to understand what data is in scope before building or refining an audience.
Prerequisites
- An active Adobe Experience Cloud organization with AEP 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 sandbox name Gradial should connect to
- A product profile with AEP API access configured in Adobe Admin Console
- A Gradial organization Administrator role to complete setup
How to Connect
Create an Adobe Developer project
- Go to Adobe Developer Console and sign in with your Adobe ID.
- Select your organization from the org switcher.
- Click Create new project and give it a name (e.g.,
Gradial – AEP Integration).
Add the Experience Platform API
- Inside your new project, click Add API.
- Filter by Experience Cloud and select Experience Platform.
- Choose OAuth Server-to-Server as the authentication type and click Next.
- Select or create a Product Profile that grants AEP API access.
| Scope | Required | Purpose |
|---|---|---|
AdobeAnalytics | Yes | Access AEP datasets and schemas |
openid | Yes | Required for OAuth token exchange |
read_organizations | Yes | Resolve IMS org context |
additional_info.projectedProductContext | Yes | Confirm AEP product entitlement |
- Click Save configured API.
Copy your credentials
From the project’s OAuth Server-to-Server credential page, copy:
- Client ID
- Client Secret
- IMS Org ID
- Technical Account ID
- Token URL
Add the integration in Gradial
- In Gradial, go to Settings → Integrations.
- Find Adobe Experience Platform and click + Add.
- Fill in the connection details:
| Field | Value |
|---|---|
| Integration Name | A display name (e.g., Acme – AEP Production) |
| IMS Org ID | From step 3 |
| Client ID | From step 3 |
| Client Secret | From step 3 |
| Technical Account ID | From step 3 |
| Token URL | From step 3 |
| Sandbox | The AEP sandbox Gradial should connect to (e.g., aep-prod) |
| Capabilities | Select the capabilities to enable: AEP, CJA, AJO, or activation via Marketo |
- Click Save. Gradial validates the credentials before the integration goes live.
How It Fits Into Broader Workflows
| Use case | How to use it |
|---|---|
| Audience creation | Describe a target group in plain language — Gradial drafts the segment definition from available datasets and shows it to you before creating anything |
| Audience retrieval | Ask Gradial to retrieve an audience by name or ID and surface its full definition, status, profile count, and namespace |
| Journey activation | Use an AEP audience as the entry condition for an AJO journey — reference the audience in the same Gradial thread where you’re building the journey |
| Analytics hand-off | Feed an AEP audience into a CJA analysis thread to understand how that segment behaves across channels |
| Cross-system activation | Activate an AEP audience through Marketo, SFMC, or another connected system in the same Gradial thread |
Audience Management
Use Gradial to create and retrieve Adobe audiences in AEP so marketers can define target groups and reuse them across AJO journeys, campaigns, and CJA analysis.
“Create an Adobe audience for retail cart abandoners (Gradial Retail Cart Abandoners June 2026) who added items to cart but did not purchase. Use the available retail cart datasets, follow the standard naming convention, and show me the audience definition before creating it.”Retrieve an audience
“Retrieve the Adobe audience named retail_cart_abandoners. Show me its audience ID, namespace, status, last evaluation time, profile count, and segment definition details if available.”
Adobe Journey Optimizer
Use Gradial to retrieve AJO journeys, inspect each journey step, view the connected audience and authored email, and prepare safe campaign or content updates for review.
“Retrieve the AJO journey named Gradial-Retail-Cart-Reminder. Show the journey as steps, including the read audience step and send email step. When I select the email step, render the exact authored email from AJO.”Prepare a journey update
“Open the send cart email step in the AJO journey. Show me the current email, then prepare an updated version with a 48-hour free shipping message. Do not publish, send, or activate anything until I approve it.”
Customer Journey Analytics
Use Gradial to query and analyze CJA data so teams can understand customer behavior, journey performance, and campaign impact across Adobe data sources.
“Analyze cart abandonment performance in Customer Journey Analytics for June. Show abandonment volume, conversion rate, and the main drop-off points by journey step or channel.”Generate a report
“Create a CJA report for the retail cart abandonment journey. Include audience size, email engagement, conversion trends, and key recommendations for improving the journey.”
What’s Not Covered Yet
- Real-time event streaming from AEP — Gradial reads processed data, not live event streams.
- Adobe Target experiments — use the Adobe Target integration for A/B and multivariate testing.
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 or product profile access | Confirm the product profile has AEP API permission in Adobe Admin Console |
| Empty audience results | Sandbox mismatch | Verify the sandbox name matches the environment where audiences are defined |
| 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
- One credential set covers the full Adobe suite: The same OAuth Server-to-Server credentials work across AEP, AJO, and CJA when the product profile has access to all three. You don’t need separate Developer Console projects for each Adobe product.
- Sandbox selection matters: Audiences, journeys, and datasets are sandbox-scoped. Make sure Gradial is pointed at the sandbox where your working data lives.
- Pair with AJO and CJA: AEP is most powerful when combined with the Adobe Journey Optimizer and Adobe Customer Journey Analytics integrations in the same Gradial Environment.