The schedule tab allows you to control when you would like your campaign to be sent.
This tab will look slightly different depending on your campaign trigger and the type of campaign. We'll look into these in detail in this guide.
Use this option if you have a campaign you want to send just once to a segment of users or to all your users at launch. This is the default selection.
This option allows to send a message in the future. When you select this option you will be presented with a number of fields to complete:
- Send on: select a calendar date to send the campaign.
- Send time: select hour and minute for your campaign to be sent.
- Send by: select time zone that will be taken into consideration to send the campaign. By default, your notifications will be delivered at the local time zone you have configured when you created your project. However, you can use a different time zone or your users' time zone. In that case, if for example 50% of you users are in New York City and 50% are in London and your campaign is scheduled to send at 1pm by 'users timezone', then your notification will be delivered at 1pm GMT to your London users and at 1pm EST to your NYC users.
Send by user's timezone
If you configure the campaign to be sent by users' timezone option, only users that have a timezone set against their profiles will receive the campaign.
- Prepare upfront: You can select this option if you want to prepare your campaign before sending it. This is useful for larger campaign sends as it pre-calculates the segment that is being used in the campaign, which in turns enables the campaign to be ready to send at the moment the campaign is due to go out.
With this option you can set-up a campaign to send daily or on certain days and is useful when new users enter a segment. A classic example is automating a message to users who haven't opened the app in a certain date range (e.g, in the last 14 days).
Here you have a number of options.
- Days of the week to send on
- Time to send at
- Time zone to send by
- Date to start on
- Date to end on
For some campaign types (Android, iOS push and web push), if users are offline when a notification is initially sent it is possible to send the notification when they are back online.
You can set:
- Retry for: The default configuration for the retry period (4 weeks) is based on Apple and Firebase's defaults, which means that the user will be able to receive the notification when/if they come back online within 4 weeks. A custom time to retry for—such as 1 day, 12 hours, 5 minutes—can be configured.
- Retry until: A time and date after which the notification expires and will not be sent. This is great for scheduled notifications related to events that run at a specific time.
- Don't retry: Not recommended for most cases. See information below:
It's best practice to set a retry time to the longest period that is relevant for the campaign. Even for time-critical content, for example breaking news stories, it's more appropriate to set a 10 minute retry period than setting don't retry.
Retry period cannot be altered after send
The retry period cannot be altered after send, as this information is sent to the push gateway at the time the campaign is launched. The setting is used by the push gateway to understand how long it should keep trying to reach offline devices.
When a message is being placed in the inbox, on the schedule screen you can set how long that message will remain in the inbox. Thus, this option is only available for inbox campaigns.
You can set:
- Don't remove: enabled by default. Suitable when your goal is to persist a message in the inbox and have it naturally move down over time.
- Remove on: a time and date at which the message will be removed from the inbox. This is great for content related to events that run at, or for a specific time for example a limited time offer that runs for a month.
- Remove after: you can indicate the time after which you want the message to be removed, such as 7 days, 12 hours, etc. The right choice if your message is repeating or triggered and should only last for a certain amount of time, for example, a limited time offer triggered by entering a location.
Once that a campaign has been launched, inbox messages can be manually expired from the inbox feed.
For campaigns triggered externally (API triggered, event-triggered or location-triggered campaigns), the Schedule tab can limit the period during which the campaign can be sent. By default, no limits will be set, but it is possible to:
- Allow or disallow specific days of the week
- Set up the hours of the days where triggering campaigns is allowed, in a specific timezone
- Date and time where the campaign starts
- Date and time where the campaign stops
Some third party integrations such as Optimove allow users to set the stop time of the campaign from Xtremepush. See our Optimove guide for more information.
Updated about 2 months ago