Skip to main content
Solved

How to stop sending flow campaigns during certain times of day?


Forum|alt.badge.img

WHAT: I am trying to create daily “blackout” times for the flows emails. For example, I may want to exclude flows emails from sending during 8 am - 11 am, and again from 5 pm - 7pm.

WHY: I want to ensure qualified customers never skip receiving our profitable daily batch emails that send twice a day. Frequently, batch emails are skipped due to receiving automated flow emails. 

CONSIDERATIONS:

  1. I don’t want to turn off smart sending because I don’t want customers to receive batch emails and flow emails back-to-back, either.
  2. The time delay is inefficient but do-able for AM emails.  But I’d prefer they be able to receive flow emails before the AM batch campaigns.
  3. The time delay won’t work for PM emails because I don’t want all automated messaged to only trigger until after the PM daily campaign.

ATTEMPTED SOLUTION:

I wanted to use a conditional split for customers who triggered an event by a certain time each day, say 08:00. Customers who entered within these certain periods would be put into a 2 hour time day. I’ve attached images of the flow and settings below.

 

PROBLEM:

The issue I’m running into is that the Klaviyo Developer documentation says the timestamp format requires it to be written as  YYYY-MM-DDTHH:MM:SS.mmmmmm.  Using a specific date in addition to the timestamp means my solution won’t work unless there’s another way to input time somehow, maybe with account/system settings?

 

Looking for other solutions to daily blackout periods, or suggestion to modify this one. Thanks!

 

IMAGE 1/2:

Condition 1 filters event time that conflict with AM emails.

Condition 2 filters event time that conflict with PM emails.

 

IMAGE 2/2:

Conditional split details for AM email

 

 

Best answer by MANSIR2094

Hi ​@awlhaint ,

Thank you for sharing your detailed requirements. To implement daily blackout times in Klaviyo Just as ​@Mich expert mentioned, you can use a combination of time-based conditional splits, delays, and smart sending. Add a conditional split after the trigger event to evaluate the time of day and determine if it falls within the blackout windows. For example, set conditions like "If time is not between 8 AM - 11 AM" or "If time is not between 5 PM - 7 PM." This ensures emails are only sent outside these periods.

For customers entering a flow during blackout windows, use time delays to push the email until after the blackout period. For instance, delay morning emails until 11 AM or evening emails until after 7 PM. Keep smart sending enabled to prevent customers from receiving batch and flow emails back-to-back.

If your event data includes timestamps, use Klaviyo's Format Date function to extract hours and minutes, then create precise conditions based on specific time windows. This avoids requiring a full timestamp format for the splits.

If this approach feels complex, another option is to segment customers by AM and PM timing and manage their email sequences in separate flows. This provides more control without relying on conditional splits.

Let me know if you'd like further guidance or assistance testing these adjustments. I’d be happy to help.

View original
Did this topic or the replies in the thread help you find an answer to your question?

3 replies

Mich expert
Problem Solver IV
Forum|alt.badge.img+11
  • Problem Solver IV
  • 64 replies
  • January 11, 2025

To create blackout times for flow emails in Klaviyo, consider these solutions:

1. **Use Conditional Splits**: Set up splits based on the event time, but instead of a specific date, check if the event occurred within your blackout periods (e.g., before 8 AM or after 5 PM).

2. **Time Zone Settings**: Ensure your account's time zone is correctly set to avoid discrepancies with timestamps.

3. **Smart Sending**: Keep smart sending enabled to prevent back-to-back emails, but adjust flow timings to avoid overlaps with batch emails.

4. **Manual Time Delays**: As a last resort, use time delays to space out flows, but be aware this may lead to inefficiency.

If issues persist, consider reaching out back to me for more tailored guidance.

Best Regard 

Mich PRO

Klaviyo expert


MANSIR2094
Problem Solver IV
Forum|alt.badge.img+13
  • Problem Solver IV
  • 174 replies
  • Answer
  • January 11, 2025

Hi ​@awlhaint ,

Thank you for sharing your detailed requirements. To implement daily blackout times in Klaviyo Just as ​@Mich expert mentioned, you can use a combination of time-based conditional splits, delays, and smart sending. Add a conditional split after the trigger event to evaluate the time of day and determine if it falls within the blackout windows. For example, set conditions like "If time is not between 8 AM - 11 AM" or "If time is not between 5 PM - 7 PM." This ensures emails are only sent outside these periods.

For customers entering a flow during blackout windows, use time delays to push the email until after the blackout period. For instance, delay morning emails until 11 AM or evening emails until after 7 PM. Keep smart sending enabled to prevent customers from receiving batch and flow emails back-to-back.

If your event data includes timestamps, use Klaviyo's Format Date function to extract hours and minutes, then create precise conditions based on specific time windows. This avoids requiring a full timestamp format for the splits.

If this approach feels complex, another option is to segment customers by AM and PM timing and manage their email sequences in separate flows. This provides more control without relying on conditional splits.

Let me know if you'd like further guidance or assistance testing these adjustments. I’d be happy to help.


Christiannoerbjerg
Expert Problem Solver II
Forum|alt.badge.img+12

Hi ​@awlhaint 

Thank you for posting in the Community!

It looks like, that you have already got some things to try with the answers above :-) I’m keen to know, if that works out for you? 

If not, i think the best way for you to fo this is possibly by saving the timestamp of the event (Like add to cart), as a property, that you can save on a customers profile in Klaviyo. 

I have not yet tried it out myself, but i’m keen to try it out. 

Can you confirm ​@stephen.trumble, if the event payload (Timestamp) is possible to save for every event tracked inside of klaviyo? 

If yes, it would be cool to built out via. webhooks for all of the events inside of klaviyo. 

Christian Nørbjerg Enger
Partner & CPO
Web: Segmento.dk
LinkedIn: @christianfromsegmento
Voldbjergvej 22b, 8240 Risskov