Both Campaign scheduling and Delivery Timing features serve to deliver notifications at a certain time (or a time frame). However, it is important to understand the difference between these two because otherwise they may overlap against themselves and lead to worsened campaign's impact.
Currently, scheduling enables you to add a time frame (with multiple time slots) for your campaign. That means that you can determine the Start and End time for your campaign (otherwise it will run infinitely). We recently added a Multiple Time Slots feature to assign more than one-time frame for a given campaign.
It's crucial to note that Scheduling only works when app users enter Beacon proximity region so if the user enters beacon proximity region before the Start Time and will stay there until a campaign will start a notification won't be delivered.
Timing feature (Deliver delay / Delivery at / Send only once / Suppression time), on the other hand, lets you define the exact moment of delivery, a delay in delivery or whether a campaign should be fired only once. See examples below:
When device gets in to beacon region, campaign will trigger with 60 seconds delivery delay.
Campaign will be delivered at 20.06.2017 at 10:45 AM.
When device gets in to beacon region, campaign will trigger only once.
With suppression time we can specify how often our campaign will trigger. In above image, our campaign will fire every 2 minutes (120 seconds).
As opposed to Scheduling, Delivery Timing will work if the user enters beacon proximity region before the delivery time. Moreover, the user doesn't have to be in the proximity range to receive a notification. The classic use case for this feature would be sending out post-event surveys to attendees who are already at home. Another one would be to deliver campaigns only once at a certain point in time.
When designing a successful beacon campaign it is important to take the above considerations into account before combining these two features.
_We generally do not recommend: Delivery at + Schedule_