When you merge contacts in the mobile app-enabled database, the system retains the mobile app message (also known as mobile push) consent status of a contact’s mobile push ID.

You can currently merge up to three contact records into one record. If the master record has the same mobile push ID as a losing record, the consent state from the losing record is merged into the winning record. In all variations of merging up to three recipients, if the mobile push ID that is in the winning record, then we will retain its consent status on the record that is in opted-in or opted-out state.

Before you begin

Here's a list of requirements to meet before you can view the consent status of a contact:

• Your organization has enabled mobile app messages.
• You (or another user) has access to mobile app messages.
• Use a flexible (non-keyed) database that is mobile-enabled and has a mobile push ID custom field.
• Multiple contacts are entered into the database.

Procedure

Complete these steps:

1. In Data, select your mobile-enabled database.
2. Click Search.
3. Click Find duplicate contacts.
4. Choose how you want to find your duplicate records and click Find. For example, you can choose the Mobile user ID field.
5. Check the boxes to select the contact records you would like to merge. Then click the Merge link to review how these records will merge together.
6. After the data job is complete, all consent data that was with the losing records will be deleted.

Common scenarios

You may experience the following scenarios that affect a contact's consent status.

Scenario 1: The master record has to include the Mobile User ID with an opted-in or opted-out status for consent to follow it.

Using the example below, if Contact 2 or Contact 3 have the same Mobile User ID, but is opted-in or opted-out of the mobile app, then the consent for the mobile app will be added or merged into the master record and vice versa for Opted-out status.

Note: The Mobile User IDs are the same. The Email fields may contain different email addresses. 

Scenario 2: If the master record does not contain the Mobile Push ID with consent, then the consent data will not be merged into the master record.

Using the example below, if the records that are being merged together have different mobile user IDs, then the winning mobile user ID is selected. If it is the mobile-enabled ID field, consent will follow.

Note: The mobile user IDs are different. The Email fields contain the same email addresses.