Adobe Experience Cloud
Adobe Target cannot offer CJA as a reporting source during migration
The Target reporting menu lacks Customer Journey Analytics. Check account settings, permissions and integration prerequisites before a live cutover.
October 23, 2026
An analytics team is moving from Adobe Analytics to Customer Journey Analytics, but CJA does not appear where the Target activity's reporting source is chosen. An Experience League question reports this exact migration blocker. Treat the missing option as a configuration and eligibility investigation before rebuilding an experiment.
Check both layers of reporting configuration
Adobe documents account-level reporting settings that determine available reporting solutions. Its Target reporting in CJA guide lists roles, sandbox and integration prerequisites, supported activity types and data requirements. Record which prerequisite has been verified by an administrator; having admin access to both products alone does not prove the integration is ready.
Protect the measurement decision
Check the activity state before editing. Adobe warns that an activity's reporting source cannot be changed after it is live. If an existing experiment is already collecting data, plan a new activity or a documented measurement handoff instead of silently changing the source of truth. Reconcile experiment IDs, exposures and conversion definitions before comparing reports across systems.
Escalate with evidence
If the account setting and documented prerequisites are correct but the option is still absent, give Adobe Support the tenant, activity type, sandbox, reporting settings and screenshots. A community reply suggests support may need to enable something in some accounts; that is a case-specific lead, not a universal fix.
Adovo’s view
Measurement belongs in the launch decision. An experiment whose reporting destination is unresolved is not ready, however polished the experience is. Lock the measurement contract before audiences see the activity.
