Retain Last Known Value for Computed Attributes Beyond Lookback Window

In multi-brand Adobe Experience Platform implementations, consent information is often captured as event data, with each brand emitting its own consent events.

These consent signals are then elevated to the profile level using Computed Attributes, so they can be reused consistently across audiences, consent policies, and activation use cases.

However, Computed Attributes currently have a maximum lookback period of 6 months. If no qualifying events are present within that window, the computed attribute value is nullified, even when no explicit consent change or withdrawal has occurred.
This behavior creates challenges when modeling consent, which is inherently a stateful attribute, not a time-bound behavioral signal.

Suggested Enhancement
Provide an option for Computed Attributes to retain the last known value beyond the lookback window, unless:
A new qualifying event updates the value, or
An explicit revocation / change event is received.
This could be implemented as:
A configuration option such as “Persist last value until updated”

Other profile attributes in AEP naturally persist until explicitly updated. Introducing similar persistence semantics for state-based computed attributes would improve consistency across the platform.