Zeotap
This integration is currently in beta. Contact your MetaRouter support team to get started.
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.
What are the benefits of integrating MetaRouter with Zeotap?
- Streamlined Data Transfer: Sends organized event data directly to Zeotap for efficient processing.
- Enhanced Security: Encodes credentials for secure data transmission.
- Flexible Data Handling: Flattens complex data structures for easier management and analysis.
Capabilities and Considerations
- 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.
Getting Started - From Your Zeotap Account
- Create a Server-to-Server Source:
- Refer to the Zeotap documentation for detailed instructions on how to create a "Server-to-Server Source."
- Access Implementation Details:
- Once the source is created, locate the Implementation Details tab within Zeotap CDP.
- This tab contains essential configuration information for your integration.
- Locate API URL & Writekey:
- Copy the API URL provided, which will be used as the endpoint for data transmission.
- Find the Writekey and copy it, as this will be required for authorization during data transfer.
Getting Started - From Your MetaRouter Account
Adding 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. |
Event Mappings
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.
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 - timestamp (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', etc. | 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. | N/A - Expression (split context.locale) |
Flattened context | Object: Flattens the context object up to a depth of 5 levels, prefixing keys with 'context_'. | context |
Flattened traits | Object: Flattens the user traits object for better mapping. | traits |
Flattened properties | Object: Flattens the properties object for more detailed event data mapping. | properties |
Recommended Identifiers
These identifiers are recommended to 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 | 12345abcde | No |
| anonymous_id | 123e4567-e89b-12d3-a456-426614174000 | No |
Additional Zeotap Documentation
Zeotap - Implement Server-to-Server Source
Updated about 1 month ago