Adobe Employee

[Mentor Abhinav Balooni] Adobe Real-Time CDP Community Mentorship Program 2024

Forum|Forum|1 year ago
July 15, 2024
17 replies
7036 views

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, Abhinav Balooni!

Abhinav 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 Abhinav Balooni (aka @abhinavbalooni )

Abhinav is a martech industry leader with more than a decade of experience across the entire Adobe stack, He is certified on all the Adobe tools and an Adobe SME for RT-CDP too. He is keen to grow mutually by exchange of ideas during the program.

He is excited to add value to the program by enabling his peers to get certified in RT-CDP.

Aspirants mapped to Abhinav Balooni

1) Shashi Chennachar aka @shashi_c23

2) Abhishek Agarwal aka @abhishekag2

3) Carlos Rojas aka @crojasm

4) Navin Agarwalla aka @nagarwalla

5) Ashish Gandhi aka @ag0531

6) Martin Liu aka @pengfeil3410424

7) Jeeva Ravi aka @jeevaravi

😎 Shruti Kulkarni aka @shrutikulkarni

9) Emmylou Jordan aka @emjordan

10) Young Min Lee aka @yabc7

11) Kartikay Sharma aka @kartikays313099

How to participate in the program

Post your Questions in this thread to connect with your Mentor, Abhinav Balooni, and fellow Aspirant peers.
Stand a chance to win the ‘Most Engaging Aspirant’ recognition from your mentor by participating in a weekly quiz.
Test your knowledge by replying to the unresolved questions in the Real-Time CDP and AEP community and tag your Mentor to get recognized as an ‘Exceptional Contributor’ by your mentor.
Stick to the schedule to cover one module/week and clear Adobe Real-Time CDP Certification during the program: July 15 – Aug 30

Suggested Next Steps for Aspirants:

Update your Community Profile photo with your latest headshot to stand out to your Mentor and Peer Aspirants.
"Like" this thread to confirm your participation in the program.
Introduce yourself to Abhinav Balooni and your Aspirant peers by Replying to this Thread! Break the ice by introducing yourself (location, org/ company, etc.) and your experience with/ interest in Adobe DX stack.
Post your Questions to this thread as you begin learning more about the Adobe Real-Time Customer Data Platform Developer Expert certification (Exam ID: AD0-E605)
Stick to schedule and ensure you track your progress in the exam prep guide.
Test your learning by replying to weekly quiz by your mentor
Practice the modules by replying to unresolved queries in the AEP community & RTCDP Community and tag your mentor.

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!

Real-Time Customer Data Platform

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

abhinavbalooni

Community Advisor

Thanks @nimashajain for mapping the aspirants for so many mentors !

Hi All,

This is Abhinav, currently working as a Principal Architect with Anchora, based out of Sydney.

I am certified as a RT-CDP developer and a Business Practitioner and I have also been part of the team helping set questions for the certification.

Looking forward to connecting with each one of you. Let's get everyone in this thread certified as a developer !

Cheers,

Abhinav

ag0531

Nice to connect with you, @abhinavbalooni. Looking forward to learn and evolve. Thanks @nimashajain for the initiative.

My name is Ashish Gandhi. I am working as Adobe Multi Solution Architect and based out of Toronto, Canada.

Let me break the ice with a question. I have a sandbox access and I have started practicing hands-on on AEP/AJO by following the reference videos on SPP. Do you have a recommendation or suggestions how to go about the learning journey from scratch to reach the certification level and eventually be job ready?

Looking forward to hearing from you. Cheers!

abhinavbalooni

Community Advisor

@ag0531 Hey Ashish ! Nice to e-meet you.

I would suggest starting with exam prep guide.that @nimashajain shared above. It has a very structured approach to each topic module wise ! This is a great resource for all the aspirants and was rolled out a couple of months ago.

Have a look and feel free to come back with any further queries.

Cheers,

Abhinav

