Streaming records getting qualified first time after it is getting exited from audience

Hey,

Yes this is expected behaviour from AEP — but totally manageable once you understand what's actually happening.

What's going on

When a profile exits an audience, AEP still sends one final record to Event Hub. That record isn't saying the profile is qualified — it's the exit notification. The problem is if your downstream system isn't reading the status field, it treats every incoming record as active.

Think of it like an unsubscribe email — the system sends you one last message to tell you someone left. You still need to process that message correctly.

The fix

Every record arriving at Event Hub has a status field in it. Check it before doing anything:

• realized → profile just joined the audience → process it
• existing → profile is still in the audience → process it
• exited → profile just left the audience → suppress or remove it

if (status === "realized" || status === "existing") {
  // active — process normally
} else if (status === "exited") {
  // left the audience — suppress or remove
}

That one check in your consumer logic solves it completely.

If you can't touch the consumer logic

Add a filter between Event Hub and your downstream system that simply drops any record where status is exited before it reaches processing.

Short answer — not natively for streaming destinations, no.

AEP sends that exit record by design. There's no setting or toggle in the platform to suppress it on the way out. The architecture is built to give downstream systems full lifecycle awareness, so the exit signal is intentional.

That said, there are two things you can do on the AEP side that change the equation:

Switch to a batch destination — batch exports are clean snapshots. Only profiles currently in the audience show up in the file. No exit records, no status noise. If your use case can work off a scheduled export (hourly/daily) rather than real-time, this removes the problem entirely.

Activation filters — when you're configuring the destination activation in RTCDP, some destination types let you filter which membership statuses get exported. Worth checking your destination's mapping/scheduling step to see if that option is available for your specific destination type.

For Event Hub specifically though — you're on a streaming enterprise destination, and those will always get the exit signal. The platform-side options are limited. 

That said, this is based on my experience and current platform behaviour — I'd recommend also raising it with Adobe Support to confirm if there's anything specific to your setup or if newer platform releases have introduced any native controls around this. They'll have visibility into your exact config and any roadmap items that may be relevant.