Get prioritised list of use cases for using Zeotap CDP
Get prioritised list of Sources to integrate with Zeotap CDP
Get prioritised list of Destinations to target your customers
Gather use cases for Profile API
Gather use cases for Calculated Attributes
Gather use cases for Journeys
Other general requirements
Get prioritised list of use cases for using Zeotap CDP
Obtain a prioritised list of use cases that your customers intend to address using Zeotap CDP. This helps you to align the integration with their specific needs and objectives. For each use case, ensure to map out the Source, Destination and establish clear timelines for when they plan to employ them. This level of detail ensures that the integration is precisely tailored to their requirements. For information about some of the real-time use cases that we have solved through Zeotap CDP, refer here.Get prioritised list of Sources to integrate with Zeotap CDP
Obtain the prioritised list of Sources, which you wish to integrate with Zeotap CDP for transferring your customer data. In addition, ensure that you have the following details readily available regarding the Source Integration:- Data model - Ensure that you have clearly defined the fields that you wish to send to Zeotap through source integration.
- Onboarding Format - Specify the preferred method for onboarding, such as Flat file, API, Data warehouse, SDK, or other applicable formats.
- Managing Deltas - Verify that customers adhere to the practice of sending only delta updates, especially when utilizing Flat Files or establishing configurations within DB tables. This ensures the efficient and incremental transfer of data, minimising redundancy.
Get prioritised list of Destinations to target your customers
Obtain the prioritised list of Destinations to concentrate your marketing efforts on targeting specific customer cohorts. In addition, ensure that you have the following details readily available regarding the Destination Integration:- Credentials of the Platforms - Secure the necessary credentials for the identified Platforms. To understand the difference between Platforms and Destinations, refer here.
- Use Cases to be Activated- Be clear about the use cases to be activated on the Destinations. For example, suppression, creating look-a-likes in the platforms and more.
-
Preferred Output Data Fields - Define the preferred output identifiers for each platform. For example, for Facebook -
emails,MAIDs, or both; for Braze -First name,Last name,email,Braze IDand so on.
Gather use cases for Profile API
You can use our Profile API to read, write and delete the user profiles from the Zeotap system. Ensure that you have the following details readily available for for effective use of our Profile API:- Identify Data for Profile API - Specify the data intended for utilisation through the Profile API, such as segment membership or other profile attributes. Note that event data is not supported through Profile API.
- Delete API Caller - Clearly define the caller of the Delete API and the responsible system or individual for the Delete API operation.
For more information about Profile API, use cases for Profile API, workflow of the API, endpoint, best practices and more, refer here.
Gather use cases for Calculated Attributes
For Calculate Attributes, identify the use case and possible conditions that you want to achieve.- For example, create a lead score for routing the leads to specific sales representatives.
- For example, to show a welcome back banner to people who did not login in the last 7 days, pre-create a Calculated Attribute counting
last_7_days_login. - To target a customer when they are viewing a product they have been most engaged with, pre-create a Calculated Attribute tracking
most_viewed_productin the last 3 days.
Calculated Attributes are computed daily and exclusively supported for events data.
Gather use cases for Journeys
For you to be able to use Journeys and create workflows, ensure the following:- You have a real-time streaming source created in Sources.
- You have mapped the streaming source in your Catalogue.
A workflow runs on the Event Name and other attributes that are mapped in the Catalogue. Hence, ensure that the above points are taken care of.
Other general requirements
Below are the general requirements that can be considered during Discovery:- Collect your precise Country/Region requirements.
- Inform that default support for the EU is available; approval is required in the contract for other regions in terms of Data Residency.