06:00 UTC
Google Ad Manager
Selected accounts
Configured job
MySQL
Destination table
Join marketing, finance, CRM, and product data inside the same warehouse.
Metrics availables
Dimensions availables
Google Ad Manager
3 advertising accounts
Connected
Google Ads
2 advertising accounts
Connected
Google Analytics 4
1 web property
Connected
HubSpot
1 CRM portal
Connected
Connect your existing MySQL database with its host, port, username, password, and database name. Then create the datastream that defines where the selected source data should go.
Choose the fields, initial history, partition field, and recurring schedule for the job. Catchr refreshes the configured import window in your MySQL 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 MySQL setup, available source data, schedules, table updates, and SQL use cases.
Authorize Google Ad Manager with OAuth, select the network code, save your MySQL connection details, and pair both systems in a datastream. You can then preview and write the selected report fields to MySQL.
Choose from 321 metrics and 488 dimensions, including total revenue, Ad server CTR, Ad Exchange CPC, date, country, inventory type, and content source name. Catchr lets you select and rename the columns used in your MySQL table.
Use supported date dimensions to structure MySQL data by day, week, month, or hour. Historical availability and recurring load frequency depend on the Google Ad Manager API and your Catchr plan.
Select a valid Google Ad Manager date field for the job. Catchr deletes and rewrites the scheduled date window in MySQL, helping limit duplicate rows when successive loads overlap.
Build MySQL queries and reusable views for total revenue, Ad server revenue, CTR, CPC, and yield group performance, broken down by dimensions such as date, country, inventory type, or content source name.
Yes. Connect an existing MySQL 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.
Connect your accounts, choose the fields, then schedule the data your team needs in MySQL.
.svg)
.svg){kind=logo}
.png){kind=logo}
