Bring sticky notes when traveling onsite to label the beacons
All documents and sessions should be loaded in QP before beacon setup begins
Make sure that each document that is linked to a beacon has a unique name that will make sense when notifications pop up on attendee devices. If attendees receive several notifications from different beacons with the same document name, it will appear as if the app is malfunctioning.
Do not link the beacons until the hardware is in-hand. It is faster to link beacons to documents or sessions once you physically have them than it is to link the beacons ahead of time and try to identify the linked beacons. If you have beacons in hand and link them before shipping onsite, make sure that each beacon is clearly labeled (coloured sticky notes are perfect for this)
Keep detailed notes on where each beacon has been deployed. If possible and if allowed by the client, take a picture of the beacon location.
If it is necessary to place a beacon with the adhesive side up, double check that the "flip to sleep" setting is disabled.
Beacon range varies greatly depending on where they are placed. Test thoroughly after setup is complete to ensure that the range setting is accurate for the beacon location.
Beacon range extends out the sides of the device in a donut shape. Avoid placing beacons sideways, or placing them high up or low to the ground.
Every beacon must be tested once deployed.
Create limited visibility sessions in your testing timeframe with check-in added and link them to your test user. Link the limited visibility sessions to the beacons for testing. If the client is testing with you, remember to assign them to the sessions as well.
Confirm that the range is appropriate for each beacon location.
By design, the app will notify you every five minutes when you are near a beacon. To reset the timer, return to the container and re-enter the event or force quit the app