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

Prevent duplicate LinkedIn events

This guide provides a clear, step-by-step process for implementing event deduplication between LinkedIn Insight Tag (client-side) and LinkedIn Conversions API (server-side) using Google Tag Manager (GTM) and TAGGRS. When you set up event deduplication, LinkedIn assigns a unique event_id parameter to identify and merge duplicate events. When both the client-side (Insight Tag) and server-side (CAPI) events share the same event_id and occur within a short time window, LinkedIn will count only one conversion.

By implementing event deduplication, you follow LinkedIn's recommendation and preserve the integrity of your reporting and optimization.

Generate a unique event ID

  1. In your GoogUse a random string, UUID, or a combination of timestamp and transaction ID for uniqueness.le Ads account, go to Tools & Settings > Measurement > Conversions.
  2. Generate the event_id in your website’s data layer or with a GTM Custom JavaScript variable.

Example Custom JavaScript Variable:

function() {
  return 'li_evt_' + Date.now() + '_' + Math.floor(Math.random() * 100000);
}

For e-commerce, combine order ID and timestamp for even stronger uniqueness:

function() {
 return 'li_order_' + {{Order ID}} + '_' + Date.now();
}

Push the event ID to the data layer

On the relevant event (e.g. purchase or lead), push the event_id into the data layer so both client and server have access:

Example (placed in your site’s JavaScript or GTM Tag)

window.dataLayer.push({
 event: 'purchase',
 event_id: 'li_evt_1721456789123_45678',
 value: 129.00,
 currency: 'EUR'
});

In case you you're using a tag to generate the event, use a custom HTML tag in GTM Web to push this structured event.

Add the Event ID to GTM web container (Insight Tag)

  1. Create a Data Layer Variable for event_id.
  2. Add the variable to your LinkedIn Insight Tag’s configuration:

Parameter name: event_id
Value: {{DLV – event_id}}

Reference the Event ID in GTM server container (CAPI Tag)

  1. Create a Data Layer Variable for event_id in the server container.
  2. Add the event_id to your LinkedIn CAPI HTTP Request payload:

json
{
 "event_name": "Purchase",
 "event_time": {{Timestamp}},
 "event_id": "{{event_id}}",
 // ...user_data and custom_data
}

Test deduplication

  1. Use GTM Preview mode to ensure the same event_id is present in both client- and server-side events.
  2. In LinkedIn Campaign Manager, use diagnostics or conversion logs to verify deduplication is working.
  3. Check that only one conversion is counted per user action.

Best practices

Consistency
Use the exact parameter name event_id in both Insight Tag and CAPI implementations.
Uniqueness
Ensure your event_id is unique per event to avoid accidental deduplication of separate actions.

Useful resources

LinkedIn server-side tracking - The full manual
Find expert support
Previous
LinkedIn CAPI
Next
TikTok Pixel
Copyright © 2025 TAGGRS. All right reserved.
TABLE OF CONTENTS
Generate a unique event IDPush the event ID to the data layerAdd the Event ID to GTM web containerReference the Event ID in GTM server containerTest deduplicationBest practicesUseful resources