Skip to content
DestinationActivation

LinkedIn Conversions API

On LinkedIn a conversion has no event name: it points to a conversion rule created in your account. You provide the rule id, and each event goes out with hashed email, value and currency — events without an identifier are skipped, because the API would reject the whole batch.

Data delivered

Data delivered

  • Conversions tied to your conversion rule (URN)
  • Hashed email (SHA256) as the identifier
  • Value and currency in the API format (conversionValue)

What it is for

What you can do with it

  • Prove B2B campaign return with the real sale from CRM or checkout
  • Feed LinkedIn's smart bidding with real conversions

Why integrate

The business reason, not just the tech

B2B with revenue proof

On LinkedIn clicks are expensive and cycles are long. Sending the real conversion — the lead that became a contract — back to your conversion rule is what turns campaigns from a cost into a channel with defensible ROI.

Corporate email is the link

Matching happens on hashed email (SHA256). Since CRM and checkout already feed the graph, events go out with the right email, no manual work.

No rejected batches

LinkedIn's API rejects the whole batch if one event has no identifier. Events without email are skipped before sending — the rest goes through.

How to connect

Step by step

  1. Step 1

    Create the conversion rule in LinkedIn Campaign Manager and copy the id.

  2. Step 2

    Create the destination with the rule id and access token.

  3. Step 3

    Create a Delivery with the event that represents the conversion.

Frequently asked questions

Do I need the Insight Tag on my site?

Not for this path — conversions go through the API, matched by hashed email. The Insight Tag can keep running in parallel.

Start measuring what actually becomes revenue

Create a free account, connect your first source and see your first lead timeline today. No card required.