Topics help categorize Community content and increase your ability to discover relevant content.
Views
Replies
Total Likes
Evaluate leveraging the Edge Network, more specifically Event Forwarding, to streamline Profile Updates with the Abandoned Cart Events
To you CRM?
Currently, as a Proof of Concept (PoC), we are capturing the event to trigger a journey and using a custom action to update the Profile through the reservation process.
Custom Action request send to CRM? If its for AEP there is an Update Action in AJO...
Hi Michael.
TY for your reply.
I'm using the Custom Action in conjunction with a Source Connection (Datastream API) to update a Dataset (XDM Individual Profile) with Profile Enable, creating or updating a profile based on the event. An AJO journey with an Event Trigger and the Custom Action is doing that for me. Once the profile is created or updated, a second journey is responsible for the Abandoned Cart nudge.
I'm not sure if the "Update Action in AJO" that you mentioned is the Update Profile Action. If so, it is not ideal once I'm pushing 10+ attributes at once.
Views
Replies
Total Likes
Hey @AlexandreSa8
I'd like to share my opinions
> Using Scheduled SQL query to fetch events and populate profile dataset (Might take 1-2hr to update profile, Depends on the site traffic and sql logic) with minimum frequency of 1hr
> Computed attributes can be used to compute aggregated events and store into profile, thereby minimizing the latency, although only supports basic aggregation options and with minimum frequency of 1hr.
I'm curious to know whether the custom action implementation is working well for your use case? If it works as per your case, I think that's the ideal way to update your profile. On the contrary, we can use "Update profile" action unless updation of objects like arrays are involved.
Thanks,
Ganesh Kumar C
Views
Replies
Total Likes
Hi IamCGK.
TY for your reply
I'm using a Query in a similar process, but I'm not able to use a Stream Audience.
It seems that the Query process, as a Batch Update, forces the audience evaluation within 24 hours or so.
On the other hand, as a stream update, the Custom Action works fine with the second journey triggered by a Stream Audience Qualification. The whole process takes roughly 30 minutes.
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies
Views
Likes
Replies