Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

LinkedIn Marketing › Troubleshooting

LinkedIn Insight Tag Not Tracking Conversions

Why LinkedIn conversions read zero and how to fix it: tag missing from templates, URL rules that never match, event tags, consent and attribution windows.
Troubleshootingintermediate9 min readUpdated

First, check the tag status and a test conversion end to end

Do one controlled test before reading any setting. Clear cookies, open the site in a browser without content blockers, accept the consent banner, walk to the form and submit it, and note the exact address of the page you land on afterwards. With the browser's developer tools open on the network tab, filter for LinkedIn requests: you should see the tag load on that confirmation page and, for an event-specific conversion, a separate request when the event fires. If the site runs the tag through Tag Manager (GTM), run the same journey in preview mode, which Google's preview and debug documentation describes, and note which tags fired on the confirmation step.

The result splits the problem in two. If no LinkedIn request leaves the confirmation page, the fault is on the site side and the first four rows of the table apply. If the request leaves and the column still reads zero after the reporting delay, the fault is on the campaign side, and the last two rows apply. Write down which half you are in; most wasted hours on this symptom come from editing campaign settings for a tag that never loaded. If the site's own records show no sign-ups from LinkedIn visitors either, the tag is not the problem, and the diagnosis of LinkedIn ads with clicks but no conversions works through the objective, audience, offer and landing page instead.

Diagnosis table

Diagnosis

SymptomCheckLikely causeFix
No LinkedIn request on the confirmation page, though other pages send oneNetwork tab on each template; container version live versus the one editedInsight Tag missing from some templates, or the container unpublishedFire the tag on every page from one trigger and publish the container
Tag loads on the thank-you page, URL-based conversion never countsThe rule's match text against the real address, including parameters and subdomainURL rule that never matches the real thank-you addressRewrite the rule to match the address the browser actually shows
Event conversion counts at odd moments, or neverPreview timeline: which interaction fires the event tagEvent-specific tag on the wrong triggerFire the event on the confirmed outcome, not a button click
Conversions appear only from visitors who ignore the banner, or none at allRequests before and after accepting consentConsent banner holding the tag back after acceptanceRelease the tag on the consent update, not only on page load
Requests leave the site, column still reads zeroConversion's campaign associations; attribution window against the sales cycleConversion not attached to the campaign, or window too shortAttach the conversion; set the window to the real buying cycle
Counts far below CRM leads from LinkedIn, never zeroShare of conversions from browsers with strict tracking rules; any server routeBrowser restrictions with no Conversions API routeAdd the server route alongside the tag

Fix, verify and prevent each cause

The tag absent where the conversion happens

The tag is often installed on the main site template while the confirmation page lives elsewhere: a booking tool on a subdomain, a checkout on a separate template, or a form provider that redirects to its own thank-you page. In a tag manager, the equivalent is a trigger limited to some pages, or a container change previewed and never published.

Fix: fire the base tag from a single all-pages trigger in the container and publish the version, following the patterns in the tags, triggers and variables guide; add the container to any template or subdomain that lacks it.

Verify: the test journey shows a LinkedIn request on every step, and the live container version number matches the one you edited.

Prevent: keep a list of every template and subdomain that can host a conversion, and test the tag on each after any site release.

A rule that describes an address nobody reaches

A URL-based conversion counts a visit to a page whose address matches the rule. Rules written from memory often miss: the real address carries a query string, a trailing path, a language folder or a different subdomain, or the form shows a success message without changing the address at all. The LinkedIn Ads hub explains the two ways a conversion can be defined.

Fix: copy the address from the browser at the end of the test journey and write the rule against it, choosing the match type so that parameters do not break it; if the address never changes, switch to an event-specific conversion.

Verify: a fresh test conversion appears against that conversion in Campaign Manager after the reporting delay.

Prevent: whenever the form, booking tool or confirmation page changes, rerun the journey and compare the address with the rule.

An event tag that fires on the wrong moment

Event-specific conversions depend on the trigger chosen in the container. A trigger on the submit button counts attempts, including failed validations; a trigger on an element that a redesign removed counts nothing. The container side of this problem is diagnosed step by step in the guide to a Tag Manager tag that will not fire, which this page does not repeat.

Fix: move the event to the confirmed outcome, usually a data layer event pushed when the form or order succeeds.

Verify: in preview, one successful submission fires the event once and a failed submission fires nothing.

Prevent: agree with developers that the success event is part of the form's contract and is tested whenever the form changes. When the same confirmed event also feeds analytics and other ad platforms, the tutorial on ad platform tags from one data layer keeps every platform's tag on that one trigger.

Where consent is required, the tag should wait for it. The fault is a banner that records acceptance but never tells the container, so the tag waits forever on the page where the visitor accepted and on every page after.

Fix: fire the tag on the consent update event as well as on later page loads, using the wiring the consent mode guide describes.

