Develop a schema document with transformation requirements
Define the data model
Define the sensitivity of the data
Establish Time-To-Live strategy
Define the granular consent fields
Provide sample files for testing
Finalise the Enrichers to use
Develop a schema document with transformation requirements
Ensure that you develop a for each source, along with the following details: A schema document is a structured document that outlines the format, structure, and specifications of data within a dataset. In the context of your requirement, it serves as a comprehensive guide for handling data transformation needs.- Confirm the presence of at least one ID, Consent and Country field.
- Explicitly map incoming fields to the corresponding Zeotap Catalogue field in the schema document.
- Specify consent details, considering the customer’s desired consent type, applicable channels and the creation of custom consent fields if the source lacks an explicit consent field.
- When no specific consent field exists, consider the entire dataset as consented for all purposes.
Define the data model
Define the consolidated data model obtained during the discovery stage, covering event, profile and other custom attributes.Define the sensitivity of the data
Specify the sensitivity of data, including Personally Identifiable Information (PII) and other sensitive data. PII and sensitive data are masked within the product and Special Personally Identifiable Information (SPII) data must be classified as PII data.Establish Time-to-Live (TTL) strategy
Establish the strategy for both and IDs. Time-to-Live (TTL) is a strategy that defines the lifespan or expiration period of data within a system. It specifies the duration for which data, particularly identifiers (IDs), remains valid and accessible. The TTL strategy is crucial for managing data freshness, security, and compliance with privacy regulations.Persistent IDs typically have a longer TTL, often set to “Forever.” These identifiers, like customer-specific IDs, are meant to persist indefinitely.Non-persistent IDs, on the other hand, have a defined TTL after which they expire. This duration is determined by the TTL strategy and ensures that outdated or irrelevant data is not retained unnecessarily.Define the granular consent fields
Define the Granular Consent fields for each source along with the following details:- Identify the attributes denoting consent.
- Determine the customer’s desired consent type.
- Define the applicable channels for consent. In cases where the source lacks an explicit consent field, establish a custom consent field and generate a hardcoded or derived enricher. If no specific consent field exists, the platform considers the complete data as consented for all purposes.