shrutikulkarni

Level 2

Thanks @NimashaJain.
Pleasure connecting with you @abhinavbalooni.

I am Shruti Kulkarni, a Adobe Multi Solution Architect, based out of Toronto, Canada.

I have been working as an AEP & Data Architect for the past year and towards implementing journeys with RTCDP, CJA & AJO. My experience has been in Marketing Analytics and Customer Data Platforms.
I have come across a lot of questions through the process as the product evolves. Hoping to have some nice exchange of thoughts with you and the community.

I am interested in getting the RTCDP developer certification and will go through the exam prep guide as you suggested earlier as well.
Looking forward to connecting more.

Cheers,

Shruti

abhinavbalooni

Community Advisor

It's amazing to see that almost everyone out here who has commented on the thread is already exposed to AEP as a platform.

With your kind of experience, it should be relatively easier to clear the certification 🙂

Also, I will be posting a relatively easy weekly quiz tomorrow just to gauge the familiarity with the platform and then from next week we start module wise quizzes and doubts.

If you have already started looking at the documentation, feel free to post your queries in here and I will be glad to answer.

Cheers,

Abhinav

abhinavbalooni

Community Advisor

@shashi_c23 @abhishekag2 @nagarwalla @pengfeil3410424 @jeevaravi @emjordan @yabc7 @kartikays313099 Hey guys ! Hope you are well !

Feel free to introduce yourselves so that we can get started with the learning from your end too.

Cheers,

Abhinav

shashi_c23

Level 2

Hi @abhinavbalooni @nimashajain and others,

I'm a Multi Solution Architect & Hands-On Developer based out of Detroit USA. Being a SME on AEM and Java, engaged in solving use cases on RTCDP and AJO platform. That's me in a nutshell.

This is a great initiative and opportunity to sharpen up the skills and deliver the best to solve the real world challenges.

Quick Question, Are you planning for a meeting dedicate for this audience monthly/quarterly? Also could you please engage me on AJO as well if we have any such enrollments going on.

abhinavbalooni

Community Advisor

Hi All,

RTCDP MP 24 | Weekly Quiz | Quiz 1

Here’s a quiz to get started ! This is more of a mixed one just to check all the topics at a macro level. Feel free to answer with a comment.

What two ways can we set identities while implementing web sdk ? Is there any advantage to using one over the other ?
I have some additional product related metadata from my backend systems that I want to use to enrich the purchase behavior data coming in from my website. How do I go about achieving it ?
We have some CRM data like address, name etc about customers that we would like to onboard, what class would we use to build a schema for this scenario ?
There are different sources of information to bring in a customer’s marital status. Source 1 mentions ‘Single’ for customer A and Source 2 mentions ‘Married’ for customer A. What are the possible ways we can resolve this conflict?
I have different batches of data feeding into a dataset during the day from different CRM tables. I observe, later during the day that my profile information that was showing up after the first load, is no more appearing for the profile after a couple of more dataflows which ran during the day. What might be causing this issue? How can we resolve it ?
I have created an audience but I am not able to activate that audience to a Meta destination. What might be the possible reason for it ?
What kind of audiences would help me achieve same page and next page personalisation?

Above are a few mix of questions around different aspects of RT-CDP/AEP which should get us started.

Let me know your responses in the comments below.

Cheers,

Abhinav

crojasm

Adobe Employee

By using identity map giving you the capability to deal with multiple id's, or you can use ECID in case you want to identify non-logged users.
LookUp Schema defining its Id as a non-person identity. You can ingest there the additional fields giving you the possibility of grow.
As CRM Data is related to a individual, it has to be Individual Profile Class.
Defining a merge policy, the kind of policy must vary depending on how the customer wants to deal with it. Time-based if they decide to keep the newest one or dataset prioritization in case one has priority over the other.
It can occur due to one batch ingesting profile data with null or empty values for the profile atts I checked after the first load. For the resolution, you could setup upsert functionality over the dataset or datasets sending that data to the pr
ofile, and relauch the batches.
Double check your destination account configuration, credentials, etc, used to be auth errors.
Edge evaluated audiences.

