06:00 UTC
Line Ads
Selected accounts
Configured job
MySQL
Destination table
Join marketing, finance, CRM, and product data inside the same warehouse.
Metrics availables
Dimensions availables
Line Ads
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.
Create the Line Ads source, then register MySQL with its host, username, password, and database name. Link both through a datastream and target the "advertisers" table in the job.
Build the Line Ads schema from available records such as accounts, advertisers, campaigns, and ad groups, plus the supported account and date dimensions. Preview the selected columns before the MySQL job is saved.
Configure the initial Line Ads period separately from the recurring schedule for "advertisers". The source API determines how much history is available.
Choose an eligible date field as the partition for Line Ads. Catchr can then replace the matching period in "advertisers"; without it, later runs append rows and may create duplicates.
With Line Ads data, a MySQL query can summarize spend, impressions, clicks, and click-through rate by campaign. Use accounts and advertisers in a MySQL view to create a reusable reporting layer for client analysis.
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}
