LinkedIn Insight Tag needs consent before it loads (KVKK/GDPR)

The LinkedIn Insight Tag drops advertising cookies to enable B2B retargeting, conversion tracking and audience insights. On page load, that is advertising processing without a legal basis.

Why it matters

The Insight Tag exists to profile visitors for ads and to match them to LinkedIn members — non-essential by definition, so prior consent is required (KVKK Art. 5 / GDPR Art. 6 / ePrivacy Art. 5(3)). It also sends data to LinkedIn in the US, engaging transfer rules. Loading it before a choice is made means the advertising cookies are set the instant the page opens.

How to fix it

Do not inject the Insight Tag on load. Set the partner ID and load snap.licdn.com only from your consent accept callback. A visitor who rejects advertising should generate no requests to snap.licdn.com.

<!-- Do NOT load on page load. Only inside the Accept handler: -->
function onConsentAccepted() {
  window._linkedin_partner_id = 'YOUR_PARTNER_ID';
  window._linkedin_data_partner_ids = window._linkedin_data_partner_ids || [];
  window._linkedin_data_partner_ids.push(window._linkedin_partner_id);
  var s = document.createElement('script');
  s.async = true;
  s.src = 'https://snap.licdn.com/li.lms-analytics/insight.min.js';
  document.head.appendChild(s);
}

Official sources

• KVKK — Law No. 6698 (official full text, mevzuat.gov.tr)
• KVKK — Kişisel Verileri Koruma Kurumu (Turkish DPA)
• GDPR — full regulation, article by article
• ePrivacy Directive 2002/58/EC — cookies, Art. 5(3)
• EDPB — guidelines on consent & cookies

Links to primary legislation for reference. PrivaScan is not affiliated with these bodies; this is information, not legal advice.

Related guides

• Stop Google Analytics from loading before consent (KVKK/GDPR) KVKK m.5 · GDPR Art. 6 · ePrivacy Art. 5(3)
• Gate Google Tag Manager behind consent KVKK m.5 · GDPR Art. 6 · ePrivacy Art. 5(3)
• Load the Meta (Facebook) Pixel only after consent KVKK m.5 · GDPR Art. 6 · Art. 26 (joint controller)
• Session recording (Hotjar, Clarity, Yandex) needs explicit consent KVKK m.5 · GDPR Art. 6 · Art. 9 risk

These guides cover automated checks for trackers, cookies and data flows. A full privacy review also needs legal input.