06:00 UTC













Join marketing, finance, CRM, and product data inside the same warehouse.
Metrics availables
Dimensions availables
Enter the Azure SQL server host, database, and login details. Catchr verifies the destination before any marketing data is exported.
Choose the fields, initial history, partition field, and recurring schedule for the job. Catchr refreshes the configured import window in your AzureSQL table.
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 AzureSQL setup, available source data, schedules, table updates, and SQL use cases.
Register Mixpanel with its service-account credentials and project ID, save your Azure SQL connection details, then pair both systems in a datastream and select the event fields to write.
Catchr exports raw Mixpanel events with fields such as UTM Campaign, Email, date dimensions, and a Records counter. Common reserved properties are flattened, while remaining properties are kept in properties_json.
A Mixpanel-to-Azure SQL job can start with a historical fetch and continue on a recurring schedule. The available history and frequency depend on the Mixpanel API and your Catchr plan.
Mixpanel service-account requests require a project ID alongside the API-key authorization details. Catchr uses those credentials to read raw event exports for the Azure SQL datastream.
Agencies can query exported events by UTM campaign, email, hour, week, month, quarter, or year, then reuse the resulting Azure SQL tables in their reporting workflows.
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.
Our teams is always here to responds to any question you could have about our data connector.