abhinavbalooni

Community Advisor

Great responses !

Most of you above answered them more or less correctly. A couple of them I left open ended on purpose. Response from my end in bold below. Feel free to ask any further questions around it.

What two ways can we set identities while implementing web sdk ? Is there any advantage to using one over the other ? Most of you answered it correctly. There are two ways of doing it - One by mapping fields to identity namespaces in the schema. Another approach and more flexible is using an Identity Map and mapping the identities in the Identity Map at runtime. This approach gives a flexibility of adding identities without the need to alter the schema.
I have some additional product related metadata from my backend systems that I want to use to enrich the purchase behavior data coming in from my website. How do I go about achieving it ? Again most of the responses were correct. You would make use of a lookup schema with a non-person identifier and have a schema relationship with the rest of the person based data.
We have some CRM data like address, name etc about customers that we would like to onboard, what class would we use to build a schema for this scenario ? Individual Profile Class Schema as it is a record based information. Correct response from pretty much everyone.
There are different sources of information to bring in a customer’s marital status. Source 1 mentions ‘Single’ for customer A and Source 2 mentions ‘Married’ for customer A. What are the possible ways we can resolve this conflict? By using merge policies and either using a timebased approach (if the latest record seems to contain the most up to date information irrespective of source) or a dataset precedence approach (where you defined the priority of the datasets based on the their relative reliability when there is same piece of information available across multiple sources mapped to the datasets)
I have different batches of data feeding into a dataset during the day from different CRM tables. I observe, later during the day that my profile information that was showing up after the first load, is no more appearing for the profile after a couple of more dataflows which ran during the day. What might be causing this issue? How can we resolve it ? @crojasm got this one spot on ! @abhishekag2 @shrutikulkarni Almost there. As @crojasm mentioned, due to the dataset not being enabled for upsert the later uploads ended up overwriting the earlier changes and set the earlier set values to null. To avoid this from happening, you need to enable the dataset for upsert. When this happens, the profiles will not remove the earlier set information but rather update+insert - meaning, it would update the piece of information available already or add any new information but anything else not available in later payloads still remains as is in the profile.
I have created an audience but I am not able to activate that audience to a Meta destination. What might be the possible reason for it ? This one I left open ended to see what all can come to mind of everyone here. Can be varied reasons, destination configuration errors, access related errors but a valid error would be an activation error when you go against a DULE marketing action policy.
What kind of audiences would help me achieve same page and next page personalisation? Edge evaluated audience

Thanks a lot to all those who are participating. As I mentioned earlier in the week, I will be posting module 1 quiz tomorrow and will also post a few important module 1 links at the same time if anyone hasn't had a chance to start prep just yet.

Happy learning guys !

Cheers,

Abhinav

AbhishekAg2

Level 2

Thanks @nimashajain for the initiative. @abhinavbalooni Glad to connect and looking forward to be mentored by you.

I am Abhishek Agarwal, an Adobe Multi Solution Architect based in Lucknow, India.

I have extensive experience with Adobe Analytics, Adobe Target, Adobe Campaign Classic, and have recently expanded my expertise to include Adobe Experience Platform, Customer Journey Analytics, and Adobe Journey Optimizer. My primary focus has been in Marketing Automation and Analytics.

I am particularly interested in learning the RTCDP to deliver comprehensive and integrated solutions for my clients. This program presents a great opportunity for me to deepen my knowledge and achieve the RTCDP developer certification.

I look forward to engaging with all of you, learning from your experiences, and contributing to our shared knowledge. Let's make the most of this journey together.

Cheers,

Abhishek

abhinavbalooni

Community Advisor

Hi All,

