What Is Zeotap?

Zeotap is a customer intelligence platform that helps brands understand and engage their customers more effectively. It combines first-party customer data with third-party data to create a comprehensive view of users, enabling precise targeting and personalized marketing campaigns. The platform also emphasizes privacy compliance, offering secure and GDPR-compliant data management solutions. Zeotap supports various marketing use cases like customer segmentation, campaign optimization, and identity resolution, making it a valuable tool for data-driven marketing.

Product Type: Customer Data Platform
Integration Type: Starter Kit
Event Source Type: Web
Event Scope: Full-Funnel Events

Capabilities

Data Integration & Enrichment: The integration supports ingesting and enriching first-party data, allowing you to enhance customer profiles by combining various first-party attributes such as behavior, demographics, and transaction history.
Customer 360° View: This integration facilitates the transfer of first-party data to Zeotap, where the data is used to build unified customer profiles. While the integration does not create customer profiles directly, it enables Zeotap to centralize customer attributes and interactions, allowing for personalized engagement within the Zeotap platform.
Privacy Compliance: Zeotap's infrastructure ensures that server-to-server data transmission adheres to GDPR and other privacy regulations, making it suitable for handling sensitive first-party data.

Limitations

Predictive Audiences: This integration may have limited support for building expansive lookalike models, as these often depend on third-party data, which is not available in this setup.
Omnichannel Journey Orchestration: Real-time coordination of customer journeys across channels is not feasible with server-to-server ingestion.
Locale Mapping: The default configuration maps the country value from context.locale by splitting it at the dash (e.g., en-GB maps to GB). This approach provides a default value but may not always align with the intended country (e.g., en-GB might map to GB when it should be RO). Since the standard AJS schema does not include a dedicated country field, customers are encouraged to update this mapping based on their data. If customers have access to country data in properties.country, they can map the value directly to ensure accuracy.

Starter Kit Setup Guide

1. Gather Credentials

Create a Server-to-Server Source in Zeotap, following their documentation.
In the source's Implementation Details tab, copy the API URL (used as the endpoint) and the Writekey (used for authorization).

2. Add a Zeotap Integration

From the integration library, add a Zeotap integration. Then, fill out the Connection Parameters:

Connection Parameter	Description
`API_URL`	API URL of your server-to-server source in Zeotap.
`WRITE_KEY`	Writekey of your server-to-server source in Zeotap.

3. Configure Event Mapping

MetaRouter provides all of the event mappings that Zeotap integrations typically require. You may add custom events, parameters, or mappings in accordance with Zeotap's API documentation.

4. Deploy to Pipeline

In the Pipelines tab, add your Zeotap integration.
Select the correct integration revision.
Click Add Integration to finalize deployment.

Event Mappings

Global

Global mappings will be applied to all events. If your parameter names do not match the Expected Inputs provided, you will need to overwrite the Inputs provided with your own.

Output Key	Description	Expected Input
`event_timestamp`	Integer: Represents the time the event occurred, captured in milliseconds.	Enrichment – event timestamp in milliseconds
`id`	String: Unique identifier for each event.	`messageId`
`user_id`	String: Identifies a known user interacting with the event.	`userId`
`previous_id`	String: Represents the previous identifier, used for user ID resolution.	`previousId`
`anonymous_id`	String: Temporary identifier for anonymous users.	`anonymousId`
`received_at`	String (ISO-8601): Timestamp indicating when the event was received.	`receivedAt`
`sent_at`	String (ISO-8601): Timestamp indicating when the event was sent.	`sentAt`
`integrations`	Object: Specifies integration settings for the event.	`integrations`
`type`	String: Specifies the type of event, e.g., `track`, `identify`.	`type`
`event`	String: Name of the event triggered by the user.	`event`
`name`	String: Name of the event or user trait.	`name`
`category`	String: Category to which the event belongs, useful for grouping events.	`category`
`_titleHash`	String (MD5): MD5 hash of the event's title, used for deduplication.	`properties.title`
`context_country`	String: A default value derived from `context.locale` by splitting at the dash (e.g., en-GB → GB), which customers can change per use case.	Expression – uppercased country from `context.locale`
`context_*`	Object: Fields within `context` flattened (up to 5 levels) with a `context_` prefix.	Spread – flattens `context` with a `context` prefix
`traits_*`	Object: Fields within `traits` flattened with a `traits_` prefix.	Spread – flattens `traits` with a `traits` prefix
`properties_*`	Object: Fields within `properties` flattened with a `properties_` prefix.	Spread – flattens `properties` with a `properties` prefix

Required & Recommended Identifiers

These identifiers must be mapped to Zeotap in order for successful user matching to occur. Without these IDs, any events sent to Zeotap may not be accurately reflected in reporting. For your convenience, recommended IDs are mapped as Global parameters to ensure they are added to every event.

Attribute	Example	Sync Injector Required?
`user_id` Recommended	`12345abcde`	No
`anonymous_id` Recommended	`123e4567-e89b-12d3-a456-426614174000`	No

Integration Validation

Coordinate with your Zeotap representative, or use the Zeotap CDP dashboard, to confirm that events are being received and processed correctly on their backend.