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 Conversions 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.
Note
Begin sharing your product with your Beta customers only after receiving the sign off.
Requirements
| Rule | API capabilities to be demonstrated in Demo |
|---|---|
| Basics | |
| CO-001 | Demonstrate OAuth 2.0 integration with right scopes and consent screen. Minimum required permissions: r_ads, rw_conversions |
| CO-002 | Demonstrate ability to periodically verify that an access token is valid (heartbeat /me) |
| CO-003 | Demonstrate ability to detect access token expiry |
| CO-004 | Demonstrate ability to re-trigger OAuth Flow in case token has expired or been invalidated |
| CO-005 | Demonstrate ability to use refresh tokens to mint new access tokens that extend access token expiry up to 1 year |
| CO-006 | Demonstrate ability to detect refresh token expiry and re-trigger OAuth Flow |
| CO-007 | Demonstrate ability to request re-auth for consent for new permission to only intended existing customers that would be sending conversions |
| Core | |
| CO-101 | Demonstrate ability to retrieve all Sponsored Accounts (ad accounts) with status for the logged in user and allow user to select one of those ad accounts where user has non-VIEWER role |
| CO-102 | Demonstrate ability to read all active CAPI conversion rules with name available in the selected ad account and allow user to select one of those existing conversion rules |
| CO-103 | Demonstrate ability to create a new conversion rule with CONVERSIONS_API as conversionMethod |
| CO-104 | Demonstrate ability to auto-associate the conversion rule to all existing active campaigns for attribution |
| CO-105 | Demonstrate ability to stream conversion events with multiple user identifiers on newly created and existing conversion rules (required: conversion, conversionHappenedAt , user : SHA256_EMAIL) |
| CO-106 | Support userInfo fields in plain text such as first name, last name, company, title, country/region etc to increase the match rate |
| Advanced | |
| CO-201 | Demonstrate ability to schedule updates in batches for streaming multiple conversion events together |
| CO-202 | Ensure email addresses are converted to lowercase and all whitespace is removed before hashing them with SHA256 |
| CO-203 | Fetch click ids / first-party cookie ids and send them as LINKEDIN_FIRST_PARTY_ADS_TRACKING_UUID for higher match rates |
| CO-204 | Schedule a daily or weekly status check on the conversion rules by sending a GET request and verify that it returns enabled: true. If it returns false, then it means user has deleted the conversion rule and you can stop event sync |