Logo Help Portal
  • Getting Started

    Introduction

    • Onboarding overview
    • Project Initiation
    • Email compliance
    • Account Administration

    Data

    • Data exchange
    • Data onboarding
    • Web data collection
    • Strategic Platform Integrations

    Channels

    • Email onboarding
    • Smart Insight
    • Predict
  • Training

    Resources

    • Introduction
    • Online Self-learning
    • Onboarding Videos

    Events

    • Instructor-led Training
    • Webinars
    • Seminars
    • Training Calendar
  • User Guides

    Strategy

    • Personalization
    • Automation
    • Data Monitoring

    Channels

    • Email
    • Mobile Apps
    • Web
    • Ads
    • SMS

    Add-ons

    • Smart Insight
    • Predict
    • Incentive Recommendation
    • AIM
    • Relational Data
  • News & Support
    Forrester Wave CCCM (Independent Platforms) Report Q4 2019

    News

    • What’s New in the Emarsys Platform
    • Updates from the CSA
    • Pilot-Features
    • Articles on Data Protection and GDPR

    Support

    • Help and Support at Emarsys
    • Managing your user profile
    • Preparing for Black Friday 2019
    • Black Friday 2019 - Best practices
  • |
  • Partners

    Enhance Partners

    • Getting Started as an Emarsys Partner
    • The Emarsys Integration Platform
    • Automation Center Integrations
  • Developers
  • System Status
Need help?
English Deutsch Español Français Русский Türkçe 简体中文 Test New Chat
Sign in
  • Mobile Apps
  • Mobile Engage
  • 0 Mobile Apps Mobile Engage

In this section:

  • Overview:: Mobile Engage - Overview
  • Overview:: The Mobile Engage data flow model
  • The Mobile Engage SDK
  • Getting started:: Importing previous push audiences to Mobile Engage
  • End-user guides:: Mobile Engage - End-user guide
  • End-user guides:: Mobile Engage - Advanced features
  • Getting started:: Creating a trackable deep link for mobile in email
  • Getting started:: Obtaining certifications and tokens for sending push messages
  • Overview:: Mobile Engage glossary
  • End-user guides:: Mobile Engage - Android Oreo Notification Channels
  • See more
EDIT
Expand all

Overview:: Mobile Engage glossary

Updated: November 12, 2019 01:00
115002683429
Overview:: Mobile Engage glossary

The following list contains the most frequently used expressions in Mobile Engage.

Application password

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

Application version

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.

Emarsys contact field/custom field

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

Emarsys contact ID

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

Event

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.

Hardware ID

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.

Mobile Engage database

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

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.

Platform

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

Push provider

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. 

Push token

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.

Sid

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.

Merge by field

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. 

Please note that this process is not supported after October 19, 2016.

Was this article helpful?

Have more questions? Submit a request
Return to top

Emarsys is a Leader

You may also be interested in:

Related articles

  • The Mobile Engage SDK
  • End-user guides:: Mobile Engage - Advanced features
  • Troubleshooting:: Mobile Engage - Undelivered push error messages
  • End-user guides:: Mobile Engage - Android Oreo Notification Channels
  • The Mobile Engage API
Copyright © 2019 Emarsys eMarketing Systems. All rights reserved
Legal Notice Privacy Policy Master Services Agreement Anti-spam Policy