Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


A Person entity is an identified entity that has interacted with or been loaded into the Mobile Database. It is identified by a PersonIDperson_id, which uniquely identifies the record. A customer can choose to also define an alternateexternal_person_id, which would be a unique identify from the customer's system for reference and cross-linking.

A person can also be tracked/linked by a Phone Number mobile number (MDN). This alternate identifier is usually sufficient in the short-term but is not an ideal identification long-term as Phone Numbers mobile numbers can be changed, returned, ported and recycled.


Because of the dynamic nature of mobile participation and campaigns, it is possible that person records could exist in either the Mobile Database or the Customer's system in any sequence/order. To do the best we can at trying to ensure the same person gets tied together as well as to avoid inadvertantly and avoid inadvertently linking two different people, the our primary emphasis will always be is on not inadvertently linking two separate people. To meet that, the following logic will apply:

  1. The person_id and external_person_id columns are always treated as the same person record , and must be unique (the external_person_id can be omitted if it is not used/exist).
  2. If the MDN and carrier_code match an existing person record, they will be considered to be the same Person entity. If the carrier_code does not match, then they will be assumed to be different people (since phone numbers get ported and/or recycled, and to ensure MMA compliance, it is not a valid assumption that carrier changes are always the same person).


Field Type

Value Representation






Object with :id and :name


An array of Objects, with each Object having the content of a Single Select