Dayparting is an advanced Blueshift feature that enables you to choose the times of the day to send your triggered campaigns (in order to avoid undesirable 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, simply click and drag to create your preferred dayparting windows. Click to select individual hour slots. 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 does not fall within 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 and these are applied to all days of the week.

In this example, all messages will be sent between the hours from 8 AM to 12 Noon, Monday through Friday, in the account timezone.

jb_delay_daypartingsection.png

Dayparting examples

Example for an event triggered campaign:

Consider a campaign where you have set dayparting between 10 AM and 12 PM for all days and there are no delays on the campaign trigger.

  • Event comes in at 9.45 AM on Monday - is queued until the next eligible window i.e. 10 AM on the same day.
  • Event comes in at 11 AM on Tuesday - gets sent immediately since it is within the 10 AM and 12 PM window.
  • Event comes in at 4 PM on Wed - is queued to be sent at 10 AM on Thursday, but campaign messaging limit for Thursday will be applied.

Example for a segment triggered campaign:

Consider a campaign where you have set dayparting between 10 AM and 12 PM for all days and there are no delays on the campaign trigger. Also, assume that the segment definition looks back for users with joined_at date in the past 1 hour only.

  • User joins segment at 9.45 AM on Monday - campaign will not execute until 10 AM, but at 10 AM, it will look for users who have joined between 9 AM - 10 AM and therefore this user will get an email.
  • User joins segment at 10.45 AM on Monday - within the day parting window and the user gets an email.
  • User joins segment at 1.45 PM on Tuesday - outside the day parting window and campaign will not execute until 10 AM on Wednesday. At 10 AM on Wednesday, segment will only look at users from past 1 hour (9 AM - 10 AM) and user will get skipped.

So in this scenario, to ensure that users are not getting missed, you must increase your segment and/or day parting window.

Example for one time and recurring campaigns:

Consider a campaign where you have set dayparting between 10 AM and 12 PM for all days and there are no delays on the campaign trigger.

  • User joins segment at 1 AM on Friday - is queued until the next eligible window i.e. 10 AM on the same day.
  • User joins segment at at 11 AM on Saturday - gets sent immediately since it is within the 10 AM and 12 PM window.
  • User joins segment at at 6 PM on Sunday - is queued to be sent at 10 AM on Monday, but campaign messaging limit for Thursday will be applied.
Was this article helpful?
1 out of 1 found this helpful

Comments

0 comments

Please sign in to leave a comment.