Targeting

Overview of the database

Each application has its own database. That is why it is possible to modify its structure by adding as many fields as you want in case you wish to develop data associated with your app users. Some fields are useful for segmenting your targets and may be used both to personalise your messages (surname, name) (See the chapter Message > Personalising a message) and to organise, analyse and segment your targets (sex, age bracket, area of activity, etc.).

List and definition of default fields in the database

  • Device ID / Mobinaute ID is the reference ID for the device. For iOS, the Device ID is the Identifier for Vendor (IDFV), depending on the OS version.

    For Android systems, the App User ID is a generated ID which is unique per device using Accengage's SDK. If needed, do not hesitate to read our documentation to find how to recover your device iD on iOS or your A4SID on Android

  • Token is a unique ID that is sent by the application to the publisher's information system only after the mobile user has agreed to receive push notifications . it is mandatory to send push notification on iOS and Android.
  • Number of visits is the number of time the user visited the app since the SDK has been installed.
  • Install date is the real date of the first app opening in the device, even if the SDK has been installed in a later version.
  • Last opened is the date on which the application was last opened by the user.
  • Device Model is a field for the app user’s terminal type (e.g. iPhone, iPad, etc.).
  • OS Version is the operating system (OS) version of the user's device.
  • Language is the code language of the user's terminal as received by the application.
  • Bundle Version / Application version is the version of your application.
  • Latitude is the last known latitude position for the user (if the application provides feedback on the user’s position)
  • Longitude is the last known longitude position for the user (if the application provides feedback on the user’s position)
  • Altitude is the last known altitude of the app user (if the application provides feedback on the user’s position)
  • Geolocation date is the date of the last feedback received on its position (if the application provides feedback on the user’s position)
  • SDK Version is the Accengage SDK version in the app user’s application
  • Feedback corresponds to negatives returns when a push is sent. In 95% of the cases, this information implies that the app has been uninstalled by the user.  For the 5% remaining, the reason is unknown. When a user having feedbacks opens the app, the feedback counter is reset at zero.
  • Time Zone is the recent code of the time zone known for the mobile internet user (e.g. Europe/Paris)
  • System push optin field updated automatically by the SDK with the information as to whether or not the user accepts notifications. On Android, all users are optin by default.
  • Enabled push identifies whether the user has opted for notifications. This information may be updated by the application.
  • Enabled in app identifies whether or not the user has opted for in-app messages. Set to opt-in by default.
  • Random Id is a 8 figures decimal between 0 and 100 randomly attributed between all the profiles in the Database.

    The random Id is unique per user and the profiles are equally divided between 0 and 100. This field can be used to perform AB testing.

  • Country code is the device country code.

Creating a new field

  • Click on the menu Targeting > Database Scheme . The list of fields associated with your application by default will then appear.

  • To create a new field, click on the button “add a field ". You will be directed to the form below that should be filled. If you want to modify an existing field, click on the edit icon.

  • There is a type of syntax expected in your field. The syntax will be checked when you import it into your database and when a field is filled in within a form for example.
  • The date fields can target users depending on when their data was updated.
  • Max size: allows you to restrict values for entering or importing long messages
  • Enable message personalization with this criterion: if checked, this option enables you to personalize a message with user values recorded in the app's database table. For example, you can start a message by saluting targeted users with their first name.
  • Custom Geofence and Custom iBeacon: these checkboxes allow you to define if the field will be used to store geofence or ibeacon IDs (for example, user's favorite store, affiliated bank branch...). You can then create messages that can be set off by several geofences or ibeacons but only triggered on a geolocated point related to the user. When creating the field, you need to chose what type of ID will be stored : Accengage ID or your own "external" ID (please note that IDs stored in this field must already exist in the geofence or ibeacon database)