Amplitude Analytics

Last updated on Jun 15, 2023

Amplitude Analytics helps generate thorough product analytics of web and mobile application usages to help you make data driven decisions. You can replicate data from your Amplitude account to a database, data warehouse, or file storage system using Hevo Pipelines.

Note: Hevo fetches data from Amplitude Analytics in a zipped folder to perform the data query.

For creating Pipelines using this Source, Hevo provides you a fully managed BigQuery data warehouse as a possible Destination. This option remains available till the time you set up your first BigQuery Destination irrespective of any other Destinations that you may have. With the managed warehouse, you are only charged the cost that Hevo incurs for your project in Google BigQuery. The invoice is generated at the end of each month and payment is recovered as per the payment instrument you have set up. You can now create your Pipeline and directly start analyzing your Source data. Read Hevo Managed Google BigQuery.


  • There is a two hour delay in the data exported from Amplitude Analytics getting loaded into your data warehouse.

    For example, data sent between 8-9 PM begins to load at 9 PM and becomes available in your Destination after 11 PM, depending on the load frequency you have set.

Revision History

Refer to the following table for the list of key updates made to this page:

Date Release Description of Change
Apr-04-2023 NA Updated section, Configuring Amplitude Analytics as a Source to update the information about historical sync duration.
Jun-21-2022 1.91 - Modified section, Configuring Amplitude Analytics as a Source to reflect the latest UI changes.
- Updated the Pipeline frequency information in the Data Replication section.
Mar-07-2022 1.83 Updated the introduction paragraph and the section,Data Replication, about automatic adjustment of ingestion duration.
Oct-25-2021 NA Added the Pipeline frequency information in the Data Replication section.
Apr-06-2021 1.60 - Added a note to the section Schema and Primary Keys
- Updated the ERD. The User object now has three fields, user_id, amplitude_id and device_id as primary keys. The field uuid in the Event object is also a primary key now.

Tell us what went wrong