One Schema or multiple Schemas ? | Community
Skip to main content
Michael_Soprano
Michael_Soprano
October 3, 2025
Solved

One Schema or multiple Schemas ?

  • October 3, 2025
  • 3 replies
  • 331 views

I am doing project for a company which consists of 3 entities. 

Data Mart would ingest to CDP 4 datasets:

- data for entity 1

- data for entity 2

- data for entity 3

- combined customer view across all entities

 

Would you make ona schema or 4 schemas? Is it some max number of fields which schema 

Best answer by arpan-garg

Hi @michael_soprano  - 

 

I’d go with one schema if all three entities have the same structure (same customer fields, same meaning). Just add a field like entity_id to tell them apart. That way, you can easily build a unified profile view and keep things simple.

If each entity’s data is very different, then make separate schemas, but still try to use the same XDM class so they can roll up into the union profile.

Also, for future proof solution and performance, Adobe recommends keeping it to max 20 datasets for Individual Profile and 20 for Experience Events, so it’s better not to over-split your data unnecessarily.

 

Thanks,

Arpan

 
 

3 replies

KumarRishii
KumarRishii
October 5, 2025

If the datasets are highly similar and managed by the same team, you could use one schema.

K
Adobe Employee
KevinFosterDXAdobe Employee
Adobe Employee
October 5, 2025

I typically combine into one dataset when:

  • the data is of the same class: profile, event, or custom
  • the data will have the same primary identity
  • the data is sourced from the same system
  • the data will be sourced the same way: streaming vs batch

 

If you combine profile-class data into one dataset when all of that isn't true then you may end up forced to use "upserts" (partial record ingestion) with all of the limitations that comes with that. 

 

 

    arpan-garg
    Community Advisor
    arpan-gargCommunity AdvisorAccepted solution
    Community Advisor
    October 8, 2025

    Hi @michael_soprano  - 

     

    I’d go with one schema if all three entities have the same structure (same customer fields, same meaning). Just add a field like entity_id to tell them apart. That way, you can easily build a unified profile view and keep things simple.

    If each entity’s data is very different, then make separate schemas, but still try to use the same XDM class so they can roll up into the union profile.

    Also, for future proof solution and performance, Adobe recommends keeping it to max 20 datasets for Individual Profile and 20 for Experience Events, so it’s better not to over-split your data unnecessarily.

     

    Thanks,

    Arpan

     
     
    Terms & ConditionsAccessibility statement

    Loading footer...