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.
Authorize Xero with OAuth2, select the relevant Xero tenant, save your Azure SQL connection details, and pair both systems in a Catchr datastream to load selected accounting fields.
Choose from 20 metrics and 112 dimensions, including invoice total, amount due, amount paid, total tax, contact receivable balances, account codes, payment account names, and contact details, then map them to Azure SQL columns.
A Xero job can start with a historical fetch and continue on a recurring schedule, with the available history and frequency depending on the Xero API and your Catchr plan.
Select a valid Xero date field when configuring the job so Catchr can delete and rewrite the scheduled window, helping limit duplicate rows across overlapping loads.
Agencies can query invoice totals, amounts paid and due, tax, overdue receivables, payable balances, contacts, and payment accounts in Azure SQL to support repeatable billing and financial reporting.
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.