LinkedIn Ads (v1)
Last updated: 9/15/2026This integration is powered by Singer's LinkedIn Ads tap and certified by Stitch. Check out and contribute to the repo on GitHub.
For support, contact Support.
LinkedIn Ads feature snapshot
A high-level look at Stitch's LinkedIn Ads (v1) integration, including release status, useful links, and the features supported in Stitch.
| STITCH | |||
| Release status |
Deprecated on February 7, 2023 |
Supported by
|
|
|
Stitch plan
|
Standard |
API availability
|
Not available
|
| Singer GitHub repository | |||
| REPLICATION SETTINGS | |||
|
Anchor Scheduling
|
Supported
|
Advanced Scheduling
|
Supported
|
|
Table-level reset
|
Unsupported
|
Configurable Replication Methods
|
Unsupported
|
| DATA SELECTION | |||
|
Table selection
|
Supported
|
Column selection
|
Supported
|
|
Select all
|
Supported
|
||
| TRANSPARENCY | |||
|
Extraction Logs
|
Supported
|
Loading Reports
|
Supported
|
Connecting LinkedIn Ads
LinkedIn Ads setup requirements
To set up LinkedIn Ads in Stitch, you need:
-
Access to a LinkedIn Ads account. This is necessary to login to the Campaign Manager account.
-
Access to a LinkedIn Ads Campaign Manager account. Verify that you have access to use the Ad accounts you want to replicate data from. This is necessary to connect to Stitch.
Step 1: Retrieve your LinkedIn Ads account IDs
- Login to your LinkedIn account.
-
Click the Work menu, then Advertise:
The LinkedIn Work and Advertise menus, highlighted -
In the Accounts table, locate the IDs for the accounts you want to replicate data from:
LinkedIn Ads account IDs highlighted in the Accounts table of the Campaign Manager page.
Step 2: Add LinkedIn Ads as a Stitch data source
- Sign into your Stitch account.
-
On the Stitch Dashboard page, click the Add Integration button.
-
Click the LinkedIn Ads icon.
-
Enter a name for the integration. This is the name that will display on the Stitch Dashboard for the integration; it’ll also be used to create the schema in your destination.
For example, the name “Stitch LinkedIn Ads” would create a schema called
stitch_linkedin_adsin the destination. Note: Schema names cannot be changed after you save the integration. - In the Accounts field, enter a comma-separated list of the account IDs of the campaign accounts you want to replicate data from. These will be the account IDs you retrieved in Step 1. For example:
503123456,503234567, etc.
Step 3: Define the historical replication start date
The Sync Historical Data setting defines the starting date for your LinkedIn Ads integration. This means that data equal to or newer than this date will be replicated to your data warehouse.
Change this setting if you want to replicate data beyond LinkedIn Ads’s default setting of 1 year. For a detailed look at historical replication jobs, check out the Syncing Historical SaaS Data guide.
Step 4: Create a replication schedule
In the Replication Frequency section, you’ll create the integration’s replication schedule. An integration’s replication schedule determines how often Stitch runs a replication job, and the time that job begins.
LinkedIn Ads integrations support the following replication scheduling methods:
-
Advanced Scheduling using Cron (Advanced or Premium plans only)
To keep your row usage low, consider setting the integration to replicate less frequently. See the Understanding and Reducing Your Row Usage guide for tips on reducing your usage.
Step 5: Set objects to replicate
The last step is to select the tables and columns you want to replicate. Learn about the available tables for this integration.
Note: If a replication job is currently in progress, new selections won’t be used until the next job starts.
For LinkedIn Ads integrations, you can select:
-
Individual tables and columns
-
All tables and columns
Click the tabs to view instructions for each selection method.
- In the integration’s Tables to Replicate tab, locate a table you want to replicate.
-
To track a table, click the checkbox next to the table’s name. A blue checkmark means the table is set to replicate.
-
To track a column, click the checkbox next to the column’s name. A blue checkmark means the column is set to replicate.
- Repeat this process for all the tables and columns you want to replicate.
- When finished, click the Finalize Your Selections button at the bottom of the screen to save your selections.
- Click into the integration from the Stitch Dashboard page.
-
Click the Tables to Replicate tab.
- In the list of tables, click the box next to the Table Names column.
-
In the menu that displays, click Track all Tables and Fields:
The Track all Tables and Fields menu in the Tables to Replicate tab - Click the Finalize Your Selections button at the bottom of the page to save your data selections.
Initial and historical replication jobs
After you finish setting up LinkedIn Ads, its Sync Status may show as Pending on either the Stitch Dashboard or in the Integration Details page.
For a new integration, a Pending status indicates that Stitch is in the process of scheduling the initial replication job for the integration. This may take some time to complete.
Initial replication jobs with Anchor Scheduling
If using Anchor Scheduling, an initial replication job may not kick off immediately. This depends on the selected Replication Frequency and Anchor Time. Refer to the Anchor Scheduling documentation for more information.
Free historical data loads
The first seven days of replication, beginning when data is first replicated, are free. Rows replicated from the new integration during this time won’t count towards your quota. Stitch offers this as a way of testing new integrations, measuring usage, and ensuring historical data volumes don’t quickly consume your quota.
LinkedIn Ads replication
Every time Stitch runs a replication job for LinkedIn Ads, the last 7 days’ worth of data will be replicated.
This is applicable to all tables in the integration.
Stitch replicates data in this way to account for updates made to existing records within the default attribution window of 7 days, thus ensuring you won’t make decisions based on stale (or false) data. As a result, you may see a higher number of replicated rows than what’s being generated in LinkedIn Ads.
Setting the Replication Frequency to a higher frequency - like 30 minutes - can result in re-replicating recent data and contribute to greater row usage. Replicating fewer tables or selecting a lower frequency can help keep your row count low.
Refer to the documentation for each of these tables in the next section for more info.
Attribution window examples
In the tabs below are examples of attribution windows behave during historical (initial) and ongoing replication jobs.
For historical and full re-replications of LinkedIn Ads data, Stitch will query for and extract data newer than or equal to the date defined in the Start Date field in the Integration Settings page.
The Start Date, in conjunction with the Attribution Window, defines the minimum date Stitch should query for when extracting historical data. This is calculated as:
Start Date - Attribution Window = Minimum Extraction Date
Example
During the initial set up, the Start Date field is set to 06/03/2017, or June 3, 2017.
To account for the Attribution Window, Stitch would calculate the Minimum Extraction Date value as: 2017-07-03 00:00:00 - 7 days = 2017-06-03 00:00:00
If you were to write a SQL query using this date for the ad_analytics_by_campaign table, it might look like this:
SELECT *
FROM linkedin_ads.ad_analytics_by_campaign
WHERE end_at >= '2017-06-03 00:00:00' /* Min. Extraction Date */
ORDER BY end_at
For ongoing replication jobs, Stitch will query for and extract data using the last saved maximum value in the table’s Replication Key column and the Attribution Window for the table.
Note: This applies to every replication job that takes place after the historical replication job.
Example
The last maximum saved Replication Key value for the ad_analytics_by_campaign table is 2017-10-01 00:00:00.
To account for the Attribution Window of 7 days, we’d subtract this from the last maximum saved Replication Key value:
2017-10-01 00:00:00 - 7 days = 2017-09-24 00:00:00
In this case, Stitch would query for and extract data that is newer than or equal to 2017-09-24 00:00:00 and older than or equal to 2017-10-01 00:00:00.
If this were a SQL query, it might look like this:
SELECT *
FROM ad_analytics_by_campaign
WHERE end_at >= '2017-09-24 00:00:00'
/* max Replication Key value - Attribution Window */
AND end_at <= '2017-10-01 00:00:00'
/* max Replication Key value from previous job */
ORDER BY end_at
LinkedIn Ads table reference
Schemas and versioning
Schemas and naming conventions can change from version to version, so we recommend verifying your integration’s version before continuing.
The schema and info displayed below is for version 1 of this integration.
Table and column names in your destination
Depending on your destination, table and column names may not appear as they are outlined below.
For example: Object names are lowercased in Redshift (CusTomERs > customers), while case is maintained in PostgreSQL destinations (CusTomERs > CusTomERs). Refer to the Loading Guide for your destination for more info.
account_users
The account_users table contains info about the users who have permissions to an ad account.
|
Key-based Incremental |
|
|
Primary Keys |
account_id user_person_id |
|
Replication Key |
last_modified_time |
| Useful links |
accounts
The accounts table contains info about your LinkedIn Ads ad accounts.
|
Key-based Incremental |
|
|
Primary Key |
id |
|
Replication Key |
last_modified_time |
| Useful links |
ad_analytics_by_campaign
The ad_analytics_by_campaign table contains analytics data for ads, segmented by campaign.
To replicate data from this table, you must also select the parent campaigns table.
Note: This table is replicated using an attribution window of 7 days. Refer to the Replication section for more info.
|
Key-based Incremental |
|
|
Primary Keys |
campaign_id start_at |
|
Replication Key |
end_at |
| Useful links |
ad_analytics_by_creative
The ad_analytics_by_creative table contains info about ad analytics, segmented by creative.
To replicate data from this table, you must also select the parent creatives table.
Note: This table is replicated using an attribution window of 7 days. Refer to the Replication section for more info.
|
Key-based Incremental |
|
|
Primary Keys |
creative_id start_at |
|
Replication Key |
end_at |
| Useful links |
campaign_groups
The campaign_groups table contains info about the campaign groups in your LinkedIn Ads account.
|
Key-based Incremental |
|
|
Primary Key |
id |
|
Replication Key |
last_modified_time |
| Useful links |
campaigns
The campaigns table contains info about the campaigns in your LinkedIn Ads account.
|
Key-based Incremental |
|
|
Primary Key |
id |
|
Replication Key |
last_modified_time |
| Useful links |
creatives
The creatives table contains info about the creatives in your LinkedIn Ads account.
|
Key-based Incremental |
|
|
Primary Key |
id |
|
Replication Key |
last_modified_time |
| Useful links |
video_ads
The video_ads table contains info about the video ads in your LinkedIn Ads account.
|
Key-based Incremental |
|
|
Primary Key |
content_reference |
|
Replication Key |
last_modified_time |
| Useful links |