In CJA, profile attributes don’t expand with the date range because they’re not event-based counts.
They come from the latest stitched profile, not from historical events.
So when you break down People by a profile field (Y / N):
The value counts stay the same → because CJA looks at each person’s current profile state.
The “No value” bucket grows with a bigger date range → because more people show up in events, but their profile didn’t have that attribute populated.
This is why the value rows (Y/N) look static across 7/14/60/180 days — you’re not counting “people who triggered events with this attribute,” you’re counting “people whose profile currently has this attribute.”
If you want the attribute to behave historically (date-range sensitive), you must store it as an event attribute, not a profile attribute.
Two options that work:
1. Add the Y/N flag into the event dataset
- Each visit/event carries the attribute
- Counts now scale with date range
- No dependence on profile stitching
2. Create a daily snapshot dataset
- Push the profile attributes as a “daily profile snapshot” event
- CJA will preserve historical values by day
- Trendable and date-range accurate
There is no native way in CJA to make profile attributes behave historically.
Only event-level data can do that.