Hi all,
I have a POC which should set or update Profile information based upon a web form which information is supposed to be sent through Web SDK / sendEvent.
The Profile schema contains a section for person information such as first name and last name (standard Adobe XDM schemas used).
The dataset is updated and contains this field group.
Now, when I try to send the information via custom code
const data = {
xdm: {
identityMap: {
myPersonId: [
{
authenticatedState: "ambiguous",
id: "12345",
primary: true
}
]
},
person: {
name: {
firstName: "John",
lastName: "Doe"
}
}
}
};
alloy("sendEvent", data).then(response => {
console.log("Profile updated successfully:", response);
}).catch(error => {
console.error("Error updating profile:", error);
});
I never see any of this data ending up in the Profile dataset.
Upon Assurance debugging, it looks like the dataset ID which is used is that one of my Experience Event instead which does not contain the field group.
The event dataset is the only dataset that is actually receiving any kind of data, and I wonder what I am doing wrong or whether it is at all possible to update the Profile without using the API.
Any hint is highly appreciated!
Topics help categorize Community content and increase your ability to discover relevant content.
Views
Replies
Total Likes
@DavidRoss91 @Hey_John @Ankit_Chaudhary would you please take a moment to review this question? We would be grateful for any wisdom you could share on this question.
Views
Replies
Total Likes
I haven't tried it myself yet but Instead of sending a XDM object using send event try sending a JSON object using streaming API.
that's the thing, I don't want to set up something on a server, I would like to use the Web SDK.
It's a basic feature that is missing somehow.
@bjoern__koth This is worth sharing as a feature request in the Ideas tab of this community.
Views
Replies
Total Likes
Yeah will do. This discussion has been going on for years now as it seems.
Btw @Ankit_Chaudhary I actually got it implemented using Launch SSF and the HTTP API. It's more of a hack, and requires a SSF license, but it actually works (tapping my own shoulders). So, I am basically sending Profile payload in the "data" payload and my SSF rule only evaluates when this is found. From there on, it makes a fetch to the HTTP API.
But yeah, why is this not a standard feature?!
Product Idea created: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-platform-ideas/support-sending-pro...
@kautuk_sahni , @Ankit_Chaudhary , @Hey_John , @DavidRoss91
Views
Likes
Replies