To update the content of an alert on the Adtag platform, you need to:

Connecting to the Adtag Platform

  • Enter your login and password
  • You are now on the interface that allows you to manage Points & their corresponding content

WARNING: make sure that your app is configured to work on the same environment as the Adtag environment you are accessing.

Selecting a point and editing its content

  • Click on a point

  • A slider menu opens, with all the characteristics of the point (Context & Content information)
  • Click on Edit in the menu

  • You can now update the information related to the point
  • Click on the iBeacon tab

Depending on the type of action that you want to trigger, you may or may not use all of the data model fields present on Adtag.

As a reminder:

  • Beacon Alert: set of attributes to configure the action/message displayed on a phone when a beacon is detected, when the application is in the foreground.

    • 2 fields can be configured:
      • Title
      • Description
  • Beacon Alert Parameters : set of parameters to specify the context of an alert’s display

    • 4 fields can be configured:
      • Range: proximity zone applicable to the alert (the alert will only be triggered if the smartphone is in the right area around the beacon)
        • Predefined values: IMMEDIATE, NEAR, FAR
      • Action: action triggered when a beacon is detected, and is in the right range/proximity zone
        • Examples:
          • popup: could open a popup and display the title of the alert, as configured in Adtag. The user could click on the popup to access additional content
          • webview: could automatically open a webview page when the device is in the right beacon’s action range
      • Default alert strategy: to implement a Default Alert Strategy - Predefined values: "=" (default value), "<=", ">="
      • Your custom strategy: to implement your own Alert Strategy - Populate the field on Adtag with the key of your custom alert strategy in the SDK.
        • If you define a Custom Strategy, then the Default Alert Strategy parameter will be ignored.
        • If the SDK cannot find a Custom Strategy, it will default back to the Default Alert Strategy.
  • URL: URL of a mobile web page that can be used to display content inside a webview (e.g. “Action” = webview)

  • URI: URI of a mobile app page that can be used to trigger the launch of specific pages inside your application


The action, the range and the alert strategy properties define what happens when a foreground application interacts with a beacon.

For example, if the range parameter is NEAR, the default strategy is '<=' (inferior or equal to the Range parameter), and the defined action is ‘popup’, then a popup appears in the application when the beacon is detected in the IMMEDIATE or NEAR range.

The ‘Action’ field accepts any values: ‘popup’ and ‘webview’ are just examples of what you can implement. The same applies for the 'custom strategy' field. It is up to developers to define the behaviors that will occur in their own applications, and the value they want to set in the Adtag platform.

  • As an easy illustration, simply update the title of the alert and click on Save on the header bar to validate your changes.

Testing the update