Experience Event and Custom Schema Merging use case

[Prithwiraj_Deb]

Session Booking for a gym is the use case and there is also a physical condition database is there for each gym subscriber.

The use case is for Gym operation team to understand user’s physical condition during a session.

I am thinking of following.

Session Booking can be a ExperienceEvent Class Schema

Session ID

User ID

Session Location

Booking Date

Physical Condition Database – Custom Schema

User ID

Weight

BMI

In order for a Merging strategy –

Session Booking should be an event schema – with Session ID as primary and User ID relation field ?

While Physical Condition – A Custom Schema with User ID as primary ID

Will this be possible to do a merging for Gym operation to understand user physical condition during a session?

[arpan-garg · Accepted solution]

Hi @Prithwiraj_Deb - What do you mean by merging the data ?

1.If your intention is to view the physical condition data integrated with Profile data, it will not be possible. This is because the Physical Condition Database is designed as a Lookup. It cannot be merged within profile data, and direct access through the profile API is not feasible. AEP will exclusively merge data associated with Individual Profile and Experience Event Schema.

2.If your goal is to segment customers based on their physical condition data, you can achieve this. When creating a segment, you have the capability to directly access their physical condition information through the segmentation UI. This accessibility is granted due to the relationship you've established between the schemas.

Thanks,

Arpan