Versions Compared

Key

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

...

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.

Note: A mobile number is required using e164 must use the E.164 format. E.164 is the official format for all international phone numbers that includes a plus sign followed by the country code and phone number.

For example:

  • U.S.: +12135551234
  • U.K.: +442135551234

...

Data Element

Type

Description

person_id

String

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

external_person_id

String

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

Person identifiers that are canonical in external systems can be assigned to Person resources in the "external_person_id" field. Any string value can be assigned as the external person id. If the external_person_id value contains non-URL-safe characters, they must be encoded if used in the URL.

mobile_phone

Object

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

mobile_phone.mdn

String

The Mobile Directory Number (a number that can be dialed). Must It must be in e164 E.164 format, for example: +12195551234.

mobile_phone.carrier_code

String

The Cellular Carrier associated with this mobile number.

custom_fields

Object

Additional Field Types like String, Date, Single-Selection, and Multi-Selection.

...