Connect Amplitude to Azure SQL

Add your Amplitude project API key and secret, choose the Standard or EU endpoint that matches your project, save your Azure SQL connection details, and pair both systems in a datastream. You can then select, preview, rename, and write Amplitude event fields to an Azure SQL table.

You can build an Azure SQL schema with Amplitude event dimensions such as Event Id, City, Amplitude Attribution Ids, Client Upload Time, and Server Upload Time. Nested event, user, group, and data properties are available as JSON strings.

Catchr processes Amplitude exports in 24-hour windows based on Server Upload Time, helping manage the Export API's 4 GB response limit. Amplitude exports can lag ingestion by up to two hours, so newly uploaded events may not appear immediately.

Use Server Upload Time as the date field for the Amplitude job. Catchr can delete and rewrite the scheduled window in Azure SQL to limit duplicate rows across overlapping recurring loads, with available history and frequency depending on the source API and your plan.

Agencies can query Amplitude events by fields such as city, attribution identifier, and upload time, then create reusable Azure SQL views for client reporting. JSON property columns preserve nested event and user details for workflows that need them.

Yes. Connect an existing Azure SQL  database first. The Catchr job creates and populates the destination table you configure inside that database.

Yes. Create a separate datastream and job for each source, write each export to its own table, then combine the data downstream with SQL, views, or your BI tool.