- Distil.ai Datasets
- Bringing in your data
- Database Sync
- Deploy Tracking
Customer data definition
Customers are at the core of the work that you do within Distil.ai. As such the Customer dataset is the most important dataset.
The table below defines the standard set of Customer Attributes in Distil. Distil.ai provides multiple methods to bring this dataset in. These are detailed in Database Sync, Tracking and Integrations.
Each Integration and database will come with its own unique set of Customer attributes. Where possible these are mapped to those listed in the table below. Any that are not able to be mapped, likely because they are unique to the third-party platform or your business, are stored in the Custom Attributes section, where you can store up to 1,000 unique attributes.
|Attribute Friendly Name||Attribute Database Name||Data Type||Used in Customer Identity Resolution||Description|
|Customer Id||id||Text||Yes||Your unique Customer Identifier.|
|First Name||first_name||Text||Yes||The Customer’s first name|
|Last Name||last_name||Text||Yes||The Customer’s last name|
|Email Address||email_address||Text||Yes||The Customer’s email address|
|Mobile Phone Number||mobile_phone_no||Text||Yes||The customer’s mobile phone number|
|GDPR Status – Marketing Subscribed||gdpr_status_subscribed||Boolean|
(True / False)
|True/false indicating if the Customer has consented to receiving marketing communications|
|GDPR Status – Right of Access Requested||gdpr_status_right_of_access_requested||Boolean(True / False)||True/false indicating if the Customer has requested to see their data.|
|GDPR Status – Anonymise Data||gdpr_status_anonymise_data||Boolean(True / False)||This value is used to indicate if this Customer wishes their data to be Deleted. If this is True no personal information will be stored against this customer, no matter what is passed through. Any historic data will also be anonymised|
|Facebook Slug||facebook_slug||Text||The unique part of the Facebook URL to see the customer’s Facebook profile, i.e. https://facebook.com/[SLUG]|
|Twitter Handle||twitter_handle||Text||The Customer’s twitter handle; i.e. @DistilAi|
|Instagram Handle||instagram_handle||Text||The Customer’s Instagram handle.|
|LinkedIn Slug||linkedin_slug||Text||The unique part of the LinkedIn URL to see the customer’s LinkedIn Profile, i.e. The customer’s LinkedIn slug, i.e. https://linkedin.com/[SLUG]|
|Postal Address Line 1||postal_address_line_1||Text||The Customer’s most recent postal address.|
|Postal Address Line 2||postal_address_line_2||Text|
|Postal Address Town||postal_address_town||Text|
|Postal Address Region||postal_address_region||Text|
|Postal Address Country||postal_address_country||Text|
|Postal Address Postcode||postal_address_postal_code||Text|
|Billing Address Line 1||billing_address_line_1||Text||The Customer’s most recent billing address|
|Billing Address Line 2||billing_address_line_2||Text|
|Billing Address Town||billing_address_town||Text|
|Billing Address Region||billing_address_region||Text|
|Billing Address Country||billing_address_country||Text|
|Billing Address Postcode||billing_address_postal_code||Text|
These are additional attributes that you may wish to store against your Customer records. For instance, this is where any data you bring in from a third-party system or your backend database will be stored that cannot be mapped directly to one of the attributes listed above.
- Demographics Profile: This Enrichment uses the Customer’s Postal and Billing Address to create profiles based on socio-economic markers and spending behaviour.