Segments & Derived Attributes
Segments are saved audience rules. Derived attributes are ResultFly-computed customer facts used by those rules.
Together they turn raw customer data into something marketing and operations teams can act on.
Derived Attributes
Derived attributes are calculated by ResultFly from profile data, channel state, and event history.
Typical examples include:
- total spend
- first purchase date
- last purchase date
- current loyalty tier snapshot
- count of qualifying events in a period
These values are managed by the platform so teams do not have to recompute them manually in every campaign or export.
Segments
A segment is a saved rule that defines an audience.
A segment may combine:
- profile fields
- derived attributes
- channel presence
- channel consent status
- event existence
- registered event-property conditions
Examples:
- customers in Gold loyalty status
- profiles with email consent granted
- users who purchased a ticket for a specific match
- customers whose total spend is above a threshold
Why Saved Rules Matter
ResultFly stores the segment definition itself, not just a temporary result set.
That gives teams:
- a reusable audience definition
- preview before export
- consistent use across operators
- a stable object that can evolve through review and validation
Guardrails
ResultFly validates segment rules against the registered CDP model.
In practice, that means:
- unknown event types are rejected
- unsupported properties are rejected
- only approved filterable properties can appear in segment rules
- export runs asynchronously for reliability
This keeps the segment builder simple for marketers and predictable for developers.