SOP 263: Set Up LinkedIn Conversion API Via Google Tag Manager
\nThis SOP guides you to deploy LinkedIn’s Conversions API using Google Tag Manager (GTM) Server-Side with Google Analytics (GA) 4 forwarding. You will prepare LinkedIn IDs/tokens, stand up a server container, configure tags/triggers, quality assurance, and prevent duplicate counting.
\nLast Updated / Reviewed: 09/29/2025
\nExecution Time: 45–90 minutes (plus 1–24 hours for LinkedIn reporting to populate)
\n🚀 Goal: Implement LinkedIn Conversions API using GTM Server-Side with GA4 as the event source.
\n🤞 Ideal Outcome: LinkedIn receives server-side conversions matched to GA4 events, Insight Tag remains for audiences, and no duplicate conversions occur.
\n🤔 Why this is important: Server-side conversions improve reliability and reduce client-side blockers while keeping web tagging minimal.
\n🧐 Where this is done LinkedIn Campaign Manager and Google Tag Manager.
\n🗓️ When this is done: Before launching conversion-optimized LinkedIn campaigns or when migrating from web-only pixels.
\n👨 Who does this: Ad ops or analytics engineer with admin access.
\n__⚠️Prerequisites or requirements: __
\n• LinkedIn Campaign Manager account: Account Manager (or higher) on the ad account
\n• Google Tag Manager account: Admin on the Web container and permission to create a Server container
\nClick here to get the most up-to-date version of this SOP
\nNote: You’ll need to capture the numeric ID for every tracked conversion you created in Campaign Manager. Keep them organized for when you set up tags in GTM.
\nNote: LinkedIn shows the token only once. Store it securely in your agency’s credential vault. Avoid keeping it in personal files.
\nYou’ll now set up a server-side container in Google Tag Manager to handle LinkedIn Conversions API events. We recommend using the automatic provisioning option in Google Cloud since it’s the fastest and most reliable method for small agencies, without requiring custom domains or DNS changes.
\nOnce connected to your GA4 property, the setup will also forward all GA4 events server-side. LinkedIn can then use these forwarded events for the Conversions API.
\nWhy this matters: Forwarding GA4 events reduces the need for extra tags and follows LinkedIn’s official best practices.
\nYou’ll now configure the LinkedIn Conversions API tag inside your Server GTM container. Each LinkedIn conversion requires its own tag with the token, Partner ID, and Conversion ID you gathered earlier. Using LinkedIn’s official Conversions API template in Server GTM, it help reduces errors and ensures LinkedIn receives reliable, server-side events tied to your GA4 conversions.
\nNow that you’ve published your server-side tags, it’s time to confirm LinkedIn is receiving events through the Conversions API. This ensures your setup works properly and campaigns optimize without duplicates.
\nDisable or pause any LinkedIn event-specific conversion tags currently firing in your GTM web container for the same actions configured via API.
\nRun preview mode in the web container and trigger the action. Confirm no LinkedIn conversion tags fire, and only your GA4 tags appear.
\nDo not remove the standard LinkedIn insight tag that loads across the site, since it powers audiences and view-through attribution.
\nIn the GTM web preview, reload a page. Confirm the LinkedIn insight tag fires once and does not duplicate conversion events.
\n"}