Topics started by John Parker
Hello,I’m working on a new “Subscription Upsell Flow” that is based on the “Fulfilled Order” event with the Shopify integration. How do I add a conditional split that is based on the actual “Fulfilled Order” event? I’m trying to send different email content based on if their purchase contained a specific item or not.For example: If one of the items they purchased was our Sun Goddess Matcha -- send them “Subscription Upsell” email X, if one of the items was our Sun Goddess Matcha Tin send them “Subscription Upsell” email Y, If one of the items was our Beauty Electrolyte send them “Subscription Upsell” email Z, etc. Any and all help is appreciated.Thanks!This is what I have so far . . .
Hello,We recently had a customer reach out to let us know that they miss receiving our marketing emails. However, we can’t send them to her because we suppress anyone who has soft-bounced 4 or more times from our campaigns & flows. Is there a way to clear the soft bounce data from her profile? Or, do you recommend we delete her contact profile altogether and re-opt her into our list? Thanks for the help!
Hello,I’m trying to create a dynamic content block that shows/hides based on if someone is subscribed to SMS. Is this possible? We currently collect SMS from multiple sources, so it would need to be based on a segment. Or, we could build a separate flow to ensure everyone has a custom property. Anyways, this is what I have so far…. Any help would be appreciated! Ultimately, I only want the dynamic block to show if they are not currently subscribed to SMS. The actual Dynamic Block The segment it’s based on
Hello,I recently put a 50% random sample conditional split to test two different flow setups however my “No” has not received any emails yet. . . I looked at the waiting group, and they seem to not be scheduled until December. Do I need to back-populate the flow? Or, is there another solution to this?
Hello,I revamping our welcome flow and want an extra set of eyes to confirm that I am doing this right. The idea is to build THREE separate email streams for the following segments:(STREAM #1) New Email Leads who signed up but have never purchased before I want this group to exit the flow if they have made a purchase since starting the flow. (STREAM #2) New Email Leads who signed up during a purchase @ checkout I do not want this group to get our Welcome Series at all, because they will be routed to our “Thank You” flow & I don’t want them to get both. (STREAM #3) New Email Leads who have signed up but have purchased before I want this group to exit the flow if they have made a purchase since starting the flow. This is what I have so far: (Please ignore the content (They are just placeholders)
Hello,We’ve been experiencing deliverability issues as of late and wanted to ask the community for best practices to implement with our campaigns and flows. Right now one of our solutions is to add the following Flow Filter logic to all flows: Our Do Not Validity list is a list of all addresses we discovered that were Invalid, Spam Traps, etc. Any Feedback? Or, do you think this is a good solution?
Hello,I’m updating our “Order Confirmation” transactional email in Klaviyo and need help building a dynamic content block that only appears when someone has purchased a specific item in their order. What syntax am I supposed to use? Use case: Someone purchases our Match Beauty Bundle Subscription and we want to display a disclaimer that tells them that the price will decrease during their second month. Thanks in advance! John
Hi All,I want to set up a flow that triggers when a contact has not Opened or Clicked any email in the last 90 days. There would be multiple emails in the stream, so if a contact Opens or Clicks on an email at any point throughout the journey I want them to exit. Can someone check over to make sure I set up this properly? Appreciate all the help. This is what I have setup so far: The “Flow_Email-Re-Engagment_90-Days” segment logic is as follows:
New Topic Guidelines
If you’ve already contacted the Klaviyo Support Team about this issue, please wait for a response and check your spam inbox for an email before posting in the Community.
Keep your private information private. That means, leave out information such as email address, links to account, private API key, customer info, etc. out of your posts.
Collaborate and discuss ideas in a positive and respectful manner. We are all here to learn and work together.
Promotion of other products/services should be relevant to the original post. The product/service should directly assist the community member with their issue.
Include as much detail as you can in your posts where applicable. The more information (integration, error message, screenshot, etc.) you include, the easier other Community members can assist or add to your discussion.
Starting a discussion or writing a feature request? Let people know how they can join in or provide feedback! Are you looking for others to share their thoughts, recommendations, examples, etc? Be as specific as you can where applicable.
Most helpful members this week
Log in to the Community
Use your Klaviyo credentials
Log in with Klaviyo
Use your Klaviyo credentialsLog in with Klaviyo
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.