• Keep alerts relevant and timely (attendees can get overwhelmed by an over-abundance of alerts).

  • If you add new alerts, they must be published to the app. In the CMS > Now tab, click the buttons Publish (Proof) to test in your proof app and then and Publish (Live) to push the alert to all your users into the live app.

  • Make sure the start/stop time is in military time and the year is correct.

  • Avoid last-minute deletion of alerts (it takes time for the app to refresh on user devices to remove a previously cached alerts).

  • Limit the number of alerts to a maximum of 5 per day.

  • Set the duration of alerts for at least 30 minutes to ensure the majority of attendees receive/see the alert.

  • If possible, schedule all your alerts in advance of your event. This increases the likelihood that your attendees will have downloaded your latest alert settings on their device and receive the alerts even when they are offline.

  • (If applicable) Assign an Action to your alerts so when users click on an alert, it takes them to related content. You can link to web pages or a variety of pages within the app itself.

  • If you want to use alerts for sponsorships / advertisements (here are alternatives for sponsorship/ad placement), limit the number to maximum 1 per day and try to make these alerts relevant to the attendee or provide actual value. 

  • Limit who would receive the alert by targeting alerts by:
    • Location (Location Alert Module)
    • Attendee Types (Targeted Content Module)
    • Just the session attendees have scheduled (included)