LinkedIn Ads

Last updated on May 20, 2024

The LinkedIn Ads API will soon be upgraded to the latest version (012024), which contains new and enhanced capabilities. This upgrade includes object changes that may impact your existing Pipelines created with this Source.

Please stay tuned for further communication about the enhancement and its release date.

LinkedIn Ads enable you to display sponsored content in the LinkedIn feed of professionals you want to reach by way of single image ads, video ads, and carousel ads. You can target your most valuable audiences using accurate, profile-based first-party data.

You can use Hevo Pipelines to replicate data from your LinkedIn reports to the desired Destination database or data warehouses for scalable analysis.


  • LinkedIn restricts the amount of data that can be fetched from certain objects. As a result, with the All Available Data option, Hevo ingests historical data for a limited period from them. The following table lists the time and the affected objects:

    Time Objects
    Up to six months - Ad Analytics by Campaign

    - Ad Analytics by Creative
    Up to one year - Page Stats
    - Follower Stats
    - View Stats

Revision History

Refer to the following table for the list of key updates made to this page:

Date Release Description of Change
Mar-05-2024 2.21 Updated the ingestion frequency table in the Data Replication section.
Sep-22-2023 NA Removed the banner from the top of the page about migration to versioned APIs.
Jul-25-2023 NA Updated section, Data Model for better clarity.
Jun-19-2023 2.14 - Added a banner at the top of the page to mention about migration to versioned APIs.
- Updated section, Data Model to add information about versioned APIs.
Feb-20-2023 NA Updated section, Configuring LinkedIn Ads as a Source to update the information about historical sync duration.
Jul-11-2022 NA Updated the ERD table in the Schema and Primary Keys section.
Oct-25-2021 NA Added the Pipeline frequency information in the Data Replication section.
Jul-26-2021 NA Added a note in the Overview section about Hevo providing a fully-managed Google BigQuery Destination for Pipelines created with this Source.

Tell us what went wrong