We are about 18 months into a mature AEP + RTCDP implementation and have crossed 400 active segments across business units. We are starting to see non-trivial evaluation latency on streaming segments during peak ingestion windows and our architecture review flagged segment sprawl as a likely contributor.Adobe's documentation sets technical limits but doesn't offer much guidance on the operational governance model to prevent getting there particularly in a large enterprise where multiple teams (CRM, digital, paid media, product) all have write access to the segment builder.A few things I'm genuinely curious how others have solved:Do you enforce a segment approval workflow before publish to production, and if so, is that a process control or is there a technical gate you've built? How do you handle segment ownership when the original creator has left the team? Orphaned segments with no owner are our single biggest hygiene problem. Have you seen a material performance difference between streaming segments that use only profile attributes vs. those that join experience events? I suspect event-join segments are our heaviest compute consumers but haven't isolated it cleanly yet.Curious if anyone has built a segment lifecycle management framework even a lightweight one that scales beyond a single team.This feels like a gap between what the platform enables and what enterprise operations actually needs.

Level 2

Question

At what segment count does AEP performance visibly degrade and what's governance model to follow to stay ahead of it?

Forum|Forum|1 month ago
May 4, 2026
3 replies
65 views

We are about 18 months into a mature AEP + RTCDP implementation and have crossed 400 active segments across business units. We are starting to see non-trivial evaluation latency on streaming segments during peak ingestion windows and our architecture review flagged segment sprawl as a likely contributor.

Adobe's documentation sets technical limits but doesn't offer much guidance on the operational governance model to prevent getting there particularly in a large enterprise where multiple teams (CRM, digital, paid media, product) all have write access to the segment builder.

A few things I'm genuinely curious how others have solved:

Do you enforce a segment approval workflow before publish to production, and if so, is that a process control or is there a technical gate you've built?
How do you handle segment ownership when the original creator has left the team?
Orphaned segments with no owner are our single biggest hygiene problem.
Have you seen a material performance difference between streaming segments that use only profile attributes vs. those that join experience events?
I suspect event-join segments are our heaviest compute consumers but haven't isolated it cleanly yet.

Curious if anyone has built a segment lifecycle management framework even a lightweight one that scales beyond a single team.

This feels like a gap between what the platform enables and what enterprise operations actually needs.

G

GaneshKalamadug

Level 2

Very good question. we don’t follow this. We do have many segments and all the scenarios you mentioned. This was my research and we do have a plan in place. Not sure if this helps you.

Yes, enforce a simple approval before production—usually process-driven + restrict publish rights to a smaller team.
Make owner (person, not team) mandatory for every segment.
Run a weekly check to flag orphaned or unused segments and clean them up regularly.
Event-based segments (especially with time windows) are much heavier than profile-only ones.
Try to convert event logic into derived profile attributes where possible.
Classify segments by complexity and limit heavy ones.
Maintain a basic segment registry (owner, use, last used).
Add lifecycle rules (e.g., disable if unused for 120–180 days).
Key idea: treat segments like managed production assets, not ad hoc builds.

K

kalarav.vasavadaAuthor

Level 2

@GaneshKalamadug Thank you for your inputs. I really appreciate you sharing this aligns closely with where we have landed. One thing I would add on the approval workflow: process controls alone tend to break down under deadline pressure. Pairing them with a technical gate (restricting "Active" publish rights to a steward role in Admin Console) gives you the PR-style review as a hard backstop, not just a guideline people bypass in Q4. On ownership, mandatory person-level is right, but we added a backup owner field specifically to prevent the "person left the team" orphaning scenario and a separate hygiene flag for "owner no longer active in org" distinct from "no owner."

On the event-join performance point this is real and underweighted in Adobe's documentation. Our profiling showed long lookback windows on high-cardinality event types (commerce and other web interactions) were driving most of our evaluation lag. Converting "did X within N days" logic into scheduled batch-computed derived profile attributes and referencing those in streaming segments made a material difference turns a heavy event-join into a simple profile attribute lookup.

One more thing worth adding to your lifecycle framework: require a complexity tier classification at publish time, not just retroactively. It creates a forcing function during authoring and gives stewards something concrete to review before sprawl becomes a performance problem.

Thanks again for your response.

Devyendar

Level 6

@kalarav.vasavada those are interesting questions, yes having a central governance of the segments being build and period review is important to control and active segment volume and thereby performance.

In our team, we follow the same governance flow where business analyst across BUs create segments but we maintain only the active campaigns segment and deactivate rest.

In fact to better manage the lifecycle of the segments I have raised an enhancement request to Adobe to also include Pause, Scheduled Start and Scheduled End like features to manage the active segments volume and avoid the Segment sprawl issue you are facing.

Work with your CSM and TAM to create a similar enhancement request, Adobe will prioritize such request if multiple customers are requesting for it.

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded