06:00 UTC
Amplitude
Selected accounts
Configured job
BigQuery
Destination table
Join marketing, finance, CRM, and product data inside the same warehouse.
Metrics availables
Dimensions availables
Amplitude
3 advertising accounts
Connected
Google Ads
2 advertising accounts
Connected
Google Analytics 4
1 web property
Connected
HubSpot
1 CRM portal
Connected
Select your Google Cloud project and BigQuery dataset. Catchr automatically prepares the destination and maps your data into analytics-ready tables.
Catchr continuously imports new and updated data into BigQuery.
Your warehouse stays fresh automatically, ready for SQL, dbt, BI tools, and AI workloads.
Open the dedicated route for each platform. Its field catalog, reporting grain, historical constraints, and warehouse use cases should be specific to that source.
Answers about available Meta Ads data, reporting cadence, history, table settings, attribution changes, and downstream joins.
Add Amplitude as a source in Catchr, enter the project API key and secret key, choose the correct Standard or EU residency endpoint, then authorize the target Google Cloud project and dataset.
Export event-level dimensions such as attribution IDs, event IDs, city, IP address, and client or server upload times. Nested group, user, event, and data properties are stored as JSON strings.
Catchr processes Amplitude exports in 24-hour windows based on server upload time. Because Amplitude exports can lag ingestion by up to two hours, the latest events may not appear immediately.
Yes. Keep Amplitude and other sources in separate tables, then use SQL views or models to connect them through compatible fields such as dates, attribution identifiers, or location dimensions.
Use Amplitude event data to examine attribution identifiers, upload timing, geographic context, and nested event or user properties alongside your other reporting data.
If your selected schema contains an eligible date field, you can configure that field as the optional date partition for the destination table. Catchr does not configure table clustering or design your downstream analytical models.
Yes. Configure the historical period supported by the source for the initial import, then keep the table updated with recurring exports. The available range is determined by the source API and the settings of your job, not an unlimited-history promise.
Our teams is always here to responds to any question you could have about our data connector.
Connect your accounts, choose the fields then send the configured export to your BigQuery project.
.svg)
.png){kind=logo}
