The Profile record is the core data object of the Customer Data Platform (CDP) component of he Omneo CX Suite. As such many other Omneo data tables link to the Profile record by using the `profileId` as a foreign key to reference the Profile including :
Profile Attribute Tables
- Addresses
- Aggregations
- Attributes (Appearance)
- Attributes (Comms)
- Identities
- Statuses
- Tags
Activity Tables
- Audits
- Interactions
- Ledgers
- Transactions
- Ratings
Incentive Tables
- Achievement History
- Achievement Levels
- Benefits
- Points
- Redemptions
- Rewards
- Tiers
Below are the default Profile fields that can be used to store attributes of a Member. Additional custom fields can be created & associated with a Profile. Read our Profile API documentation here.
| Field | Description | |
| Id | A unique identifier assigned automatically upon record creation by Omneo. [String, system-generated] e.g. 8ad465ea-4b2c-4d2a-bace-87b3a45f76a1 |
|
| Title | Alpha-numeric field to record the Profile's title. [String, nullable] e.g. MR, MRS, MISS, MASTER, DR, etc |
|
| First Name | Alpha-numeric field to record the Profiles first name [String, required] e.g. Megan |
|
| Last Name | Alpha-numeric field to record the Profiles last name [String, required] e.g. Jones |
|
| Gender | Defined set of values to record the Profiles gender, namely MALE, FEMALE, WITHHELD or OTHER. [Enum, nullable] |
|
| Alpha-numeric field to record the Profiles unique email address. No Profile may have the same email address as another. [String, required, unique] e.g. megan@gmail.com |
||
| Mobile Phone | Alpha-numeric field to record Profiles mobile phone number in E.164 format. No Profile may have the same email address as another. [String, required, unique] e.g. +61412374263 |
|
| Secondary Phone | Alpha-numeric field to record Profiles secondary phone number in E.164 format format. [String, required, unique] e.g. +61299784317 |
|
| Birth Day | Numeric field to record the calendar day of month of the Profiles date of birth. [Integer, nullable] e.g. 15 |
|
| Birth Month | Numeric field to record the calendar month of year of the Profiles date of birth. [Integer, nullable] e.g. 9 |
|
| Birth Year | Numeric field to record the year of the Profiles date of birth. [Integer, nullable] e.g. 1984 |
|
| Next Birthday | Omneo constructs & maintains the full next birthday anniversary. [Date, system generated] e.g. 1984-09-15 |
|
| Company | Alpha-numeric field to record the business name that the Profile is associated with. [String, nullable] e.g. Megan's Wedding Photography |
|
| Occupation | Alpha-numeric field to record the occupation of the Profile. [String, nullable] e.g. Photographer |
|
| Avatar URL | A full URL reference to an image avatar for the Profile. [String, nullable] e.g. https://encrypted-tbn0.gstatic.com/images?q=tbn:ANd9GcTyS3j0nqwRfeWF1kysGh0N-DnDmMvsmUUIBhKsbMOmGJtg-CXK |
|
| Currency | The Profiles currency in ISO 4217 format which is utilised to convert foreign financial activities (transaction, reward, redemptions, etc) back to this defined currency. If the currency is not defined when the record is created then a default Tenant value is inserted. [String, nullable] e.g. AUD |
|
| Preferred Location ID | The Profiles preferred location/store as defined by user input/API (user-defined). [Integer, foreign key (Locations table)] e.g. 122 |
|
| Join Location ID | The location/store where the Profile joined/signed up. [Integer, foreign key (Locations table)] e.g. 87 |
|
| Joined At | The UTC date & time the Profile was created is ISO 8601 format. If a value is not defined when the record is created then this field defaults to the Created At timestamp. [Timestamp, nullable] e.g. 2018-07-03 05:02:13 |
|
| Created At | The UTC date & time the Profile record was last updated in ISO 8601 format. [Timestamp, system generated] e.g. 2018-07-03 05:02:13 |
|
| Updated At | The UTC date & time the Profile record was last updated in ISO 8601 format. [Timestamp, system generated] e.g. 2002-01-31 13:43:41 |
| Status | A Status is a label that can be applied to a customer profile based on particular attributes such as “Staff”, “Stylist” or “Influencer” See explainer here. [String, nullable] | |
| Tags | Tags can be used to assign a shared term or attribute to a profile.[String, nullable] e.g. “Christmas campaign” or “handle with care” or “green”. |