06:00 UTC
LinkedIn Ads
Selected accounts
Configured job
MySQL
Destination table
Join marketing, finance, CRM, and product data inside the same warehouse.
Metrics availables
Dimensions availables
LinkedIn 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.
Connect LinkedIn Ads and add MySQL as the stored destination. Create a datastream, then save a job that sends the required records to the "advertisers" table.
Select concrete LinkedIn Ads fields such as Account Notified On Creative Approval, Action Clicks, Ad Unit Clicks, and Date. You can rename the chosen columns, preview the result, and write them to MySQL tables such as accounts, advertisers, and campaigns.
Choose how far back the first LinkedIn Ads load should go and how much recent data each "advertisers" run should refresh. Catchr splits large backfills into smaller intervals.
For recurring LinkedIn Ads loads, assign an eligible partition field to "advertisers". Otherwise Catchr cannot match the refresh window and will append the returned records.
With LinkedIn Ads data, a MySQL query can summarize spend, impressions, clicks, and click-through rate by campaign. Join Account Notified On Creative Approval and Action Clicks with shared account or date keys to build a reusable performance model in MySQL.
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}
