Sending multiple message for single profile using event and lookup data stored one day ago in Adobe journey optimiser | Community
Skip to main content
June 1, 2024
Solved

Sending multiple message for single profile using event and lookup data stored one day ago in Adobe journey optimiser

  • June 1, 2024
  • 1 reply
  • 648 views

Hi...

We are trying to send multiple message for single customer based on his last day purchase data.

All the purchase history related information is stored as events in XDM experience event schema.

We need to use the past day purchase related information for personalisation and need to send individual message for all his purchase in single journey......Is there a way to implement this solution in Adobe Journey optimiser?

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

If you want to activate this data more like a batch kind of a use case, you can either explore computed attributes functionality https://experienceleague.adobe.com/en/docs/experience-platform/profile/computed-attributes/overview or data distiller https://experienceleague.adobe.com/en/docs/experience-platform/query/data-distiller/overview (if customer has license for this)

 

If this is more of a purchase confirmation type use case and if the data is being streamed in, you can use unitary journeys (starting with an event) to activate the same. If there is an element of delay needed, wait activities can be used.

1 reply

Mohan_Dugganab
Adobe Employee
Mohan_DugganabAdobe EmployeeAccepted solution
Adobe Employee
June 1, 2024

If you want to activate this data more like a batch kind of a use case, you can either explore computed attributes functionality https://experienceleague.adobe.com/en/docs/experience-platform/profile/computed-attributes/overview or data distiller https://experienceleague.adobe.com/en/docs/experience-platform/query/data-distiller/overview (if customer has license for this)

 

If this is more of a purchase confirmation type use case and if the data is being streamed in, you can use unitary journeys (starting with an event) to activate the same. If there is an element of delay needed, wait activities can be used.