Scheduled Alarms

You can also trigger reminders for your app users relating to their in-app behaviour/activity, a specific date or range of time. With the local notifications, you can make the most of Accengage segmentation to activate or deactivate scheduled alarms on the terminals of your app users.

Setting scheduled alarms

As with in-app messages, the views of your application which will trigger the alarm have to be set in your application beforehand.

Creating a scheduled alarm

Click on the menu Actions > Scheduled Alarms tab. A display comes up with the list of campaigns and messages associated with your application. If you want to modify an existing application, click on the edit icon

  • To create a new message, click on the button "New Alarm". You will be directed to the form below. 

The form for creating a scheduled alarm is the same as the one for setting triggers in in-app messages except that it is possible schedule it. The various fields of the form are clarified below:

  • Name: Message name is the title of your campaign which will simply appear in your campaign list.
  • Categorie(s): You may add custom button categories for interactive notifications. Please note, that these custom categories have to be supported by your application. You can select up to 5 categories for a same message. For further details, please refer to our documentation. Interactive notifications are compatible since iOS 8 and with iOS SDK versions 5.4 and up.
  • Persistent message: This option allows you to display the message even if the app is launched without connection. Function compatible with iOS SDK versions 5.5 and up.

  • Dates:  Allows to schedule alarms the sending of a notification in a calendar date Days, Hours, Minutes (management a local time or GMT).
  • Display capping: Allow to define maximum number of times your message should be displayed per user over lifetime. When the limit is met the message does not display any more.
  • Marketing Pressure: By default, the message is integrated into pressure counter, if you want to exclude this message from marketing pressure of your application, simply uncheck this option.
  • Minimun delay between 2 alarms schedulings: This is the minimum delay that should be elapse between the displaying of two different in-app messages or two different scheduled alarms. Available from iOS SDK version 5.4 and up. This display delay between 2 distinct scheduled alarms specified in the advanced settings of the application. If you want to exclude this message from pressure counter of your application simply uncheck option.
  • Priority: Assign an order of priority to a message.

Choose the triggering rules of your message

It is possible to condition the display of a scheduled alarm over the events that have been realized within the application. These parameters must be tagged in the application and reported in the advanced settings of the application:

  • Event(s):  Possibility of including and/or of excluding events to prevent the display of the notification.
  • View(s): Possibility of authorizing and/or of restricting the display of the notification on certain screens.
  • Geofence(s) and ibeacon: Possibility of including and/or of excluding the display of the notification according to its geographical position.
  • Network restriction: Possibility of including and/or of excluding the connectivity.
  • Display only once per event: By ticking this field, you set capping for the event. In other words, your alarm will only go off once the event occurs. If the event occurs again, the capping is set to 0 and you can therefore use a new alarm


The Alarm can be programmed in two ways:

  • Timer: the message is triggered in X seconds/minutes/hours/days. The field must be filled in with a value greater than 0.
  • Calendar date: the message is triggered on the chosen date and hour. You can trigger message sending according to the app user’s date and hour by selecting the interface.

If you do not tick “local hour”, the message will be sent on GMT time.

Exclusion When you are in timer mode, you can define exclusion ranges using the button You can exclude time ranges by selecting or exclude by calendar date with a start date and end date by selecting .

In the example, there is an exclusion zone for triggering alarms between 8 p.m. and 7 a.m. for the app user's local time.

In the example, the sending of messages is excluded from 19/02/2013 8 p.m. until 20/02/2013 7 a.m. In Date/Hour exclusion, the reference hour is GMT time.

  • Cancel alarm: By default, if the alarm is scheduled to be displayed during an exclusion range, its display will be postponed until the next available time range. if you want to cancel the display of the alarm in this case, please tick the check box.
  • Start timer : If the app is already open, you can choose whether or not you want to display the scheduled alarm within the application.
  • Cancel Alarm: It is also possible to cancel a scheduled alarm. For that select the Template "Cancel Alarm" then select the alerts you want to cancel:

Create the message which will be displayed on the screen of the mobile user

Specifics details on Android

The form of creation of an alarm scheduled on your application Androïd proposes different template of notifications with specific fields.

Select Template of message that will display on the mobile of the user and complete the specific fields to your message.

> > >For a specific description of Android formats supported

When you have filled in these various fields of your form, select which segments will receive your alarm then set-up:

For a specific detailed of the creation of your target segments, refer to the topic targeting> segments and static lists.

There are two ways to set up a scheduled alarm :

  • From the form of creation of your Alarm, push the button "Activate" of your form.
  • From the dashboard click on the icone or to activate or to desactivate your alarm.