Merge Profiles

Overview

Engage supports multiple channels for contacting users, such as mobile number, email address, and mobile app alias. To ensure accurate communication and consistent data, Engage merges different contact profiles into a single unified profile whenever it identifies that the channel-specific data belongs to the same individual.

This merging process helps avoid duplicate profiles, ensures compliance with opt-in regulations, and enables efficient multi-channel marketing.

Key Characteristics

• Each contact in Engage should have only one profile, regardless of the number of communication channels used.

• Engage uses a designated attribute to identify and merge duplicate profiles.

• Available merging attributes:

  • user['Identifier'] (recommended)

  • user['Email']

  • user['MobileNumber']

  • user['FaxNumber'] (used as mobile app alias)

• A consistent, unique identifier must be transferred across all channels to support merging.

• Using system-wide selections can bypass opt-in validation, risking unwanted communication. Use dedicated groups for email and SMS sendouts.

Advanced Configuration

Choosing a Merging Attribute

• If your app allows usage without registration:

  • Use user['Identifier'] or user['FaxNumber'] (mobile app alias).

• If app registration is required:

  • Any attribute containing address data can be used.

• Make sure your SDK integration includes the merging attribute as an alias.

Transferring the Merging Attribute

• Always transfer the merging attribute value when known.

• For user['Email'], ensure the email is sent with mobile data upon subscription.

• For user['Identifier'], set up CRM processes to transfer the ID during email/mobile app registration.

Behavior and Impact

• Engage merges incoming data based on the selected attribute:

  • If a matching identifier exists, new data is added to the profile.

  • If not, a new profile is created.

• Missing merging values lead to duplicate or incomplete profiles.

• The merging process requires upfront data hygiene and consistent value forwarding.

Example Scenario

1. A user installs your app from the Google Play Store.

2. Engage creates a new contact profile using minimal data for push notifications.

3. If the app later transmits a merging attribute (e.g., CRM ID), Engage updates the existing profile or merges it with a matching one.

4. The result is one profile combining mobile, email, and SMS data.

Important Considerations

• Avoid creating duplicate contacts by ensuring merging attributes are filled before adding new mobile app users.

• Notify Mapp of your chosen merging attribute.

• An incomplete setup may require manual cleanup, risking data loss.