Logo of TAGGRS, written in blue and with a small favicon
HomeServer-side Tracking
Start for free
Introduction
Get started
Get started with TAGGRSSet up Google Tag ManagerAdd the GTM Data LayerConfigure GTM transformationsTest the setupDebuggingAnalytics dashboard
Migrate from Google CloudMigrate from hosting
Shortcuts
GTM Copy PasteReady-made templates
GA4 Server-side Tracking
Setup in GTMCreate GA4 Event TagsGA4 tag setup in server containerE-commerce events in GTM
Google Ads Server-side Tracking
Install Conversion LinkerSet up Conversion TrackingConfigure Enhanced ConversionsDeploy Remarketing Tags
Facebook Server-side Tracking
Set Meta PixelImprove your EMQ ScoreInstall Meta CAPIMeta Events DeduplicationMeta CAPI Gateway
LinkedIn Server-side Tracking
Install LinkedIn Insight TagSet up LinkedIn CAPILinkedIn Events Deduplication
TikTok Server-side Tracking
Set up TikTok PixelInstall TikTok Events APITikTok Events Deduplication
Pinterest Server-side Tracking
Set up Pinterest TagConfigure Pinterest Conversions APIPinterest Events Deduplication
Snapchat Server-side Tracking
Set up Snap PixelSnapchat Conversions APISnapchat Events Deduplication
TAGGRS Tracking Tags and Tools
Tracking TagsGoogle Service Account integrationsGTM LogsProfit TrackingData Enricher ToolWebhooks TesterEnhanced Tracking ScriptMulti Domain ToolClick ID RecoveryConsent Tool
Configurations
Billy Grace Server-side TrackingLeadPages Server-side TrackingPiwik PRO Server-side TrackingCDN Server-side TrackingShopify Server-side TrackingActiveCampaign Server-side TrackingKlaviyo Server-side Tracking
Server-side Tracking for e-commerce
Shopify Data LayerShopware Data LayerMagento Data LayerWooCommerce Data LayerPrestashop Data LayerLightspeed Data Layer
Consent Management server-side
Activate Consent ModeConfigure TAGGRS with Axeptio

Set up LinkedIn Conversions API

This guide gives you a step-by-step process for implementing the LinkedIn Conversions API (CAPI) using Google Tag Manager (GTM) and TAGGRS. With LinkedIn CAPI, you can reliably track key actions (like purchases, form submissions, and sign-ups), improve attribution, and help LinkedIn optimize your ad spend for better results and lower cost.

Why using LinkedIn Conversions API?

Challenge

CAPI Solution

Ad blockers

Sends data server-to-server, unaffected by browser-based blockers

Cookie restrictions

Relies on first-party data, not third-party cookies

Data loss in browsers

Ensures conversion tracking even as browsers limit client-side scripts

Attribution accuracy

Enables deduplication and full-funnel measurement

Privacy requirements

Allows you to filter or anonymize data before sending to LinkedIn

Prerequisites

• A LinkedIn Campaign Manager account with access to your ad account and Insight Tag.
• A deployed server container in TAGGRS.
• Google Tag Manager (web and server containers).
• Your LinkedIn Partner ID and (if required) Conversion ID.

Prepare your data layer

  1. Double-check that your website pushes relevant event data (e.g. purchase value, currency, and transaction ID) to the data layer for each conversion action.
  2. For e-commerce or lead generation, use a structured data layer that includes all parameters LinkedIn recommends.

Create data layer variables in GTM

  1. In both your web and server containers, create data layer variables for each parameter you plan to send (e.g., value, currency, transaction_id, email).
  2. Use descriptive names for easy mapping.

Set up the LinkedIn CAPI tag in GTM server container

  1. In your GTM server container, create a new HTTP Request tag (or use a LinkedIn CAPI template if available).
  2. Configure the tag:
    • Endpoint URL: Use the LinkedIn CAPI endpoint provided in your Campaign Manager.
    • Method: POST.
    • Headers: Set Content-Type: application/json and include any required authorization tokens.
    • Request Body: Build a JSON payload with all required event and user parameters, using the variables created earlier.
  3. Link the tag to a trigger that fires on your desired conversion event (e.g., purchase, lead).

Test and validate

  1. Use GTM Preview mode and LinkedIn’s diagnostics in Campaign Manager to verify that events are firing and data is received server-side.
  2. Check for deduplication if you are sending both client-side (Insight Tag) and server-side (CAPI) events.

Troubleshooting

Events not received
Verify endpoint, headers, and data mapping
Duplicate conversions
Ensure consistent event IDs for deduplication
Missing parameters
Check data layer and variable configuration
Data privacy concerns
Hash all personal data and review consent mechanisms

Useful resources

LinkedIn server-side tracking - The full manual
Find expert support
Previous
LinkedIn Insights Tag
Next
LinkedIn Event Deduplication
Copyright © 2025 TAGGRS. All right reserved.
TABLE OF CONTENTS
PrerequisitesEnable Enhanced ConversionsPrepare your data layerCreate data layer variablesSet up the LinkedIn CAPI tagTest and validateTroubleshootingUseful resources