CJA - Summation for Derived Fields

[JaniceAk]

Hi all,

I have created a derived field summing events (denoted by 1 and -1) at a People level for analytics use case to understand group membership. I was wondering, how does this derived field summation apply when you adjust the date range within a workspace?

For example: In the derived field, I am denoting 1 as a subscribe/opt-in event and a -1 as an unsubscribe event/opt-out event, then summing at a Person level scope to understand who's net subscribed and who has net unsubscribed. When I drag this dimension into a freeform and adjust the date ranges, is it going to sum those values at a Person level according to the date range set (e.g. summing all events Jan1-Jan30)? Or is it going to return a 1 for anyone who, at any point in the date range, had 1 as their net status (e.g. user was was subscribed jan1-jan15, but unsubscribed after on jan24)

I ask because of two use cases: 1) I want to create a time series graph plotting this information, for a use case to track net entries to the opt-in group day by day or WoW. I.e. how much is our subscribe/opt in population growing by. and 2) I want to be able to isolate those who, on a given day, or week, had a net status of 1. But was not sure how the summation works when you incorporate date ranges & plot against time. Any ideas would be helpful--thanks!

[bjoern__koth]

Hi @JaniceAk 

Derived fields at the person level (like summing opt-in/opt-out events) will respect the date range you’ve set in your analysis.

The person-level scope defines how the data is aggregated (across all events tied to a person), but the date range filters which events are included in that aggregation.

That means if you’re looking at data from, say, Jan 1 to Jan 30, the derived field will only consider events within that window—even though it’s scoped to the person.

So, if a user subscribed on Jan 10 and unsubscribed on Jan 24, the derived field will reflect that net change only within that timeframe.

[Vinay_Chauhan]

Hi @JaniceAk 

A derived field scoped at the Person level still respects the date range you set in Workspace. The scope just controls how events are rolled up (all events for that person), while the date range defines which events are included in that rollup.

So in your example, if you look at Jan 1 - 30, the derived field will only sum subscribe/unsubscribe events within that window. A person who subscribed on Jan 10 and unsubscribed on Jan 24 would net out to 0 for that range.

This also means -

• For a time series, you’ll see net changes calculated based only on the events in each interval (day/week).

• To isolate people who had a net status of 1 on a given day/week, set the date range accordingly, the derived field will reflect their status within that slice of time.