Get Started with Unify
To get started with the Unify module, follow the step-by-step process outlined:Note:Ensure to obtain initial customer information as detailed in the Prerequisites section of `the Get Started Guide before getting started with Unify.
Step-by-Step Process
Step 1 - Source Creation:
To get started with Zeotap CDP, begin by creating a new source in the Sources module. You must also select a source category and source type that align with your specific needs and create the source accordingly. For more information about how to create sources for different categories, refer here.
Step 2 - Source Implementation:
Once the source is created, proceed with its implementation. Refer to the step-by-step instructions provided in the Implementation guide tailored to the chosen Source Type. You can download this document from the IMPLEMENTATION DETAILS tab of the source that you created.

Step 3 - Previewing Data:
After implementation, you can examine the data that has been received into the system under the PREVIEW DATA tab. Note that once the data starts flowing into the system, the status of the source changes to Integrated.

Note:If no data is ingested, then a message stating “We haven’t received any data yet. please check again later and ensure that thesource is implemented correctly. In case of any issues, contact support@zeotap.com” message appears on the screen.
Step 4 - Catalogue Mapping:
This is the stage in which you can standardise the incoming data to a single organisational-level catalogue by mapping and applying the required data transformations. Ensure that your ingested data such as identifiers, traits, consent, events and more are appropriately mapped against the fields available in the Zeotap catalogue. This ensures the structuring the data flow efficiently. You can map the ingested fields to the Catalogue fields by clicking MAP TO CATALOGUE under CATALOGUE MAPPING. For more information about the types of data that you can map and for detailed steps of mapping, refer here.

Note:You can only map a source that has moved to the Integrated state. Once the mapping is successfully done,then the Source transitions to Mapped state. Post this state, the file/data dropped against this sources will be resolved and ingested into your Zeotap system.
Step 5 - Create Calculated Attributes:
This step allows you to derive user-level insights by aggregating your users’ isolated actions. You can then use this data to create more powerful customer cohorts. As a marketer, you can use calculated attributes to create new attributes for a user by aggregating their event data over a specific time period. For example, 
90_day_revenue of a user, 1_week_page_views to check the engagement of a user, units_purchased by a user for a specific category like T-shirts. These calculated attributes are used as segmenting criteria and can then be forwarded to different integrations. For example, in a workflow, you can define High Spenders as users with 90_day_revenue > €500 or Low Engagement Users by putting 1_week_page_views < 5 criteria. For more information about Calculated Attributes, refer here.
Related Topics
- For information about how to configure the ID Strategy, refer here.
- For information about the data entities supported by the system, refer here.
- For information about how to map the Catalogue, refer here.
- For information about how to add a Catalogue field, refer here.
- For information about the enrichers supported and how to configure them, refer here.
- For information about how to work with the Calculated Attributes, refer here.
Non-Customer Entity Data (NCE) Related Topics
- For information on creating the Non-Customer Entity (NCE) sources from the Zeotap CDP App, refer here. Note that you can create an NCE source for the source types: Flat Files, Server to Server, CRM Data, and Data Warehouse.
- For information about the Non-Customer Entity Data (NCE) data, refer here.
- For information about how to map the Catalogue for Non-Customer Entity (NCE) data, refer here.
- For information about how to add a Non-Customer Entity (NCE) attribute, refer here.
- For information about Join Key Enricher and how to configure it, refer here.