Amplitude Connector
Connector status: Planned Not built yet. Tajo does not run this connector today.
Illustration · sample data
Sync example
Source
Amplitude
Connector status: Planned
Destination
Your other tool
Connector status: Custom tool
Field mapping
| Source field | Destination field | Sample value |
|---|---|---|
record.id | source_id | record_1042 |
record.updated_at | updated_at | 2026-10-18T08:00:00Z |
record.value | value | sample_value |
- Draft
- Review one record
- Approve this version
Statuses describe individual connectors; they do not guarantee this sync is ready. Illustrative fields. Review the actual schema and permissions before a sync runs.
Tajo does not run a Amplitude connector today. Early code exists, but it has not been run against a live Amplitude account and syncs nothing yet.
What exists so far
- Reads users through User Search, behavioural cohorts and the project’s event types.
Planned, not built
- Event forwarding
- Cohorts as contact lists
- User properties as contact attributes
Open-Source Implementation Map
No official open-source repository was found in the current Tajo connector catalog for Amplitude. Keep this page focused on the verified public API contract and vendor documentation until an official schema, SDK, MCP server, or public integration repository is available.
Tajo Revamp Checklist
- Verify authentication and scope requirements against the vendor documentation before each connector release.
- Document primary sync objects, external IDs, pagination strategy, and rate limits explicitly.
- Add smoke tests from public API examples rather than undocumented behavior.
- Capture webhook signature verification and replay protection when the vendor supports webhooks.
- Record gaps where no official public repository or schema exists so future maintainers know what still needs source-backed validation.