Can we use Computed Attributes to surface Experience Event-derived values at Profile level for Activation in AEP?

Hi Community,

We're working on a use case where we need to surface ExperienceEvent-derived values at the profile level so they can be activated to a destination specifically Adobe Campaign Classic  for email personalization.

Can we use Computed Attributes to aggregate ExperienceEvent data (e.g. last purchase date, total orders in last 90 days, last product viewed) onto the profile, and then have those values flow through standard Audience Activation to ACC as regular profile fields?

Specifically looking to validate:

• Whether Computed Attributes are fully supported in the ACC destination activation flow
• Whether the aggregated values appear as mappable fields during the audience-to-destination mapping step
• Whether there are any limitations or gotchas with Computed Attributes in this context (e.g. lookback window limits, supported aggregation functions, refresh latency)

Our current stack:

• AEP (Real-Time CDP)
• Adobe Campaign Classic as destination
• Azure Data Lake Storage as intermediary

Any guidance, real-world experience, or documentation pointers would be greatly appreciated. Thanks!