06:00 UTC
Impact.com
Selected accounts
Configured job
Azure SQL
Destination table
Join marketing, finance, CRM, and product data inside the same warehouse.
Metrics availables
Dimensions availables
Impact.com
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.
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.
Register impact.com with your Account SID and Auth Token, save your Azure SQL connection details, then pair both systems in a datastream. Configure a job to preview and write the selected impact.com fields to Azure SQL.
You can select fields from company information, partners, programs, and ads, including Program Name, Company Homepage, Example Landing Page, Additional Category, and Timezone. Rename the chosen columns, preview the result, and write it to your Azure SQL tables.
An impact.com job can start with a historical fetch and continue on a recurring schedule. The available history and scheduling frequency depend on the impact.com API and your Catchr plan.
When an impact.com job includes a valid date field, select it during configuration so Catchr can delete and rewrite the scheduled window, helping limit duplicate rows across overlapping Azure SQL loads.
Azure SQL queries and views can organize impact.com programs and ads by program name, category, mobile readiness, future-ad visibility, or trademark-bidding policy, giving freelancers and agencies reusable datasets for program inventory and account reviews.
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)
.svg){kind=logo}
.png){kind=logo}
