06:00 UTC
Criteo
Selected accounts
Configured job
MySQL
Destination table
Join marketing, finance, CRM, and product data inside the same warehouse.
Metrics availables
Dimensions availables
Criteo
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.
This example summarizes spend, impressions, clicks, and click-through rate by campaign.
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 Criteo, 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 Criteo fields such as Advertiser All Value, Advertiser Value, App Installs, and Channel Name. You can rename the chosen columns, preview the result, and write them to MySQL tables such as accounts, advertisers, and campaigns.
The "accounts" job can begin with a historical Criteo 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 Criteo job for "accounts". Catchr deletes and rewrites the scheduled window, limiting duplicate rows across overlapping runs.
With Criteo data, a MySQL query can summarize spend, impressions, clicks, and click-through rate by campaign. Turn Advertiser All Value and Advertiser 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.
.svg){kind=logo}
.png){kind=logo}
