06:00 UTC













Join marketing, finance, CRM, and product data inside the same warehouse.
Metrics availables
Dimensions availables
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.
This example summarizes product impressions, clicks, conversions, and click-through rate.
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.
Register Google Merchant Center, save the MySQL connection details, and pair both systems in a datastream. The associated job previews and writes the selected columns to "accounts".
Select concrete Google Merchant Center fields such as Average Orders Sales, Average Orders Value, Clicks, and Account Status - Account Level Issue Country. You can rename the chosen columns, preview the result, and write them to MySQL tables such as accounts, products, and product groups.
The "accounts" job can begin with a historical Google Merchant Center fetch and continue on a recurring schedule. Available history and frequency depend on the source API and your plan.
Select a valid date field when configuring the Google Merchant Center job for "accounts". Catchr deletes and rewrites the scheduled window, limiting duplicate rows across overlapping runs.
With Google Merchant Center data, a MySQL query can summarize product impressions, clicks, conversions, and click-through rate. Turn Average Orders Sales and Average Orders Value into a stable MySQL view that analysts and reporting tools can query repeatedly.
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.