Profile attributes not updated | Community
Skip to main content
Level 3
November 28, 2024
Solved

Profile attributes not updated

  • November 28, 2024
  • 3 replies
  • 1071 views

Hi,

 

The profile attributes are not updated when user is created with websdk integration tags extension.

when user registers or logins, profile is created with events, but profile attributes are not updated

 

 

I need guidance on how to update profile attributes with event schema (as we can only use event schema in websdk integration tags extension)

 

Is it an expected behavior as we are using event schema ? 

 

Profile events are updated as expected.

Best answer by Harveer_SinghGi1

Hi @arunla ,

To update the profile attributes you need to send data to a profile dataset and not and event dataset. WebSDK sendEvent method send data to an even dataset and cannot update the profile attributes except for identity attributes. Only WebSDK method that can update profile attributes is setConsent but that is also limited to standard fields available in Consents and Preferences field group.

To updates all other standard or custom profile attributes you should use other ingestion methods like HTTP API connector and send data directly to a profile dataset.

Just for validation I uploaded two dummy profiles to AEP with same schema fields as below,

//payload for event dataset [ { "_id": "", "timestamp": "2024-11-12T20:20:39+00:00", "eventType": "web.webInteractions.linkClick", "homeAddress": { "street1": "#1, San Jose" }, "identityMap": { "---Person": [ { "authenticatedState": "authenticated", "id": "----PersonID_1.0.0", "primary": true } ] }, "mobilePhone": { "number": "9999999999" }, "person": { "birthDayAndMonth": "01-23", "gender": "male", "name": { "firstName": "John", "lastName": "Doe" } }, "personalEmail": { "address": "john.doe@abc.com" } } ] //payload for profile dataset [ { "_id": "", "personID": "----PersonID_1.0.1", "homeAddress": { "street1": "#1, San Jose" }, "mobilePhone": { "number": "9999999998" }, "person": { "birthDayAndMonth": "02-23", "gender": "male", "name": { "firstName": "John", "lastName": "Smith" } }, "personalEmail": { "address": "john.smith@abc.com" } } ]

And in AEP the result were seen as below,

First through event dataset,

Second through profile dataset,

And as you can see the attributes sent directly to profile dataset are updated correctly but the attributes sent to events dataset are not. Although the same attribute fields are available in the events send to first profile they won't land as profile attributes.

3 replies

RiteshY18
Community Advisor
Community Advisor
December 20, 2024

@arunla you can use both [Event and Profile ] with WebSDK, if still an issue update your Event schema for given profile attribute you are planning to capture 

Harveer_SinghGi1
Community Advisor and Adobe Champion
Harveer_SinghGi1Community Advisor and Adobe ChampionAccepted solution
Community Advisor and Adobe Champion
December 30, 2024

Hi @arunla ,

To update the profile attributes you need to send data to a profile dataset and not and event dataset. WebSDK sendEvent method send data to an even dataset and cannot update the profile attributes except for identity attributes. Only WebSDK method that can update profile attributes is setConsent but that is also limited to standard fields available in Consents and Preferences field group.

To updates all other standard or custom profile attributes you should use other ingestion methods like HTTP API connector and send data directly to a profile dataset.

Just for validation I uploaded two dummy profiles to AEP with same schema fields as below,

//payload for event dataset [ { "_id": "", "timestamp": "2024-11-12T20:20:39+00:00", "eventType": "web.webInteractions.linkClick", "homeAddress": { "street1": "#1, San Jose" }, "identityMap": { "---Person": [ { "authenticatedState": "authenticated", "id": "----PersonID_1.0.0", "primary": true } ] }, "mobilePhone": { "number": "9999999999" }, "person": { "birthDayAndMonth": "01-23", "gender": "male", "name": { "firstName": "John", "lastName": "Doe" } }, "personalEmail": { "address": "john.doe@abc.com" } } ] //payload for profile dataset [ { "_id": "", "personID": "----PersonID_1.0.1", "homeAddress": { "street1": "#1, San Jose" }, "mobilePhone": { "number": "9999999998" }, "person": { "birthDayAndMonth": "02-23", "gender": "male", "name": { "firstName": "John", "lastName": "Smith" } }, "personalEmail": { "address": "john.smith@abc.com" } } ]

And in AEP the result were seen as below,

First through event dataset,

Second through profile dataset,

And as you can see the attributes sent directly to profile dataset are updated correctly but the attributes sent to events dataset are not. Although the same attribute fields are available in the events send to first profile they won't land as profile attributes.

RiteshY18
Community Advisor
Community Advisor
December 30, 2024

@harveer_singhgi1  did you use different data stream for profile and event ?

profile value are not dependent of schema they are mapped to schema . just a value captured in data element can be mapped to any schema

kautuk_sahni
Community Manager
Community Manager
January 29, 2025

@arunla Did you find the suggestions helpful? Please let us know if you require more information. Otherwise, please mark the answer as correct for posterity. If you've discovered a solution yourself, we would appreciate it if you could share it with the community. Thank you!

Kautuk Sahni