Amplitude
Send events and user identifications to Amplitude for behavioral analytics, and keep Amplitude behavioral cohorts in sync with your Zeotap audiences. Sync your warehouse data to enrich Amplitude user profiles, track events, and drive cohort membership.
Prerequisites
- An Amplitude account
- Your Amplitude project API key and Secret key
- For cohort syncs: your numeric Amplitude Project (App) ID and a valid Amplitude login email to own the cohort
Authentication
Amplitude uses API Key + Secret authentication.
- In Amplitude, go to Settings > Projects
- Select your project
- Copy the API Key and Secret Key
- Enter both values in Zeotap
The Secret Key is required for cohort syncs, which authenticate to the Cohort API with HTTP Basic auth.
Configuration
| Field | Type | Required | Description |
|---|---|---|---|
| Data Center | Select | Yes | Amplitude data center: United States or European Union. Default: US |
Target Settings
| Field | Type | Required | Description |
|---|---|---|---|
| Sync Type | Select | Yes | Type of data to send: Track Events, Identify Users, or Behavioral Cohort |
| Cohort ID Type | Select | Conditional | For Behavioral Cohort: which identifier keys the cohort — User ID (BY_USER_ID) or Amplitude ID (BY_AMP_ID) |
| Cohort Name | Text | Conditional | For Behavioral Cohort: the cohort to keep in sync. Reused if it already exists, created on the first sync |
| Project (App) ID | Text | Conditional | For Behavioral Cohort: the numeric Amplitude project ID that owns the cohort |
| Cohort Owner Email | Text | Conditional | For Behavioral Cohort: the Amplitude login email that owns the cohort |
| Publish Cohort | Toggle | No | For Behavioral Cohort: make the cohort discoverable to other users in Amplitude |
Supported Operations
Sync Modes: Upsert, Insert
Audience Sync Modes: Mirror
Amplitude cohorts are replace-only: every sync uploads the complete membership and replaces the cohort’s contents. Mirror is therefore the only audience sync mode — the cohort is kept identical to your Zeotap audience each run (members who leave the audience are removed from the cohort).
Features
- Field Mapping: Yes
- Schema Introspection: No
Required Mapping Fields
| Sync Type | Required Fields |
|---|---|
| Track Events | user_id, event_type |
| Identify Users | user_id |
| Behavioral Cohort (User ID) | user_id |
| Behavioral Cohort (Amplitude ID) | amplitude_id |
Default Destination Fields
Track Events: user_id, event_type, time, device_id, event_properties, user_properties, ip, platform, os_name
Identify Users: user_id, device_id, user_properties
Behavioral Cohort: user_id or amplitude_id (the identifier column that becomes the cohort membership)
How Cohort Sync Works
When you select Behavioral Cohort as the sync type, Zeotap:
- Resolves the cohort by name — it reuses an existing cohort with the configured name, or creates a new one on the first sync.
- Computes the complete current audience membership on every run and uploads it to Amplitude’s Cohort API, which replaces the cohort’s members with the uploaded set.
- Keys membership on
user_idoramplitude_id, according to the Cohort ID Type setting.
Because each sync sends the full membership, additions and removals are both reflected automatically — there is no separate add/remove operation. Cohort syncs run against Amplitude’s cohort hosts (amplitude.com for the US, analytics.eu.amplitude.com for the EU), which are distinct from the event-ingestion hosts.
If the audience becomes empty, Zeotap skips the upload rather than clearing the cohort — Amplitude does not accept an empty cohort upload, so the previous membership is left in place. To empty a cohort, archive or delete it in Amplitude directly.
Rate Limits
- A single cohort sync can upload up to 100,000 identifiers. Because a cohort sync is a single full-replace upload, audiences larger than this cannot be synced and the sync will report an error.
- Zeotap retries rate-limited requests automatically.
Best Practices
- Give each synced cohort a distinct, stable Cohort Name so Zeotap reuses the same cohort across runs instead of creating duplicates.
- Choose the Cohort ID Type that matches how your users are identified in Amplitude — use Amplitude ID only if your audience carries Amplitude’s internal id.
- Keep cohort audiences under the 100,000-identifier per-sync limit.
Troubleshooting
Invalid API credentials
Verify your API Key and Secret Key in Amplitude Settings > Projects. Ensure you are using the correct project. Cohort syncs require the Secret Key.
Events not appearing
Amplitude can take a few minutes to process incoming events. Check the Amplitude User Lookup to verify events are being received.
User properties not updating
When using Identify mode, user properties are set on the user profile. Ensure the user_id matches the existing Amplitude user.
Cohort not appearing in Amplitude
Confirm the Project (App) ID matches the project you are viewing and that the Cohort Owner Email is a valid user in that project. A newly created cohort appears under the owner’s cohorts; enable Publish Cohort to make it visible to others.
Audience too large
Cohort syncs are limited to 100,000 identifiers per run. Reduce the audience size (for example with a priority list or a tighter segment) to stay under the limit.
Members not matching
If the sync reports unmatched identifiers, verify the Cohort ID Type matches your mapped column — user_id values must map to User ID, and Amplitude IDs must map to Amplitude ID. Amplitude skips identifiers it cannot resolve.