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 review volume and average rating by location over the last 30 days.
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.
Start with a connected Appstore Review source and an existing Azure SQL database. Create a datastream between them, then configure the accounts, fields, schedule, and "locations" table.
Select concrete Appstore Review fields such as Average Rating, Rating, Review Count, and Day of the year. You can rename the chosen columns, preview the result, and write them to Azure SQL tables such as review sources, locations, and reviews.
Set an initial fetch period for Appstore Review, then choose the frequency and lookback window for the job writing to "locations". Catchr rewrites that selected period on each run.
The partition field tells Catchr which Appstore Review rows in "locations" belong to the period being refreshed. If you omit it, every run appends records rather than updating them.
With Appstore Review data, an Azure SQL query can summarize review volume and average rating by location over the last 30 days. A query built around Average Rating and Rating can support trend reviews, account comparisons, and operational 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.