Hope you all are preparing well for the certification as we start to delve into specific topics. Here is the quiz from module 1 - Data Architecture.

RTCDP MP 24 | Weekly Quiz | Module 1 | Quiz 2

1. What is a union schema and where can you find it ?

2. What is an identity namespace ? How does it help ?

3. What functions do identities serve in the platform ?

4. Identity fields have to be defined as string - True or False ?

5. Which field group do you use to capture values in eVars and props when using web SDK ?

6. What is a profile fragment ?

7. How can you handle consent of a user while creating segments?

8. What is the cardinality of a customer and cart checkouts relationship ? What kind of entity would be involved in this relationship ?

9. A company tracks active subscriptions for their customers, where one customer can have many subscriptions. The company also wants to include subscriptions for segmentation use cases, such as finding all users with active subscriptions.

In this scenario, the company has two potential options for representing a customer’s subscriptions in their data model. What are they and the pros and cons of each option?

10. What is _id field used for ? Should you use it as an identity ?

I might add more to the above questions in the coming few days.

Have a great weekend ahead !

Cheers,

Abhinav

AbhishekAg2

Level 2

A union schema in Adobe Experience Platform is a combination of multiple schemas that share the same XDM class and are enabled for Profile. It merges fields from these schemas to create a centralized, comprehensive profile of each customer, reflecting all their interactions across integrated systems. Union Schema can be found under Customer - Profiles > Union Schema
An identity namespace in Adobe Experience Platform provides context to identity values, distinguishing types like email addresses, phone numbers, or CRM IDs. It helps by ensuring accurate matching and merging of profile data across fragments. For Real-Time Customer Profile to consolidate profiles, both the identity value and the namespace must align, enabling the system to accurately identify and combine data for the same individual, thus creating a unified customer profile.
Identities enable data integration, unify profiles for personalization, resolve multiple identifiers into a single customer, and help coordinate customer experiences across channels.
True, identity fields must be defined as strings
Adobe Analytics ExperienceEvent Template or Adobe Analytics ExperienceEvent Full Extension
Profile fragment is a piece of customer data that represents a part of a customer's profile in AEP. These fragments come from various data sources and contain information such as customer attributes and behaviours. Using merge policies, these fragments form a complete, unified customer profile that provides a holistic view of the customer's interactions and experiences across different touchpoints.
To handle user consent while creating segments in AEP, special fields must be added to segment definitions to ensure opted-out profiles are excluded. This involves integrating consent data into segment criteria and including these fields in both existing and new segment definitions. By doing so, only profiles with the necessary consent are included in the segments, ensuring compliance with user preferences.
Customer and Cart Checkouts relationship exhibits one to many cardinality as one customer could have multiple cart checkouts; in this case 2 entities would be involved, customer (profile entity) and cart checkout (event entity).
a. Array of Subscriptions within Customer Profile

Pros: Unified view; Simplified querying and efficient excess without using joins
Cons: Can result into large profile size if customers have multiple subscriptions; could have scalability issues

b. Separate Subscription entity linked to customer profile

Pros: Modularity; scalability; updating of individual subscriptions would be easy
Cons: Queries on this would be slow as joins would be required; added segmentation complexity as we would need to refer separate entity

10._id field is typically used as a unique identifier for individual records within a dataset. The _id field should not be used as an identity for customer profiles. While it uniquely identifies records, it does not provide context about the type of identity.

abhinavbalooni

Community Advisor

Hi All,

If you've still not looked into the exam guide, I am putting the module content links below for your easy reference. Feel free to check them out.

Real-Time Customer Profile Overview

Adobe Experience Platform enables you to drive coordinated, consistent, and relevant experiences for your customers regardless of their interaction with your brand. With Real-Time Customer Profile, you can see a holistic view of each customer by combining data from multiple channels, including online, offline, CRM, and third party. Profile allows you to consolidate customer data into a unified view, offering an actionable, timestamped account of every customer interaction. This overview will help you understand the role and use of Real-Time Customer Profile in the Experience Platform.

