Markitech / LinkedIn Ads AI Agent / LinkedIn Conversions API
LinkedIn Conversions API through server-side GTM
Send conversions from your server so LinkedIn can match more of them, and count each one once.
Updated November 4, 2026 · Markitech team
The LinkedIn Conversions API lets you send conversion events from a server rather than relying only on the browser. That recovers conversions lost to blockers and browser restrictions and lets you send offline or CRM events such as qualified leads.
The quality of the result depends on what you send with each event: hashed email, LinkedIn’s click identifier where available, and a consistent event ID when the Insight Tag reports the same conversion.
How to do it
- Create the conversion in Campaign Manager and choose Conversions API as a source.
- Capture the conversion in the data layer with an event ID and hashed email where consent allows.
- Send the event from your server-side Tag Manager container to LinkedIn.
- Use the same event ID in the Insight Tag so LinkedIn can deduplicate.
- Compare browser, server and total conversions before switching campaign optimization.
Common mistakes
- Sending unhashed personal data.
- Using different event IDs in the browser and on the server.
- Pointing optimization at a new server conversion before it has history.
- Forgetting consent: user data should be sent only where consent allows.
Ask Markitech
Key terms
Approved by you, every time
Markitech proposes each change in chat and holds it until you approve. Nothing is published, created or changed in your accounts without that approval.
Part of the LinkedIn Ads AI Agent guide.
LinkedIn Conversions API questions
Do I still need the Insight Tag?
Yes. Running both with deduplication gives the most complete picture.
Can I send offline conversions?
Yes. Qualified leads and other CRM stages can be sent server-side, which is often the most valuable signal for B2B campaigns.