Five Steps to Unlock AJO, AEP, and CJA in Your MiaProva Integration

A quick guide for MiaProva customers extending their existing Adobe Developer Console project

If MiaProva has been running against your Adobe Analytics and Target data for a while, you already have most of the plumbing in place. Good news: you don’t need a new project, a new organization, or a new integration to bring Adobe Journey Optimizer (AJO), Adobe Experience Platform (AEP), and Customer Journey Analytics (CJA) into the fold. You’re extending the project you already have.

There is one twist worth knowing up front: getting MiaProva’s newer AA/CJA reporting features fully working also means adding a second, different kind of credential — one that requires an actual human login — and flipping on a permission that lives in a completely different console than the one you’re used to. This post walks through all of it.

The Short Version

You’re going to touch two Adobe consoles:

1. Adobe Developer Console — where you add the new APIs (AEP, AJO, CJA) and a new authentication credential.
2. Adobe Admin Console — where you flip on a permission item that Analytics and CJA use to gate their MCP-based reporting tools.

Here’s the full sequence:

Why You Need a Second Credential Type

Your existing integration almost certainly runs on an OAuth Server-to-Server credential — the standard choice for machine-to-machine calls where no person is sitting at a keyboard. That credential will keep working fine for AEP, AJO, and CJA data calls.

But MiaProva’s Analytics and CJA reporting features lean on Adobe’s MCP (Model Context Protocol) tools, and those tools specifically require a user-authenticated token. A service account token — no matter how well-permissioned — won’t get you in the door. That means your project needs a second credential type alongside the first: an OAuth Web App credential, which runs an interactive browser login.

Think of it as two keys to two different doors. You need both on the same keyring.

Step-by-Step

1–3. Add the AEP, AJO, and CJA APIs

From inside your existing project in the Adobe Developer Console:

1. Click Add API, filter by Experience Cloud, and select the API you need (Experience Platform, Journey Optimizer, or Customer Journey Analytics).
2. Click Next, then choose OAuth Server-to-Server as the authentication method.
3. On the product profile screen, select the profiles you want this credential to reach.
4. Click Save configured API.

Repeat for each of the three APIs. Do this one at a time — Adobe walks you through one API per pass.

4. Add the OAuth Web App Credential

Still inside the project, add a second credential — this time choosing OAuth Web App instead of Server-to-Server. You’ll need to supply the redirect URI(s) MiaProva gives you, and you’ll come away with a separate Client ID and Client Secret from your Server-to-Server credential. Keep the two straight — MiaProva needs both, and they aren’t interchangeable.

One Habit Worth Building: Select All Product Profiles

At every one of the steps above, when Adobe asks which product profiles the credential should reach, select all available profiles rather than picking just the one you need today.

It’s tempting to scope things narrowly and lock everything down. In practice, MiaProva’s feature set is still growing — governance surfaces, alerting, and Journey Readiness tooling all reach into different product profiles as they mature — and a narrow grant today just means someone has to come back and widen it later. Match the broader access you likely already gave Analytics and Target.

5. Enable MCP Access — in the Other Console

This is the step people miss, because it isn’t in the Developer Console at all. Adobe Analytics and CJA gate their MCP reporting tools behind a specific permission item, and that permission lives inside the Admin Console, attached to a product profile rather than to your API project.

To find it:

1. Go to adminconsole.adobe.com.
2. Click Products → Adobe Analytics, open the relevant product profile, go to Permissions → Reporting, and switch on MCP Access.
3. Repeat under Products → Customer Journey Analytics for the matching CJA profile.

Skip this step and everything else will look correctly configured — the APIs are attached, both credentials authenticate cleanly — but MiaProva’s MCP-driven Analytics and CJA reporting calls will still get turned away.

Wrapping Up

Once you’ve worked through all five steps, hand your MiaProva contact:

• Your (now broader) OAuth Server-to-Server Client ID, Client Secret, and Organization ID
• Your new OAuth Web App Client ID, Client Secret, and configured redirect URI(s)
• Confirmation that MCP Access is switched on for both the Analytics and CJA product profiles

From there, MiaProva can light up AJO, AEP, and CJA the same way it already lights up Analytics and Target — no new project, no do-over, just the same integration doing more.