How Mobile Push works

The following is the process for mobile push:

  • The contact installs your mobile app.

  • When the contact launches the app, a dedicated event (called SetInfo) is automatically called in the SDK, and device-related data is sent (device token, device ID, platform, etc.) and stored in a dedicated Engage Device List.

    Note: There is one Device List per app in Marigold Engage.

  • When the contact registers in the app, a check is done on the email address to verify if the contact already exists in a linked Audience List.

    • If the contact is found, the USER_ID in the Device List gets updated (pointing to the contact found).
    • If the contact is not found, a record is created in the Audience List (storing at least their email address) and the USER_ID in the Device List gets updated (pointing to the new contact).

      • Note: Registration is not mandatory, but allows to identify the device and link it to a contact.

  • When the contact logs in to the application, the linked Audience List is updated with any additional information such as email, language, gender, etc.

    In addition, the contact’s status as logged in/out and registered/unregistered is also stored in the Device List.

    Note: This data comes from the 'login'/'register' event called in the SDK. By default, the mobile platform can fill two optional fields ('registered' and 'logged') which will be updated depending on the 'login'/'logout' and 'register'/'unregister' SDK methods if triggered by the app.

  • If multiple contacts use the same device :
    - When a first contact logs into the app, the device is linked to the contact's record.
    - When a second contact logs into the app on the same device, the device is then linked to the second contact.

    Note: This behavior also applies to the 'register' event. The device ID is always associated with the ID of the contact who most recently used the app (whether it's through a register or a login event).

  • After the contact has installed the app and exists in Engage’s Device List, dedicated mobile content can be created and used in a journey (single batch or transactional) to send the contact push notifications.

  • When the push notification is delivered, opened or clicked, this information is stored.

Please consult the following document for more information on mobile integration.