https://experienceleague.adobe.com/en/docs/experience-platform/profile/home

Real-Time Customer Profile provides a centralized consumer profile for targeted and personalized experience management. Each profile contains data aggregated across all systems and includes actionable timestamped accounts of events involving the profile subject. These events may have occurred in any of the systems you use with Experience Platform.

Real-Time Customer Profile consumes schema-formatted data based on the XDM Individual Profile and XDM ExperienceEvent classes and responds to queries based on that data.

https://experienceleague.adobe.com/en/docs/experience-platform/xdm/home#real-time-customer-profile

Working with nested data structures in Query Service

Adobe Experience Platform Query Service supports the use of nested data fields. The complexity of enterprise data structures can complicate transforming or processing this data. This document provides examples of creating, processing or transforming datasets with complex data types, including nested data structures.

https://experienceleague.adobe.com/en/docs/experience-platform/query/key-concepts/nested-data-structures

Schema field groups endpoint

Schema field groups are reusable components that define one or more fields that represent a particular concept, such as a person, a mailing address, or a web browser environment. Field groups are intended to be included as part of a schema that implements a compatible class, depending on the behavior of the data they represent (record or time series). The ^/fieldgroupsendpoint in the Schema Registry API allows you to manage field groups within your experience application programmatically.

Create an Adobe Analytics source connection in the UI

This tutorial provides steps to create an Adobe Analytics source connection in the UI to bring the Adobe Analytics report suite data into the Adobe Experience Platform.

https://experienceleague.adobe.com/en/docs/experience-platform/sources/ui-tutorials/create/adobe-applications/analytics

XDM ExperienceEvent class

XDM ExperienceEvent is a standard Experience Data Model (XDM) class. Use this class to create a timestamped snapshot of the system when a specific event occurs, or a particular set of conditions has been reached.

An Experience Event is a fact record of what occurred, including the point in time and identity of the individual involved. Events can be either explicit (directly observable human actions) or implicit (raised without a direct human action) and are recorded without aggregation or interpretation. For more high-level information on using this class in the Platform ecosystem, refer to the XDM overview

https://experienceleague.adobe.com/en/docs/experience-platform/xdm/classes/experienceevent

Consents and Preferences field group

Consents and Preferences is a standard field group for the XDM Individual Profile class(opens in a new tab) that captures consent and preference information for an individual customer.

https://experienceleague.adobe.com/en/docs/experience-platform/xdm/field-groups/profile/consents

Define XDM fields in the UI

The Schema Editor in the Adobe Experience Platform user interface allows you to define your own fields within custom Experience Data Model (XDM) classes and schema field groups. This guide covers the steps for defining XDM fields in the UI, including the available configuration options for each field type.

https://experienceleague.adobe.com/en/docs/experience-platform/xdm/ui/fields/overview

Define a one-to-one relationship between two schemas using the Schema Editor

The ability to understand the relationships between your customers and their interactions with your brand across various channels is an integral part of the Adobe Experience Platform. Defining these relationships within the structure of your Experience Data Model (XDM) schemas allows you to gain complex insights into your customer data.

While schema relationships can be inferred through the union schema and Real-Time Customer Profile, this only applies to schemas that share the same class. To establish a relationship between two schemas belonging to different classes, a dedicated relationship field must be added to a source schema, which references the identity of the other related schema.

https://experienceleague.adobe.com/en/docs/experience-platform/xdm/tutorials/relationship-ui

Best practices for data modeling

Experience Data Model (XDM) is the core framework that standardizes customer experience data by providing common structures and definitions for use in downstream Adobe Experience Platform services. By adhering to XDM standards, all customer experience data can be incorporated into a common representation and used to gain valuable insights from customer actions, define customer audiences, and express customer attributes for personalization purposes.

