Amplitude
Version LATEST
Checkout the API docs here for more information
Set up
Enter your API key into the username text area. Enter your Secret Key into the password text area.
To find these credentials, please follow these instructions.
Features
| Feature | Support | Notes |
|---|---|---|
| Backfill | ℹ️ | The kleene connector only supports 24 hours of backfill, however, you can export backfill data directly into your filestore or warehouse here. |
| Incremental | ✅ | |
| Custom backfill | ℹ️ | See above |
| API reliability | 🟢 | Reliable |
Reports detail
| ⬇️ Report | 🔑 Incremental key | 🔑 Primary key | 📄 Link to API endpoint |
|---|---|---|---|
| Incremental | server_upload_time | insert_Id | https://developers.amplitude.com/docs/export-api |
| Incremental filtered by event type | server_upload_time | insert_Id | https://developers.amplitude.com/docs/export-api |
Limitations
Incremental filtered by event typereport limitations
- Matching is exact and case-sensitive.
viewed pagewill not matchViewed page. A mistyped name silently keeps that event out of your warehouse while the others continue to load — nothing fails and no warning is raised.- Filters the
EVENT_TYPEcolumn, notAMPLITUDE_EVENT_TYPE.- Event names containing a comma cannot be configured, as the comma separates entries.
The field cannot be left blank. An empty Event Types list fails the run rather than loading every event.- Best suited to events that occur regularly. The connector resumes from the most recent event in your destination table. If none of your chosen events occur for an extended period, each run re-checks a progressively longer window — no data is lost, but runs become slower and can go beyond the size limit the API allows
- The table layout is identical to the standard incremental extract; only rows are reduced
Updated 9 days ago
Did this page help you?
