In the Normalized datalayer interface, you will be able to define the schema of your data.
Adding event specifications allows you to define the payload and what is expected, so that you can see if the data is meeting those specifications, in case there are any errors.
Then, in the Source data quality view, you are able to see the summary of all specification violations, so that you fix it at your source or with the live Data Cleansing feature
Write your event specifications
The schema of standard events is already defined, but you can modify it by adding more properties (standard or custom properties).
You can create custom properties and add it to your event specification.
- String: most used type, it corresponds to a text format (ex: name = 'ABC')
- Number: corresponds to a number (float, entire) (ex: value = '12')
- Boolean: the property can take only 2 values, true or false (ex: paid = 'true')
- Object: corresponds to an array of values (ex: items = shirt, pant, shoes)
- Default (simple value): most used structure, corresponds to a single value. (ex: name = 'ABC')
- List (array of values): list of all values on the property (ex: items = shirt, pant, pant)
- Set (array of unique values): list of unique values (ex: items = shirt, pant)
You can define your property as 'Personal Identifiable Information (PII)', meaning this property contains personal information that could identify a user (email address, postal address, Customer ID...).
If this option is set to true, the property will be considered as PII.
If this property is stored and set as PII, it will be automatically encrypted in AES-256 before being written to the database.