Skip to main content
Ram_KK
Level 1
September 16, 2026
Question

Email Opens and clicks not displaying in CJA despite data availability

  • September 16, 2026
  • 1 reply
  • 20 views

The customer Journey Management > message Execution field group physically exists in both the AJO message feedback schema and the AJO email tracking schema. I can see the field in the tracking schema and build a CJA report against it. But at runtime, the value is never actually populated on tracking events.

Since opens are tracking events, and tracking events never carries messageExecution. metadata, any CJA report keyed on that metadata for opens/clicks will be blank.

I tried identity stitching for tracking and feedback events datasets in CJA with an Identity Map as EID in both datasets. But still unable to see engagement metrics (email opens and email clicks) when using the metadata LOB value filter for email opens and clicks in Email Journey Reporting in CJA. Is anyone facing a similar issue in CJA?

 

 

 

 

 

 

 

1 reply

Prasanth
Prasanth
Level 2
September 17, 2026

Hi ​@Ram_KK ,

The underlying problem stems from the fact that messageExecution metadata is generated during the delivery phase. While the _experience.customerJourneyManagement.messageExecution field exists in the AJO Email Tracking Schema, tracking events generated dynamically via redirect links/tracking pixels often lack this full metadata payload at runtime. As a result, applying a filter based on messageExecution or Line of Business (LOB) metadata drops the tracking events, leaving Opens and Clicks blank in Customer Journey Analytics (CJA).

Root Cause Analysis

  1. Missing Metadata on Tracking Events: Opens and Clicks occur downstream from delivery. The AJO tracking engine often populates messageID, actionID, or journeyVersionID, but omits custom execution metadata like LOB metadata on tracking hits.

  2. Strict Component Filtering: When you apply your LOB filter, CJA evaluates each event line-by-line. Because the Tracking dataset lacks those specific metadata fields, all open/click events are filtered out.

  3. Identity Stitching Limit: Identity Stitching merges profile timelines based on standard person IDs (e.g., ECID, IdentityMap), but it does not copy over event-level execution metadata from Feedback events to Tracking events.

Recommended Solutions

Option 1: Use Derived Fields in CJA (Best Practice)

Instead of relying on the raw event field, create a Derived Field inside your CJA Data View to infer or copy the LOB metadata across the session.

  1. Go to CJA Data View Settings > Derived Fields.

  2. Create a new field that sets a Session-level or Person-level persistence for the LOB value.

  3. Set the condition so that when messageExecution.LOB is present (from the Message Feedback Event), it persists across subsequent Tracking Events within the same session/journey.

Option 2: Join Datasets via CJA Lookup or Derived Key

If you need exact reporting based on messageExecutionID or actionID:

  1. In your Data View, bring in the key messageExecution.messageID or actionID present on both schemas.

  2. Map your LOB metadata filter to Feedback Events or pass LOB via URL tracking parameters (UTM parameters) mapped in tracking schemas.

  3. Build your Workspace report using Attribution Models (e.g., Last Touch or Participation) so that the Open/Click metrics inherit the LOB dimension from the antecedent Feedback Event.

Option 3: Query Service / Data Prep Transformation

If you require this metadata natively in the dataset:

  1. Create a Data Prep mapping rule in Adobe Experience Platform (AEP) to pass LOB metadata into link tracking parameters (e.g., custom URL parameters on email links).

  2. Ensure the Email Tracking Schema extracts this parameter into the tracking event payload.

Terms & ConditionsAccessibility statement

Loading footer...