Amplitude
Prerequisites
To set up the Amplitude source connector, you'll need your Amplitude API Key and Secret Key.
Tables in the Amplitude connector
Table: active_users
| No | Column Name | Type | Notes |
|---|
| 1 | date | VARCHAR | Incremental sync key, Primary Key |
| 2 | statistics | VARCHAR | |
Table: average_session_length
| No | Column Name | Type | Notes |
|---|
| 1 | date | VARCHAR | Incremental sync key, Primary Key |
| 2 | length | DOUBLE | |
Table: annotations
| No | Column Name | Type | Notes |
|---|
| 1 | date | VARCHAR | |
| 2 | details | VARCHAR | |
| 3 | id | INTEGER | Primary Key |
| 4 | label | VARCHAR | |
Table: events
| No | Column Name | Type | Notes |
|---|
| 1 | country | VARCHAR | |
| 2 | $schema | INTEGER | |
| 3 | data | VARCHAR | |
| 4 | device_type | VARCHAR | |
| 5 | language | VARCHAR | |
| 6 | device_carrier | VARCHAR | |
| 7 | uuid | VARCHAR | Primary Key |
| 8 | user_creation_time | VARCHAR | |
| 9 | location_lng | DOUBLE | |
| 10 | event_type | VARCHAR | |
| 11 | paying | BOOLEAN | |
| 12 | location_lat | DOUBLE | |
| 13 | app | INTEGER | |
| 14 | device_id | VARCHAR | |
| 15 | group_properties | VARCHAR | |
| 16 | idfa | VARCHAR | |
| 17 | server_upload_time | VARCHAR | |
| 18 | amplitude_attribution_ids | VARCHAR | |
| 19 | server_received_time | VARCHAR | |
| 20 | user_id | VARCHAR | |
| 21 | processed_time | VARCHAR | |
| 22 | amplitude_event_type | VARCHAR | |
| 23 | region | VARCHAR | |
| 24 | device_model | VARCHAR | |
| 25 | city | VARCHAR | |
| 26 | user_properties | VARCHAR | |
| 27 | start_version | VARCHAR | |
| 28 | is_attribution_event | BOOLEAN | |
| 29 | device_family | VARCHAR | |
| 30 | client_event_time | VARCHAR | |
| 31 | platform | VARCHAR | |
| 32 | device_manufacturer | VARCHAR | |
| 33 | library | VARCHAR | |
| 34 | adid | VARCHAR | |
| 35 | $insert_id | VARCHAR | |
| 36 | client_upload_time | VARCHAR | |
| 37 | event_properties | VARCHAR | |
| 38 | amplitude_id | INTEGER | |
| 39 | os_version | VARCHAR | |
| 40 | groups | VARCHAR | |
| 41 | session_id | DOUBLE | |
| 42 | ip_address | VARCHAR | |
| 43 | version_name | VARCHAR | |
| 44 | event_id | INTEGER | |
| 45 | sample_rate | VARCHAR | |
| 46 | device_brand | VARCHAR | |
| 47 | dma | VARCHAR | |
| 48 | os_name | VARCHAR | |
| 49 | event_time | VARCHAR | Incremental sync key |
Table: cohorts
| No | Column Name | Type | Notes |
|---|
| 1 | hidden | BOOLEAN | |
| 2 | description | VARCHAR | |
| 3 | finished | BOOLEAN | |
| 4 | owners | VARCHAR | |
| 5 | published | BOOLEAN | |
| 6 | type | VARCHAR | |
| 7 | is_official_content | BOOLEAN | |
| 8 | archived | BOOLEAN | |
| 9 | size | INTEGER | |
| 10 | is_predictive | BOOLEAN | |
| 11 | appId | INTEGER | |
| 12 | name | VARCHAR | |
| 13 | definition | VARCHAR | |
| 14 | id | VARCHAR | Primary Key |
| 15 | lastMod | INTEGER | |
| 16 | lastComputed | INTEGER | |
External Resources
Zipstack Cloud features a powerful SQL querying engine on top of many types of connectors, including those from Trino, some custom connectors and connectors from the open source Airbyte project. Some Zipstack cloud connectors are designed to utilize and expand upon Airbyte's connector protocol, but they do not use Airbyte's EL core. Additionally, some parts of the documentation for these connectors have been adapted from the connector documentation found in Airbyte's open source project.