Dayparting

Dayparting is an advanced Blueshift feature that lets you choose the times of day to send your triggered campaigns (to avoid undesirable send times). It indicates when the campaign is allowed to message the user. This can be set for the customer or account timezone.

Dayparting is available for one-time, recurring, segment-triggered, and event-triggered campaigns.

You can set the required send times from the Dayparting section of the Delay tab for the trigger.

To select the hours when the messages get delivered, in the Schedule tab, click and drag to create your preferred dayparting windows. Click to select individual hour slots. Dayparting includes the beginning hour and excludes the ending hour. You can also set for messages to be queued or skipped if the send time is outside the dayparting windows. If the user is outside the dayparting window, you can configure whether to queue or skip the user. Queuing will introduce a delay until the next eligible dayparting window. Skipping will exclude the user from this trigger if the send time falls outside your dayparting windows, and the message will be discarded and not sent.

You can also see an Overview of the dayparting windows.

• For event-triggered campaigns and segment-triggered campaigns, you can select hourly slots for the various days of the week.
• For one-time and recurring campaigns, you can select hourly slots that apply to all days of the week.

In this example, all messages will be sent between 8 AM and 12 Noon, Monday through Friday, in the account's time zone.

Dayparting examples

Example for an event-triggered campaign:

Consider a campaign with dayparting set to 10 AM to 12 PM for all days, with queuing, and no delays on the campaign trigger.

• Event comes in at 9.45 AM on Monday. The user is queued for 10 AM on the same day.
• Event comes in at 11 AM on Tuesday. The user is sent immediately since it is within the dayparting window.
• Event comes in at 12 PM on Wednesday. The user is queued to be sent at 10 AM on Thursday because dayparting excludes the ending hour.
• Event comes in at 4 PM on Thursday. The user is queued to be sent at 10 AM on Friday because they are outside of the dayparting window.

Example for a continuous segment-triggered campaign:

Consider a campaign with dayparting set to 10 AM to 12 PM for all days, with queuing, and no delays on the campaign trigger. Also, assume that the segment definition looks back only to users with a joined_at date within the past 1 hour.

• User joins the segment at 9.45 AM on Monday. The campaign executes at 10 AM. Since dayparting includes the beginning hour, the user will receive a message at 10 AM.
• User joins the segment at 10.45 AM on Monday. The campaign executes at 10:50 AM. Since the user is within the dayparting window, the user will receive a message at 10:50 AM.
• User joins the segment at 11:45 AM on Wednesday. The campaign executes at 12 PM. The user will be queued until 10 AM on Thursday because dayparting excludes the ending hour. At 10 AM on Thursday, the user will still receive the message, even though they are no longer part of the segment, because segment-triggered campaigns don't require you to be part of the segment to receive messages.
• User joins the segment at 1.45 PM on Tuesday. The campaign executes at 1:50 PM. The user will get queued to 10 AM on Wednesday since they are outside dayparting. At 10 AM on Wednesday, the user will still receive the message, even though they are no longer part of the segment, because segment-triggered campaigns don't require you to be part of the segment to receive the message.

Example for one-time and recurring campaigns:

Consider a campaign with dayparting set to 10 AM to 12 PM for all days, with queueing, and no delays on the campaign trigger. Assume the user is a part of the segment when the campaign executes.

• The campaign executes at 1 AM on Friday. The user is queued for 10 AM on the same day.
• The campaign executes at 11 AM on Saturday. The user is sent immediately since it is within dayparting.
• The campaign executes at 12 PM on Wednesday. The user is queued to 10 AM on Thursday because dayparting excludes the ending hour.
• The campaign executes at 6 PM on Sunday. The user is queued for 10 AM on Monday.