{"id":10140,"date":"2026-09-06T08:18:00","date_gmt":"2026-09-06T06:18:00","guid":{"rendered":"https:\/\/www.lukaswojcik.com\/blog\/?p=10140"},"modified":"2026-10-09T23:19:59","modified_gmt":"2026-10-09T21:19:59","slug":"tutorial-precise-b2b-tracking-with-the-linkedin-insight-tag-and-gtm","status":"publish","type":"post","link":"https:\/\/www.lukaswojcik.com\/blog\/en\/digital-marketing\/tutorials-en-digital-marketing\/tutorial-precise-b2b-tracking-with-the-linkedin-insight-tag-and-gtm\/","title":{"rendered":"Tutorial: Precise B2B Tracking with the LinkedIn Insight Tag and GTM"},"content":{"rendered":"

The LinkedIn Insight Tag pasted site-wide produces exactly one useful thing: a retargeting audience. Every conversion defined on top of it tends to be a URL rule \u2014 a thank-you page, a path fragment \u2014 which works until the form posts back to the same address, the demo plays inside a single-page application, or the download starts without any navigation at all. At that point the campaign optimises against a page view that has nothing to do with the action worth paying for.<\/p>\n\n

The alternative is to define each action as its own conversion in Campaign Manager and fire it deliberately from Google Tag Manager. The following walkthrough covers the base tag, the conversion ids, the tag that sends them, and the triggers that decide when.<\/p>\n\n

\n\"One\n
The base tag only makes tracking possible – the conversion id is what makes a campaign optimisable against one specific action.<\/figcaption>\n<\/figure>\n\n

Step 1: The Base Tag, Loaded Once<\/h2>\n

The Insight Tag belongs in the web container as a single tag on all pages \u2014 the community template in the GTM gallery takes only the partner id, and a Custom HTML tag with LinkedIn’s snippet does the same job. What matters is that it loads once and early, because everything afterwards depends on the function it exposes.<\/p>\n

It also belongs behind a consent check. The Insight Tag has no cookieless mode: without advertising consent it does not send a reduced signal, it stops entirely, so gating it in GTM’s consent settings is the whole of the implementation rather than a compromise between two behaviours.<\/p>\n\n

Step 2: Creating the Conversions in Campaign Manager<\/h2>\n

Each action needs its own conversion object, created in Campaign Manager under the account’s conversion tracking section. Choosing the event-specific method rather than the URL method is the decision that makes the rest possible \u2014 LinkedIn then issues a numeric conversion id<\/strong> per conversion, and that id is what separates a whitepaper download from a demo view in reporting.<\/p>\n

Two settings are worth deciding rather than accepting. The attribution windows control how long after a click or a view a conversion still counts, and the conversion value, if the action has a plausible commercial value, is what lets campaigns be compared on more than volume. Reusing a single id across several events collapses them back into one number, which is the problem the URL-rule setup had in the first place.<\/p>\n\n

Step 3: Firing a Conversion from GTM<\/h2>\n

With the base tag loaded, a conversion is one function call. A Custom HTML tag carries it, with a guard, because the function only exists once the Insight Tag has actually loaded \u2014 and it will not have, for anyone who declined consent or blocked the script:<\/p>\n\n\n\n

HTML<\/span>