Profiles received count doesn’t match audience size in AEP activation monitoring

Profiles received in Adobe Experience Platform (AEP) activation monitoring often appears higher or different than expected when compared to audience size or destination output. That difference causes confusion when validating activations or troubleshooting delivery results. The key reason is that Profiles received tracks input processed by the activation pipeline, not the final number of profiles delivered. This article explains what Profiles received actually represents and how to interpret it correctly for batch and streaming destinations, including scenarios where the audience type and destination type don’t match.

Description description

Environment

Issue/Symptoms

Resolution resolution

How to understand the Profiles received metric

Profiles received is an activation input metric. It represents the profile records and change events processed by the activation pipeline for a specific run or time window, before filtering, deduplication, consent checks, and final export logic are applied. It doesn’t represent the current audience size, the number of unique profiles exported, or the number of rows delivered to a destination. Because of this, Profiles received should always be interpreted as pipeline input volume, not delivery output.

Interpretation for batch destinations

For batch destinations, Profiles received reflects the total records the batch activator ingests and processes during a run. This includes both snapshot data and incremental change‑event data over a lookback window. The same logical profile can appear multiple times across these inputs, which causes Profiles received to be higher than the audience size. In this context, the metric represents profiles plus change events processed by the batch activator, not the final exported count. This interpretation applies whether the audience itself is batch or streaming.

Streaming audiences activated to batch destinations

When a streaming audience is activated to a batch destination, the batch export includes streaming qualification deltas through incremental change‑event processing. Because of this, the exported state can appear newer than a visible snapshot or different from a static audience count. Profiles received reflects the processing of these incoming changes rather than a one‑time snapshot of qualified members.

Interpretation for streaming destinations

For streaming destinations, Profiles received represents the number of profile change or qualification events processed and pushed during the selected time window. The same profile can be counted multiple times if it generates multiple relevant updates. As a result, this metric reflects activity volume over time, not a static count of unique audience members.

Batch audiences activated to streaming destinations

When a batch audience is activated to a streaming destination, delivery is driven by qualification or profile change events going forward. Mapping a batch audience to a streaming destination doesn’t trigger a full historical backfill of all existing qualified profiles. Profiles received therefore reflects ongoing event‑driven processing rather than the total size of the batch audience.

Similar or overlapping guidance in the reference

The reference content includes two conceptually similar clarifications:

Both sections explain expectations when the audience type and destination type don’t match, and clarify that Profiles received reflects processing behavior, not audience size.

Related reading