Verify: with consent refused, no LinkedIn request leaves the browser; after accepting, the request appears on the same page without a reload.

Prevent: test both consent branches after every banner or container change, not only the accepted one.

A conversion the campaign does not own, or a window that closes too soon

Campaign Manager credits a conversion to the campaigns it is associated with, within the attribution windows chosen for it, as the LinkedIn Ads hub sets out. A conversion created after the campaign, or attached only to an older campaign, records nothing for the new one; a click window shorter than the time a business buyer takes to fill in a demo form drops conversions that did happen.

Fix: associate the conversion with every campaign meant to drive it, and set the windows to the buying cycle you see in the CRM rather than the default.

Verify: the conversion appears in the campaign's columns and the count moves within a few days of a known conversion from a tracked click.

Prevent: attach conversions as part of building each campaign, and record the window chosen and the date, so later comparisons use the same basis.

Browsers that drop what the tag sends

When counts are low rather than zero, browser restrictions and blockers are usually removing a share of conversions the tag would otherwise report. The LinkedIn Ads hub describes the Conversions API (Conversions API) as the server route for this.

Fix: send the key conversion from the server as well, with the identifiers the help centre documents, and let the platform reconcile the two.

Verify: the platform's count rises towards the CRM count without exceeding it.

Prevent: treat the server route as standard for the conversion that defines the programme's cost per acquisition (CPA).

Prevention: a conversion test in every release

Conversion tracking breaks most often on the day something else ships. Make a short test part of every website or container release: submit the key form in a clean browser with consent accepted, confirm the LinkedIn request on the confirmation step, confirm that a refused-consent session sends nothing, and check that the address or event still matches the conversion definition. Keep a register of each conversion with its rule or event, the campaigns it is attached to, its windows and the date each was set. Review the register whenever a campaign is created, so attachment is never forgotten. The LinkedIn Ads launch QA checklist makes the attachment and the tag check part of every new campaign's sign-off. Weekly, compare the platform's conversion count with LinkedIn-sourced leads in the CRM; a steady gap is measurement, a sudden drop is a break. The recommended traffic setup explains why the tag belongs on every page, and the tracking verification checklist adds the wider checks for other platforms in the same release. Where the tracking was never built properly, or a new site needs it from scratch, the tutorial on setting up the Insight Tag and conversions installs the tag and defines each conversion in an order that avoids these causes from the start. A rebuild, a new platform or a new address structure can set off several of these causes in one release, and the tutorial Moving a Website Without Breaking LinkedIn Ads covers the LinkedIn side of that release from the first inventory to the weeks after launch.

Illustrative example — not a real result

A training provider whose demo requests vanished

A corporate training provider runs two website conversion campaigns aimed at learning and development managers. After a site redesign in June, Campaign Manager shows zero conversions for eleven days while the CRM records 37 demo requests with a LinkedIn source. The end-to-end test shows the tag loading on every page and a LinkedIn request on the confirmation step, so the site half passes. The conversion rule reads "/thank-you", but the redesigned form now lands on "/demo/confirmed?ref=form". The team rewrites the rule against the new address and finds that the conversion is also attached only to last year's campaign; they attach it to both live campaigns and lengthen the click window from 7 to 30 days to match a buying cycle that averages three weeks. Over the next fortnight Campaign Manager records 29 conversions against 41 LinkedIn-sourced CRM leads, a steady gap the team now tracks weekly.

Common mistakes

Editing campaign settings before proving the tag loads on the confirmation page. Writing URL rules from memory. Counting button clicks as conversions. Testing only the accepted-consent path. Creating a conversion and never attaching it to the new campaign. Reading a short default window as proof that LinkedIn does not drive demos.

Frequently asked questions

The Insight Tag is on the site, so why does the conversion column stay at zero?

A tag that loads only proves that LinkedIn can see visits. A conversion also needs a rule or an event that matches the moment of the action, an association with the campaign being reported, and a click or view that falls inside the attribution window. Check those three in order after confirming the tag loads on the confirmation page itself, not just the home page.

Why does Campaign Manager show fewer conversions than our CRM shows leads from LinkedIn?

Some gap is expected. Campaign Manager counts only conversions it can tie to an ad click or view within its windows, and it cannot see visitors whose browsers block the tag or who refused consent. The CRM counts every lead with a LinkedIn source, including ones that arrived days after the window closed. A gap that is steady is measurement; a column at zero is a fault.

Will adding the Conversions API fix conversions that read zero?

Only when browser restrictions are the main cause. If the rule never matches, the conversion is not attached to the campaign, or the window is too short, the server route inherits the same problem. Fix the tag, rule, attachment and window first, then add the server route to recover the share of conversions the browser loses.

Terms used on this page

Where this page is used

Also related

Sources

  1. LinkedIn Marketing Solutions Help — LinkedIn
  2. LinkedIn Ads — LinkedIn Marketing Solutions
  3. Preview and debug containers — Google Tag Manager Help

Related