Solved! Go to Solution.
Views
Replies
Total Likes
For activation take a look at Computed Attributes:
https://experienceleague.adobe.com/en/docs/experience-platform/profile/computed-attributes/overview
That's normally all that's needed versus activating a long list of events.
When they need more complex logic then people schedule Data Distiller SQL INSERT statements to populate profile-enabled, profile-class datasets. Running these once per day is about right as they are batch data.... plus you don't want to unnecessarily subtract from the overall 90 per day batch ingestion guardrail with unnecessary batches throughout the day.
No, Event dataset fields cannot be activated directly to destinations. Event XDM schemas capture time-series behavioral data (e.g., clicks, app events) and are not stored in the unified profile unless properly linked and ingested. Even then, event-level fields are generally unsuitable for activation, as destinations require static, profile-level attributes—not time-series data.
Source Link: https://experienceleague.adobe.com/en/docs/experience-platform/destinations/ui/activate/activate-bat...
Event XDM schemas capture time-series behavioral data (e.g., clicks, app events) and are not stored in the unified profile
I think this one is false. These are stored in the RTCP but cannot be activated. Could somebody confirm?
Views
Replies
Total Likes
Hi @sinrajNa1 ,
You cannot map Experience Event fields in the Activate audiences (Profile-only) workflow.
But you can export entire event datasets via the Export datasets workflow for supported destinations.
Reference:
https://experienceleague.adobe.com/en/docs/experience-platform/destinations/ui/edit-activation
For partial event exports, use Query Service or Event Forwarding and then export the derived dataset.
Thanks,
Ankit
For activation take a look at Computed Attributes:
https://experienceleague.adobe.com/en/docs/experience-platform/profile/computed-attributes/overview
That's normally all that's needed versus activating a long list of events.
When they need more complex logic then people schedule Data Distiller SQL INSERT statements to populate profile-enabled, profile-class datasets. Running these once per day is about right as they are batch data.... plus you don't want to unnecessarily subtract from the overall 90 per day batch ingestion guardrail with unnecessary batches throughout the day.