# Amplitude (v1) Information note **Amplitude is supported by the Singer community** This integration is powered by [Singer's](https://www.singer.io/) Amplitude tap. For support, [visit the GitHub repo](https://github.com/singer-io/tap-amplitude) or [join the Singer Slack](https://singer-slackin.herokuapp.com/). ## Amplitude integration summary Stitch’s Amplitude integration relies on the Amplitude [Query product add-on](https://help.qlik.com/en-US/stitch/integrations/saas/amplitude#setup-requirements), which utilizes a Snowflake database to store data. Amplitude integrations can replicate event and merged user ID data. Refer to the [Schema](https://help.qlik.com/en-US/stitch/integrations/saas/amplitude#schema) section for more info. ## Amplitude feature snapshot A high-level look at Stitch's Amplitude (v1) integration, including release status, useful links, and the features supported in Stitch. | **STITCH** | | | | | --- | --- | --- | --- | | **[Release status](https://help.qlik.com/en-US/stitch/integrations/identify-an-integration-version)** | Released on August 29, 2018 | **Supported by**

the Info icon

Indicates if the integration is supported by Stitch or the Singer community. | [Singer Community](https://www.singer.io/) | | **Stitch plan**

the Info icon

The type of Stitch plan required to use the integration. | Standard | **[API availability](https://help.qlik.com/en-US/stitch/developers/stitch-connect/guides/source-destination-reference)**

the Info icon

Indicates if the integration is available as a source in Stitch Connect. | the Success icon

This version of the integration is available via the API.


Available | | **Singer GitHub repository** | [singer-io/tap-amplitude](https://github.com/singer-io/tap-amplitude) | | | | **REPLICATION SETTINGS** | | | | | **[Anchor Scheduling](https://help.qlik.com/en-US/stitch/replication/replication-scheduling/anchor-scheduling)**

the Info icon

A type of replication scheduling where an integration's Replication Frequency is anchored to a time you select. | the Success icon

This feature is supported for this version of the integration.


Supported | **[Advanced Scheduling](https://help.qlik.com/en-US/stitch/replication/replication-scheduling/advanced-scheduling)**

the Info icon

A type of replication scheduling that allows you to specify granular start times for data extraction using cron expressions. | the Success icon

This feature is supported for this version of the integration.


Supported | | **Table-level reset**

the Info icon

Indicates if data can be reset at the table level. If unsupported, data can only be reset at the integration level. | the Remove icon

Table-level resets are not supported for this integration. Resets are only supported at the integration level.


Unsupported | **[Configurable Replication Methods](https://help.qlik.com/en-US/stitch/replication/replication-methods)**

the Info icon

Indicates if Replication Methods can be defined by you for tables in the integration. | the Remove icon

Configurable Replication Methods are not supported for this integration. Stitch will use pre-defined replication methods for tables you set to replicate.


Unsupported | | **DATA SELECTION** | | | | | **Table selection**

the Info icon

The ability to select individual tables for replication in the Stitch interface. If table selection is unavailable, all tables and all the columns they contain will be set to replicate by default. | the Success icon

This feature is supported for this version of the integration.


Supported | **Column selection**

the Info icon

The ability to select individual columns for replication in the Stitch interface. If column selection is unavailable, all columns will be set to replicate by default. | the Success icon

This feature is supported for this version of the integration.


Supported | | **Select all**

the Info icon

Indicates if the integration supports selecting all available tables and columns. | the Success icon

Supported


Supported | | | | **TRANSPARENCY** | | | | | **[Extraction Logs](https://help.qlik.com/en-US/stitch/replication/extractions/integration-extraction-logs)**

the Info icon

Logs detailing the Extraction phase of the replication process for a given integration. Includes error info, should an error occur. | the Success icon

This feature is supported for this version of the integration.


Supported | **[Loading Reports](https://help.qlik.com/en-US/stitch/replication/integration-loading-reports)**

the Info icon

Reports detailing the Loading phase of the replication process for a given integration. Includes the number of rows loaded for each table and error info, should an error occur. | the Success icon

This feature is supported for this version of the integration.


Supported | ## Connecting Amplitude ### Amplitude setup requirements To set up Amplitude in Stitch, you need: * **To be on an Amplitude Enterprise or Growth plan**. Amplitude requires this to access the Query product add-on. * **To have purchased the Amplitude Query product add-on.** [Query](https://amplitude.zendesk.com/hc/en-us/articles/115001902492-Query-Snowflake) is an Amplitude-managed Snowflake database, which Stitch’s integration replicates data from. ### Step 1: Retrieve your Snowflake credentials Stitch’s Amplitude integration connects to your Amplitude-managed Snowflake database to replicate data. To connect Stitch to Amplitude, you’ll need to retrieve your Snowflake credentials from Amplitude. Reach out to [Amplitude support](https://amplitude.zendesk.com/hc/en-us/requests/new) or your Amplitude Success Manager to get your credentials. When you receive your credentials, you can move onto the next step. ### Step 2: Add Amplitude as a Stitch data source 1. [Sign into your Stitch account](https://app.stitchdata.com/). 2. On the Stitch Dashboard page, click the **Add Integration** button. 3. Click the **Amplitude** icon. 4. Enter a name for the integration. This is the name that will display on the Stitch Dashboard for the integration; it’ll also be used to create the schema in your destination. For example, the name “Stitch Amplitude” would create a schema called `stitch_amplitude` in the destination. **Note**: Schema names cannot be changed after you save the integration. 5. In the **Amplitude Snowflake Username** field, enter your Snowflake username. 6. In the **Amplitude Snowflake Password** field, enter the Snowflake user’s password. 7. In the **Amplitude Snowflake Account** field, enter the Snowflake account. 8. In the **Amplitude Snowflake Warehouse** field, enter the name of the Snowflake warehouse. 9. In the **Amplitude Snowflake Database** field, enter the name of the Snowflake database. ### Step 3: Create a replication schedule Information note Replication schedules affect the time Extraction begins, not the time to data loaded. Refer to the [Replication Scheduling](https://help.qlik.com/en-US/stitch/replication/replication-scheduling) documentation for more information. In the **Replication Frequency** section, you’ll create the integration’s [replication schedule](https://help.qlik.com/en-US/stitch/replication/replication-scheduling). An integration’s replication schedule determines how often Stitch runs a replication job, and the time that job begins. Amplitude integrations support the following replication scheduling methods: * [Replication Frequency](https://help.qlik.com/en-US/stitch/replication/replication-scheduling/replication-frequency) * [Anchor Scheduling](https://help.qlik.com/en-US/stitch/replication/replication-scheduling/anchor-scheduling) * [Advanced Scheduling using Cron](https://help.qlik.com/en-US/stitch/replication/replication-scheduling/advanced-scheduling) (Advanced or Premium plans only) To keep your row usage low, consider setting the integration to replicate less frequently. See the [Understanding and Reducing Your Row Usage guide](https://help.qlik.com/en-US/stitch/getting-started/understanding-stitch-usage) for tips on reducing your usage. ### Initial and historical replication jobs After you finish setting up Amplitude, its **Sync Status** may show as **Pending** on either the Stitch Dashboard or in the Integration Details page. For a new integration, a **Pending** status indicates that Stitch is in the process of scheduling the initial replication job for the integration. **This may take some time to complete.** Information note **Initial replication jobs with Anchor Scheduling** If using Anchor Scheduling, an initial replication job may not kick off immediately. This depends on the selected Replication Frequency and Anchor Time. Refer to the [Anchor Scheduling](https://help.qlik.com/en-US/stitch/replication/replication-scheduling#job-scheduling-and-anchor-times) documentation for more information. #### Free historical data loads The first seven days of replication, beginning when data is first replicated, are free. Rows replicated from the new integration during this time won’t count towards your quota. Stitch offers this as a way of testing new integrations, measuring usage, and ensuring historical data volumes don’t quickly consume your quota. Information note **Replication will continue after the seven days are over**. If you’re no longer interested in this source, be sure to **pause** or **delete** the integration to prevent unwanted usage. ## Amplitude table reference Information note **Schemas and versioning** Schemas and naming conventions can change from version to version, so we recommend verifying your integration’s version before continuing. The schema and info displayed below is for **version 1** of this integration. This is the latest version of the Amplitude integration. Stitch’s Amplitude replicates two types of tables: Events and merged user IDs. For each project in your Amplitude account, a set of these tables will be available for replication. Stitch will append a project’s ID to each table name to make them easily identifiable. For example: If a project has an ID of `168342`, the events table for the project will be named `events_168432`. You can identify which tables are for a specific project by comparing the ID in the table name to the projects in your Amplitude account. You can access this page in your Amplitude account by clicking the **User menu (top right corner) > Settings > Projects**. ![Highlighted project ID field in the Amplitude UI](https://help.qlik.com/en-US/stitch/images/integrations/amplitude-project-id.png)Highlighted project ID field in the Amplitude UIHighlighted project ID field in the Amplitude UI Information note **Table and column names in your destination** Depending on your destination, table and column names may not appear as they are outlined below. For example: Object names are lowercased in Redshift (`CusTomERs` > `customers`), while case is maintained in PostgreSQL destinations (`CusTomERs` > `CusTomERs`). Refer to the [Loading Guide](https://help.qlik.com/en-US/stitch/replication/loading/destination-guides) for your destination for more info. ### events `events_[project_id]` tables contain info about the events logged in your Amplitude projects. **Note**: Each event table will have the project ID appended. For example: If a project has an ID of `168342`, the events table for the project will be named `events_168432`. | **Replication Method [](https://help.qlik.com/en-US/stitch/replication/replication-methods)[the Info icon](https://help.qlik.com/en-US/stitch/replication/replication-methods)[](https://help.qlik.com/en-US/stitch/replication/replication-methods)** | Key-based Incremental | | --- | --- | | **Primary Key ![](https://help.qlik.com/en-US/stitch/images/replication/primary-key-icon.svg)** | uuid | | **Replication Key ![](https://help.qlik.com/en-US/stitch/images/replication/replication-key-icon.svg)** | event\_time | | **Useful links** | [Amplitude documentation](https://amplitude.zendesk.com/hc/en-us/articles/115001902492-Query-Snowflake#column-schema "Opens in new tab: Amplitude documentation") | events table schema | **adid**


STRING | | --- | | **amplitude\_event\_type**


STRING | | **amplitude\_id**


NUMBER | | **app**


NUMBER | | **city**


STRING | | **client\_event\_time**


DATE-TIME | | **client\_upload\_time**


DATE-TIME | | **country**


STRING | | **data**


STRING | | **device\_brand**


STRING | | **device\_carrier**


STRING | | **device\_family**


STRING | | **device\_id**


STRING | | **device\_manufacturer**


STRING | | **device\_model**


STRING | | **device\_type**


STRING | | **dma**


STRING | | **event\_id**


NUMBER | | **event\_properties**


STRING | | **event\_time**


DATE-TIME | | **event\_type**


STRING | | **followed\_an\_identity**


BOOLEAN | | **groups**


STRING | | **idfa**


STRING | | **ip\_address**


STRING | | **location\_lat**


NUMBER | | **location\_lng**


NUMBER | | **os\_name**


STRING | | **os\_version**


STRING | | **paying**


STRING | | **region**


STRING | | **server\_upload\_time**


DATE-TIME | | **session\_id**


NUMBER | | **start\_version**


STRING | | **user\_creation\_time**


DATE-TIME | | **user\_id**


STRING | | **user\_properties**


STRING | | **uuid**


STRING | | **version\_name**


STRING | ### merge\_ids `merge_ids_[project_id]` tables contain info about merged users. These are users whose records have been merged with other user records to eliminate duplicates. For example: If an anonymous user logs events anonymously before signing in, they will go from being anonymous to a recognized user. Without merging the user’s records, it’ll look like two users with two sets of events, rather than one user completing a series of events. For more info on how Amplitude handles merging users, [refer to their documentation](https://amplitude.zendesk.com/hc/en-us/articles/115003135607). **Note**: Each table will have the project ID appended. For example: If a project has an ID of `168342`, the merged ID table for the project will be named `merge_ids_168432`. | **Replication Method [](https://help.qlik.com/en-US/stitch/replication/replication-methods)[the Info icon](https://help.qlik.com/en-US/stitch/replication/replication-methods)[](https://help.qlik.com/en-US/stitch/replication/replication-methods)** | Key-based Incremental | | --- | --- | | **Primary Keys ![](https://help.qlik.com/en-US/stitch/images/replication/primary-key-icon.svg)** | amplitude\_id

merge\_server\_time

merged\_amplitude\_id

merge\_event\_time | | **Replication Key ![](https://help.qlik.com/en-US/stitch/images/replication/replication-key-icon.svg)** | merge\_event\_time | | **Useful links** | [Amplitude documentation](https://amplitude.zendesk.com/hc/en-us/articles/115001902492-Query-Snowflake#column-schema "Opens in new tab: Amplitude documentation") | merge\_ids table schema | **amplitude\_id**


NUMBER | | --- | | **merge\_event\_time**


DATE-TIME | | **merge\_server\_time**


DATE-TIME | | **merged\_amplitude\_id**


NUMBER |