Integration Requirements for Ads Lead Generation Program

LinkedIn has a technical sign off process for the Ads LeadGen 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 are 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 will be asked to showcase all your product capabilities. During this evaluation, LinkedIn may suggest modifications which will need to be completed for the sign off. If all criteria are met (as per the envisioned scope), the technical sign-off is awarded.

This page documents the requirements for Ads Lead Gen integrations only. If you are building an Events Lead Gen integration, see Events Lead Generation Requirements.


You can begin sharing your product with your Beta customers only after receiving the sign off.


Rule API capabilities to be demonstrated in Demo
LGF-001 Demonstrate OAuth 2.0 integration, with right scopes, consent screen
LGF-002 Demonstrate ability to periodically verify that an access token is valid (heartbeat /me)
LGF-003 Demonstrate ability to detect access token expiry
LGF-004 Demonstrate ability to rep-trigger OAuth Flow incase token has expired or been invalidated.
LGF-005 Demonstrate ability to use refresh tokens to mint new access tokens.
LGF-006 Demonstrate ability to detect refresh token expiry and rep-trigger OAuth Flow
LGF-007 Demonstrate ability to check user access and permissions to start receiving leads
LGF-101 Demonstrate ability to retrieve all Sponsored Accounts with status for the logged in user
LGF-102 Demonstrate ability to read all adForms available per sponsored account
LGF-103 Demonstrate ability to automatically read all predefined fields of a form
LGF-104 Demonstrate ability to read all custom questions (and options) of a form
LGF-105 Demonstrate ability to read all Hidden Fields of a form
LGF-106 Demonstrate ability to read all Consent texts of a form
LGF-107 Demonstrate ability to create datastore/tables as required for a leadgen form
LGF-108 Demonstrate ability to PULL all leads and store them in the data store.
LGF-109 Demonstrate an E2E test, when a lead flows from CMT UI all the way to data store.
LGF-110 Demonstrate ability to recover from outages using a time-bound PULL request.
LGF-111 Demonstrate ability to teardown, delete integrations and recreate integrations.
LGF-112 Demonstrate ability to re-pull forms periodically
LGF-113 Demonstrate a single field failure does not block the lead syncing
LGF-114 Demonstrate a single lead failure will not break syncing of other leads
LGF-115 Deomonstrate all mapping are based on pre-defined field value
LGF-201 Demonstrate ability to configure the intervals between PULL requests.
LGF-202 Demonstrate ability to register and listen for webhooks for specific forms and specific accounts
LGF-203 Demonstrate ability to recover from outages, missed PUSH notifications.
LGF-204 Demonstrate ability to update or delete and re-register webbhooks and test leads