Conversion ID: 1
Demo request
The main call to action on a landing page.
Not fired yet.
Analytics Lab / Instrumentation
The Insight Tag records page views and conversions for LinkedIn ads. Each conversion is created in
Campaign Manager, which assigns it a numeric ID. The page then fires
lintrk('track', { conversion_id: ID }) when the action happens. Use the controls
below to see the call each interaction would make.
The tag call only needs conversion_id. The extra fields on each card show the context the
page has at that moment. A fixed conversion value can be set on the conversion in Campaign Manager.
Per-event value and currency, hashed identifiers and offline events are sent server side through the
Conversions API.
Each card fires one lintrk('track') call. LinkedIn reports conversions for ad attribution,
so in production you would tag business outcomes such as leads, sign-ups and purchases. The later
sections apply the same pattern to smaller interactions.
Buttons and forms that create leads.
Conversion ID: 1
The main call to action on a landing page.
Not fired yet.
Conversion ID: 4
Fires when a visitor books a sales call. Compare it with offline conversions sent through the Conversions API.
Not fired yet.
Conversion ID: 3
A short lead form. The form values are added to the payload on submit. The hashed email is a placeholder; the Conversions API expects a SHA-256 hash.
Not fired yet.
Mid-funnel interactions used to build retargeting audiences.
Conversion ID: 2
Tracks a click to the pricing page. Navigation is blocked in this demo so you can read the payload.
View pricingNot fired yet.
Conversion ID: 5
Fires when a visitor watches half of the product overview video. Useful for a retargeting audience of engaged viewers.
Not fired yet.
Conversion ID: 6
A newsletter sign-up form. The payload includes a hashed email and the selected preferences.
Not fired yet.
Cart, checkout and purchase events.
Conversion ID: 7
Fires when a product is added to the cart. Value and currency are shown for reference.
Not fired yet.
Conversion ID: 8
Fires when a visitor starts checkout. Compare with purchases to measure drop-off.
Not fired yet.
Conversion ID: 9
Fires on the order confirmation page. The order ID lets you match the event to backend orders and deduplicate it against a Conversions API event.
Not fired yet.
Preference changes, modals, help text and ratings.
Conversion ID: 10
Records a light/dark theme change. The payload includes the previous and next state.
Current theme: Light
Theme set to light.
Conversion ID: 11
Records an email preference change with its consent state.
Consent granted.
Conversion ID: 12
Opening the modal fires conversion 12. Dismiss fires 20 and Register fires 21. Only the registration would normally be a LinkedIn conversion.
Modal closed.
Conversion ID: 13
Shows or hides a pricing FAQ answer. The payload records the content ID and whether it is visible.
Yes. Annual plans can be cancelled at any time and stay active until the end of the term.
Answer hidden.
Conversion ID: 14
Records a 1–5 rating for a help-center article. The payload includes the rating and the scale maximum.
No rating yet.
Copy, share, print, scroll depth and error events.
Conversion ID: 15
Copies the article URL to the clipboard and records the URL in the payload.
Not fired yet.
Conversion ID: 16
Records a social share. Change channel for other networks.
Conversion ID: 17
Records a print or save-to-PDF action.
Not fired yet.
Conversion ID: 18
An IntersectionObserver fires once when the marker below is fully in view.
Waiting for scroll.
Conversion ID: 19
Records a recoverable error, such as a checkout request timing out.
No errors logged.
The base tag sets _linkedin_partner_id and loads insight.min.js
asynchronously. Page views are recorded automatically. Calls made before the script loads are queued in
lintrk.q.
<script type="text/javascript">
_linkedin_partner_id = 'LINKEDIN-ID';
window._linkedin_data_partner_ids = window._linkedin_data_partner_ids || [];
window._linkedin_data_partner_ids.push(_linkedin_partner_id);
</script>
<script type="text/javascript">
(function(l) {
if (!l) {
window.lintrk = function(a, b) { window.lintrk.q.push([a, b]); };
window.lintrk.q = [];
}
var s = document.getElementsByTagName('script')[0];
var b = document.createElement('script');
b.type = 'text/javascript'; b.async = true;
b.src = 'https://snap.licdn.com/li.lms-analytics/insight.min.js';
s.parentNode.insertBefore(b, s);
})(window.lintrk);
</script> An event-specific conversion is created in Campaign Manager and fired from the page with its ID:
window.lintrk('track', { conversion_id: 1234567 });
Server-side events go to the Conversions API instead. They reference the same conversion rule, carry
hashed user identifiers and an optional conversionValue, and can be deduplicated against
tag events with a shared event ID.