LinkedIn advertising is a powerful B2B marketing tool that helps businesses generate qualified leads and measure campaign performance. However, it uses customers’ data that is protected by data privacy regulations. Thus, B2B marketers must ensure their conversion tracking practices respect user consent and comply with applicable privacy laws.

The two main tracking tools to measure advertising performance are the LinkedIn Insight Tag and LinkedIn Conversions API. While both help businesses measure conversions, they collect and transmit data differently. As a result, compliance procedures should differ.

This guide explains how LinkedIn tracking works, outlines essential consent requirements, and provides a practical checklist for LinkedIn consent management.

Understanding LinkedIn Insight Tag and Conversions API: What B2B Teams Need to Know

Although the LinkedIn Insight Tag and Conversions API serve similar measurement goals, they collect data differently.

What is the LinkedIn Insight Tag?

The LinkedIn Insight Tag is a JavaScript tracking code that is installed on websites and measures visitor interactions and advertising performance.

It helps marketers understand what happens after someone interacts with a LinkedIn advertisement, providing insights into website visits, conversions, and audience characteristics.

The Insight Tag could be used for several important B2B marketing activities:

• Conversion tracking: Measure website actions, such as demo requests, content downloads, and contact form submissions.
• Website retargeting: Track previous website visitors and build a database for subsequent LinkedIn advertising campaigns.
• Audience insights: Help you understand website visitors' characteristics, such as industries, job functions, age, interests, and company information.
• Campaign optimization: Identify which advertising campaigns are the most effective to reach business goals.

The Insight Tag uses cookies and other identifiers to track visitors. It sets cookies on visitors’ browsers and can collect user information such as visited URLs, referral sources, IP addresses, browser characteristics, and timestamps.

Thus, businesses need user consent to use The Insight Tag. In EU, LinkedIn conversion tracking must remain disabled by default until the visitor provides valid consent.

What Is LinkedIn Conversions API?

The LinkedIn Conversions API is a server-side tracking solution that lets businesses send conversion data directly from their systems to LinkedIn. Unlike the Insight Tag, which collects data through browser-based tracking, Conversions API doesn’t use cookies for tracking.

LinkedIn Conversions API allows organizations to share qualifying events from backend systems, customer relationship management (CRM) platforms, and other supported data sources.

With Conversions API, marketers can connect eligible online and offline conversion events to LinkedIn campaigns. This is particularly valuable for B2B companies with long sales cycles, where conversions often happen after the initial website interaction. Businesses can see how theitheir campaigns influenced actions taken on theitheir website, sales completed over the phone, or leads collected in person.

LinkedIn Conversions API could be used to:

• Send marketing data directly from your server to LinkedIn to measure the performance of your LinkedIn campaigns;
• Track offline conversions and CRM-based sales activities;
• Reduce reliance on browser-based tracking technologies;
• Improve measurements for campaigns with long sales cycles and measure lead quality beyond initial form submissions;
• Integrate multiple types of conversion data;
• Increase performance by making a more efficient Cost Per Action;
• Respect user privacy using a secure data connection that doesn’t rely on cookie-based tracking.

LinkedIn recommends using Conversions API alongside the Insight Tag to improve conversion measurement. Using both tools to report the same conversion improves data quality.

However, server-side tracking does not eliminate consent obligations. To reach LinkedIn Conversions API GDPR compliance, businesses must still establish an appropriate legal basis or obtain user consent.

Consent Requirements for LinkedIn Tracking Under GDPR and Privacy Regulations

The GDPR regulates the processing of personal data, including information that can directly or indirectly identify an individual. When businesses use the LinkedIn Insight Tag or Conversions API, they may collect IP addresses, online identifiers, contact details, conversion activity, and other Personal Information.

Under the GDPR, every processing activity involving personal data requires an appropriate lawful basis.

Cookie Consent requirements

LinkedIn Insight Tag consent requirements include:

• Explicit cookie consent
  eprivacy Directive and GDPR require businesses to obtain valid, prior, and explicit opt-in consent from visitors in the EEA before the LinkedIn Insight Tag sets marketing and analytics cookies.
• Cookie blocking
  The LinkedIn Insight Tag should be blocked by default until the necessary consent is received.
• Cookie Banner
  Websites must provide a Cookie Banner so that visitors can accept or reject non-essential tracking.
• Granular control
  Users must be able to accept and reject specific categories of cookies separately.
