Overview:: Mobile Engage glossary

An Emarsys-generated token used to authenticate Mobile Engage requests. The application password is available on the App details page on the Apps tab.

The version number of your app. We store the version in the major/minor/patch format and these values are available for segmentation using the greater than option.

A JSON object representing a pairing between Emarsys contact data fields and data provided by the mobile app.

A unique numeric identifier of a contact in the Emarsys database.

An event in Mobile Engage is a message, sent from the mobile app. It consists of information about the device, the app and a certain operation completed in the app.

A unique string to identify the device. (IDFA/IDFV on iOS and ANDROID_ID on Android. We use IDFA as default, but when ad tracking is limited and IDFA is not available, we fall back on IDFV).

The hardware IDs are stored in the Mobile Engage database. In addition to that, the hardware IDs of devices connected to anonymous contacts are also stored in the contact database, but hardware IDs of devices connected to known contacts are not available in the contact database.

If the appLogin call contains the contact_field_id and contact_field_value keys, Mobile Engage connects the Emarsys contacts to the devices. Also, if the hardware_id is known, the individual push tokens can be searched for at the Users menu item on the Apps tab of the Mobile Engage interface.

This stores the app installs of Emarsys contacts. It consists of the Emarsys contact_id, the application_id, the hardware_id and the push_token.

We also store device-level information in this database, such as:

• platform
• language
• timezone
• device_model
• application_version
• os_version

The operating system version reported by the platform. We store the version in the major/minor/patch format and these values are available for segmentation using the greater than option.

The overall name of the device platform, currently iOS or Android. Please note that the values should be in lower case in the call.

The name of the push services provider used to deliver messages to devices. Previously, Emarsys used a third-party provider to deliver push messages but now it is directly connected to Google or Apple. 

A unique token, often referred to as “device token”, generated by Google or Apple, linked to an app where push notifications have been accepted.

The push tokens are stored in the Mobile Engage database, which means that they are not available in any contact fields of the Emarsys database. If the appLogin call contains the contact_field_id and contact_field_value keys, Mobile Engage connects the Emarsys contacts to the devices.

Also, if the hardware_id is known, the individual push tokens can be searched for at the Users menu item on the Apps tab of the Mobile Engage interface.

Please note that push messages can only be sent if there is a valid push token for them.

A unique campaign number generated by Emarsys and automatically included in every message from the campaign, including the test messages. This parameter is automatically extracted from the push message and sent to Mobile Engage once the user opens the message and our SDK is integrated.

A set of rules, applied when an anonymous contact – an active user of an app – is replaced by an authenticated user. A field should be defined with the information used for identifying users. You must use a hashed version of the user_id in the customer’s own system.