Data Storage Requirements
Warning
Deprecation Notice
The Marketing Version 202311 (Marketing November 2023) and earlier versions (excluding 202306 and 202307) have been sunset. Additionally, the unversioned APIs will be sunset soon. We recommend that you migrate to the versioned APIs as well as migrate to the new Content and Community Management APIs to avoid disruptions. See the Migration page for more details.
If you haven’t yet migrated and have questions, submit a request on the LinkedIn Developer Support Portal.
This documentation specifies how long you can store or cache data received via the LinkedIn Marketing API Program. If LinkedIn has granted you access to the LinkedIn Marketing API Program, it will appear in the list of products that your application has access to on the LinkedIn developer portal. Of note, you may not have access to all of the following data fields.
Please consult the LinkedIn Marketing API Program Terms for other restrictions, conditions, and data deletion obligations relating to this data. For example, the LinkedIn LinkedIn Marketing API Program Terms require that you obtain an authenticated member’s consent to store their profile data and delete data upon the member’s request. If there is any conflict between these requirements and the requirements in the terms, the requirements that are more restrictive or more protective of the data apply. Similarly, if a given data field is encompassed by two or more of the following requirements, the shortest storage/caching duration shall apply.
LinkedIn reserves the right to update these requirements at any time, upon posting the updated requirements on our developer documentation. The following requirements do not apply to data that is independently provided to you by your clients and not retrieved via the LinkedIn Marketing APIs.
Data Field(s) | Description | Allowed Storage/Caching Duration |
---|---|---|
Authenticated Members' Person ID and Person URN | Person ID and Person URN for a LinkedIn member (e.g. organization page admin or advertising account manager) who has authenticated into your application | No Restriction on Duration |
Authenticated Members' Profile Data | Basic Profile Information for a LinkedIn member (e.g. organization page admin or advertising account manager) who has authenticated into your application | No Restriction on Duration |
Other Members' Person ID and Person URN | Person ID and Person URN retrieved for a LinkedIn member, other than in connection with the member authenticating into your application. For example, Person ID and Person URN for a LinkedIn member who has taken a social action (e.g. like, comment) on an organization post managed by your application. | No Restriction on Duration |
Other Members' Profile Data | Basic Profile Information retrieved for a LinkedIn member, other than in connection with the member authenticating into your application or completing a lead gen form. For example, profile information for a LinkedIn member who has taken a social action (e.g. like, comment) on an organization post managed by your application. For clarity, nothing in these requirements or the LI MDP Terms shall permit you to cache this data in excess of 24 hours or store this data. | 24 Hour Caching |
IDs and URNs associated with Managing Advertising and Organization Activity | ID and URN identifiers for organizations, posts/shares, social actions (e.g. likes, comments), ad accounts, ad campaigns, ad creatives, lead gen forms, ad targeting, and other IDs and URNs for managing advertising and organization activity on LinkedIn. | No Restriction on Duration |
Members' Social Activity Data | Data relating to social activity by LinkedIn members, including articles, posts/shares, likes, comments, mentions, and the metadata relating thereto (e.g. time of creation, content, visibility, etc.). For clarity, this restriction shall not limit your ability to store data relating to social activity by organizations, provided such data doesn’t relate to LinkedIn members. For example, if an organization comments on a member’s share, the organization’s comment is not subject to this restriction but the content of the member’s share is. | 48 Hours |
Organizations’ Social Activity Data | Data relating to social activity by organizations on LinkedIn, including articles, posts/shares, likes, reshares, mentions, and comments, and the metadata relating thereto (e.g. time of creation, content, visibility, etc.). For clarity, if a social activity by an organization includes member content or results in a social action by a member, the member content can only be stored for 48 hours and the member profile data can only be cached for 24 hours as specified by the preceding requirements. | Six Weeks. If content is being pulled that relates to an organization that has authenticated into your application, you may store it for six months. |
Organization Profile Data | Profile data retrieved from an organization's LinkedIn page (e.g. name, size, industry, description, etc.). | If organization profile data is being pulled that relates to an organization that has authenticated into your application, you may store it for eight weeks. Otherwise, storing/caching is not allowed, except organization name and logo URL for 30 days. |
Organization Pages' Admin and Reporting Data | Data relating to administration and reporting for an organization’s LinkedIn page (e.g. number of followers, summary of social actions, visitor information). Does not include individual member level data. | One Year |
Advertising Accounts' Admin and Reporting Data | Data relating to administration of a LinkedIn advertising account (e.g. forecasting reach, budget pricing, targeting options) and reporting for the LinkedIn advertising account. Does not include individual member level data. | One Year |
Lead Gen Response Data | Data provided by a LinkedIn member as part of a response to a lead gen form | No Restriction on Duration |
Standardized Data | LinkedIn's Standardized Lists of industries, job functions, degrees, skills, locations, etc. | One Year (but expressly excluding the Microsoft Bing Maps location data which may not be stored) |