Skip to main content
Solved

Consolidating Customer Events in Flow

  • June 18, 2022
  • 1 reply
  • 349 views

Forum|alt.badge.img+5

Hey All πŸ‘‹

First post so sorry if i’ve missed this in the forum...

Wondering if anyone has tried to consolidate events for a customer into single email?
We have multiple event type (β€œview_products” and β€œAdd_to_cart” for example) which are independent events, what IΒ would like to do is consolidate these events into a single emailΒ (effectively looping through the customer events).

I could probably write a script on my server side to do this, or do this via segment but figured I would save the MTU’s if there was an easier solution. im also not against firing one event and then performing a lookup to the customer to see the events within a set period of time.Β 

Β 

preferablyΒ not trail-blaze this oneβ€¦Β πŸ˜‚Β 

Best answer by Dov

HiΒ @chrisB,

Thank you for sharing this question with us!

This is an interesting idea! For context, we’re only able to use a single event as a trigger for a flow. Additionally, only information about that particular event can be used in the flow email. For example, only the event-data for a flow triggered off ofΒ Added to CartΒ could be used in a flow. WeΒ cannot combineΒ events (and therefore we cannot simultaneously look to extract event data from multiple events in a flow). For more information on this, see our guide:Β About Using Event Variables to Personalize Flows.

With that said, you can still loop through customer events in a single metric i.e.Β inΒ Viewed ProductΒ by using event variable arraysΒ in your flow email.Β 

We have a few lively discussions on this topicΒ below:

While segments will allow you to consolidate multiple events in a single definition i.e. What somebody has done > Added to Cart OR what somebody has done > Viewed Product, segment-triggered flows will not allow you to pull event-data from those metrics into your flow.

I hope that helps address yourΒ question.

This topic has been closed for replies.

1 reply

Dov
Forum|alt.badge.img+61
  • Klaviyo Alum
  • Answer
  • June 21, 2022

HiΒ @chrisB,

Thank you for sharing this question with us!

This is an interesting idea! For context, we’re only able to use a single event as a trigger for a flow. Additionally, only information about that particular event can be used in the flow email. For example, only the event-data for a flow triggered off ofΒ Added to CartΒ could be used in a flow. WeΒ cannot combineΒ events (and therefore we cannot simultaneously look to extract event data from multiple events in a flow). For more information on this, see our guide:Β About Using Event Variables to Personalize Flows.

With that said, you can still loop through customer events in a single metric i.e.Β inΒ Viewed ProductΒ by using event variable arraysΒ in your flow email.Β 

We have a few lively discussions on this topicΒ below:

While segments will allow you to consolidate multiple events in a single definition i.e. What somebody has done > Added to Cart OR what somebody has done > Viewed Product, segment-triggered flows will not allow you to pull event-data from those metrics into your flow.

I hope that helps address yourΒ question.