Skip to main content

Hey Klaviyo Community! 👋

I'm stuck on a flow filtering challenge and hoping someone has cracked this nut before. Would love your input!

The Situation

We run a marketplace connecting bike shops with customers. Here's our automation flow:

  1. Event: mkt_quote_request_sent (includes project_id: "proj_123")
  2. Goal: Send quote reminders to shops until they respond
  3. Stop trigger: mkt_partner_quote_submitted for the same project

The Challenge 🤔

A single shop can have multiple quote requests running simultaneously for different projects. When they respond to Project A, we need to stop reminders for Project A only - not Project B, C, etc.

What I need (but can't figure out how to do):

Profile Filter: Has mkt_partner_quote_submitted zero times since starting this flow 
WHERE project_id equals {{event.project_id}}

 

Real-World Example

 

Day 1: Shop gets quote request for Project A → Reminder flow starts
Day 2: Shop gets quote request for Project B → Another flow starts
Day 3: Shop responds to Project A only

Expected: Project A reminders stop, Project B continues
Reality: Can't differentiate between projects 😩

Questions for the Community

  1. Has anyone solved multi-project/multi-instance filtering?
  2. Any creative workarounds using segments, lists, or other features?
  3. Am I missing an obvious Klaviyo feature?
  4. Should I handle this logic backend-side instead?

Additional Context

  • Using metric-triggered flows
  • Project IDs are dynamic (proj_abc123, proj_def456, etc.)
  • Events sent via API
  • This seems like a common automation pattern, so maybe others hit this too?

Anyone dealt with something similar? Would love to hear how you approached it!

Even if you haven't solved this exact problem, any creative ideas are welcome. Sometimes fresh eyes spot things we miss! 🧠✨

Thanks in advance for any help, insights, or "have you tried..." suggestions!

Hey ​@Clément,

Thanks for explaining the dilemma you’re facing with this flow. At the time, I can confirm that there isn’t a way to remove someone from a flow if a property on a subsequent event they record matches an event property in the event that triggered the flow. The reason for this is because profile/trigger filters can’t contain dynamic values, so there wouldn’t be a way to check if the value of an event property of one event matched another.

I definitely see how this would be useful, and I can reach out to our product team and recommend that we implement this in the future, though.


Reply