Skip to main content
Level 2
Nov 18, 2026 1:58 AM UTC
Question

Experience Event schema design for multi-type transactional data in AEP

We are implementing transactional event data in Adobe Experience Platform (AEP) and are looking for Adobe's recommended best practice for Experience Event schema design.

Our initial use case is Add Mobile transactions, but we expect to onboard additional transaction event types in the future, such as: Add Video, Add Data, Value-added service transactions.

This transaction event feed that would be ingested into AEP as Experience Events for reporting, segmentation, and Customer Journey Analytics (CJA).

Some attributes are common across event types, while others are unique. We are also planning to enable the schemas for profile.

We would like guidance on the following: Is it recommended to use a single Experience Event schema for all transaction event types and distinguish events using an event type field? Or is it recommended to create separate Experience Event schemas and datasets for different transaction event types?

Are there any Adobe-recommended patterns or reference architectures for transactional event ingestion in AEP?

Any best practice recommendations would be greatly appreciated as we finalize our schema design strategy.

1 reply

Elanchezhiyan_E
Level 3
Nov 18, 2026 5:50 AM UTC

Hi ​@AEPuser16 ,

 

It would be better if you use a single Experience Event schema for transaction event ingestion into AEP if the new events share a similar data structure.

However, you can consider creating separate schemas if the event structures differ significantly or have distinct business requirements.

You can use the eventType field to distinguish between different transaction types. Additionally, you can leverage Adobe's standard transaction-related field groups (ex: Commerce Field Group) or create custom field groups based on your business requirements and overall architecture. These fields will be available for CJA reporting, also CDP Segmentation and activation.

 

You can use separate datasets with the same Experience Event schema if you need to manage ingestion from different transaction sources independently. 

This approach will help maintain consistency, simplify schema management, and support future transaction event ingestion.

 

Please let me know if you need further assistance.

 

Thanks,

Elan

Translate