Sprig

Sync user attributes and events to Sprig for in-product research and surveys. Zeotap keeps your Sprig user profiles enriched with the latest warehouse data so you can target the right users for studies and surveys.

Prerequisites

• A Sprig account (Starter plan or above)
• A Sprig API key with Admin or Developer role permissions
• HTTPS access to api.sprig.com

Permissions

To generate an API key, you need Admin or Developer role access in Sprig. API keys are scoped to a specific environment (Production or Development).

Authentication

Sprig uses API Key authentication.

1. Log in to your Sprig dashboard
2. Navigate to Settings > API Keys
3. Click Generate API Key (or copy an existing key)
4. Select the environment that matches your intended use (Production or Development)
5. Copy the API key and paste it into Zeotap

Configuration

Supported Operations

Sync Modes

Audience Sync Modes

Sprig does not support audience/list membership management. Use standard sync modes to enrich user profiles.

Features

• Field Mapping: Yes
• Schema Introspection: No

Required Mapping Fields

Default Destination Fields

How It Works

1. Zeotap reads rows from your warehouse model or audience
2. Each row is sent as an individual user upsert to the Sprig Users API (POST /v2/users)
3. The userId and emailAddress fields are mapped to top-level Sprig fields
4. All other mapped fields are sent as user attributes in the attributes object
5. Sprig returns 202 Accepted for each successful upsert
6. Failed rows are retried up to 3 times with exponential backoff

Attribute Limits

Sprig allows up to 100 attribute values per user. If you are syncing many fields, ensure the total attribute count stays within this limit.

Events

Events included via the API are for historical tracking purposes only and will not trigger in-product studies through the Sprig SDK. To trigger studies based on events, use the Sprig JavaScript or mobile SDK directly.

Rate Limits

Zeotap automatically retries requests that receive 429 Too Many Requests responses with exponential backoff.

Best Practices

• Match user IDs: Ensure the userId you sync from Zeotap matches the user ID set in the Sprig SDK on your website or app. Mismatched IDs create duplicate user profiles.
• Use Production keys for production syncs: Keep Development API keys for testing only. Data sent with a Development key is isolated from production.
• Keep attributes under 100: Sprig limits users to 100 attribute values. Map only the fields you need for targeting studies.
• Sync incrementally: Use the Upsert sync mode to update only changed records rather than re-sending your entire user base each time.

Troubleshooting

Invalid API key

Verify your API key in Sprig under Settings > API Keys. Ensure the key matches the environment (Production or Development) selected in Zeotap.

Users not appearing in Sprig

Sprig may take a few minutes to process incoming user data. Check the Sprig People tab to confirm users are being received. Ensure the userId field is mapped and contains non-empty values.

Attributes not updating

Confirm that the total number of attributes per user does not exceed 100. Attributes beyond this limit may be silently dropped.

422 Unprocessable Entity errors

This typically means the request body is malformed. Ensure that userId is mapped to a non-empty string value. Check your field mappings for any null or invalid data types.

Connection timeout

Sprig’s API requires HTTPS. Verify that your network allows outbound HTTPS connections to api.sprig.com. Large syncs may also hit request timeouts — Zeotap retries these automatically.

Rate limit errors (429)

If you are on a Starter or Free plan, you may hit lower rate limits. Zeotap retries 429 responses automatically with backoff. For high-volume syncs, contact Sprig support about Enterprise rate limits.