Connect Amplitude to PostgreSQL

Add your Amplitude project using its API key and secret key, enter your PostgreSQL connection details, and pair both systems in a datastream. You can then select and preview the Amplitude columns before writing them to a PostgreSQL table.

You can select dimensions such as attribution IDs, city, event ID, client upload time, server upload time, and normalized date fields. Nested event, user, group, and data properties are stored as JSON strings that PostgreSQL queries can retain and process.

Catchr processes Amplitude’s zipped event exports in 24-hour windows based on server upload time, then writes the selected columns to PostgreSQL. Amplitude exports can lag ingestion by up to two hours, so this workflow should not be treated as real-time.

Use Server Upload Time as the date field for the Amplitude job. Catchr deletes and rewrites the scheduled window in PostgreSQL, helping limit duplicate rows when recurring loads overlap.

PostgreSQL queries can organize exported Amplitude events by city, day, hour, month, or quarter and retain attribution identifiers for further analysis. Agencies can expose the resulting tables or views to their preferred reporting tools.

Yes. Connect an existing PostgreSQL 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.