https://experienceleague.adobe.com/en/docs/experience-platform/xdm/schema/best-practices#sort-entities-into-profile%2C-lookup%2C-and-event-categories

Convert your data model to XDM

This video shows how data architects can take their existing transactional data model and convert it to an Experience Data Model. It shows the difference in modeling approaches using entity-relationship diagrams. For more information, please visit the best practices for data modeling documentation

https://experienceleague.adobe.com/en/docs/platform-learn/tutorials/schemas/convert-your-data-model-to-xdm

I have also put quiz 2 in the comments for the above module. Feel free to attempt it and respond using the comments.

Cheers,

Abhinav

abhinavbalooni

Community Advisor

Hi All !

Hope you are prepping well for the exam ?

I have seen responses from @AbhishekAg2 and @crojasm. Amazing work guys ! Will wait till Friday to post the responses from my end so that others can also chime in.

Below I am putting in the module 2 links and a brief summary from the prep guides for a quick reference for the ones who've not had a chance to go through it just yet.

Real-Time Customer Profile UI guide

Real-Time Customer Profile creates a holistic view of each of your individual customers, combining data from multiple channels including online, offline, CRM, and third-party data. This document serves as a guide for interacting with Real-Time Customer Profile data in the Adobe Experience Platform user interface (UI).

https://experienceleague.adobe.com/en/docs/experience-platform/profile/ui/user-guide

Merge policies UI guide

Adobe Experience Platform enables you to bring data fragments together from multiple sources and combine them in order to see a complete view of each of your individual customers. When bringing this data together, merge policies are the rules that Platform uses to determine how data will be prioritized and what data will be combined to create the unified view.

Using RESTful APIs or the user interface, you can create new merge policies, manage existing policies, and set a default merge policy for your organization. This guide provides step-by-step instructions for working with merge policies using the Adobe Experience Platform user interface (UI).

To learn more about merge policies and they role they play within Experience Platform, please begin by reading the merge policies overview(opens in a new tab).

Entities endpoint (Profile access)

Adobe Experience Platform enables you to access Real-Time Customer Profile data using RESTful APIs or the user interface. This guide outlines how to access entities, more commonly known as “profiles”, using the API. For more information on accessing profiles using the Platform UI, please refer to the Profile user guide.

https://experienceleague.adobe.com/en/docs/experience-platform/sources/ui-tutorials/create/adobe-app...

Identity stitching

Identity stitching (ID stitching) is the process of identifying data fragments and combining them together to form a complete profile record. To help illustrate the different stitching behaviors, consider a single customer who interacts with a brand using two different email addresses.

https://experienceleague.adobe.com/en/docs/experience-platform/profile/merge-policies/overview#id-st...

Send partial row updates to Real-Time Customer Profile using Data Prep

Streaming upserts in Data Prep allows you to send partial row updates to Real-Time Customer Profile data while also creating and establishing new identity links with a single API request.

By streaming upserts, you can retain the format of your data while translating that data to Real-Time Customer Profile PATCH requests during ingestion. Based on the inputs you provide, Data Prep allows you to send a single API payload and translate the data to both Real-Time Customer Profile PATCH and Identity Service CREATE requests.

https://experienceleague.adobe.com/en/docs/experience-platform/data-prep/upserts

Map identities

In this lesson, we will create identity namespaces and add identity fields to our schemas. After doing so, we’ll also be able to complete the schema relationships from the previous lesson.

Adobe Experience Platform Identity Service helps you to gain a better view of your customers and their behaviors by bridging identities across devices and systems, allowing you to deliver impactful, personal digital experiences in real-time. Identity fields and namespaces are the glue that joins different data sources together to build the 360-degree real-time customer profile.

Data Architects will need to map identities outside of this tutorial.

XDM System overview

Standardization and interoperability are key concepts behind Adobe Experience Platform. Experience Data Model (XDM), driven by Adobe, is an effort to standardize customer experience data and define schemas for customer experience management.

