Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 56 Next »

A Person entity is an identified entity that has interacted with or been loaded into the Mobile Database. It is identified by a person_id, which uniquely identifies the record, or an external_person_id, which is a unique identifier from the customer system for reference and cross-linking.

A Person can also be tracked/linked by a Mobile Directory Number (MDN). This alternate identifier is sufficient in the short-term, but it is not an ideal long-term identification method because mobile numbers can be changed, returned, ported, and recycled.

Associating Person Records

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 system in any sequence/order. The following logic ensures that if the records exist in more than one place, the same Person entity gets tied together to avoid inadvertently linking two different people:

  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 the same Person entity. If the carrier_code does not match, then they will be assumed to be different people.

Note: Since phone numbers often get ported and/or recycled, and to ensure Mobile Marketing Association (MMA) compliance, it is not a valid assumption that carrier changes are made to the same person.

Person Entity

The following is the JSON representation of a Person entity within the APIs.

            "name":"My Hardware Store"
            "name":"Local Grocery"


Data Element





Vibes unique identifier for each Person record in the Mobile Database.



Customer unique identifier for a Person in the Mobile Database. This value is optional, but if specified, must be unique within the Mobile Database.



Object representation of a Person's mobile phone. A Person can have only one active Mobile Phone at a time.



The Mobile Directory Number (a number that can be dialed).



The Cellular Carrier associated with this Mobile number. Please see #TBD for a list of valid Carrier Codes.




Custom Field Types

Field Type

Value Representation






Object with :id and :name.


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

otherNew data types will be added in the future.
  • No labels