| Column Name | Description (EN) | Values | Type | Nullable | Default Value for Not Nullable Columns |
|---|---|---|---|---|---|
| contact_key | It is the unique identifier of each contact. It must be the same as the contact_key sent within the SDK. | text | NO | ||
| contact_status | Indicates whether a contact is active or passive. Any contact who is Passive cannot be communicated via any channel. | A:Active P:Passive | text | NO | A |
| Email address information | text | NO | Empty Text | ||
| email_permission | Email channel permission | true/false | boolean | NO | true |
| email_status | Information about whether the email address is valid or not. Apart from the initial import, this information is updated by Dengage according to the return from ISPs for emails sent to the email address. For email addresses that spam clicks or gets hard bounce, this field is updated as Passive. | A:Active P:Passive | text | NO | A |
| email_status_reason | In case the email address is not valid, the information about why it is invalid is updated by Dengage with the data received from the ISP. | HB:Hard Bounce SB:Soft Bounce US:Unsubscribe | text | YES | |
| is_email_active | It is updated by Dengage to distinguish between those who are actively reading email and those who are not. | boolean | YES | ||
| is_email_engaged | It is updated by Dengage to distinguish between those who actively click on the email and those who do not. | boolean | YES | ||
| gsm | It should be sent in the format of gsm number - 905351234567. | Phone | NO | Empty Text | |
| gsm_permission | Communication permission status for the SMS channel | true/false | boolean | NO | true |
| gsm_status | Information about whether the GSM number is valid or not. This information is received from the aggregator that sends SMS and updated by Dengage. | A:Active P:Passive | text | NO | A |
| gsm_status_reason | In case the email gsm number is not valid, the information about why it is invalid is updated by Dengage with the data received from the vendor. | text | YES | ||
| name | Contact's name information | text | NO | Empty Text | |
| surname | Contact's surname information | text | NO | Empty Text | |
| gender | Gender information | text | NO | Empty Text | |
| birth_date | Birthday information | YYYY-AA-GG | date | YES | |
| segment | If there is a segment in which the contact is included, it can be shared | text | NO | Empty Text | |
| source | Source information where the contact is registered | text | NO | Empty Text | |
| subscription_date | Registration date of the contact | date | NO | 0001-01-01 | |
| created_at | the date of registration of a contact in the master_contact table. It is filled by dengage. | date & time | NO | Current Date | |
| created_by | information about which method the contact came to the master_contact table. It is filled by Dengage | text | NO | 0 | |
| updated_at | the date of updating any information about a contact to the master_contact table.It is filled by Dengage. | date & time | NO | Current Date | |
| updated_by | information about which method a contact was updated to the master_contact table. It is filled by Dengage. | text | NO | 0 | |
| gsm_consent_date | Only required for Turkish companies | İYS formatında | date & time | YES | |
| email_consent_date | Only required for Turkish companies | İYS formatında | date & time | YES | |
| gsm_source | Only required for Turkish companies | İYS formatında | text | YES | |
| email_source | Only required for Turkish companies | İYS formatında | text | YES | |
| contact_type | Only required for Turkish companies | İYS formatında | text | YES | |
| rfm_score | Information about the RFM Score where the contact is located as a result of Dengage RFM scoring.It is filled in by Dengage only on accounts that receive RFM scoring service. | integer | YES | ||
| rfm_segment | Information about the RFM Segment where the contact is located as a result of Dengage RFM scoring.It is filled in by Dengage only on accounts that receive RFM scoring service. | text | YES | ||
| rfm_mobile_score | Mobile score information of the contact as a result of Dengage RFM scoring. It is filled in by Dengage only on accounts that receive RFM scoring service. | integer | YES | ||
| rfm_mobile_segment | Information about the Mobile RFM Segment where the contact is located as a result of Dengage RFM scoring. It is filled in by Dengage only on accounts that receive RFM scoring service. | text | YES | ||
| language | Language information of the contact | In the format given here: https://dev.dengage.com/reference/supported-language-codes | text | YES | |
| email_permission_reason | The reason for closing the permission that unsubscribe contacts will transmit via the Custom unsubscribe page is written by Dengage. | text | YES | ||
| gsm_permission_reason | The reason for closing the permission that unsubscribe contacts will transmit via the Custom unsubscribe page is written by Dengage. | text | YES | ||
| timezone | This column is required for the Blackout feature. | in postgre sql format: ie. Turkey, Europe/Vienna | text | YES | |
| whatsapp_number | It should be sent in the format of gsm number that your sms vendor supports. | For Karix, the allowed format is: COUNTRYCODE + MOBILE NUMBER Example: 971xxxxxxxxx (UAE è 12 digits – 971[country code] + xxxxxxxxx [9-digit mobile number]) | Phone | NO | Empty Text |
| whatsapp_permission | Communication permission status for the Whatsapp channel | boolean | boolean | NO | true |
| whatsapp_status | Information about whether the GSM number is valid or not. This information must be received from the aggregator that sends Whatsapp and updated in the table. | text | text | NO | A |
| country | Country information of the contact. | in postgre sql format: ie. Turkey, Europe/Vienna | text | YES | |
| is_online | This is a system field created for tracking online & offline customers. It is updated by Denge when "online-offline mapping" is used. For online customers, this field should be "TRUE". | boolean | boolean | NO | true |
| is_offline | This is a system field created for tracking online & offline customers. It is updated by Denge when "online-offline mapping" is used. For offline customers, this field should be "TRUE". | boolean | boolean | NO | false |