Why should we select the ExperienceEvent class when creating a schema for the Web SDK implementation? If we select ExperienceEvent class, then How do we get a profile in RTCDP?

[Sathya_Murugaiyan]

Dear all,

I am new to Web SDK and AEP. I recently had various troubles with AEP.

I used AEP to set up a web SDK for my website. The website data was successfully sent to the dataset, but it is not available in RTCDP due to the ExperienceEvent Schema class. Additionally, I was unable to connect to a third-party destination.

Thanks 

[Nirmal_Jose · Accepted solution]

Hi Satya,

Trying to simplify the CDP essence in simple words -  a customer profile consists of two types of data
1. Profile attributes - age, gender etc.
2. Events - add to cart, purchase etc. 
Hence there are three types of schemas 

In order to register the actions done by the customer registered to a profile, we need to send the event using webSDK into a event dataset aligned to an experience event schema. 

How do we make an experience event connect to a profile - using the identities defined in the event. Along with the experience event, you need to specify which identity you are sending through - ECID, email, loyaltyID etc. Once the data is received in platform, identity service will stitch the identity and the profile fragment is updated. 

[Sathya_Murugaiyan]

Thank you for your reply. Now I understand profile attributes and experience events.

In my example, I have a website where the user logs in , at successful login i sent an event (experience) called "logged In" Here, I pass the email-id of the user.

Now I have to send this email id to a destination, how can I achieve this?

[Nirmal_Jose]

Hi Satya,

Hope you have enabled the event dataset for profile by toggling it on in the dataset. 
Now that you have sent the event with the identity as email, if all good, after profile stitching you should be able to see the customer profile. 
Go to https://experience.adobe.com/#/@<org>/sname:<sandbox>/platform/profile/browse?limit=25&page=1 and select email namespace and type the email. If the profile is stitched correctly, you should be able to see the profile and in events tab, you can see the logged in event.

Coming into sending the profile into destinations, there was various types of destinations. A quick summary can be as below. 

There are destinations where we export profiles, there are destinations where we export audiences(segments) and it can differ based on the frequency on how the data is sent - can be streaming or can be batch. 
Depending on the destination, once you setup the account, the next tab will be select the mapping where you say email attribute of your schema needs to be mapped to email attribute in the destination payload schema. 

Hope this gives you a pathway to understand, the documentation is pretty descriptive. 

Kindly mark the answer as correct if you feel the answer is helpful. Thanks!

[Sathya_Murugaiyan]

Hi @Nirmal_Jose,

Thank you for your reply. I have enabled the event dataset for the profile. I can see a profile in the event tab. Kindly look into the screenshots below.

I have created segments and exported these to two Destinations which are Adobe Target and MoEngage but I got these segments in Adobe Target only not in MoEngage.

[Kumar_Saurabh_]

Hi @Sathya_Murugaiyan ,
In addition to @Nirmal_Jose comment, you should also enable the Event dataset for Profile.
Once enabled, only the data that has landed post you have enabled it, will flow to the Profile store. 
Now these profiles can be viewed under Customer -> Profile -> Put the ECID as namespace and search for the profile with a valid ECID.

You can also use a known identity to explore profiles as well.