• Consent withdrawal
  Users must be able to withdraw consent as easily as they gave it, and businesses must stop collecting and processing any collected personal data immediately.
• Consent recording
  Websites must record user consent preferences.

Because LinkedIn's Insight Tag uses cookies and other website trackers, businesses need to obtain prior consent for advertising and analytics.

Under GDPR and the eprivacy Directive, consent must be:

• Freely given: Users must have a genuine choice without inappropriate pressure.
• Specific: Users must be able to consent to specific processing purposes and reject other, non-related purposes.
• Informed: Users should understand what data businesses collect, why they collect and process it, and who receives it.
• Unambiguous: Consent must involve a clear affirmative action.
• Withdrawable: Users must be able to withdraw consent as easily as they provided it.

Businesses that use strictly First-party data on aggregated ad delivery (such as total clicks and impressions) for reporting metrics may rely on legitimate interest. In contrast, detailed conversion tracking and audience building require valid user consent.

Transparency and Privacy Policy requirements

B2B organizations should clearly explain how they use LinkedIn tracking technologies.

A privacy notice should therefore provide relevant information about:

• The use of LinkedIn Insight Tag and Conversions API.
• The categories of personal data businesses collect and share.
• The purposes of conversion tracking, advertising measurement, and retargeting.
• Applicable lawful bases for processing.
• Relevant recipients and international data transfers.
• Data retention practices.
• Methods for users to exercise their privacy rights and manage consent preferences.
• The identity of the business and contact details for personal data management.

LinkedIn states that advertisers are responsible for obtaining user consent before sharing user data with the platform. 

For businesses operating across multiple markets, it is important to evaluate local privacy requirements. Different jurisdictions may have different privacy requirements for tracking and marketing.

To manage user consent properly, websites should install a Consent Management Platform (CMP) and integrate it with their tracking implementation so it blocks non-essential tracking before valid consent is obtained.

CookieScript CMP is a professional tool for consent management. It delivers the right balance of compliance, affordability, and ease of use. You’ll get a fully compliant CMP for as little as €8 per month/ per domain for basic features or for €19 per month/ per domain for full compliance with global privacy laws.

CookieScript CMP offers the following features:

• Integrations with CMS platforms like Magento, WordPress, Shopify, etc.
• Cookie banner customization
• Google Consent Mode v2 integration
• IAB TCF v2.2 integration
• Google Tag Manager integration
• Certification by Google
• CookieScript API
• Cookie Scanner
• Consent recordings
• Third-party cookie blocking
• Geo-targeting 
• Self-hosted code 
• Cookie banner sharing 
• Cross-domain cookie consent sharing 

LinkedIn Insight Tag and Conversions API Consent Checklist for B2B Marketers

A structured consent checklist helps businesses identify privacy risks related to LinkedIn Insight Tag, Conversions API, and other tracking tools.

The following checklist covers essential areas of consent collection, tracking configuration, data governance, and monitoring.

1. Audit your current LinkedIn tracking setup

First, you should know how LinkedIn tracking is currently implemented across your website and marketing systems. This audit should identify all data that LinkedIn Insight Tag and Conversions API collect, how they collect it, which systems receive LinkedIn data, and whether you have valid consent for this type of data.

Audit your existing setup:

• Identify pages where the LinkedIn Insight Tag is installed.
• Review tags deployed through Google Tag Manager or other tag management systems.
• Document all conversion events transmitted through Conversions API.
• Identify CRM platforms and third-party integrations sending data to LinkedIn.
• Check that tracking does not reveal sensitive Personal Information to third parties.

2. Implement a reliable Consent Management Platform (CMP)

A CMP helps organizations collect, store, and manage visitors' privacy preferences.

Implement a reliable CMP, such as CookieScript, and configure it to support relevant GDPR and ePrivacy requirements.

A CMP must:

• Provide a cookie notice that details your data collection and management practices.
• Explain to visitors that your website uses LinkedIn Insight Tag and Conversions API for advertising and analytics purposes.
• Provide a Cookie Banner that allows users to accept, reject, or customize non-essential tracking.
• Block LinkedIn Insight Tag before required consent is granted.
• Allow users to withdraw their consent.
• Store user consent preferences.

3. Configure consent-aware LinkedIn Insight Tag tracking

The LinkedIn Insight Tag should be integrated with the website's CMP.

