LinkedIn Ads

Last updated on Apr 11, 2025

Effective April 10, 2025, Hevo uses Version 202503 to fetch data from Linkedin Ads. To ensure uninterrupted service, your Pipelines will be automatically upgraded.


This upgrade impacts the data ingestion for the following objects:

Object Changes
Campaign Groups Addition of budget_optimisation_bid_strategy, budget_optimisation_budget_optimization_strategy, and objective_type fields.
Campaigns Addition of connected_television_only and optimization_preference fields.
Creatives Addition of name field.
Ad Analytics Addition of audience_penetration, average_dwell_time, subscription_clicks, and viral_subscription_clicks fields.


To avoid any data loss, we recommend making the necessary adjustments to accommodate these changes. The upgrade process will be seamless, with no downtime for your Pipelines. The values for newly added fields will show as NULL for data ingested before the upgrade. If you require historical data for these fields, you can restart the historical load for the respective object.


This change applies to all new and existing Pipelines created with this Source.

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.


Limitations

  • 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
  • Hevo does not load an Event into the Destination table if its size exceeds 128 MB, which may lead to discrepancies between your Source and Destination data. To avoid such a scenario, ensure that each row in your Source objects contains less than 100 MB of data.


Revision History

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

Date Release Description of Change
Apr-11-2025 NA - Added a warning container in page overview to mention about API upgrade.
- Updated Schema and Primary Keys as per API version 202503.
Jan-07-2025 NA Updated the Limitations section to add information on Event size.
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