Important: Please review the best practices for alerts and consider only alerts that offer a true benefit for your attendees. We have seen attendees complain on X (formerly Twitter) when organizers add too many notifications or alerts that don't provide value (such as "welcome to the conference").
Adding an Alert / Notification
- Log in to the Conference App Builder > select the Design menu > Alerts
- Select the Add New button
- Fill in the fields as necessary and add an action if needed. Tip: Set alerts to last at least 30 minutes to ensure the majority of attendees will see it. Several hours is ideal.
- Attendees that have seen the notification will not receive a second notification. The accompanying alert on the home screen will automatically disappear at your specified end time or if the attendee closes the alert card.
- Press the Publish button when you have set up the alert. Note that this will add the alert to both your proof and live platforms.
- Note: if you are linking an alert to a newly created data record such as a new speaker, then you must publish a full data set first. The apps must first receive the data update with the new speaker information first. We recommend to plan all your alerts in advance of the conference.
- When the event is over, you can access analytics to review which alerts were viewed or clicked on. (Remember that users may have turned OFF receiving device notifications in their operating system settings.)
Ensure to set up all your notifications in advance of your event. This increases the likelihood that your attendees will have downloaded your latest alert settings on their device.
Adding Location Alerts / Notifications (geolocation)
GPS based location alerts are available as an add-on service for EventPilot Pro implementations. These alerts appear for native apps installed on iOS and Android and if the user allowed location based notifications as part of the installation process.
Contact your Project Manager to receive a template you can fill in. You will need the following for each location alert:
- GPS coordinates
- radius distance (for example: for your convention center, you may want to use 250m to encompass anyone in and around the convention center)
- if the alert should appear if the user is inside or outside that radius
- alert label
- alert text
- any action you wish to be available when the user clicks
- if you have implemented targeted content, which user type
Examples of GPS location alerts
Inside the geolocation
- You have a special event happening onsite. You only want to remind attendees who are in or near the convention center that this special event is about to start.
- You want to remind exhibitors, who are at or near the convention center, where they can find exhibitor resources. You could have a special custom view in the native app with important exhibitor info and link to that from the alert.
Outside the geolocation
- You have an offsite event that starts at 5pm. You want to remind any attendees who are not at the offsite location at 5:30pm where the buses leave from and they still have time to join.
- You want to remind your remote attendees how they can access your streaming content. You'd set up the alert for anyone who is not in the event city (use a radius of 100km)
- Your exhibit hall opens at 10am. You want to remind any user of type exhibitor who is currently not at the convention center that the expo hall will open soon and to ensure to staff their booth.