XDM is a publicly documented specification designed to improve the power of digital experiences. It provides common structures and definitions that allow any application to use to communicate with Platform services. By adhering to XDM standards, all customer experience data can be incorporated into a common representation that can deliver insights in a faster, more integrated way. You can gain valuable insights from customer actions, define customer audiences through segments, and express customer attributes for personalization purposes.

XDM is the foundational framework that allows Adobe Experience Cloud, powered by Experience Platform, to deliver the right message to the right person, on the right channel, at exactly the right moment. The methodology on which Experience Platform is built, XDM System, operationalizes Experience Data Model schemas for use by Platform services.

Learn about the role of XDM System within Experience Platform

Identity namespace overview

Learn more(opens in a new tab) about what you can do with identity namespaces in Adobe Experience Platform Identity Service.

Profile entity composition

A Real-Time Customer Profile comprises a central entity, called the primary entity, and various supporting entities. In the context of the Experience Platform, the primary entity is typically a profile entity composed of traits, behaviors, and a person's audience membership. Other entities allow the segmentation engine to utilize data outside of the primary entity of the profile and include the following:

Dimensional entity: The entity that is used to simplify the data modeling process for information sharing across events or profile records. This is also known as the lookup entity or classification entity.
B2B entity: Entities that describe the profile’s relationship with business-to-business accounts and opportunities.

Learn more.(opens in a new tab)

Define a source and reference schema

For demonstration purposes, this tutorial creates a relationship between members of an organization’s loyalty program (defined in a “Loyalty Members” schema) and their favorite hotel (defined in a “Hotels” schema).

Learn more.

To all the aspirants - make the most of these modules ! When I attempted the certifications, we needed to clear two exams to get certified as dev expert. That has now been reduced to 1 exam and with such structured modularized learning, you have a lot of options to learn from.

Happy Learning !

Cheers,

Abhinav

abhinavbalooni

Community Advisor

Hi All,

Great responses from @abhishekag2 @shrutikulkarni and @crojasm on quiz 2 !

I am not going to post the responses for each of them as you all have pretty much nailed them !

I will just put the responses where I think there were different responses and I need to call out the right ones so that everyone is across those.

5. Which field group do you use to capture values in eVars and props when using web SDK ?

@abhishekag2 and @crojasm got this right. Others can refer to their response.

6. What is a profile fragment ?

@abhishekag2's answer here is a bit more aligned then the rest but the complete answer is as provided below right from the documentation (https://experienceleague.adobe.com/en/docs/experience-platform/profile/home)

Each individual customer profile is composed of multiple profile fragments that have been merged to form a single view of that customer. For example, if a customer interacts with your brand across several channels, your organization will have multiple profile fragments related to that single customer appearing in multiple datasets. When these fragments are ingested into Platform, they are merged together in order to create a single profile for that customer.

In other words, profile fragments represent a unique primary identity and the corresponding record or event data for that ID within a given dataset.

When the data from multiple datasets conflicts (for example one fragment lists the customer as “single” while the other lists the customer as “married”) the merge policy determines which information to prioritize and include in the profile for the individual. Therefore, the total number of profile fragments within Platform is likely to always be higher than the total number of merged profiles, as each profile is typically composed of multiple fragments from multiple datasets.

In this scenario, the company has two potential options for representing a customer’s subscriptions in their data model. What are they and the pros and cons of each option?

The above question was a lift from the documentation to check if you are actually looking into the exam prep guide 😉

Here's the detailed solution from the documentation: https://experienceleague.adobe.com/en/docs/experience-platform/xdm/schema/best-practices

Have a read !

Do let me know if you need any specific question answer and I would add more to the already correct responses. Please refer to the above question as these were a bit less detailed in your responses.

Will post Module 2 quiz in a separate post.

Cheers,

Abhinav

Show more replies

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded