Question about the "Profile" Dataset doing in Datastream Setup

[bestImv]

Hello Community,

I'm trying to understand the purpose of the "Profile" dataset when configuring Datastream for web tracking. My usual setup process is:

1. Define the event schema.
2. Create the event dataset.
3. Configure Datastream to point to this event dataset.
4. Implement web SDK tracking.

Understood that we can't send data directly to the "Profile" schema using the web SDK. Therefore, I'm curious about the purpose of including the profile dataset during Datastream setup. Can anyone shed light on this?

Thanks!
Imv

[ReenaJohn]

hi @bestImv ,

The Profile dataset in DataStream is used to select the AEP dataset to which the customer attribute data will be sent. Along with the Event Data if there is any attribute data that needs to updated into Profile you could use this Profile dataset [Schema Type is Individual Profile] for that.

Please refer to this link for details - https://experienceleague.adobe.com/en/docs/experience-platform/datastreams/configure#aep

Warm Regards,

Reena John

[bestImv]

Hi @ReenaJohn ,

Thanks for your response and the info link, but I'm still unsure how this works with profile attributes.

Specifically, can we send profile-type attributes via Adobe's data collection if we added Profile Schema in the datastream setup?

Normally we are using the Adobe Experience Web SDK extension, which works well for capturing dataLayer key-value pairs. However, this data seems to be directed only to the "event" side via xdm content object.

Certain events, like login or registration, typically include profile attributes in the data layer (e.g., member ID, phone, email, loyalty program). Ideally, we want to store this information on the profile side.

Is it possible to capture these profile attributes using Data Collection and the Datastream configuration? How can I set up data collection to populate the profile attributes rather than just event data?

Thanks,

Imv

[Parvesh_Parmar · Accepted solution]

Hello @bestImv , 

If I understand correctly, the process might work as follows:

1. In your event schema, where you're collecting event data, you'll need to add the person details field group.

2. You also need to enable this event for profile.

3. When defining your data stream, make sure to select your profile data sets. As mentioned in this document, all customer attributes will be sent to these datasets.

https://experienceleague.adobe.com/en/docs/experience-platform/datastreams/configure#aep

4. In Data Collection, when creating a data element, you'll select your event schema. The customer attributes or field group will be updated in both the event dataset and the profile dataset.

If possible, I recommend testing this in a lower environment to validate the results.

Kr,

Parvesh

[AtulChavan]

Hi @bestImv ,

The reason to have that option is,  if you're willing to capture below information and let sdk handle/populate it automatically for you on profile..... 

- User Consents & Preferences

- Push notification details.

- Region data for Target Use-case.

Ensure you have all those required OOTB fieldgroups part of your profile schema and its profile enabled
Few examples of fieldgroups : 

• Push notification details....
• Consens and Preferences...
• Data capture region....

I read you mentioning if can we populate traits or attributes of the profile via data collection, answer is no. You may use "AJO - update profile" action after triggering the journey in response to an event comprised of some data that you wish to update profile with. 

Hope this helps. 

Regards,
Atul