The Adtag Application Management section allows you to configure your SDK options directly from the Adtag Platform.

Access to the Adtag Application Management section

1- Connect to your Adtag account

2- In the upper, right-hand corner of the page, click on your user name > Application Management

3- In the list of applications that appears, select the desired application: the Adtag Application editor opens

4- Start configuring

Overview of the Adtag Application editor

The Adtag Application editor contains 7 tabs:

  • Context: to manage language settings and accessibility
  • Parameters: contains your credentials to initialize the SDK in your application
  • Notifications: to manage your notification settings
  • Welcome Notifications: to manage your Welcome Notifications
  • Android: to manage your Android SDK settings
  • iOS: to manage various iOS SDK settings
  • Logs: to manage the log process for our QR, NFC, and Beacon SDK

The Notifications Tab

This tab contains various settings to help you manage your sdk notifications. For more information, refer to the Notification overview document

Enable notifications

This switch enables you to turn ON/OFF the notifications related to your app. For instance, if you only wish to leverage interaction logs to measure foot traffic, you can switch OFF notifications here.

Enable Timing Filters

This switch allows you to activate notification filters, to define the appropriate moment when a user receives a notification. When the option is activated, you can manage three settings:

  • Max # of notifications: maximum number of notifications that can be sent to a user, over a specific period of time
  • Min notification interval: minimum time lapse between two beacon notifications
  • Minimum time before displaying a notification: minimum time lapse prior to generating a notification after the application starts running in the background

Enable Custom Filters

You also have the ability to code and register your own Notification Filter, to implement additional filters to refine your user experience (learn more in the Notification Filter overview).

Use this section to add the key of the custom strategies that you have coded, to activate them in the SDK.

The Welcome Notification Tab

This tab allows you to activate and manage Welcome Notifications in your app. For more information on Welcome Notifications, refer to our Welcome Notification overview

Enable notifications

The switch allows you to enable/disable Welcome Notifications for your application.


This section allows you to define:

  • Min notification interval: minimum time lapse between two Welcome Notifications
  • Max # of notifications: maximum number of Welcome Notifications a user can receive in the app

For example, if you set the maximum number to 3, and the minimum time lapse to 24h, your app users will receive a maximum of 3 Welcome Notifications in the app, with at least a 24-hours time lapse between each.

Notification Content

This section allows you to configure the content of your Welcome Notification, as described in the overview document:

  • The title of the notification
  • The description of the notification (optional)
  • The thumbnail associated with the notification (optional - Android only)
  • The image associated with the notification (optional)
  • The textToSpeech, if talkback or voiceover is activated (optional)
  • The deep link / URI used to configure the engagement action with the Welcome Notification (optional)

You can also manage two additional parameters:

  • Minimum Display Time: for the Welcome Notification to remain visible for the end user
  • Replace Default Notification: to choose whether or not to display the default beacon notification in addition to the Welcome Notification

The Android Tab

Bluetooth Management

Our mobile SDK uses Bluetooth scanning to detect nearby beacons, and has the ability to automatically enable Bluetooth on smartphones. As Bluetooth can have a strong impact on battery consumption, AdTag and our SDK enable you to optimize access to this functionality, based on the state of the application (opened, running in the background, or closed). When the application is opened by a user, you can choose:

  • Automatically activate Bluetooth, for the SDK to automatically enable Bluetooth, if it is disabled
  • Never activate Bluetooth, for Bluetooth to be left disabled

When the application is closed or starts running in the background, you can choose:

  • Ask one time, for the SDK to send a notification and ask permission to enable Bluetooth the first time that the app goes into the background + Bluetooth is disabled.
  • Automatically activate Bluetooth, for the SDK to automatically enable Bluetooth, if it is disabled
  • Never activate Bluetooth, to leave Bluetooth disabled

Background Scanning Strategy

This section contains additional parameters to define the way the SDK performs background beacon scans. For more information, please refer to our Background Scanning Strategy overview You can choose between two scanning strategies:

  • Regular scanning
  • Scan when display is turned ON

For both strategies, you can update:

  • The Scanning duration: the duration of the SDK scanning periods
  • The Scanning interval: the amount of time between two Bluetooth scans

With the "Scan when display is turned ON" strategy, you can configure an additional setting: the Intensive scanning duration, which corresponds to the amount of time the SDK continues to perform background scans after the screen is switched ON, unless a beacon is detected.

For the "Regular scanning" strategy, the default settings are:

  • Scanning Interval: 12'
  • Scanning Duration: 12'

For the "Scan when display is turned ON" strategy, the default settings are:

  • Scanning Duration: 12'
  • Scanning Interval: 10'
  • Intensive Scanning Duration: 20'


The "Scan when display is turn ON" is not yet available in the version 3.0 of the SDK.

The iOS Tab

This tab contains one setting to enable you to manage Bluetooth detection on iOS.

The Always ask for BT activation switch allows you to activate notifications to encourage your users to turn on Bluetooth, each time it is disabled upon app opening.


The SDK 3.0 does not include this feature. It does not generate a notification asking the users to switch on the Bluetooth. However, it does generate an sdk error, alerting the application that the beacon scanning cannot start as the Bluetooth is disabled.

Therefore, we let you choose what you think to be the best action to realize when receiving this error.

You can learn more by reading the document about managing the SDK error

The Logs Tab

This tab allows you to manage log updates back into the AdTag system. Logs are saved in a specific database, and sent in a dedicated thread when a maximum number or a maximum waiting time is reached. You can manage three parameters on AdTag:

  • Send through Wi-Fi only: the network that your application can use to send the logs to the Adtag platform: it can be WIFI_ONLY or ALL (for all types of networks)
  • Send threshold: the maximum number of logs mentioned above
  • Frequency: the maximum waiting time mentioned above

Default settings are:

  • Network type: ALL
  • Maximum number of logs: 30
  • Maximum waiting time: 25 seconds