06:00 UTC
Bing Webmaster Tool
Selected accounts
Configured job
Azure SQL
Destination table
Join marketing, finance, CRM, and product data inside the same warehouse.
Metrics availables
Dimensions availables
Bing Webmaster Tool
3 advertising accounts
Connected
Google Ads
2 advertising accounts
Connected
Google Analytics 4
1 web property
Connected
HubSpot
1 CRM portal
Connected
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 clicks, impressions, click-through rate, and average position by search query.
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 Bing Webmaster Tool as a Catchr source. Add your existing Azure SQL database, create a datastream, and configure a job that writes the selected fields to the "sites" table.
Select concrete Bing Webmaster Tool fields such as All Other Codes, Avg Click Position, Avg Impression Position, and Day of the month. You can rename the chosen columns, preview the result, and write them to Azure SQL tables such as sites, pages, and queries.
Catchr first processes the historical range configured for Bing Webmaster Tool. Later runs update the "sites" table using the saved frequency and rolling import window.
Catchr uses the selected partition field to refresh the relevant Bing Webmaster Tool period inside "sites". Leaving it blank changes the job to append-only behavior.
With Bing Webmaster Tool data, an Azure SQL query can summarize clicks, impressions, click-through rate, and average position by search query. A Azure SQL view comparing All Other Codes and Avg Click Position 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.
.svg){kind=logo}
.png){kind=logo}
