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.