Contact Data Usage
This document should list all the places where contact data is used in mobile. It should also include a description of how the data is used and where the relevant code is.
Creating Contacts
Anonymous Contacts
Anonymous contacts are created by the Mobile Engage platform when a client registers. The client is identified by the client-id, which is a unique identifier for the device. Anonymous contacts are used to track user behavior and interactions with the application without requiring any personal information from the user.
Updating Contacts
Reading Contacts
Resolving Anonymous Contacts
When a client registers, the Mobile Engage platform resolves the anonymous contact associated with the client-id. This process involves checking if the client-id already exists in the system and linking it to the corresponding anonymous contact. If no matching contact is found, a new anonymous contact is created.
Resolving Identified Contacts
When a client registers, the Mobile Engage platform resolves the identified contact associated with the external-id. This process involves checking if the external-id already exists in the system and linking it to the corresponding identified contact.
Resolving Contacts by Email for In-app test messages
When sending a test-message in In-app the user enters an email adress which is resolved to the contact id. This is done by the contact service and the result is sent back to the in-app service.
Get Contact by Email in Push Service
For the UI to show the contact data of a user identified by email, the push service needs to resolve the contact id from the email address. This is done by the contact service and the result is sent back to the push service.
Get Contacts of a Contact-list in Push Service
For the UI to show the contacts inside a contact-list, the push service fetches the contact-ids from the contact-list service and then resolves the contact data from the contact service by the id.