LinkedIn Insight Tag Complete Setup Guide: The Foundation of Your B2B Funnel
28 min read
If you spend a single dollar on LinkedIn Ads, installing the Insight Tag is not optional. It is the foundational piece of code that powers your entire advertising ecosystem on the platform.
Simul Sarker
Founder & Product Designer of DataCops
Last Updated
June 2, 2026
The LinkedIn Insight Tag is not broken. It is just being used by the wrong people in the wrong way, and the industry has handed you a server-side CAPI fix that does not actually solve the core problem.
Here is what nobody explains clearly: the Insight Tag is a third-party JavaScript file. It loads from LinkedIn's CDN. uBlock Origin, Brave Shields, and privacy-focused corporate browsers know that domain by name and block it at the network level. Your B2B audience, specifically the software engineers, IT directors, and senior executives worth $10 a click on LinkedIn, are precisely the people who have installed ad blockers. Consumer ad blocker adoption averages around 31.5% globally, but the B2B audiences most valuable to LinkedIn advertisers are consistently above that average. These are precisely the people who know what a tracking pixel is and have chosen to block one. When you pay LinkedIn $10 per click and 40-50% of your audience is invisible to the Insight Tag, you are making budget decisions on half your data.
The standard advice is to add LinkedIn Conversions API server-side. Good advice. Incomplete advice. LinkedIn's Insight Tag drops li_fat_id as a browser cookie when someone clicks your ad, but Safari deletes it after 7 days under ITP restrictions. B2B sales cycles average 3-6 months, meaning the cookie dies long before leads convert. Dreamdata's 2026 benchmarks, based on 3.5 million customer journeys, found the average time from first LinkedIn impression to closed revenue is 281 days. Your CAPI is reading from a dead identifier. Server-side does not save you when the browser never sent the signal in the first place, or sent it in week one of a nine-month deal.
This guide covers the actual setup, layer by layer. It also covers which tools handle the full stack competently versus which ones address the browser problem while ignoring the li_fat_id persistence problem. Fifteen tools get reviewed. Some are the right answer. Some are expensive ways to feel like you solved it.
What the LinkedIn Insight Tag actually does
The Insight Tag is a lightweight JavaScript snippet you install site-wide. Once running, it does three things that matter. First, it builds matched audiences by anonymously linking your site visitors to their LinkedIn profiles, letting you retarget people who hit your pricing page but never converted. Second, it feeds LinkedIn's demographic reporting, showing you the job titles, seniority levels, industries, and company sizes of your organic and paid visitors. Third, it fires conversion events back to Campaign Manager so LinkedIn's algorithm knows which clicks turned into leads, trials, or demos.
LinkedIn's attribution is particularly accurate for desktop B2B traffic because LinkedIn members are often logged in during work hours, providing deterministic identity matching. However, mobile and logged-out visitors see reduced match rates, and multi-touch attribution is limited, with LinkedIn primarily reporting last-click conversions within a 30-day window.
The demographic reporting and audience building functions are where the Insight Tag genuinely earns its place. For conversion tracking, it has a structural weakness that has gotten worse every year Apple tightens ITP.
Installing the Insight Tag: the three methods
Direct code installation. Pull the Partner ID from Campaign Manager under Account Assets, then Insight Tag. Copy the global JavaScript snippet and paste it into every page of your site, ideally in the header so it fires before page content loads. If your site runs a CMS with a global header field, this is a ten-minute job.
Google Tag Manager. In GTM, create a new tag, select LinkedIn Insight Tag 2.0 as the tag type, paste your Partner ID, and set the trigger to All Pages. This approach inherits GTM's own blocking problem: sGTM deployments running from your own subdomain bypass most blockers, but standard GTM's script is a known fingerprint. More on that below.
Platform integrations. Shopify, WordPress, Webflow, and Wix all have native LinkedIn Insight Tag integrations or plugin-based installs. These route through the platform's standard tag injection, which is fine for audience building but identical to the blocking problem as any other third-party CDN.
The install itself is not the hard part. The hard part is what happens after the tag fires.
Setting up conversion tracking
In Campaign Manager, navigate to Analyze, then Conversion Tracking. Create a new conversion and select Insight Tag conversion. You have two paths.
URL-based tracking is the simplest. If a successful form submission sends the user to a dedicated thank-you page, set the conversion to fire whenever that URL is matched. No additional code. LinkedIn counts a conversion whenever a tagged user who clicked your ad arrives at that URL within your attribution window. Set your attribution window to match reality, not LinkedIn's default. If you are using the default 7-day click window, you are likely undercounting LinkedIn's influence. A prospect might see your ad, go dark for two weeks, then come back and convert after reading three more pieces of content. Start at 30 days and adjust from there based on your average sales cycle length.
Event-specific conversion tracking fires on a particular user action rather than a URL. A form submission on a single-page application, a button click, a file download. This requires either adding LinkedIn's event-specific pixel snippet inline on the page or firing it via GTM when the event is detected. More accurate. More maintenance.
One setup mistake consistently appears in B2B implementations: tracking content downloads or whitepaper views as conversions. Define conversion events by revenue signal, not activity. A page visit is not a conversion. Neither is a content download, usually. Focus your tracking on actions that indicate genuine buying intent: demo requests, trial signups, pricing page visits, webinar registrations. The closer the event is to revenue, the more useful the data.
Conversions only report when attached to at least one campaign. If you create a conversion and never link it to a campaign, it records nothing. This is a common silent failure.
The li_fat_id problem nobody explains
When someone clicks your LinkedIn ad, LinkedIn appends a li_fat_id parameter to the destination URL. This is LinkedIn's first-party click identifier, analogous to Meta's fbclid. The Insight Tag reads it from the URL and stores it as a browser cookie so it can attribute later conversions back to that specific ad click, with high confidence, even if the user is not logged into LinkedIn at the time of conversion.
Here is the gap. Safari's Intelligent Tracking Prevention limits first-party cookies set by JavaScript to 7 days. Since the LinkedIn Insight Tag stores li_fat_id via JavaScript, it's subject to this limit. The timeline: Day 1, a prospect clicks your LinkedIn ad. li_fat_id cookie is set. Everything works. Day 7: Safari deletes the cookie. The prospect hasn't even opened your eBook yet. Day 30: Prospect downloads your whitepaper. LinkedIn CAPI tries to match. No li_fat_id, email doesn't match.
The email matching problem makes this worse. In B2B, many users sign up with LinkedIn using personal emails but use business emails to sign up on your platform. This mismatch can lead to attribution issues. If li_fat_id is gone by the time they convert, and the email they submit does not match their LinkedIn profile email, the conversion is simply lost.
The correct fix is to capture li_fat_id from the URL at click time and store it server-side, where ITP cannot touch it, then send it with every subsequent CAPI event throughout the entire sales cycle. Most basic CAPI implementations do not do this. They send events with email matching only, leave li_fat_id on the browser, and wonder why match rates sit at 40-60%.
Why server-side CAPI alone does not solve this
The pitch for LinkedIn server-side CAPI is straightforward. Events go from your server directly to LinkedIn's API. Ad blockers cannot intercept server-to-server traffic. Browser privacy settings do not apply. This is true and useful.
The part that gets left out: server-side CAPI still depends on the browser sending the data first, before it can route that data server-side. If the Insight Tag was blocked on page load, the browser never captured li_fat_id. The server has nothing to forward. You are sending a server-side event that says "a conversion happened" with only a hashed email and no click ID. LinkedIn still matches it, but with lower confidence, lower match rate, and weaker signal for algorithm optimization.
The full solution has three components working together. A first-party script that loads from your own subdomain, so it is not on any filter list and cannot be blocked by name. A mechanism to capture li_fat_id from the URL at click time and persist it somewhere that Safari cannot expire. Server-side CAPI that sends events with both the hashed email and the persisted li_fat_id. Most tools give you the third component only, treating it as the complete answer.
Quick answers
Does the LinkedIn Insight Tag work with Consent Mode? Yes. LinkedIn supports Google's Consent Mode v2 signals for EEA traffic. If you are running a first-party CMP that passes consent signals correctly, the tag will respect them. If you are running OneTrust or Cookiebot loading from a third-party CDN, those CMPs get blocked 30-40% of the time by the same privacy tools blocking your Insight Tag, so consent never registers and the tag never fires, even for users who would have consented.
What is the difference between Insight Tag conversions and LinkedIn CAPI? The Insight Tag sends conversion signals from the user's browser. LinkedIn CAPI sends them from your server. They are complementary, not alternatives. Running both in deduplication mode gives you the highest event match rate.
How long does it take for conversion data to appear? After adding the Insight Tag, it may take up to 24 hours to start recording conversions. New conversion actions can take additional time to verify.
What is a good LinkedIn CAPI match rate? Email-only matching typically delivers 40-60% match rates. Server-side tracking that persists li_fat_id lifts match rates to 95%+.
Can you use LinkedIn CAPI without GTM? Yes. LinkedIn CAPI is a server-to-server API that sends events directly from your server to LinkedIn's endpoint. GTM is one implementation path, not a requirement.
What attribution window should I use? Your actual average sales cycle length. Default LinkedIn windows were designed around e-commerce, not B2B pipelines. If your deals close in 90 days on average, set a 90-day window and measure against closed revenue, not form fills.
The tools: fifteen reviewed
DataCops
DataCops is a first-party analytics, CAPI, bot filtering, and consent management platform in one architecture, built specifically for the multi-layer failure between a real user and a campaign dashboard.
The LinkedIn CAPI implementation handles what most tools miss. DataCops loads from your own subdomain via CNAME, so the script is invisible to blockers by name. It captures li_fat_id from the URL at click time and stores it server-side with first-party persistence, no ITP decay, no 7-day expiry. When a lead converts on day 45 of a 90-day sales cycle, the li_fat_id is still there. First-party script from your analytics subdomain bypasses ad blockers. li_fat_id stored in first-party cookie persisting 90 days. Native LinkedIn CAPI connector pre-configured, sends to LinkedIn API within minutes, includes li_fat_id for 95%+ attribution match rate.
The bot filtering layer matters specifically for LinkedIn CAPI. Sending bot conversions to LinkedIn trains the algorithm to optimize toward automated traffic. DataCops filters against 361 billion IPs, including 11.9 billion VPN endpoints and 620 million proxies, before any CAPI event fires. The same pipeline that routes to LinkedIn also routes to Meta, Google Ads Enhanced Conversions, and TikTok Events API. One architecture, four platforms, one price.
The TCF 2.2 first-party CMP loads from your subdomain alongside the analytics script. It is not on any CDN filter list. The banner loads on every session, EU or otherwise, and anonymous analytics continue after rejection because anonymous data is always legal under GDPR. You keep the 70% of intelligence you were legally allowed to keep.
CAPI starts at Business at $49/month for 50,000 sessions. That tier includes Meta, Google, TikTok, and LinkedIn CAPI plus HubSpot integration. The Free and Growth plans at $0 and $7.99 include analytics, bot detection, and the CMP but not CAPI. For teams comparing this against a $17 Stape subscription plus $50-300/month Cloud Run hosting plus developer time for GTM configuration, the math shifts quickly.
Honest limitations: SOC 2 Type II is in progress but not yet certified. Newer brand than Stape, Elevar, or Datahash. Narrower enterprise integration catalog than Tealium or mParticle. No Pinterest or Snapchat CAPI.
Right for: B2B SaaS and lead gen teams running LinkedIn plus at least one other paid channel who want full-stack first-party tracking, bot filtering, and consent in a single CNAME install.
Value 9/10. $49/month for CAPI.
Stape
Stape is the cheapest and most widely used server-side GTM hosting service, with 80+ tag templates and a connector ecosystem covering most major ad platforms.
Stape gives you the infrastructure. LinkedIn CAPI fires through a server-side GTM container Stape hosts on your behalf. The setup is well-documented, actively maintained, and the community is large enough that most edge cases have been solved somewhere on the internet. For teams who know GTM and want to own their tracking configuration fully, Stape is a legitimate choice.
The gap is that Stape is infrastructure, not an outcome. You configure what fires, how it fires, and what data goes with it. There is no built-in li_fat_id persistence strategy, no bot filtering before events reach LinkedIn, and no CMP. Bounteous research found that 80% of sGTM deployments are still detectable by sophisticated blockers even when hosted on custom domains because of container fingerprinting patterns. Getting a truly invisible first-party deployment on Stape requires deliberate configuration work beyond the defaults.
Right for: In-house GTM engineers who want full container control and are comfortable managing the persistence and consent layers separately.
Value 7/10. $17/month Pro, plus Cloud Run $50-300/month, plus your time.
Tracklution
Tracklution is a managed server-side tracking platform with a focus on simplicity, multi-platform CAPI, and EU compliance. SOC 2 Type II certified and ISO 27001 certified, which matters for enterprise procurement.
Tracklution claims 34.2% more conversions tracked compared to regular pixel-based tracking through its server-side LinkedIn connector. The 15-minute no-code setup is genuine. You connect your platform, configure events, and Tracklution routes them server-side. The managed infrastructure removes the Cloud Run cost and the ongoing maintenance burden of self-hosted sGTM.
The weakness is bot filtering. Tracklution does not filter bot traffic before events fire. If 20% of your LinkedIn traffic is automated, 20% of your CAPI events are teaching LinkedIn's algorithm to find more bots. For B2B where competitor research bots, scrapers, and AI agents hit pages that look like genuine professional interest, this matters more than it does in ecommerce.
Right for: EU agencies and SMBs wanting simple multi-platform CAPI without a developer, who need documented compliance certifications.
Value 8/10. €31/month Starter.
Elevar
Elevar is a Shopify-native tracking platform with deep order-level data fidelity and a long track record in the ecommerce space.
For Shopify stores spending heavily on LinkedIn for B2B ecommerce, Elevar handles the technical complexity of checkout event tracking with precision that generic platforms miss. Order IDs, revenue values, product data, all passed with server-side fidelity. The quality of the data Elevar sends to LinkedIn CAPI is high.
The problem is platform lock-in and price escalation. Elevar is Shopify-only. The pricing model is usage-based in practice: $200/month for 1,000 orders and $950/month at 50,000 orders. B2B ecommerce brands growing into mid-market find themselves renegotiating pricing as their order volume climbs. There is also no bot filtering and no first-party CMP bundled.
Right for: Shopify-only seven-figure ecommerce brands with in-house tech capacity and a genuine need for millisecond-level order tracking fidelity.
Value 6/10. $200/month at 1K orders, $950/month at 50K orders.
Datahash
Datahash is an enterprise-grade first-party data platform focused on CAPI implementation across Meta, Google, LinkedIn, and TikTok, with particular depth in CRM data activation and offline conversion import.
The LinkedIn Leads Conversions API integration is designed specifically for lead ads, enabling businesses to send updated lead information back to LinkedIn for more precise optimization of lead generation campaigns. The CRM integration depth is a genuine differentiator for enterprise B2B teams wanting to close the loop between a LinkedIn click, a form fill, a CRM opportunity, and a closed-won event. The full lifecycle attribution, from ad impression to deal closed, is where Datahash earns its price.
The price is the barrier. Most Datahash implementations run $500-2,000/month. There is no self-serve plan. You go through their sales team. For enterprise teams where LinkedIn ad spend justifies the investment, the setup is professional and the support is strong. For SMBs and mid-market teams, the cost structure does not fit.
Right for: Enterprise B2B companies with dedicated RevOps teams, six-figure LinkedIn ad budgets, and a need for deep CRM closed-loop attribution.
Value 7/10. Custom quote, most $500-2,000/month.
Segment (Twilio)
Segment is a customer data platform, not a CAPI tool specifically, but it routes events to LinkedIn CAPI as one of many destinations in its connector library.
The advantage of Segment is the single SDK collecting events from web, mobile, and server, then fanning them out to any downstream destination including LinkedIn CAPI, without rewriting tracking code for each platform. If you are already a Segment customer with events flowing, adding LinkedIn CAPI is a destination configuration, not a new implementation.
The disadvantage is cost and complexity for teams who are not already invested in the Segment ecosystem. Segment's pricing is volume-based and escalates significantly at scale. It also does not solve bot filtering upstream. Events that enter the pipeline from bots flow to LinkedIn the same as human events.
Right for: Mid-market to enterprise SaaS companies already running Segment who want LinkedIn CAPI as an additional destination without a new vendor relationship.
Value 6/10. Volume-based pricing, typically $120-1,200/month depending on MTUs.
CustomerLabs
CustomerLabs is a no-code first-party data platform with visual configuration for server-side event tracking and a specific focus on unifying website data with CRM data before activation across platforms including LinkedIn CAPI.
CustomerLabs removes the technical barrier entirely with a visual interface for setting up server-side tracking. You can configure which events to track and where to send them without writing any code or managing servers. The platform excels at unifying data from both your website and CRM, then activating that combined dataset across ad platforms.
The CRM unification is the genuine differentiator for B2B teams. If your form captures a business email, CustomerLabs can enrich that with CRM data before sending to LinkedIn CAPI, improving match confidence. The no-code interface also reduces dependence on engineering for tracking changes, which matters for marketing teams that cannot queue every tag change through a development sprint.
No bot filtering. No bundled CMP. Pricing is mid-range and not fully transparent on their public site.
Right for: B2B teams with active CRM data who want to close the loop between LinkedIn conversions and pipeline without custom development.
Value 7/10. Pricing not fully public; contact for quote.
Ingest Labs
Ingest Labs is a server-side event pipeline with a specific focus on B2B attribution and high-confidence identity matching for long sales cycles.
Ingest Labs sends events to the LinkedIn Conversions API server-side, enriched with first-party email for high-confidence matching, deduplicated against the Insight Tag, and gated by user consent. B2B match rates climb, long-cycle attribution works, and every dollar of LinkedIn spend maps to real pipeline. The deduplication logic against the browser-fired Insight Tag is important: if both the pixel and the server fire for the same event, you do not want to double-count in Campaign Manager.
The platform is newer and less documented than Stape or Segment. The LinkedIn-specific B2B focus is real but it is a narrower product surface than full-stack CAPI platforms. No bot filtering. No CMP.
Right for: B2B SaaS teams specifically trying to solve LinkedIn attribution accuracy in long-cycle sales, who want a managed pipeline without building custom server-side infrastructure.
Value 7/10. Pricing contact-based.
JENTIS
JENTIS is an Austrian-built server-side tracking platform built with GDPR compliance as the primary architecture constraint. It replaces all third-party tracking scripts with one compliant first-party measurement script that the advertiser controls fully.
JENTIS shows real-time tracking health with metrics like Tracking Lift (+61.5% additional server-side data measured) and a Tracking Score. For EU-first companies where every data processing decision lives under legal review, JENTIS provides the audit trail and data sovereignty documentation that most other platforms do not. LinkedIn CAPI is one of the connectors available.
The price is enterprise-only. JENTIS starts at €199/month and moves to €549/month, with enterprise custom pricing above that. For SMBs, this is not a realistic option. For EU enterprise teams where compliance is not optional, it is worth a serious evaluation.
Right for: EU enterprises with dedicated privacy and legal teams who need documented data sovereignty for every signal sent to ad platforms.
Value 7/10. €199-549/month, enterprise custom above.
Addingwell (now Didomi)
Addingwell was acquired by Didomi in April 2025 for $83 million, and the combined entity now offers server-side tracking infrastructure paired with a consent management layer. The strategic rationale was exactly what the market needs: CMP and sGTM in one vendor for EU compliance.
The Didomi CMP is one of the better enterprise-grade consent tools. LinkedIn CAPI routing through Addingwell's sGTM-based infrastructure is functional and well-documented. The post-acquisition integration is still maturing, and pricing has shifted from Addingwell's original free tier toward Didomi's enterprise pricing model.
The free tier that Addingwell offered (100,000 requests per month) made it a compelling starting point for small teams. That tier still exists but the product direction is clearly enterprise, and mid-market teams may find support and documentation skewing toward larger implementations.
Right for: EU enterprise teams who want CMP and server-side CAPI from a single vendor under Didomi's legal and compliance umbrella.
Value 7/10. Free up to 100K requests, EUR-based paid tiers above that.
Cometly
Cometly is an attribution platform with server-side tracking and multi-touch reporting, focused specifically on connecting ad spend to closed revenue in B2B SaaS sales cycles.
Cometly ties ad spend to closed-won revenue across long B2B SaaS sales cycles, with server-side tracking and multi-touch attribution out of the box. The auto-pause and budget reallocation features operate on top of attribution data rather than raw last-click platform data, which is a meaningful step up from optimizing inside LinkedIn Campaign Manager directly.
LinkedIn CAPI is one of the platform connectors. The focus is clearly on attribution intelligence rather than raw tracking infrastructure. If you want to know which campaigns generate pipeline, Cometly is a usable tool. If you want the cleanest possible signal going into LinkedIn's algorithm, the infrastructure layer is secondary to the reporting layer in Cometly's design.
Right for: B2B SaaS teams spending across Meta, Google, and LinkedIn who want unified attribution reporting and budget decisions driven by pipeline revenue rather than platform-reported conversions.
Value 7/10. $199-499/month.
SignalBridge
SignalBridge is a server-side tracking platform with built-in bot filtering and funnel analytics, positioned as the best-value option for small-to-mid-size businesses needing multi-platform CAPI.
SignalBridge offers the best value for small-to-mid businesses at $29/month with built-in analytics, bot filtering, and funnel insights. The bot filtering is real, though the IP database scale is not publicly documented in the same detail as DataCops' 361 billion IP database. LinkedIn CAPI is a supported connector alongside Meta and Google.
The platform is relatively new and the feature depth does not match Stape's ecosystem breadth or Elevar's Shopify integration depth. For teams on a tight budget who want basic bot filtering plus CAPI without a new infrastructure project, SignalBridge is a credible option at the price point.
Right for: Small B2B teams spending $2,000-10,000/month across two or three platforms who want server-side tracking with basic bot filtering under $50/month.
Value 8/10. $29/month.
Littledata
Littledata is a server-side tracking platform built around Shopify and headless ecommerce, with a focus on accurate order-level events and CRM integration.
LinkedIn CAPI is available as a connector, but Littledata's architecture is ecommerce-first and the B2B use case is a secondary fit. The platform is strong on subscription and LTV data, Recharge integration, and Shopify checkout events. For B2B SaaS or lead gen tracking, the feature set is generic.
Right for: Shopify ecommerce brands running LinkedIn ads alongside Meta and Google, who want subscription and LTV data flowing server-side.
Value 6/10. $89/month and up.
Triple Whale
Triple Whale is an attribution and analytics platform, not a CAPI infrastructure tool, though it includes a server-side event layer that feeds its attribution dashboards.
The distinction matters. Triple Whale shows you attribution. It does not primarily exist to improve signal quality to LinkedIn's algorithm. Running Triple Whale alongside a clean CAPI setup makes sense: one cleans the pipe, the other visualizes the results. Treating Triple Whale as your CAPI implementation while skipping the infrastructure layer means you have good dashboards built on the same incomplete browser data.
Right for: DTC and ecommerce brands who want attribution reporting and already have a clean CAPI layer underneath.
Value 6/10. $179/month annual.
Northbeam
Northbeam is a media mix modeling and attribution platform for high-spend advertisers. LinkedIn CAPI data feeds its cross-channel models, but Northbeam is not a CAPI implementation tool.
At $1,500/month entry pricing, Northbeam is for brands with significant enough LinkedIn spend that the attribution accuracy at a campaign level materially affects allocation decisions. The signal quality improvements from proper CAPI setup upstream directly improve the quality of Northbeam's models downstream.
Right for: Enterprise ecommerce and DTC brands spending $500,000+ per month across channels who need media mix modeling, not just last-click attribution.
Value 6/10 for most, 9/10 for the specific tier it serves. $1,500/month entry.
Raw sGTM (self-hosted)
Building your own server-side GTM container on Google Cloud Run, Cloudflare Workers, or Akamai gives you full control and maximum flexibility. You define every data transformation, every destination, every consent rule.
The TCO math is painful for most teams. Setup costs run $5,000-10,000 when a developer does it properly. Cloud Run hosting adds $50-150/month. Ongoing maintenance, template updates, and debugging add more. The first-year total runs $11,880-36,600 compared to $588 in DataCops Business plan annual cost, for largely equivalent CAPI output. For enterprise teams with dedicated tagging engineers who genuinely need custom data transformations no managed platform supports, raw sGTM earns its cost. For everyone else, the managed alternatives have gotten good enough to eliminate the gap.
Right for: Enterprise teams with dedicated tagging and data engineering capacity who need configuration depth that no managed platform provides.
Value 7/10 for enterprises, 3/10 for everyone else. $5,000-10,000 setup plus $50-300/month hosting.
Feature comparison
| Tool | First-party script | Bot filtering | Built-in CMP | li_fat_id persistence | LinkedIn CAPI | Multi-platform CAPI | Entry CAPI price |
|---|---|---|---|---|---|---|---|
| DataCops | Yes (CNAME) | Yes (361B IPs) | Yes (TCF 2.2) | Yes (server-side) | Yes | Meta, Google, TikTok, LinkedIn | $49/mo |
| Stape | Optional (custom domain) | No | No | Manual config required | Yes (sGTM template) | Yes (80+ connectors) | $17 + Cloud Run |
| Tracklution | Yes | No | No | Partial | Yes | Meta, Google, TikTok, LinkedIn | €31/mo |
| Elevar | Shopify subdomain | No | No | Limited | Yes | Meta, Google, TikTok, LinkedIn | $200/mo |
| Datahash | Yes | No | No | Yes (CRM-based) | Yes | Meta, Google, TikTok, LinkedIn | Custom ($500+) |
| Segment | Depends on setup | No | No | Manual | Yes (destination) | Yes (300+ destinations) | $120/mo |
| CustomerLabs | Yes | No | No | Partial | Yes | Meta, Google, TikTok, LinkedIn | Contact |
| JENTIS | Yes | No | Partial | Yes | Yes | Major platforms | €199/mo |
| Addingwell/Didomi | Yes (sGTM) | No | Yes (Didomi) | Manual | Yes | Major platforms | Free / EUR-based |
| SignalBridge | Yes | Basic | No | Limited | Yes | Meta, Google, LinkedIn | $29/mo |
| Cometly | Partial | No | No | No | Yes | Meta, Google, LinkedIn | $199/mo |
| Littledata | Shopify | No | No | No | Yes | Meta, Google, LinkedIn | $89/mo |
| Triple Whale | Partial | No | No | No | Attribution layer | Meta, Google, TikTok | $179/mo |
| Raw sGTM | Yes (custom domain) | No | No | Manual config | Yes | Full control | $5K+ setup |
| Ingest Labs | Yes | No | No | Yes | Yes | Meta, Google, LinkedIn | Contact |
Buyer decision tree
B2B SaaS, 90+ day sales cycles, LinkedIn primary channel. The li_fat_id persistence problem is existential. Your leads convert after Safari has killed the click ID. Start here: do you have server-side li_fat_id persistence? If not, your match rate is capped at 40-60% regardless of which tool you use. DataCops, Datahash, and Ingest Labs all solve this. DataCops at $49/month, the others at custom pricing starting significantly higher.
Shopify ecommerce running LinkedIn ads. Elevar if order-level fidelity at the checkout level is your primary need and you can absorb $200-950/month. DataCops if you are also running Meta and Google and want bot filtering across all channels. Littledata if subscription LTV data matters more than LinkedIn-specific accuracy.
Agency managing multiple LinkedIn ad accounts. Tracklution's white-label feature and SOC 2 certification make it easier to present to clients. Stape's low per-account cost scales across many accounts if your team has GTM expertise. DataCops' multi-platform CAPI at $49/month is viable if clients are on multi-channel paid programs.
EU enterprise with heavy compliance requirements. JENTIS or Didomi/Addingwell. Both provide the data sovereignty documentation that procurement and legal teams require. DataCops Business includes TCF 2.2 CMP and qualifies for most SME compliance requirements. DataCops Enterprise adds dedicated EU data residency for teams with stricter requirements.
Early stage, small LinkedIn budget. DataCops Free or Growth for analytics, bot detection, and CMP. Upgrade to Business at $49/month when LinkedIn CAPI becomes worth the investment. Do not pay Elevar $200/month or set up sGTM before you have proven the channel.
When NOT to use DataCops
You have a dedicated GTM engineering team and want full container control over every event, every transformation, every consent rule. Stape plus your own custom sGTM configuration gives you flexibility that no managed platform matches.
You need SOC 2 Type II certification documented and audited today. DataCops is in progress. Tracklution and Datahash have it now.
Your entire paid stack is Meta and you have no interest in LinkedIn, Google, or TikTok. The multi-platform CAPI bundling is the core value. Single-platform Meta operators can use Meta's free 1-click CAPI and spend nothing.
You are running a Shopify store doing $5 million-plus in monthly GMV with hundreds of orders per day where Elevar's order-level millisecond tracking fidelity directly affects revenue reconciliation. That Shopify-native precision is worth the premium for that specific use case.
The setup nobody pairs with the Insight Tag
The Insight Tag installation is complete. Conversion tracking is live. CAPI is configured. And you are still making one decision by default without realizing it.
The bot and AI agent traffic hitting your B2B site right now does not look like bots from 2021. AI agents crawling gated content, competitors running automated research, VPN-masked traffic from data centers: this traffic triggers your LinkedIn conversion events the same way real prospects do. ChatGPT Ads Manager launched on May 5, 2026, and at LinkedIn's typical CPCs of $5-$15+ per click, every untracked conversion is a direct loss of attribution accuracy in a channel that's already expensive to run. Unfiltered bot conversions are equally a loss, just in the opposite direction: they inflate your conversion count, lower your reported CPA, and teach LinkedIn's algorithm to find more automated traffic because that is what your conversion signal is rewarding.
The Advanced Conversion Tracking guide on this site covers the full technical implementation in depth, including the li_fat_id persistence architecture and bot filtering pipeline before CAPI events fire. The B2B Conversion Tracking Best Practices guide covers what to measure and when. The LinkedIn Conversion API Implementation guide walks through the specific server-side setup.
Your LinkedIn Campaign Manager is reporting conversions right now. How many of them came from the humans you are trying to reach?
