Documentation

Resolving audience count discrepancies in Adobe Journey Optimizer

Last update: Mon Jun 02 2025 00:00:00 GMT+0000 (Coordinated Universal Time)

The number of processed entries in the Read Audience feature of Adobe Journey Optimizer can be lower than the expected audience count. This issue often arises due to incorrect namespace configurations, leading to profiles being excluded from journeys. The resolution involves checking and correcting namespace configurations, reviewing relevant documentation, and adjusting priorities to ensure smoother operations in Adobe Journey Optimizer.

Description description

Environment

Adobe Journey Optimizer (AJO)

Issue/Symptoms

When using the Read Audience feature in Adobe Journey Optimizer, the expected audience count often differs from the actual number of entries processed. For example, an audience with a count of 200,000 in the Audiences page may only show 99,000 entries processed. This discrepancy can impact email campaigns and related processes.

Profiles without values for every namespace may not enter the journey, causing the count mismatch. To validate counts, use the following SQL query to check the profile snapshot for the specific namespace and audience:

Note: You will need to find the name of your profile snapshot table within your Datasets section. Search for “snapshot.” You will have one snapshot table for each merge policy.

SELECT
count(identityMap[ 'namespace-code'] )
FROM profile_snapshot_export_###
WHERE
segmentMembership[ 'ups'] [ 'audience-id'] .status = 'realized'

Resolution resolution

To resolve the discrepancy in audience count within Adobe Journey Optimizer, follow these steps:

  1. Ensure all namespaces used within your journey are correctly configured. Incorrect or bad namespaces can lead to profiles being discarded and discrepancies in processing counts.
  2. Refer to the Identity namespace overview documentation for guidance on verifying and correcting namespace configurations. This will help you understand the proper setup and avoid future issues.
  3. If the issue persists without immediate resolution requirements, consider downgrading its priority. Continue to monitor its impact on operations to ensure it doesn’t affect critical processes.

For detailed information about the Read Audience  feature, refer to the Use an audience in a journey section of the Adobe Journey Optimizer Guide.

recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f