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 listing views, calls, and direction requests by location.
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.
Create the Google My Business source, then register Azure SQL with its server host, database name, username, and password. Link both through a datastream and target the "posts" table in the job.
Select concrete Google My Business fields such as Actions, Directions requests, Phone calls, and Day of the month. You can rename the chosen columns, preview the result, and write them to Azure SQL tables such as accounts, locations, and posts.
Configure the initial Google My Business period separately from the recurring schedule for "posts". The source API determines how much history is available.
Choose an eligible date field as the partition for Google My Business. Catchr can then replace the matching period in "posts"; without it, later runs append rows and may create duplicates.
With Google My Business data, an Azure SQL query can summarize listing views, calls, and direction requests by location. Use Actions and Directions requests in an Azure SQL view to create a reusable reporting layer for client analysis.
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.