Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Warning
Deprecation Notice: The Marketing Version 202507 (Marketing July 2025) has been sunset. We recommend that you migrate to the latest versioned APIs to avoid disruptions. For information on all the supported versions, refer to the migrations documentation. If you haven’t yet migrated and have questions, submit a request on the LinkedIn Developer Support Portal.
LinkedIn is in the process of rolling out a Technical Sign Off process for the Reporting program. This ensures that our members get the best experience whether using LinkedIn's native UI or a partner product. The technical review and sign off also ensures that there are no gaps in integrations and that partner products keep up with the latest features and updates released by LinkedIn.
As an API partner, please go through the requirements listed below. These are the capabilities that an integrating partner is expected to build in their product. We request you to plan and incorporate these features early in your design. When you're nearing completion, you must initiate a Technical Sign Off request by contacting your LinkedIn POC on the Business Development team.
A demo will be scheduled during which you'll be asked to showcase all your product capabilities. During this evaluation, LinkedIn can suggest modifications which should be completed for the sign off. If all criteria are met (as per the envisioned scope), the technical sign-off is awarded.
Requirements
| Rule | API capabilities to be demonstrated in Demo |
|---|---|
| Basics | |
| ANA-001 | Demonstrate OAuth 2.0 integration, with right scopes, consent screen. |
| ANA-002 | Demonstrate ability to periodically verify that an access token is valid (heartbeat /me). |
| ANA-003 | Demonstrate ability to detect access token expiry. |
| ANA-004 | Demonstrate ability to re-trigger OAuth Flow in case token has expired or been invalidated. |
| ANA-005 | Demonstrate ability to use refresh tokens to mint new access tokens. |
| ANA-006 | Demonstrate ability to detect refresh token expiry and re-trigger OAuth Flow. |
| Account Structure (Hierarchy) and Basic control | |
| ANA-101 | Demonstrate ability to retrieve all Sponsored Accounts for the logged in user. |
| ANA-102 | Demonstrate ability to retrieve all CampaignsGroups with status within Sponsored Accounts. |
| ANA-103 | Demonstrate ability to retrieve all Campaigns with status within Sponsored Accounts. |
| ANA-104 | Demonstrate ability to retrieve all Creatives within Campaigns. |
| ANA-105 | Demonstrate ability to visualize account hierarchy (accounts -> Creative (Ad)). |
| Campaign Reporting | |
| ANA-201 | Demonstrate ability to perform Campaign Reporting (LI performance metrics) based on Campaign hierarchy. |
| ANA-202 | Demonstrate ability to perform Campaign Reporting (LI performance metrics) based on Demographic pivots (example: MEMBER_COMPANY). |
| ANA-203 | Demonstrate ability to perform Campaign Reporting (LI performance metrics) using all pivots and time ranges using Analytics Finder. |
| ANA-204 | Demonstrate ability to perform Campaign Reporting (LI performance metrics) using all pivots and time ranges using Statistics Finder. |
| ANA-205 | Demonstrate ability to show conversion metrics and provide insights into campaign spending (Prove ROI). |
| ANA-206 | Demonstrate ability to match LinkedIn Reporting UI results on CONVERSION pivot for a specific date range. |
| ANA-207 | Demonstrate the ability to pull in all current LinkedIn Ad Formats. |
| ANA-208 | Demonstrate ability to match LinkedIn Campaign Manager UI results with your app reporting on a selected pivot for a specific date range. |
| ANA-209 | Custom or templated options for visualizing LI metrics, built for B2B Marketer. |