User Interviews
User research recruiting and participant management platform. Zeotap syncs participant profiles to User Interviews Research Hub via the Participants Batch API, keeping your research panel up to date with the latest customer data for streamlined recruitment.
Prerequisites
- A User Interviews Research Hub account
- API access enabled for your account (contact api@userinterviews.com or your Customer Success Manager)
- An API key generated from your User Interviews account
Authentication
User Interviews uses API Key authentication.
- Contact your User Interviews Customer Success Manager or email api@userinterviews.com to request API access
- Once approved, you will receive your API key
- In Zeotap, navigate to Destinations > Add Destination > User Interviews
- Paste the API key into the API Key field
Configuration
The User Interviews destination does not require any non-credential configuration — all syncs target the User Interviews Hub API production endpoint.
Supported Operations
Sync Modes
| Mode | Supported |
|---|---|
| Upsert | Yes |
| Insert | Yes |
| Update | Yes |
| Mirror | — |
Audience Sync Modes
| Mode | Supported |
|---|---|
| Add | — |
| Upsert | — |
| Remove | — |
| Mirror | — |
Features
- Field Mapping: Yes
- Schema Introspection: No
Required Mapping Fields
| Field | Description |
|---|---|
| Participant email address. Used as the matching key for upsert and update operations. |
Default Destination Fields
| Field | Type |
|---|---|
| string | |
| first_name | string |
| last_name | string |
| phone_number | string |
| title | string |
| company | string |
| city | string |
| state | string |
| country | string |
How It Works
Zeotap sends participant data to User Interviews using the Participants Batch API (PATCH /api/participants/batches). Participants are chunked into batches of up to 100 per request.
Upsert
Creates new participants or updates existing ones matched by email address. All mapped fields are included in the participant payload. This is the recommended mode for keeping your Research Hub panel in sync with your customer data.
Insert
Creates new participant records only. User Interviews automatically generates identifiers for new records. Email matching is not required in insert mode, though providing email is recommended for deduplication.
Update
Updates existing participant records matched by email address. Only participants with a matching email in Research Hub are updated. Rows without a matching participant are skipped.
Rate Limits
The User Interviews API enforces rate limits on batch operations. Zeotap uses a conservative batch size of 100 participants per request and handles 429 Too Many Requests responses with automatic exponential backoff and retry.
Best Practices
- Validate your sync configuration against a small test model before running a full panel sync
- Use Upsert mode to keep participant profiles continuously updated as customer data changes
- Map as many demographic and firmographic fields as possible to improve recruitment targeting in Research Hub
- Ensure email addresses are valid and properly formatted — User Interviews rejects entire batches containing invalid participants
- Use Zeotap models to filter participants to only those eligible for research recruitment
Troubleshooting
Entire batch rejected
User Interviews counts all participants in a batch as rejected if the request contains a single invalid participant. Check that all email addresses are valid and that required fields are populated. Review the sync error log for specific rejection reasons.
Authentication failed
Verify that your API key is correct and has not been revoked. API keys are issued by User Interviews directly — contact api@userinterviews.com if you need a new key.
Participants not appearing in Research Hub
Confirm the sync completed successfully in Zeotap and that the mapped email addresses match the participants you expect. Newly upserted records may take a short time to appear in the Research Hub UI after the API response is returned.
Update mode skipping all rows
In Update mode, participants are matched by email address. If no matching participants exist in Research Hub, all rows are skipped. Switch to Upsert mode to create new participants automatically.
Rate limit errors
If you see 429 Too Many Requests errors, Zeotap automatically retries with exponential backoff. For very large syncs, consider reducing sync frequency or splitting your model into smaller segments.
Field values not updating
Verify that your model column data types match the expected types in User Interviews. String fields should contain text values, and phone numbers should be formatted consistently. Check the field mapping configuration in your sync settings.