User-Generated Content
BR
0
Not Available
EU
24
Minimal
UK
0
Not Available
Advertising
BR
46
Deficient
EU
64
Limited
UK
46
Deficient
17 LinkedIn
LinkedIn’s UGC data transparency relies on a Beta Researcher Access Program in the European Union under the DSA’s Article 40, with no equivalent resource available in Brazil or the UK. Advertising transparency is assessed through the LinkedIn Ad Library across all three regions, although data access regimes vary. During our assessment, a research access request was submitted but received no response, preventing empirical verification of the Researcher Access Program’s API. On the advertising side, the LinkedIn Ad Library API provides programmatic access to all ad types across the three regions, with data retained for up to one year after an ad’s last impression. However, key information—such as ad delivery periods and targeting criteria—is only verifiable in the EU. The tool’s graphical interface does not offer any data export functionality in any region, and persistent gaps include the absence of engagement metrics, advertiser verification status, AI-content labeling, and ad spending data. As a result, the advertising framework falls within the Deficient to Limited band globally, reflecting API availability offset by significant completeness gaps, while the UGC framework is Not Available outside the EU and remains unverifiable within it.
17.1 Transparency Assessment
17.2 User-Generated Content
Coverage: BR, EU, UK
17.2.1 Special Criteria
17.2.1.1 UGC_SC1: Does the platform provide an API that enables the structured extraction of public user-generated content data for independent analysis?
| Region | Answer | Note |
|---|---|---|
| BR | ❌ No | - |
| EU | ✅ Yes, but only for approved researchers | LinkedIn provides a Beta Researcher Access Program to comply with their legal requirements under article 40 of the European Union's Digital Services Act (DSA), which includes an API access. |
| UK | ❌ No | - |
17.2.1.2 UGC_SC2: Can the full scope of public content data be extracted through the platform’s API?
| Region | Answer | Note |
|---|---|---|
| BR | ❌ No | - |
| EU | ❌ No | We submitted a request to the LinkedIn Researcher Access Program in accordance with the platform’s documentation, but we never received any response. As a result, we cannot guarantee the proper functioning of its features or the quality of the data it returns, due to the impossibility of conducting empirical tests. |
| UK | ❌ No | - |
17.2.1.3 UGC_SC3: Is access to the platform’s API free of charge?
| Region | Answer | Note |
|---|---|---|
| BR | ❌ No | - |
| EU | ✅ Yes, but only for approved researchers | The LinkedIn Researcher Access Program does not impose any fees on researchers. |
| UK | ❌ No | - |
17.2.1.4 UGC_SC4: Does the platform offer a graphical interface for extracting data?
| Region | Answer | Note |
|---|---|---|
| BR | ❌ No | - |
| EU | ❌ No | The platform does not provide a graphical interface for extracting structured data on public user-generated content data. |
| UK | ❌ No | - |
17.2.2 Accessibility
17.2.2.1 UGC_OC1: Can the requested data be extracted directly from the platform’s API response?
| Region | Answer | Note |
|---|---|---|
| BR | ❌ No | - |
| EU | ❌ No | Verification was not possible because API access was unavailable at the time of assessment, due to a pending request and the absence of any response from the platform. |
| UK | ❌ No | - |
17.2.2.2 UGC_OC2: Does the platform’s API support renewable authentication mechanisms without risk of data loss?
| Region | Answer | Note |
|---|---|---|
| BR | ❌ No | - |
| EU | ❌ No | Verification was not possible because API access was unavailable at the time of assessment, due to a pending request and the absence of any response from the platform. |
| UK | ❌ No | - |
17.2.2.3 UGC_OC3: Does the platform’s API offer an endpoint for extracting data from an individual publication?
| Region | Answer | Note |
|---|---|---|
| BR | ❌ No | - |
| EU | ❌ No | Verification was not possible because API access was unavailable at the time of assessment, due to a pending request and the absence of any response from the platform. |
| UK | ❌ No | - |
17.2.2.5 UGC_OC5: Does the platform’s API provide an endpoint for extracting data based on search terms?
| Region | Answer | Note |
|---|---|---|
| BR | ❌ No | - |
| EU | ❌ No | Verification was not possible because API access was unavailable at the time of assessment, due to a pending request and the absence of any response from the platform. |
| UK | ❌ No | - |
17.2.2.6 UGC_OC6: Does the API use locale-neutral data representations?
| Region | Answer | Note |
|---|---|---|
| BR | ❌ No | - |
| EU | ❌ No | Verification was not possible because API access was unavailable at the time of assessment, due to a pending request and the absence of any response from the platform. |
| UK | ❌ No | - |
17.2.3 Compliance
17.2.3.1 UGC_OC7: Does the platform implement a proper deprecation strategy to avoid breaking client applications while rolling out major changes in the API?
| Region | Answer | Note |
|---|---|---|
| BR | ❌ No | - |
| EU | ❌ No | The LinkedIn Researcher API documentation does not provide a proper deprecation strategy. |
| UK | ❌ No | - |
17.2.3.2 UGC_OC8: Is the platform’s API documentation published in open access?
| Region | Answer | Note |
|---|---|---|
| BR | ❌ No | - |
| EU | ❌ No | The LinkedIn Researcher API documentation is partially available in open access; however, the full documentation, including detailed explanations and usage examples, is not publicly accessible. Given that previous researcher access documentation was made available to users only after approval under the applicable terms, it is likely that the complete documentation is not fully published in open access. As full Researcher API access was not granted at the time of this assessment, this material was therefore not visible. |
| UK | ❌ No | - |
17.2.3.3 UGC_OC9: Is the platform’s API documentation clearly written and exemplified?
| Region | Answer | Note |
|---|---|---|
| BR | ❌ No | - |
| EU | ❌ No | The open access LinkedIn Researcher API documentation is not clearly written and exemplified. |
| UK | ❌ No | - |
17.2.3.4 UGC_OC10: Does the platform’s documentation include or link to the API or data access terms of use?
| Region | Answer | Note |
|---|---|---|
| BR | ❌ No | - |
| EU | ✅ Yes | The LinkedIn Researcher API documentation links to its terms of use. |
| UK | ❌ No | - |
17.2.3.5 UGC_OC11: Does the platform’s API documentation detail the response format of each endpoint?
| Region | Answer | Note |
|---|---|---|
| BR | ❌ No | - |
| EU | ❌ No | The open access LinkedIn Researcher API documentation does not detail the response format of each endpoint. |
| UK | ❌ No | - |
17.2.3.6 UGC_OC12: Does the platform provide its API documentation in the official languages of the assessed region?
| Region | Answer | Note |
|---|---|---|
| BR | ❌ No | - |
| EU | ❌ No | While the open access LinkedIn Researcher API documentation is available in English, French, German, Spanish, Danish, Hungarian, Italian, Finnish, Italian, Romanian, Portuguese, Polish, Greek, Dutch, and Swedish, it is not available in all of the 24 official languages of the EU. |
| UK | ❌ No | - |
17.2.3.7 UGC_OC13: Does the platform’s API documentation detail the quota or rate limits applicable to each available endpoint?
| Region | Answer | Note |
|---|---|---|
| BR | ❌ No | - |
| EU | ❌ No | The open access LinkedIn Researcher API documentation does not detail the quota or rate limits applicable to each available endpoint. |
| UK | ❌ No | - |
17.2.3.8 UGC_OC14: Does the platform provide a way to label content that has been generated with artificial intelligence?
| Region | Answer | Note |
|---|---|---|
| BR | ❌ No | - |
| EU | ❌ No | Verification was not possible because API access was unavailable at the time of assessment, due to a pending request and the absence of any response from the platform. |
| UK | ❌ No | - |
17.2.4 Completeness
17.2.4.1 UGC_OC15: Can data from a publication’s comments be extracted using the platform’s API?
| Region | Answer | Note |
|---|---|---|
| BR | ❌ No | - |
| EU | ❌ No | Verification was not possible because API access was unavailable at the time of assessment, due to a pending request and the absence of any response from the platform. |
| UK | ❌ No | - |
17.2.4.2 UGC_OC16: Can data from temporary content be extracted through the platform’s API?
| Region | Answer | Note |
|---|---|---|
| BR | ❌ No | - |
| EU | ❌ No | Verification was not possible because API access was unavailable at the time of assessment, due to a pending request and the absence of any response from the platform. |
| UK | ❌ No | - |
17.2.4.3 UGC_OC17: Can historical data be extracted through the platform’s API?
| Region | Answer | Note |
|---|---|---|
| BR | ❌ No | - |
| EU | ❌ No | Verification was not possible because API access was unavailable at the time of assessment, due to a pending request and the absence of any response from the platform. |
| UK | ❌ No | - |
17.2.4.4 UGC_OC18: Is the number of requests allowed by the API sufficient for monitoring more than 10,000 publications in 24 hours?
| Region | Answer | Note |
|---|---|---|
| BR | ❌ No | - |
| EU | ❌ No | Verification was not possible because API access was unavailable at the time of assessment, due to a pending request and the absence of any response from the platform. |
| UK | ❌ No | - |
17.2.5 Consistency
17.2.5.1 UGC_OC19: Are the results returned by the API consistently reproducible?
| Region | Answer | Note |
|---|---|---|
| BR | ❌ No | - |
| EU | ❌ No | Verification was not possible because API access was unavailable at the time of assessment, due to a pending request and the absence of any response from the platform. |
| UK | ❌ No | - |
17.2.5.2 UGC_OC20: Is the data returned by the platform’s API consistent with the parameters and filters used in the request?
| Region | Answer | Note |
|---|---|---|
| BR | ❌ No | - |
| EU | ❌ No | Verification was not possible because API access was unavailable at the time of assessment, due to a pending request and the absence of any response from the platform. |
| UK | ❌ No | - |
17.2.6 Relevance
17.2.6.1 UGC_OC21: Does the data extracted by the platform’s API reflect what is displayed on its user interface?
| Region | Answer | Note |
|---|---|---|
| BR | ❌ No | - |
| EU | ❌ No | Verification was not possible because API access was unavailable at the time of assessment, due to a pending request and the absence of any response from the platform. |
| UK | ❌ No | - |
17.2.6.3 UGC_OC23: Does the platform’s API allow for filtering data based on content language?
| Region | Answer | Note |
|---|---|---|
| BR | ❌ No | - |
| EU | ❌ No | Verification was not possible because API access was unavailable at the time of assessment, due to a pending request and the absence of any response from the platform. |
| UK | ❌ No | - |
17.2.6.4 UGC_OC24: Does the platform’s API allow for filtering data by specific time periods?
| Region | Answer | Note |
|---|---|---|
| BR | ❌ No | - |
| EU | ❌ No | Verification was not possible because API access was unavailable at the time of assessment, due to a pending request and the absence of any response from the platform. |
| UK | ❌ No | - |
17.2.7 Timeliness
17.2.7.1 UGC_OC25: Can data from newly published content be extracted from the platform’s API in near real time?
| Region | Answer | Note |
|---|---|---|
| BR | ❌ No | - |
| EU | ❌ No | Verification was not possible because API access was unavailable at the time of assessment, due to a pending request and the absence of any response from the platform. |
| UK | ❌ No | - |
17.3 Advertising
Coverage: BR, EU, UK
17.3.1 Special Criteria
17.3.1.1 AD_SC1: Does the platform provide an API to access its ad repository and extract data on advertising content for independent analysis?
| Region | Answer | Note |
|---|---|---|
| BR | ✅ Yes, with full availability | Data from all types of ads can be retrieved through the LinkedIn Ad Library API and remains available for collection for up to one year after the ad’s last impression. |
| EU | ✅ Yes, with full availability | Data from all types of ads can be retrieved through the LinkedIn Ad Library API and remains available for collection for up to one year after the ad’s last impression. |
| UK | ✅ Yes, with full availability | Data from all types of ads can be retrieved through the LinkedIn Ad Library API and remains available for collection for up to one year after the ad’s last impression. |
17.3.1.2 AD_SC2: Does the platform provide a graphical user interface to its ad repository for extracting advertising content data?
| Region | Answer | Note |
|---|---|---|
| BR | ❌ No | Although the LinkedIn Ad Library GUI allows users to view ads served on the platform for up to one year after their last impression, it does not provide any means to export structured data. |
| EU | ❌ No | Although the LinkedIn Ad Library GUI allows users to view ads served on the platform for up to one year after their last impression, it does not provide any means to export structured data. |
| UK | ❌ No | Although the LinkedIn Ad Library GUI allows users to view ads served on the platform for up to one year after their last impression, it does not provide any means to export structured data. |
17.3.1.3 AD_SC3: Can data from both active and inactive ads be extracted?
| Region | Answer | Note |
|---|---|---|
| BR | ❌ No | Although LinkedIn claims that advertising data can be collected for up to one year after an ad stops running, it is not possible to verify the running period of ads that were served outside the European Union. Therefore, this item cannot be properly assessed. |
| EU | ✅ Yes, with full availability | Both the LinkedIn Ad Library GUI and API allow users to see the most recent date an ad was served, enabling verification that data can be retrieved for both active and inactive ads. |
| UK | ❌ No | Although LinkedIn claims that advertising data can be collected for up to one year after an ad stops running, it is not possible to verify the running period of ads that were served outside the European Union. Therefore, this item cannot be properly assessed. |
17.3.2 Accessibility
17.3.2.1 AD_OC1: Does the platform provide a GUI for accessing and visualizing its ad repository?
| Region | Answer | Note |
|---|---|---|
| BR | ✅ Yes, with full availability | The LinkedIn Ad Library GUI allows users to query and filter ads served to LinkedIn users for up to one year after their last impression. |
| EU | ✅ Yes, with full availability | The LinkedIn Ad Library GUI allows users to query and filter ads served to LinkedIn users for up to one year after their last impression. |
| UK | ✅ Yes, with full availability | The LinkedIn Ad Library GUI allows users to query and filter ads served to LinkedIn users for up to one year after their last impression. |
17.3.2.2 AD_OC2: Is access to the platform’s ad repository free of charge?
| Region | Answer | Note |
|---|---|---|
| BR | ✅ Free API and GUI access | Access to the LinkedIn Ad Library, via both the API and the GUI, is free of charge. |
| EU | ✅ Free API and GUI access | Access to the LinkedIn Ad Library, via both the API and the GUI, is free of charge. |
| UK | ✅ Free API and GUI access | Access to the LinkedIn Ad Library, via both the API and the GUI, is free of charge. |
17.3.2.3 AD_OC3: Can the requested data be extracted directly from the ad repository response?
| Region | Answer | Note |
|---|---|---|
| BR | ❌ No | The LinkedIn Ad Library API returns only the ad URL and information about the advertiser—including their name, page URL, and funder—but does not provide the ad creative or its publication date itself. |
| EU | ❌ No | The LinkedIn Ad Library API returns only the ad URL, the period during which it ran and information about the advertiser—including their name, page URL, publication date and funder—but does not provide the ad creative itself. |
| UK | ❌ No | The LinkedIn Ad Library API returns only the ad URL and information about the advertiser—including their name, page URL, and funder—but does not provide the ad creative or its publication date itself. |
17.3.2.4 AD_OC4: Does the platform’s ad repository API provide a form of authentication that allows for renewal without the risk of data loss?
| Region | Answer | Note |
|---|---|---|
| BR | ✅ Yes | The LinkedIn Ad Library API provides a form of authentication that allows for renewal without the risk of data loss. |
| EU | ✅ Yes | The LinkedIn Ad Library API provides a form of authentication thatallows for renewal without the risk of data loss. |
| UK | ✅ Yes | The LinkedIn Ad Library API provides a form of authentication that allows for renewal without the risk of data loss. |
17.3.2.5 AD_OC5: Can data from an individual ad be retrieved from the platform?
| Region | Answer | Note |
|---|---|---|
| BR | ✅ Yes, through the GUI | Through the LinkedIn Ad Library GUI, it is possible to access the page of a specific ad. By contrast, the API does not allow ads to be retrieved by their ID. |
| EU | ✅ Yes, through the GUI | Through the LinkedIn Ad Library GUI, it is possible to access the page of a specific ad. By contrast, the API does not allow ads to be retrieved by their ID. |
| UK | ✅ Yes, through the GUI | Through the LinkedIn Ad Library GUI, it is possible to access the page of a specific ad. By contrast, the API does not allow ads to be retrieved by their ID. |
17.3.2.6 AD_OC6: Can data from ads served by a specific advertiser be retrieved from the platform?
| Region | Answer | Note |
|---|---|---|
| BR | ❌ No | On both LinkedIn Ad Library GUI and API, the advertiser search function retrieves only records containing the queried keyword, rather than allowing direct filtering by a specific advertiser via their username or unique identifier. |
| EU | ❌ No | On both LinkedIn Ad Library GUI and API, the advertiser search function retrieves only records containing the queried keyword, rather than allowing direct filtering by a specific advertiser via their username or unique identifier. |
| UK | ❌ No | On both LinkedIn Ad Library GUI and API, the advertiser search function retrieves only records containing the queried keyword, rather than allowing direct filtering by a specific advertiser via their username or unique identifier. |
17.3.2.7 AD_OC7: Can ad data be retrieved from the platform using search terms?
| Region | Answer | Note |
|---|---|---|
| BR | ✅ Yes, through both GUI and API | It is possible to use keywords to perform searches both through the LinkedIn Ad Library GUI and API. |
| EU | ✅ Yes, through both GUI and API | It is possible to use keywords to perform searches both through the LinkedIn Ad Library GUI and API. |
| UK | ✅ Yes, through both GUI and API | It is possible to use keywords to perform searches both through the LinkedIn Ad Library GUI and API. |
17.3.2.8 AD_OC8: Does the platform use locale-neutral data representations?
| Region | Answer | Note |
|---|---|---|
| BR | ❌ No | This item cannot be verified because time-related data are not available for ads served outside the European Union in the LinkedIn Ad Library. |
| EU | ✅ Yes, through the API | Timestamps retrieved through the LinkedIn Ad Library API follow the Unix format (e.g., 1763337597116). By contrast, the LinkedIn Ad Library GUI returns abbreviated and extended date strings (e.g., “Jan 13, 2026 to Jan 15, 2026”), which hinders both readability and automated processing. |
| UK | ❌ No | This item cannot be verified because time-related data are not available for ads served outside the European Union in the LinkedIn Ad Library. |
17.3.3 Completeness
17.3.3.1 AD_OC9: Does the platform provide data that allows the identification of advertisers who ran ads?
| Region | Answer | Note |
|---|---|---|
| BR | ✅ Yes, through both GUI and API | The LinkedIn Ad Library provides URLs for the pages and profiles of the entities that ran the ads. |
| EU | ✅ Yes, through both GUI and API | The LinkedIn Ad Library provides URLs for the pages and profiles of the entities that ran the ads. |
| UK | ✅ Yes, through both GUI and API | The LinkedIn Ad Library provides URLs for the pages and profiles of the entities that ran the ads. |
17.3.3.2 AD_OC10: Does the platform provide data on the funders who paid for ads?
| Region | Answer | Note |
|---|---|---|
| BR | ✅ Yes, through both GUI and API | The LinkedIn Ad Library provides the registered names of the ads’ funders. |
| EU | ✅ Yes, through both GUI and API | The LinkedIn Ad Library provides the registered names of the ads’ funders. |
| UK | ✅ Yes, through both GUI and API | The LinkedIn Ad Library provides the registered names of the ads’ funders. |
17.3.3.3 AD_OC11: Does the platform provide data on the period during which ads were served?
| Region | Answer | Note |
|---|---|---|
| BR | ❌ No | The LinkedIn Ad Library does not provide any data on the running period of ads that were only served outside the European Union. |
| EU | ✅ Yes, through both GUI and API | For ads served to users in the European Union, the LinkedIn Ad Library provides the time period during which they ran, both through the API and the GUI. |
| UK | ❌ No | The LinkedIn Ad Library does not provide any data on the running period of ads that were only served outside the European Union. |
17.3.3.4 AD_OC12: Does the platform provide data on user engagement with ads?
| Region | Answer | Note |
|---|---|---|
| BR | ❌ No | The LinkedIn Ad Library does not provide any data on user engagement with ads. |
| EU | ❌ No | The LinkedIn Ad Library does not provide any data on user engagement with ads. |
| UK | ❌ No | The LinkedIn Ad Library does not provide any data on user engagement with ads. |
17.3.3.5 AD_OC13: Does the platform indicate whether ads were placed by verified or unverified advertisers?
| Region | Answer | Note |
|---|---|---|
| BR | ❌ No | The LinkedIn Ad Library does not provide any data on advertisers’ verification status. |
| EU | ❌ No | The LinkedIn Ad Library does not provide any data on advertisers’ verification status. |
| UK | ❌ No | The LinkedIn Ad Library does not provide any data on advertisers’ verification status. |
17.3.4 Compliance
17.3.4.1 AD_OC14: Does the platform flag ads that were removed due to violations of its guidelines or relevant legislation?
| Region | Answer | Note |
|---|---|---|
| BR | ❌ No | Although moderated ads can be identified through the LinkedIn Ad Library, the platform provides no information about their content or advertiser, only their unique ID. Moreover, it offers no indication of the moderation date or the reasons for moderation. |
| EU | ✅ Yes, through both GUI and API | Although restricted and moderated ads are difficult to search for and locate, they remain accessible through both the LinkedIn Ad Library API and GUI. In these cases, the interface specifies when the ads were last shown to users and includes a message explaining the reason for moderation. However, the ad content itself is not available for viewing. |
| UK | ❌ No | Although moderated ads can be identified through the LinkedIn Ad Library, the platform provides no information about their content or advertiser, only their unique ID. Moreover, it offers no indication of the moderation date or the reasons for moderation. |
17.3.4.2 AD_OC15: Does the platform indicate whether ad content was generated using artificial intelligence?
| Region | Answer | Note |
|---|---|---|
| BR | ❌ No | The LinkedIn Ad Library does not provide any information regarding the use of generative AI in the creation or manipulation of ad content. |
| EU | ❌ No | The LinkedIn Ad Library does not provide any information regarding the use of generative AI in the creation or manipulation of ad content. |
| UK | ❌ No | The LinkedIn Ad Library does not provide any information regarding the use of generative AI in the creation or manipulation of ad content. |
17.3.4.3 AD_OC16: Is the platform’s ad repository documentation published in open access?
| Region | Answer | Note |
|---|---|---|
| BR | ✅ Yes, both API and GUI documentation | Any user can access LinkedIn Ad Library’s documentation. Some public documentation for the GUI is available in the form of an FAQ. |
| EU | ✅ Yes, both API and GUI documentation | Any user can access LinkedIn Ad Library’s documentation. Some public documentation for the GUI is available in the form of an FAQ. |
| UK | ✅ Yes, both API and GUI documentation | Any user can access LinkedIn Ad Library’s documentation. Some public documentation for the GUI is available in the form of an FAQ. |
17.3.4.4 AD_OC17: Is the platform’s ad repository documentation clearly written and exemplified?
| Region | Answer | Note |
|---|---|---|
| BR | ✅ Yes, the GUI documentation | The LinkedIn Ad Library API’s documentation lacks sufficient explanations and references, as it provides only a single response example, limited to ads served in European Union countries. |
| EU | ✅ Yes, both API and GUI documentation | From the perspective of a European user, the LinkedIn Ad Library API documentation is comparatively more informative, as it includes a concrete response example for ads served in European Union countries. While limited in scope, this example offers clearer guidance on the structure and fields of the API’s output for EU-based transparency data. |
| UK | ✅ Yes, the GUI documentation | The LinkedIn Ad Library API’s documentation lacks sufficient explanations and references, as it provides only a single response example, limited to ads served in European Union countries. |
17.3.4.5 AD_OC18: Does the platform’s ad repository documentation include or link to its terms of use?
| Region | Answer | Note |
|---|---|---|
| BR | ❌ No | The LinkedIn Ad Library does not reference any specific terms of use for either its API or its GUI. |
| EU | ❌ No | The LinkedIn Ad Library does not reference any specific terms of use for either its API or its GUI. |
| UK | ❌ No | The LinkedIn Ad Library does not reference any specific terms of use for either its API or its GUI. |
17.3.4.6 AD_OC19: Does the platform provide its ad repository documentation in the official languages of the assessed region?
| Region | Answer | Note |
|---|---|---|
| BR | ✅ Yes, both API and GUI documentation | The LinkedIn Ad Library’s documentation is displayed in the language defined by the user. |
| EU | ✅ Yes, both API and GUI documentation | The LinkedIn Ad Library’s documentation is displayed in the language defined by the user. |
| UK | ✅ Yes, both API and GUI documentation | The LinkedIn Ad Library’s documentation is displayed in the language defined by the user. |
17.3.4.7 AD_OC20: Does the platform implement a proper deprecation strategy to avoid breaking client applications while rolling out major changes in the API?
| Region | Answer | Note |
|---|---|---|
| BR | ❌ No | The LinkedIn Ad Library API’s documentation does not describe any deprecation strategy intended to prevent breaking changes in client applications. |
| EU | ❌ No | The LinkedIn Ad Library API’s documentation does not describe any deprecation strategy intended to prevent breaking changes in client applications. |
| UK | ❌ No | The LinkedIn Ad Library API’s documentation does not describe any deprecation strategy intended to prevent breaking changes in client applications. |
17.3.4.8 AD_OC21: Does the platform’s ad repository API documentation detail the response format of each endpoint?
| Region | Answer | Note |
|---|---|---|
| BR | ✅ Yes | The LinkedIn Ad Library API’s documentation details the response format of its sole available endpoint. |
| EU | ✅ Yes | The LinkedIn Ad Library API’s documentation details the response format of its sole available endpoint. |
| UK | ✅ Yes | The LinkedIn Ad Library API’s documentation details the response format of its sole available endpoint. |
17.3.4.9 AD_OC22: Does the platform’s ad repository API documentation detail the quota or rate limits applicable to each available endpoint?
| Region | Answer | Note |
|---|---|---|
| BR | ❌ No | The LinkedIn Ad Library API’s documentation does not specify any usage quotas or rate limits. |
| EU | ❌ No | The LinkedIn Ad Library API’s documentation does not specify any usage quotas or rate limits. |
| UK | ❌ No | The LinkedIn Ad Library API’s documentation does not specify any usage quotas or rate limits. |
17.3.5 Consistency
17.3.5.1 AD_OC23: Does the data retrieved by the API reflect what is displayed on the platform’s ad repository GUI?
| Region | Answer | Note |
|---|---|---|
| BR | ❌ No | Although the data retrieved via the LinkedIn Ad Library API broadly corresponds to what is displayed in the GUI, the platform does not provide sufficient information or mechanisms to enable a proper comparison between the two. The GUI search interface presents a preview of each ad’s media and text, whereas the API returns no information about ad content, providing only the ad’s URL and advertiser metadata. |
| EU | ❌ No | Although the data retrieved via the LinkedIn Ad Library API broadly corresponds to what is displayed in the GUI, the platform does not provide sufficient information or mechanisms to enable a proper comparison between the two. The GUI search interface presents a preview of each ad’s media and text, whereas the API returns no information about ad content, providing only the ad’s URL, advertiser metadata, and the period during which the ad ran |
| UK | ❌ No | Although the data retrieved via the LinkedIn Ad Library API broadly corresponds to what is displayed in the GUI, the platform does not provide sufficient information or mechanisms to enable a proper comparison between the two. The GUI search interface presents a preview of each ad’s media and text, whereas the API returns no information about ad content, providing only the ad’s URL and advertiser metadata. |
17.3.5.2 AD_OC24: Are the results returned by the platform consistently reproducible?
| Region | Answer | Note |
|---|---|---|
| BR | ✅ Yes, through both GUI and API | We conducted a test using the LinkedIn Ad Library API by issuing five identical requests with the same parameters, saving each response to a separate file, and comparing whether all ads appeared consistently across the files. We observed that the full set of ads was present in every response. The GUI was likewise found to return consistent results across repeated queries. |
| EU | ✅ Yes, through both GUI and API | We conducted a test using the LinkedIn Ad Library API by issuing five identical requests with the same parameters, saving each response to a separate file, and comparing whether all ads appeared consistently across the files. We observed that the full set of ads was present in every response. The GUI was likewise found to return consistent results across repeated queries. |
| UK | ✅ Yes, through both GUI and API | We conducted a test using the LinkedIn Ad Library API by issuing five identical requests with the same parameters, saving each response to a separate file, and comparing whether all ads appeared consistently across the files. We observed that the full set of ads was present in every response. The GUI was likewise found to return consistent results across repeated queries. |
17.3.5.3 AD_OC25: Is the data returned by the platform consistent with the parameters and filters used in the request?
| Region | Answer | Note |
|---|---|---|
| BR | ❌ No | This item cannot be verified through either the LinkedIn Ad Library API or GUI. Because the platform provides no time-related data for ads that ran outside the European Union, it is impossible to assess whether this parameter is correctly applied. Moreover, since the API does not expose ad creative content, it is also not possible to verify whether ads actually match the queried keywords. |
| EU | ✅ Yes, through the GUI | Because the LinkedIn Ad Library API does not return any information about ad creatives, it is not possible to verify whether the ads actually correspond to the queried keywords. This verification is, however, possible through the LinkedIn Ad Library GUI, where users can directly assess whether the returned ads match both the queried keywords and the specified time period. |
| UK | ❌ No | This item cannot be verified through either the LinkedIn Ad Library API or GUI. Because the platform provides no time-related data for ads that ran outside the European Union, it is impossible to assess whether this parameter is correctly applied. Moreover, since the API does not expose ad creative content, it is also not possible to verify whether ads actually match the queried keywords. |
17.3.6 Relevance
17.3.6.1 AD_OC26: Does the platform allow the use of temporal filters to retrieve data on ads?
| Region | Answer | Note |
|---|---|---|
| BR | ❌ No | The LinkedIn Ad Library allows the application of a time period filter. However, because time-related data is not available for ads that ran outside the European Union, this feature cannot be fully or reliably assessed. |
| EU | ✅ Yes, through both GUI and API | The LinkedIn Ad Library supports the application of a time period filter through both its API and GUI. |
| UK | ❌ No | The LinkedIn Ad Library allows the application of a time period filter. However, because time-related data is not available for ads that ran outside the European Union, this feature cannot be fully or reliably assessed. |
17.3.6.2 AD_OC27: Does the platform allow filtering advertising data by ad category?
| Region | Answer | Note |
|---|---|---|
| BR | ❌ No | The LinkedIn Ad Library does not allow data to be filtered by ad category. |
| EU | ❌ No | The LinkedIn Ad Library does not allow data to be filtered by ad category. |
| UK | ❌ No | The LinkedIn Ad Library does not allow data to be filtered by ad category. |
17.3.6.3 AD_OC28: Does the platform allow filtering advertising data by geographic location?
| Region | Answer | Note |
|---|---|---|
| BR | ❌ No | The LinkedIn Ad Library only allows data to be filtered by country. |
| EU | ❌ No | The LinkedIn Ad Library only allows data to be filtered by country. |
| UK | ❌ No | The LinkedIn Ad Library only allows data to be filtered by country. |
17.3.7 Accuracy
17.3.7.1 AD_OC29: Does the platform provide age and gender data on the audiences of ads?
| Region | Answer | Note |
|---|---|---|
| BR | ❌ No | The LinkedIn Ad Library does not provide any age or gender information about an ad’s audience. |
| EU | ❌ No | The LinkedIn Ad Library does not provide any age or gender information about an ad’s audience. |
| UK | ❌ No | The LinkedIn Ad Library does not provide any age or gender information about an ad’s audience. |
17.3.7.2 AD_OC30: Does the platform provide subnational geographic data on the audience reached by ads?
| Region | Answer | Note |
|---|---|---|
| BR | ❌ No | The LinkedIn Ad Library does not provide any subnational location data about an ad’s audience. |
| EU | ❌ No | The LinkedIn Ad Library does not provide any subnational location data about an ad’s audience. |
| UK | ❌ No | The LinkedIn Ad Library does not provide any subnational location data about an ad’s audience. |
17.3.7.3 AD_OC31: Does the platform include data on audience targeting criteria defined by advertisers?
| Region | Answer | Note |
|---|---|---|
| BR | ❌ No | The LinkedIn Ad Library provides audience targeting criteria data only for ads that were served within the European Union. |
| EU | ❌ No | Both the LinkedIn Ad Library API and GUI display some of the targeting criteria applied to ads. However, even when targeting is used and the API responses indicate its application, these criteria are not described in sufficient detail. As a result, the platform does not meet the requirements for this item. |
| UK | ❌ No | The LinkedIn Ad Library provides audience targeting criteria data only for ads that were served within the European Union. |
17.3.7.4 AD_OC32: Does the platform provide granular volume ranges for ad impressions?
| Region | Answer | Note |
|---|---|---|
| BR | ❌ No | The LinkedIn Ad Library provides impressions data only for ads that were served within the European Union. |
| EU | ❌ No | The LinkedIn Ad Library provides data on ad impressions, but not at a sufficiently granular level. |
| UK | ❌ No | The LinkedIn Ad Library provides impressions data only for ads that were served within the European Union. |
17.3.7.5 AD_OC33: Does the platform provide granular investment ranges for ad spending?
| Region | Answer | Note |
|---|---|---|
| BR | ❌ No | The LinkedIn Ad Library does not provide any data on ad spending. |
| EU | ❌ No | The LinkedIn Ad Library does not provide any data on ad spending. |
| UK | ❌ No | The LinkedIn Ad Library does not provide any data on ad spending. |