Rudderstack

Send identify, track, group, page, and screen calls to Rudderstack via the HTTP Tracking API. Use Zeotap to push warehouse data into your Rudderstack pipeline for downstream activation.

Prerequisites

• A Rudderstack account (Cloud or self-hosted)
• A Rudderstack source with an HTTP API type
• The source Write Key from your Rudderstack dashboard
• Your Data Plane URL (found in Settings in the Rudderstack dashboard)

Authentication

Rudderstack uses Write Key authentication (Basic auth).

1. In your Rudderstack dashboard, go to Sources
2. Create or select an HTTP API source
3. Copy the Write Key from the source settings
4. Paste it into the Write Key field in Zeotap

Configuration

Target Settings

Supported Operations

Sync Modes

Audience Sync Modes

Features

• Field Mapping: Yes
• Schema Introspection: No

Required Mapping Fields

Default Destination Fields

Identify: user_id, anonymous_id, email, name, phone

Track: user_id, event, properties, timestamp

Group: user_id, group_id, traits

Page: user_id, page_name, page_category, url

Screen: user_id, screen_name

How It Works

1. Zeotap reads rows from your warehouse model
2. Each row is transformed into a Rudderstack API message (identify, track, group, page, or screen) based on the configured event type
3. Messages are sent in batches of up to 500 per request to the /v1/batch endpoint
4. Rudderstack routes the data to all connected downstream destinations

All remaining mapped fields that are not standard Rudderstack fields (like user_id or event) are placed into traits (for identify/group calls) or properties (for track/page/screen calls).

Rate Limits

• Rudderstack Cloud Free: 1,000 events per minute
• Rudderstack Cloud Pro/Enterprise: No event volume limit
• Self-hosted: No event volume limit
• Per-request size: 4 MB maximum per batch, 32 KB per individual event

Zeotap batches events into chunks of 500 and uses automatic retry with exponential backoff for rate limit (429) and server errors (5xx).

Best Practices

• Use Identify calls to update user profiles and traits in downstream tools
• Use Track calls to send behavioral events for analytics and activation
• Map the anonymous_id field alongside user_id when you need to merge anonymous and known user activity
• Keep individual event payloads small (under 32 KB) to avoid rejection
• For high-volume syncs on Rudderstack Cloud Free, consider scheduling syncs during off-peak hours

Troubleshooting

Invalid Write Key

Ensure the Write Key is from a valid Rudderstack HTTP API source. The source must be enabled and not deleted. You can verify the key in Sources > [Your Source] > Settings.

Connection failed: cannot reach data plane URL

Verify that the Data Plane URL is correct and accessible. For Rudderstack Cloud, the URL looks like https://hosted.rudderlabs.com or a custom subdomain. For self-hosted installations, ensure the data plane is running and the URL is publicly reachable.

Events not appearing in downstream destinations

1. Check the Rudderstack Live Events tab in the dashboard for incoming events
2. Verify that downstream destinations are connected and enabled on the source
3. Check destination-specific connection settings and credentials in Rudderstack

429 Too Many Requests errors

You are exceeding the rate limit for your Rudderstack plan. Reduce the sync frequency, lower the batch size, or upgrade your Rudderstack plan.

Events rejected with 400 Bad Request

The batch payload exceeds the 4 MB limit or an individual event exceeds 32 KB. Reduce the number of mapped fields or split large JSON payloads.

Wrong event type

If data appears in Rudderstack but not in the expected format, verify the Event Type setting matches your use case. For example, use Identify for user profile updates and Track for behavioral events.