Make sure you configure LinkedIn Insight Tag tracking and record consent choices correctly:

• Connect the Insight Tag to the appropriate advertising consent category.
• Prevent the tag from loading or collecting non-essential tracking data before consent.
• Check that conversion events don’t transmit consent restrictions.
• Review First-party cookie and enhanced conversion tracking settings.
• Test LinkedIn tracking behavior when users accept, reject, or withdraw consent.

Pay particular attention to automatic website event collection and enhanced matching features, since these can behave differently than other settings which you set manually.

4. Configure LinkedIn Conversions API

You should also control server-side tracking.

Even when browser-based tracking is disabled, a backend system may still send conversion data if the settings don’t restrict.

Control LinkedIn Conversions API:

• Map the personal data fields included in Conversions API requests.
• Identify and document the lawful basis for each conversion data-sharing purpose.
• Obtain valid consent before transmitting events (where consent is required).
• Anonymize data by removing personal identifiers.
• Make sure users can withdraw their consent.
• Check that integration providers comply with privacy regulations.

The key principle: server-side tracking must respect applicable privacy choices rather than trying to bypass them.

5. Keep accurate consent records

Record user consent for proof of compliance.

Consent records should contain details about consent, including when consent was granted or withdrawn, which purposes the individual agreed to, and the current version of the consent notice.

Link relevant consent preferences to CRM and server-side workflows so that third parties also respect user consent.

For B2B businesses with several marketing systems, a consistent consent record can also help avoid contradictions between website tracking and CRM-based data sharing.

6. Review conversion deduplication and data accuracy

When you use the Insight Tag and Conversions API together, businesses may receive the same conversion through both browser-side and server-side systems.

To keep conversion reporting accurate, perform deduplication:

• Configure LinkedIn conversion rules for browser-side and server-side sources.
• Use matching event IDs for conversions reported through both tracking methods.
• Ensure duplicate conversions aren't counted twice.
• Review conversion reporting in LinkedIn Campaign Manager.

7. Regularly review privacy and compliance

Consent compliance isn't a one-time event; it needs regular review, especially after website changes, new integrations, and updated conversion events. Privacy requirements are also changing.

Test tracking whenever website tags, APIs, or CMP configurations change.

Schedule periodic reviews of LinkedIn tracking and consent settings to ensure privacy notices align with actual data collection practices and that third-party marketing integrations and data-sharing agreements remain valid.

Businesses running LinkedIn campaigns across several countries should also check that privacy requirements follow applicable jurisdictions.

In conclusion, the goal of browser and server-side tracking is not simply to collect more conversion data, but to collect and use data in a lawful, transparent, and compliant way. LinkedIn advertising compliance helps B2B businesses balance marketing effectiveness with their customers' privacy obligations and expectations.

Frequently Asked Questions

Does LinkedIn Conversions API require Consent?

Although Conversions API sends information from an organization's server rather than directly from a visitor's browser, the processing may still involve personal data. Therefore, businesses need an appropriate lawful basis or valid consent before collecting or sharing personal data through Conversions API.

How to implement LinkedIn Insight Tag with GDPR consent?

Install the LinkedIn Insight Tag through Google Tag Manager and integrate the tag with a Consent Management Platform (CMP). Then, configure your CMP to categorize LinkedIn tracking under advertising or marketing cookies, allow visitors to accept, reject, or withdraw consent, and block non-essential tracking before consent. Update your privacy and cookie policies to explain how LinkedIn collects and processes personal data and test your implementation to verify that the Insight Tag only fires after consent.

How to manage consent for LinkedIn server-side tracking?

First, share personal data through the LinkedIn Conversions API only when you have a valid legal basis. Then, integrate a Consent Management Platform (CMP) like CookieScript with your website, CRM, and server-side tracking systems to capture and communicate user consent preferences. Where consent is required, configure your server-side tracking to prevent sending conversion data to LinkedIn until valid consent is obtained. Maintain accurate consent records, respect consent withdrawals, and avoid sharing unnecessary personal information.

What are LinkedIn Conversions API consent requirements for B2B?

B2B businesses must collect and share personal data in compliance with GDPR. Establish a valid legal basis for processing, obtain user consent where required, and clearly explain how conversion data is shared with LinkedIn. Also maintain consent records, honor withdrawal requests, and practice data minimization. Use a CMP like CookieScript to manage user consent.