06:00 UTC
.svg)
Mixpanel
Selected accounts
Configured job
BigQuery
Destination table
Join marketing, finance, CRM, and product data inside the same warehouse.
Metrics availables
Dimensions availables
Mixpanel
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 Mixpanel as a source in Catchr, provide the required service-account credentials and Mixpanel project ID, choose Big Query as the destination, and authorize the target Google Cloud project and dataset.
Export raw Mixpanel events with a Records counter and dimensions such as UTM campaign, email, hour, week, month, quarter, and year.
Catchr flattens common reserved Mixpanel properties into fields and keeps the remaining event property bag in properties_json for further querying.
Yes. Keep each source in a separate table, then use SQL views or models to join data on shared dimensions such as date or campaign.
Use the Records counter to measure exported event volumes and break them down by UTM campaign or normalized time dimensions for campaign and product-usage reporting.
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.
.png){kind=logo}
