LinkedIn Conversion API Tag for server GTM

Following other marketing platforms, LinkedIn also began to support server-side conversion tracking. We’ve developed our LinkedIn Conversion API tag for server GTM, which makes the setup much simpler and intuitive than the native one. With its help, you can track leads, purchases, or other key metrics.

In this article, we will talk about Stape’s tag in detail, highlighting its benefits and showing how to set up LinkedIn Conversions API with Google Tag Manager, which includes the following steps:

Quick note: If you would like to go straight to the LinkedIn CAPI, watch the setup guide:

The LinkedIn Conversion API tag developed by Stape provides an efficient solution that helps track LinkedIn ad campaigns' performance accurately.

With this tag, you can transmit conversion data directly from your server to LinkedIn’s server. LinkedIn server-side tracking allows for easier compliance with privacy regulations since all the data is processed on your server. 

Despite the events you need to track (whether tracking leads, purchases, or interactions with ads), the LinkedIn Conversion API tag provides reliable data transfer. It minimizes discrepancies from browser restrictions (such as Intelligent Tracking Prevention (ITP) or ad blockers. It also supports transmitting event data from GA4 or a data client to the LinkedIn Conversion API.

To set up LinkedIn Conversions API, you will need to configure a server GTM container. It is also preferable to use a custom domain, which allows you to set first-party cookies. 

Also, you need to set up sending data from the web to the server GTM container. You can use the two most popular solutions for doing it - Google Analytics 4 or Data Tag/Data Client.

Firstly, have it added Linkedin Conversions API from the server GTM Tag Gallery.

The tag itself is very easy to use, we’ve added the ability to enter explicit variables that will be reported to LinkedIn in a proper format. Tag configuration consists of the event types - PageView and Conversion events.

To send an event via LinkedIn CAPI you require an access token, a conversion rule ID and one of the 4 first party parameters LinkedIn requires you to send (hashed email, LinkedIn click ID value, Acxiom ID or Moat ID).

As already mentioned the process for obtaining CAPI access token has been greatly simplified - all you need to do now is the following:

Don’t forget to add the trigger for an event.

Below is the example of configured Linkedin Conversion API Tag:

LinkedIn web + CAPI event reporting is designed in a way commonly called “redundant event setup”. This means that you may report an event from the LinkedIn Insight tag and additionally via the LinkedIn CAPI tag. In order to avoid overreporting, you should send an identical event ID with the web and server event. The web event has a higher priority and will be counted as a conversion, and if the same conversion with the same event ID will be delivered via CAPI - such event will be discarded. Please be sure to handle this process properly for accurate conversion tracking.

1. Please make sure to use the latest version of the official LinkedIn Insight tag, that supports reporting of the event ID.

2. When you send a conversion through multiple methods, you need to create a conversion rule for each data source (browser and server). For the browser source - conversion rule ID will be available to you during the conversion creation process in the user interface.

3. To create a conversion that will be reported from the server GTM, please click Create conversion → Conversions API. On the Sources step, you may select Direct API integration. Once you are done, select the newly created conversion, and the Conversion Rule ID will be available to you in the URL right after conversions/

4. That’s pretty much it, make sure to add identical event_id sent from the web and any user data that is available for better event matching. li_fat_id cookie value will be automatically added to the payload if received in the incoming request cookie header.

5. To verify your setup, you may trigger your conversion event. The status for your conversions should change to “Active”. If your deduplication is properly set up, after a while you’ll see a message confirming it if you click on a status for the CAPI conversion.

With LinkedIn CAPI, you are also able to report offline conversion events, which may significantly help in measuring the performance of your LinkedIn campaigns. See our related blog posts for more instructions on offline conversions tracking:

With the recent updates introduced by LinkedIn and Stape’s server GTM tag, setting up the LinkedIn Conversion API became a much easier process. Adding conversion API will strengthen your existing web pixel tracking, providing additional resistance to adblockers and latest ITP changes, especially in conjunction with other Stape power-ups like Custom Loader, Cookie Keeper or Own CDN.