Hello Team,
Welcome to the Adobe Real-Time CDP Community Mentorship Program 2024! This is the featured Community Discussion/Contextual thread for your Adobe Real-Time CDP Community Mentor, Jayakrishnaa Parthasarathy!
Jayakrishnaa Parthasarathy will be your dedicated mentor, providing valuable support and guidance on your Adobe Real-Time CDP queries as you upskill yourself and prepare for Real-Time CDP certification throughout the program.
Know your Mentor Jayakrishnaa
Jayakrishnaa brings his extensive experience with Adobe Analytics, Launch, Target, and Audience Manager, and more recently, he has been working with AEP and AJO technology. He is passionate about working on Adobe platforms, finding it both challenging and rewarding. He looks forward to further collaboration and exploration with other experts in the Adobe community.
Aspirants mapped to Jayakrishnaa Parthasarathy (aka @jayakrishnaaparthasarathy )
1) Ankit Chaudhary aka @Ankit_Chaudhary
2) Kandavadivelan S aka @Kanda_SR
3) Ramakrishna zalaki aka @ramakrishna3
4) Mohd Kashaf Tahirhussain Momin akaMohd_KashafMo
5) Deepak K V aka @DeepakK_
6) Laxa Devda aka @LaxaDe
7) Parvesh Sharma aka @parveshsh
9) Revanth Ponnuru aka @RevanthPonnuru
10) Koti Reddy Syamala aka @kotisyamala
11) Enok Lee aka @EnokLe
12) Michael Giddings aka @fondofhatsKey
13) Mohd Kashaf Tahirhussain Momin aka @Mohd_KashafMo
How to participate in the program
Suggested Next Steps for Aspirants:
Remember that every post / like / comment you make in your contextual thread and the Real-time CDP Community throughout the program helps increase your chance to be recognized by your Mentor and win exclusive Adobe swag, so bring your best efforts!
We wish you all the best as you embark on this learning experience!
Hi Team,
Hope everyone had a good weekend. Please find the below quiz/questions that is related to XDM concepts. Feel free to post your understanding on the quiz and let me know if any. I have created few questions based on the document shared earlier on this thread. Will be adding few more shortly.
Thank you,
Jayakrishnaa P.
Ans :
2. Is it really required to consider the secondary identifier for the entity? What is the actual purpose of having secondary identifier on the schema?
Ans :
We have 2 categories of identity. Primary and secondary. Primary identity is required in every record of profile-enabled schemas. They should exist in every record that we are ingesting, and it should be unique.
Secondary identities are other fields that can uniquely identify an individual, but which may or may not be present.
Secondary identifiers play a crucial role in establishing relationships and managing data within the platform. When there are multiple identities associated with an entity, one of them is designated as the primary identity, while the remaining identities are designated as secondary. This distinction allows Identity Service to establish links between identities, enabling comprehensive data management.
The presence of secondary identifiers ensures that Identity Service can effectively link identities across platform.
3.Under what circumstance we should be considering the custom class? i.e., look up schema.
Ans :
Custom classes are ideal when there are no Adobe-defined core classes available to describe a unique use case. If data requires specific attributes and behaviors that are not covered by standard XDM classes, creating a custom class allow us to define the structure and properties that align with the specific use case.
Example: capturing product meta data details like Product Name, Product Category etc.
4. Is it necessary to have email attribute as “Email” data type or just a string should be fine? What is the difference on using email & string as a data type for email attribute?
Ans :
Email address is a standard Experience Data Model (XDM) data type that describes the details of an email address.
The technical address of the email as commonly defined in RFC2822 and subsequent standards (for example, name@domain.com).
In XDM, email addresses must contain a valid top-level domain to pass validation.
Source : https://experienceleague.adobe.com/en/docs/experience-platform/xdm/data-types/email-address#
The "String" data type is a fundamental data type used in Adobe Experience Platform to represent text-based information. It doesn’t have any validation.
If the attribute is solely meant to store email addresses, using the "Email Address" data type is generally the better choice due to its validation benefits.
5.Sources like CRM, Loyalty, Member entity. Etc. with respective identities. What is the identity namespace type that would be considered for the respective identities for the mentioned entities?
Ans :
1. Loyalty: Loyalty programs often have unique identifiers for their members, such as loyalty IDs. In this case, a custom namespace specific to the loyalty program, such as "Loyalty," would be considered for the respective identities. This custom namespace would help separate loyalty-related identity values from other sources.
2. Member Entity: If the members are part of a specific program or entity, a custom namespace reflecting that program or entity could be considered. Additionally, standard identity namespaces such as Email or Phone may also be relevant.
3. CRM: For CRM sources also, the identity namespace will be a custom.
6.Give me some examples of source/entity name where we will use “non-people identifier” as primary identifier? What is the main objective of considering “non-people identifier” as primary identifier?
Ans :
Non-people identifiers are used to store identifiers that require namespaces but are not connected to a person cluster
.
1. Product SKU: Non-people identifiers are commonly used to store product SKUs, which are unique codes assigned to each product in a retailer's inventory.
2. Organization ID: Non-people identifiers can also be used to store unique identifiers for organizations, such as business entities or institutions.
Hi @jayakrishnaaparthasarathy , I tried to answer all your questions based on my knowledge and with the help of documentation.
Thanks
Deepak
Great @DeepakK_ , Massive!! I appreciate your answer and your understanding on the questions are fine. Please make sure to cover all the remaining document if any.
Thank you,
Jayakrishnaa P.
There's no one-size-fits-all approach, but here's a good process for converting normalized sources to AEP XDM:
It's not mandatory to have secondary identifier in your schema, but secondary identifiers offer several benefits:
Any field which is marked as an identity but not as primary identity will behave as secondary identifier.
Use a custom class when no existing XDM class perfectly aligns with your data structure. For example, you might create a "LoyaltyMember" class to capture specific data points from your loyalty program or productDetail class to capture data points related to different products.
using a "String" data type is technically possible for an e-mail field however, AEP recommends using the "Email" data type for email addresses. This offers benefits like:
Namespaces will provide additional context to a value available in the identity field
The main objective of using a non-people identifier is to create a schema focused on a specific entity that isn't a person. This allows for efficient data management and analysis related to that entity.
Here are some examples of using non-people identifiers as primary identifiers:
@Ankit_Chaudhary Awesome. I appreciate your understanding on the questions, and you are really great on explaining the stuff. Please make sure to cover remaining topics if any.
Thank you,
Jayakrishnaa P.
@Ankit_Chaudhary @DeepakK_ @RevanthPonnuru I appreciate you for taking time and giving your answer. Please make sure to cover remaining documentation if any.
@others - Please take some time and try to give your understanding for the question mentioned. I will be sharing the module 2 along with documentation end of this week, so let's make sure to cover XDM fundamental before we move to the exiting topics.
Thank you,
Jayakrishnaa P.
Views
Replies
Total Likes
1.
Using sources and destinations to get the data in to AEP as normalized data means already cleaned data which we can use for further queries and analysis.
3.
When you want to have the data for that particular schema in the system but need not to link the schema with the profile, then we use the lookup schema. The data in the lookup schema will not be linked with profile as we use non-identifier profiles namespace.
3.Is it necessary to have email attribute as “Email” data type or just a string should be fine? What is the difference on using email & string as a data type for email attribute?
Ans: We can use email as an datatype as it accepts only valid high profile domain addresses.
4.Sources like CRM, Loyalty, Member entity.etc. with respective identities. What is the identity namespace type that would be considered for the respective identities for the mentioned entities?
we will be using individual cross device id for the mentioned id's above.
6.Give me some examples of source/entity name where we will use “non-people identifier” as primary identifier? What is the main objective of considering “non-people identifier” as primary identifier?
This will be used to track the interactions at the device level and helps in collecting anonymous data.
@jayakrishnaaparthasarathy I tried to answer the questions please correct me if wrong, will be helpful in learning new things or things which i don't know.
Thanks,
Revanth
Thank you, @RevanthPonnuru . Please check the answer for the last question. I appreciate your try and most of them are correct. I request you to elaborate the answer from next time to know your exact understanding.
Regards,
Jayakrishnaa P.
Views
Replies
Total Likes
1. What are the ideal steps to convert any normalized sources of data to AEP XDM?
2. Is it really required to consider the secondary identifier for the entity? What is the actual purpose of having secondary identifier on the schema?
Secondary identifiers provide additional layers of identity resolution and data integration, which can enhance data accuracy and consistency. However, this is not mandatory.
3. Under what circumstance we should be considering the custom class? i.e., look up schema.
You have unique or specialized data needs not met by standard classes.
You need to extend existing schemas with additional attributes.
4. Is it necessary to have email attribute as “Email” data type or just a string should be fine? What is the difference on using email & string as a data type for email attribute?
The "Email" data type in AEP is specifically designed to store email addresses. It comes with built-in validation to ensure that the value conforms to the standard email format. Using String is possible, but it would be better to manage data quality with using Email.
5. Sources like CRM, Loyalty, Member entity.etc. with respective identities. What is the identity namespace type that would be considered for the respective identities for the mentioned entities
CRM: crmId
Loyalty: loyaltyId
Member: memberId
6. Give me some examples of source/entity name where we will use “non-people identifier” as primary identifier? What is the main objective of considering “non-people identifier” as primary identifier?
Transaction Records, Device Data, Order ID.
The primary reason of using a non-people identifier is to ensure unique and consistent identification of non-human entities within a system.
Thank you, @EnokLe . I appreciate your answer. Please check the answer for 5th & 6th question. Request you to make sure to cover all documentation if any.
Regards,
Jayakrishnaa P.
Views
Replies
Total Likes
Hi Team,
Few best practices that need to be considered on data modelling.
Thank you,
Jayakrishnaa P.
Hi Team,
Good afteroon. Please find the quiz for the week and try to give your answer. Feel free to comment if any.
Happy Learning!
Jayakrishnaa P.
Hi @Ankit_Chaudhary @EnokLe @DeepakK_ Good evening. Please take some time to answer the Week 2 questions and feel free to DM if any.
Thank you,
Jayakrishnaa P.
1. Checking Dataset and batches responsible for a merge
To check the dataset and batches responsible for a merge in identity graph follow the mentioned steps:
2. "No identity graphs found" Error
After selecting an identity namespace and entering its corresponding value you can face this error for the following reasons:
3. How to View the Union View of schemas
Union Schema : With in experience platform UI you can view any union schema for a specific class.
4. Deleting profiles after ingestion
Adobe Experience Platform generally doesn't support direct profile deletion. However, you can delete a specific profile by making a delete API request using profile API this will remove the profile from profile profile store but not the underlaying data from the data lake.
5. Data Ingested but Profiles aren't visible
6. Impacts of Data Type Mismatch
Data type mismatches can lead to:
7. Maximum Number of Identities and Consequences
The maximum number of identities in an Identity Graph for an individual profile is 50. Any profiles with more than 50 identities are excluded from segmentation, exports, and lookups.
8. Consequences of Deleting a Profile Enabled Dataset
If a dataset is enabled for Profile, deleting that dataset through the UI will delete it from the data lake, Identity Service, and also any profile data associated with that dataset in the Profile store.
9. Common Challenges in Data Ingestion
To mitigate these challenges, implement robust data validation, error handling, and monitoring processes
Thank you @Ankit_Chaudhary , Awesome.
1.When two profiles are merged due to having the same email ID in the identity service, how can you identify the datasets and batches responsible for this merge?
Ans:
Using Identity Graph:
2. If profile fragments ingested with an email as an identity are not appearing in the identity graph and the system returns "No identity graphs found," what could be the potential reasons for this issue?
Ans:
An identity graph requires a minimum of two linked identities to be generated and a valid identity namespace and value combination.
3. Which feature in Adobe Experience Platform allows you to view the union of specific class fields, attributes, and the corresponding schemas and datasets?
Ans:
In Adobe Experience Platform, the feature that allows you to view the union of specific class fields, attributes, and the corresponding schemas and datasets is the Union Schema . This provides a comprehensive view of the union schema for a specific XDM class, allowing you to explore the fields contained within each schema that shares the same class.
4. Is it possible to delete profiles that have been ingested into Adobe Experience Platform? If so, what methods can be utilized to remove these profiles from all three services?
Ans:
Yes, it is possible to delete profiles that have been ingested into Adobe Experience Platform. To remove profiles, we can utilize the Real-Time Customer Profile API to create a Profile system job.
5. What troubleshooting steps should be taken if batch data has been successfully ingested into Adobe Experience Platform, but the profiles are not visible in the profile tab?
Ans:
6. What are the potential impacts on the system if data is ingested with a data type mismatch, such as specifying "String" during data modelling but receiving "Integer" data?
Ans:
7. What is the maximum number of identities that Adobe Experience Platform can hold for an individual profile, and what happens if this limit is exceeded?
Ans:
The maximum number of identities that Adobe Experience Platform can hold for an individual profile is 50. If this limit is exceeded, the affected profiles with more than 50 identities are excluded from segmentation, exports, and lookups.
8.What are the consequences of deleting a dataset that has been enabled for profiles in Adobe Experience Platform?
Ans: If a dataset is enabled for Profile, deleting it through the UI will remove it from the data lake, Identity Service, and any profile data associated with that dataset in the Profile store. This means that any profile data linked to the deleted dataset will be permanently removed.
9.What are some common challenges encountered during data ingestion in Adobe Experience Platform, and how can these issues be mitigated?
Ans:
Thank you @DeepakK_ , good one. Can you check the answer for 4th question and make sure to familiarize on deleting profiles from all the services from AEP.
Views
Replies
Total Likes
Hi Team - Glad for all your answers and good to see your understanding on the XDM fundamentals, Profiles, Identities and data ingestion. However, there is slight change on the answer that everyone would have replied on identities & profile deletion. So, please take a moment to read the document and familiarize on the same.
Here you go the question -
What is the maximum number of identities that Adobe Experience Platform can hold for an individual profile, and what happens if this limit is exceeded? Identity Deletion login - Understanding the deletion logic.
Is it possible to delete profiles that have been ingested into Adobe Experience Platform? If so, what methods can be utilized to remove these profiles from all three services? Privacy Service (profile deletion on RESTful API) - https://experienceleague.adobe.com/en/docs/experience-platform/privacy/home
Would request everyone to take a look on the given documentation to surprise your thoughts (hope so) on identity and feel free to comment if any.
Views
Replies
Total Likes
Need to check the preferred merge policy on how the identity service has been configured.
Views
Likes
Replies
Views
Likes
Replies
Views
Likes
Replies