LinkedIn Ads
Advertising
How your LinkedIn advertising is set up, in every ad account you can reach, with each account's campaign groups, campaigns and creatives. Ingest delivers this data to a data warehouse you own as 4 tables, and updates it on the schedule you choose. There is no code to write and nothing to install.
What people use it for
- See every ad account in one placeList every LinkedIn ad account you can reach, found for you, with no account id to paste.
- See how each account is organizedFollow each account's campaign groups, campaigns and creatives side by side.
- Check why a creative is not runningSee each creative's review result and any reasons LinkedIn is holding it back.
- Review targetingSee each campaign's targeting as LinkedIn stores it.
What you get
| Table | Each row is |
|---|---|
Ad accountsad_accounts | One ad account |
Campaign groupscampaign_groups | One campaign group |
Campaignscampaigns | One campaign |
Creativescreatives | One creative |
Good to know
- Ad accounts: Each run re-reads every ad account you can reach, which picks up new ones, and updates rows that changed. Rows the source removes stay in your table.
- Campaign groups: Each run reads the campaign groups of every ad account again, so changes show up after the next run.
- Campaigns: Each run reads the campaigns of every ad account again, so changes show up after the next run.
- Creatives: Each run reads the creatives of every ad account again, so changes show up after the next run.
How it works
- Choose LinkedIn Ads. Connect your LinkedIn Ads account once, from Ingest.
- Pick where it goes. BigQuery, Snowflake, Databricks, Redshift and 11 more, in an account you own.
- Pick a schedule. Daily is the default, and weekly and monthly are there too.
- Ingest runs it from then on. If a run fails, your dashboard shows which table and why.
Questions
- What does the LinkedIn Ads data include?
- 4 tables: ad accounts (one row per ad account), campaign groups (one row per campaign group), campaigns (one row per campaign) and creatives (one row per creative).
- Do I need an account with LinkedIn Ads?
- Yes. You connect your own LinkedIn Ads account once, from Ingest, and the data comes from what that account can see.
- Which warehouses can LinkedIn Ads data go to?
- Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, ObsessionDB, MySQL / generic SQL and Snowflake, in an account you own.
- How fresh is the data?
- As fresh as your schedule: daily by default, or weekly or monthly. Schedules as often as every 20 minutes are on the Enterprise plan.
- Will running it again create duplicate rows?
- No. Each row is stored once, by its key: when a run reads a row that is already there, it replaces that copy instead of adding a second one.
- Do I need to write code?
- No. Ingest builds, runs and maintains the connector. Someone with access to your warehouse connects it once, following a short guide.
For your data team: technical reference
Connector linkedin_ads, version 0.1.0, a REST source, status beta, authentication oauth2.
Vendor documentation: https://learn.microsoft.com/en-us/linkedin/marketing/integrations/ads/getting-started
Configuration
No configuration required.
Resources
| Resource | Status | Plan | Write | Primary key | Overrides |
|---|---|---|---|---|---|
ad_accountsEvery ad account the signed-in member can reach, from the LinkedIn Ads "search for accounts" finder. This is the anchor of the connector: the account ids it yields are what the campaign group, campaign and creative resources are fetched against, so nobody has to paste an account id. Re-read in full on every run, which is what picks up newly created accounts. | beta | full | merge | id | - |
campaign_groupsCampaign groups in each ad account (transformer child of ad_accounts). One request per account discovered on the parent resource; the account id comes from the parent's own record. The audit-stamp times are LinkedIn's native Unix epoch MILLISECONDS, kept as bigint and not cast to a timestamp. | beta | parent_child | merge | id | - |
campaignsCampaigns in each ad account (transformer child of ad_accounts). One request per account discovered on the parent resource. `runSchedule.start` and the audit-stamp times are LinkedIn's native Unix epoch MILLISECONDS, kept as bigint; the targeting criteria and offsite preferences are kept as JSON because their shape varies per campaign. | beta | parent_child | merge | id | - |
creativesCreatives in each ad account (transformer child of ad_accounts), from the "criteria" finder. One request per account discovered on the parent resource. The primary key is LinkedIn's own creative URN, which is globally unique. `createdAt` and `lastModifiedAt` are Unix epoch MILLISECONDS, kept as bigint; the review block and serving hold reasons are kept as JSON. | beta | parent_child | merge | id | - |
Where this lands, and what else connects
Setting up the destination is its own short guide, one per warehouse or lake: Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, ObsessionDB, MySQL / generic SQL, Snowflake.
Get LinkedIn Ads data into your warehouse
Last updated .