Adobe Target and CJA: From Clicks to Outcomes That Matter

Publication date: November 2, 2026

The A/B test is over, and the team has a reason to celebrate: version A earned more clicks. Somebody is already pitching it for the next campaign when another person asks an awkward question: “But how many people finished the application?” Suddenly the morning’s winner needs a second look.

In personalization, attention, intent and business value are not interchangeable. Clicking, beginning an application and completing it are different stories. When each department chooses the metric that makes its own design look best, a single experiment can produce several winners. That sounds diplomatic; analytically, it is a mess.

One experiment, more useful questions

Adobe Target decides which experience to deliver; Customer Journey Analytics (CJA) extends the story of what happens afterward. With CJA as the reporting source for Target, teams can analyze Target activities using CJA success metrics and calculated metrics and use the Experimentation panel. Target and Adobe Journey Optimizer reporting can also be explored in CJA when the required data and configuration exist.

Imagine a fictional financial-services application. Variant A persuades more visitors to begin the process, while variant B leads to more completed applications. If the business objective is completion, clicks alone cannot select the winner. This example is illustrative, not a real client result.

CJA gives analysts flexibility to examine success metrics during analysis. That differs from explicitly choosing a CJA metric as an optimization objective during the setup of certain manual A/B or Auto-Allocate activities. We should separate what the experiment optimizes from what the team later investigates. And a pretty chart never replaces a look at sample size, attribution, effect size and statistical confidence.

The hidden data story behind an A/B result

Implementation requires access to Adobe Target and CJA, an Editor or Approver role in Target and the relevant Adobe Experience Platform role. The activity must select CJA as its reporting source and use the appropriate sandbox. A Data View may be selected for manual A/B tests and is required for Auto-Allocate. The CJA connection and Data View must include the relevant event and Target classification data.

One deceptively small detail matters enormously: dimension persistence. When someone sees an experience on the home page and buys later, that purchase event may not carry the original activity dimensions. Without persistence for Activity Name and Activity ID, CJA can miss the association between a later metric and the experience. Test the full path: exposure, interaction and outcome, not just the dashboard.

This integration is not Adobe Analytics for Target (A4T), and there is no equivalent prebuilt A4T report. Teams build reports in CJA. The reporting source cannot be changed once an activity goes live. Manual A/B, Auto-Allocate, Experience Targeting, Multivariate Test and Recommendations are supported; Auto-Target and Automated Personalization are not. Data View and goal-metric options depend on activity type.

Next time someone says “we won the A/B test,” perhaps ask for the rest of the story. What happened after the click, which event captured it, and would we make the same decision if we had to defend it to the business?

Technical reference: Adobe Experience League, Target reporting in Adobe Customer Journey Analytics, updated October 27, 2026 — https://experienceleague.adobe.com/en/docs/target/using/integrate/cja/target-reporting-in-cja

Note: the financial-services example and numerical values in the cover artwork are fictional.