Real-World Insights on Using AEP Standard Data Types

[JeanBaro_]

Hi there,

I’m looking for some real-world input on using AEP’s standard data types (like Person and Consent) while building out our data model.

In other SaaS platforms, using standard data types (AKA objects in some platforms) has usually been a win for compatibility and future-proofing, even with custom fields added to them.

Does that hold true in AEP? Are the standard data types generally flexible enough, or do teams end up building only custom data types to meet their needs?

Any insights or experiences would be hugely appreciated!

Thanks so much,

[kautuk_sahni]

@Parvesh_Parmar @Tof_Jossic @adobechat @Anuhya-Y @dwright-adobe @Jimalytics_G @Abhishek_Narula25 @shuaib27811 @PratheepArunRaj @sartsche Kindly take a moment to review this question and share your valuable insights. Your expertise would be greatly appreciated!

[jayakrishnaaparthasarathy · Accepted solution]

Hi @JeanBaro_  -  AEP standard data types itself cover almost most of the data types from source side. As you mentioned it is really flexible enough to handle any standard data that are coming into platform. However, platform allowing us to create a custom data type as well based on the use case or ingestion we do. Personally, most of the time we just end up leveraging standard data type to bring the data. Please refer the below XDM field constrains document as well for more reading about the data type handling in platform. 

https://experienceleague.adobe.com/en/docs/experience-platform/xdm/ui/resources/data-types
https://experienceleague.adobe.com/en/docs/experience-platform/xdm/schema/field-constraints

Thank you,
Jayakrishnaa P.