Skip to Content
Platform.Ontology

Conversions API (server to server events)

Advertisers send purchase and lead events straight from their servers with hashed identifiers.

Used to track youTracking across apps and sitesServer side trackingWeb browsersAfter you leave the site

In one line

Can send your purchases and sign ups to LinkedIn from a company's servers

Advertisers send purchase and lead events straight from their servers with hashed identifiers.

Moves tracking off the browser where blockers and cookie limits apply. LinkedIn matches events to members using hashed email, click ID, IP hash and other IDs.

What it can and can't do

What the user does: Nothing on your side. It happens after you buy or sign up on an advertiser's site

It can

  • Send a purchase or lead event straight from the advertiser's servers to LinkedIn
  • Include a scrambled version of your email or other details to match you to a member
  • Count conversions even if your browser blocks tracking scripts
  • Report events that happened days after the ad click

It cannot

  • Be seen or blocked by your browser, since it never touches your device
  • Match you without the advertiser having your details or click ID
  • Be switched off by a cookie banner choice alone, unless the advertiser honors it
  • Send events from sites that have not set it up

Browser support

BrowserStatusFirst versionNote
ChromeSupportedNot availableNone
EdgeSupportedNot availableNone
FirefoxSupportedNot availableNone
SafariSupportedNot availableNone
Safari on iPhoneSupportedNot availableNone
Chrome on AndroidSupportedNot availableNone
Samsung InternetSupportedNot availableNone

How a site asks for it

APIPOST https://api.linkedin.com/rest/conversionEvents (up to 5,000 events per batch)
How access is grantednone
What the user seesNone (no browser prompt)
Needs a secure context (HTTPS)No
Needs a user gestureNo
How long it lastsMapping of externalIds kept 1 year; events must be within 90 days
How to take it backNot listed
Inside an iframeNot listed

Typical flow

  1. Create a rule with conversionMethod CONVERSIONS_API (POST /rest/conversions)
  2. Server sends events with user.userIds and userInfo
  3. LinkedIn deduplicates on eventId and matches to members
  4. Rate limits 600 per minute and 500,000 per day; scopes rw_conversions and r_ads

Data you get

What comes back: Conversion events
Shape: object
How often: batch

FieldTypeUnitRangePrecision
idTypeenumNoneSHA256_EMAIL, LINKEDIN_FIRST_PARTY_ADS_TRACKING_UUID, ACXIOM_ID, PLAINTEXT_IP_ADDRESS, SHA256_IP_ADDRESS, GOOGLE_AIDNot listed
userInfoobjectNonefirstName, lastName, hashed names (from 202609), companyName, title, countryCodeNot listed
conversionHappenedAtintegerms epochwithin 90 days1 ms

Technical limits

  • Not a browser mechanism: needs the advertiser's server
  • Marketing API version 202511 sunsets 2026-11-16
  • Old ORACLE_MOAT_ID is not in the current schema

The story

What it is

Advertisers tell LinkedIn about your purchase or sign up from their own servers, not your browser.

For you

You never see it. After you fill in a form or buy something, the company's server quietly sends LinkedIn a note with a scrambled version of your email. Your browser cannot block it, because it never passes through your browser.

For makers

Browsers and blockers cut what scripts can see, so advertisers lose sales they used to count. A server to server note fills the gap and lets LinkedIn match the sale to an ad. It also lets a company report offline leads, such as a signed contract after a sales call.

Where you see it

TypeExampleApps
adsA software company sends LinkedIn the name of each lead that turns into a paid customer, so the ad team sees which campaign paid off.HubSpot, Salesforce
analyticsA marketing team compares LinkedIn reported sales to its own records, using server events that skip ad blockers.Segment
enterpriseA B2B firm tells LinkedIn when a sales rep closes a deal weeks after the web form, linking it to the first ad click.Salesforce, HubSpot
shoppingAn online shop sends a purchase event from checkout servers so a sale still counts when a shopper uses a blocker.Shopify
securityThe company hashes your email on its server before sending, which it says protects privacy, though the hash still identifies you.None named
educationA university sends LinkedIn an event when a prospect finishes an application, to find more people like them.Coursera

Risks

  • Cannot be blocked in your browser
  • Hashed email still identifies you

What the platform says

  • LinkedIn: Conversions API. LinkedIn pitches it as a way for advertisers to send conversion data directly, for more complete measurement as browser tracking weakens.

Good uses and abuse

Legitimate uses

  • Reliable conversion measurement
  • Offline sales feedback

Known abuse

  • Hidden matching of customers to LinkedIn profiles

Scores

ScoreValueMeaning
Sensitivity4 of 5How revealing the data is
Utility4 of 5How useful it is to honest apps
Friction0 of 5How much the user has to do
Fingerprint bitsNot ratedRough identifying entropy, when known

A real example: LinkedIn

Server side companion to the Insight Tag, documented on Microsoft Learn.

Sources

How well checked: Checked against real behavior.

On this page