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.
This example summarizes delivery, opens, clicks, and engagement rates by email campaign.
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.
Connect MailerLite as a Catchr source. Add your existing Azure SQL database, create a datastream, and configure a job that writes the selected fields to the "accounts" table.
Select concrete MailerLite fields such as Automation Step Email Click Rate, Automation Step Email Clicks Count, Automation Step Email Forwards Count, and Day of the month. You can rename the chosen columns, preview the result, and write them to Azure SQL tables such as accounts, campaigns, and contacts.
Catchr first processes the historical range configured for MailerLite. Later runs update the "accounts" table using the saved frequency and rolling import window.
Catchr uses the selected partition field to refresh the relevant MailerLite period inside "accounts". Leaving it blank changes the job to append-only behavior.
With MailerLite data, an Azure SQL query can summarize delivery, opens, clicks, and engagement rates by email campaign. A Azure SQL view comparing Automation Step Email Click Rate and Automation Step Email Clicks Count can feed agency dashboards or downstream BI models.
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.