Hi @SCB21  With AEP & Target, you can implement same-page personalization or next-page personalization - so segments (realtime) get evaluated in real-time in Edge. So sharing depends on the type of segments as well.   With AJO - we executed near real-time email send as well eg: user registers on the...

Good to know @maggod. Thank you! 

I don't think model evaluation will be in real-time.

Hi @RexChen,   The profile dataset is utilized for consent preferences via WebSDK - here are some links to refer https://experienceleague.adobe.com/docs/experience-platform/landing/governance-privacy-security/consent/sdk.html?lang=en https://experienceleague.adobe.com/docs/experience-platform/landin...

Hi @irohitshukla,   As @arijitg mentioned this is expected. In the real world, if the same email is used (eg: husband & wife using sharing the same email id) for different profiles then the profiles will get merged. So do your data analysis thoroughly and understand how the data is captured since th...

Hi @NidhiAgrawal1 if you are not worried about page performance then I don't see a major impact. Its just additional scripts on the page and capturing stats multiple times. We have had situations where we kept analytics connector & websdk enabled and were capturing stats twice since there were issue...

Hi @navink386520, make sure you do it in this order: Create the schemaEnable for profileCreate the dataset and enable for profileLoad the datasetEstablish the relationship with any other schema that you need the lookup for. (This step can be done anytime after the lookup schema is created) Unless th...

@Vasipallikotireddy were you able to resolve this? If so, can you please post the response here?

Hi @Ikmoo, Try this option: Create a new events schemaConfigure the new Datastream and select the schema created in step 1Create the dataset for the schema in step 1Within the datastream add the AEP service and select the dataset created in step 3To update the data in the event dataset use Edge Serv...

Hi @Sebastiane_Edberg_ please raise the Adobe ticket to find the actual root cause.   There are times when we do not have access to the error logs and we have no choice but to raise the ticket.   Please share your findings when you hear back from Adobe.