Setting up a successful beacon campaign

The Sensorberg platform enables users to create, edit and manage proximity campaigns powered by beacon technology. Let’s walk through the campaign set-up options in order to start running successful campaigns that will have a great impact on your app’s user-base.

  • Name - Select an appropriate name for your campaign. This will make it easier for you to find it on your campaign list screen (remember: campaign names are always ordered alphabetically).
  • Toggle switch - The toggle should be set to  ‘Active’. Your campaign is always set to be active by default, however, you can deactivate a desired campaign by simply shifting the toggle (located in the upper right corner).  
  • Beacons - Select the beacons you want to use for a given campaign. Click on the Beacons form field and a dropdown list with all your registered beacons will appear. Please bear in mind that beacons settings (transmission power, transmission interval) are only adjustable during the beacon configuration. For smooth configuration of our Accent Systems beacons we recommend you to use our BeaCfg app:
  • Apps - Similar to the beacons, your apps registered on the platform will appear in a dropdown menu once you click on the app form field. Don’t forget to integrate our SDK into your native app first (more information on SDK integration is available here:
  • Schedule - Set up a schedule for your campaign (otherwise it will run always, unless deactivated using the toggle switch). The schedule feature, for instance, is very useful for short-term promo codes. 

  • Action - Action options determine how your notifications will appear to the end user (or dialog message if the app is in the foreground). Currently, the Sensorberg platform enables 4 types of notification actions: send notification, visit website, trigger an in-app function and silent analytics. First 3 notification type has to built according to the following format:
    • title
    • description
    • url (website or “in-app” deep link)

Silent analytics don't require above settings to be used.

Should you wish to use more advanced functionalities, we also allow you to place JSON objects in the custom data field to trigger custom actions for your notifications.

Please note that ‘visit website’ and ‘in-app function’ both require SDK version 0.9 or higher.   

  • Trigger - Campaign trigger determines when the message should be sent. “On Enter” campaigns will be triggered when an app user enters the beacon proximity region. “On Exit” campaigns will be delivered when an app user leaves the beacon area. “On Enter & Exit” will trigger the campaign twice.
  • Timing - The time feature allows you to define the moment a notification will be delivered. Currently, the following options are available: send instantly, send delayed after ‘xx’ minutes/hours/days or send at a clearly specified date and time. Note: the timing will work only if it’s in line with a trigger. In other words, if you want your campaign to be delivered at 3:15PM on February 15th, 2016 the app user has to have “entered” or “exited” the beacon proximity region before or at the specified time.

Please remember that for Android devices this functionality requires SDK version 1.0 or higher.

  • Frequency - This feature defines the repetition interval, at which a notification will be sent. Currently you can set your campaigns to be ‘sent always’, ‘once only’ or ‘once every ‘xx’ amount of time.’

Don’t forget to take the trigger feature into consideration, as well, when defining the frequency of your campaign.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Back to top