Hi Possum,

To fix your issue, try these solutions:

1. Custom Event Trigger: Set up a custom event (e.g., "Custom Form Submission") via Klaviyo’s API for each form submission. This ensures all submissions, including repeats, trigger the internal alert flow.

2. Hulk Form Integration: Use a tool like Zapier to link Hulk forms to Klaviyo, allowing multiple submissions to create unique triggers.

3. Segment Trigger: Ensure your segment updates frequently and use a metric trigger instead of just list-based actions for better accuracy.

Let me know if you need help setting this up—reach out via PM or WhatsApp +234 9151237531 anytime!

Hello Possum,

It sounds like you're encountering a common challenge with handling repeat submissions in Klaviyo, especially when using embedded forms on Shopify. Let’s explore some potential solutions and best practices to streamline your Custom Product Request Form for repeat orders.

Current Situation

You have a form that adds users to a list called "Custom Request," triggering an internal alert. However, repeat submissions are not being processed as expected.

Suggested Solutions

1. Unique Identifier for Repeat Orders

To handle repeat submissions effectively, consider implementing a unique identifier for each order. This could be a combination of the user's email and a timestamp or a unique order ID. Here’s how you can approach it:

• Modify the Form: Add a hidden field in your Klaviyo form that generates a unique ID for each submission.
• Flow Trigger: Change your flow trigger to activate on this unique ID rather than just the list addition. This way, every submission will be recognized as a unique event.

2. Utilize Custom Properties

You can use custom properties to track repeat orders:

• Add a Custom Property: Create a custom property in Klaviyo to track the number of orders or the last order date for each client.
• Flow Logic: Modify your flow to check this property. If a client submits a new order, increment the order count or update the last order date, which can help in triggering alerts for repeat orders.

3. Adjusting Flow Triggers

For your attempts, here are some tweaks:

• Attempt 1: Ensure that Klaviyo recognizes the form submission by checking if the form ID is correctly set in the Klaviyo integration settings. Sometimes, re-saving the integration can help.

• Attempt 2: When using segments, ensure that your flow is set to trigger on segment membership changes. You can also check the frequency of segment updates in Klaviyo settings; it typically updates every few minutes.

4. Using Hulk Form App

If you decide to use the Hulk Form App, you can:

• Integrate with Klaviyo: Check if the Hulk Form App has a way to send data to Klaviyo via API or webhooks. This would allow you to capture multiple submissions while still notifying Klaviyo about each order.
• Custom API Calls: If you’re comfortable with coding, you can create custom API calls to send form data directly to Klaviyo upon submission.

Conclusion

Implementing these strategies should help you manage repeat orders more effectively. Remember to test each change thoroughly to ensure that the internal alerts are functioning as expected.

If you need more detailed guidance on any of these steps, feel free to ask. I'm here to help! reach out via PM or WhatsApp +234 8087340172  anytime!

Best,
Mic pro
email marketing expert

Hi ​@possum! I can appreciate how frustrating this must be - thanks for bringing your question to the community.

First, let’s start with a foundational understanding of how Klaviyo works. For any list OR segment, a flow triggered by joining that list/ segment can only be triggered one time - ever. 

Part of why ​@MANSIR2094 may be recommending you use a Custom Event Trigger for your flow that’s intended to capture new Custom Product Requests is because any flow triggered by an event can be entered multiple times. So for example: anytime someone has an “added to cart” event tracked by Klaviyo, that event “fires” the flow trigger, and they enter the queue each time that event occurs.

I have several clients who also do custom orders, and I can appreciate the benefit of automating the follow-up process your team would otherwise have to do manually. 

However, creating a custom event means implementing custom API work that your team might not be able to do on your own, or may find overwhelming. Hulk forms with a Zapier integration similarly creates several extra steps for your team to setup, and then maintain over time in case things happen like a question on the form is changed or removed. 

An alternative easier solution is using Typeform instead.

Typeform has a native integration with Klaviyo - you can explore those details here. https://help.klaviyo.com/hc/en-us/articles/115000107112

That would replace the need for both Hulk forms AND the custom event integration since any time someone submits a Typeform, this event data is sent to Klaviyo: Filled Out Form

THEN you can trigger the flow based on that event, and because it is not triggered by a list or segment, each time someone takes that Filled Out Form action, the flow trigger will fire, and they’ll enter the queue. 

Typeform’s integration will also sync questions and answers to Klaviyo as custom profile properties, so you might consider asking a question like “how many times have you placed a custom product order” and specify it as a Number data type field, so people can only enter normalized values like 1, 2, 3, etc.

You could later use that data to create segments to identify your repeat custom order customers, in case you wanted to send a campaign specifically to them. Or similarly, identifying people who’ve only placed 1 custom order over all time, and nurture them towards a second custom order. 

Happy to answer any other questions this brings up for you. 

~ Gabrielle

​@possum i got you but For any list OR segment, a flow triggered by joining that list/ segment can only be triggered one time so typeform is there : )