Conversion tracking on LinkedIn works through the LinkedIn Insight Tag, a JavaScript snippet you install site-wide that fires when someone completes a goal action after clicking one of your ads. You define conversions in Campaign Manager—could be a contact form submission, a PDF download, a demo booking, or an e-commerce transaction—and LinkedIn records when tagged visitors complete those events within the attribution window (typically 30 days post-click, 1 day post-view). The tag drops a browser cookie that connects the ad click to the conversion event. When someone fills out your contact form three days after clicking a sponsored post, LinkedIn attributes that lead back to the campaign, ad creative, audience segment, and keyword if applicable. You see conversion counts, cost per conversion, and conversion rate directly in Campaign Manager, which tells you whether your $8–$15 CPCs in the Canadian B2B market are actually producing pipeline. LinkedIn offers auto-tagging if you use their lead gen forms (conversions fire automatically when someone submits), but for off-platform goals you manually create conversion events by specifying the thank-you page URL or using event-specific tracking. You can track multiple conversion types simultaneously—one for whitepaper downloads at top-of-funnel, another for demo requests mid-funnel. At Ottawa SEO we install the Insight Tag on all client domains running LinkedIn campaigns because without it you're flying blind—you'll see clicks and impressions but no idea if those turned into actual business outcomes. The data also feeds LinkedIn's algorithm for conversion optimization bidding, where the platform prioritizes serving ads to users statistically more likely to convert. Two things to watch: LinkedIn's attribution is last-touch by default, so if someone clicks a Google ad after your LinkedIn ad, Google gets credit. Also, privacy controls and cookie blockers mean you'll undercount conversions by 10–25% compared to server-side tracking, though LinkedIn's CAPI (Conversions API) option helps close that gap if you have dev resources to implement it.