Skip to Content
Platform.Ontology

LinkedIn telemetry endpoint (/li/track)

A single endpoint receives batched interaction and fingerprint events from the page.

Used to track youTracking across apps and sitesTelemetryWeb browsersWhen the page loadsWhile you use itAfter you leave the site

In one line

Can send batches of your clicks and device traits from LinkedIn pages to LinkedIn

A single endpoint receives batched interaction and fingerprint events from the page.

Carries tracking events including AedEvent, SpectroscopyEvent and the encrypted fingerprint in batches, so one request can hold many data points.

What it can and can't do

What the user does: Nothing. It happens as you use LinkedIn

It can

  • Collect your clicks and other page interactions
  • Send them in batches to LinkedIn's own address
  • Include device and fingerprint traits with the batch

It cannot

  • See other sites, tabs or apps
  • Show a prompt, so you cannot tell when it runs
  • Run if blocked, though blocking can break parts of the site
  • Name you beyond what LinkedIn already knows from your session

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://www.linkedin.com/li/track (batch up to 29 events, 4 retries per BrowserGate)
How access is grantednone
What the user seesNone (no browser prompt)
Needs a secure context (HTTPS)No
Needs a user gestureNo
How long it lastsEvents sent per page and on unload
How to take it backNot listed
Inside an iframeNot listed

Typical flow

  1. fireTrackingPayload queues events
  2. Batch is posted
  3. Retries up to 4 times

Data you get

What comes back: Telemetry batch
Shape: event
How often: per page

FieldTypeUnitRangePrecision
batch_sizeintegerevents1 to 291

Technical limits

  • Batch size and retry numbers are BrowserGate figures

The story

What it is

One web address that receives batches of events from the page, including device check data.

For you

You never see these calls. As you use the page, small bundles of data go back to LinkedIn in the background. They hold clicks, timings and, per a public analysis, encrypted device check results.

For makers

Product teams need to know what people click and where they get stuck. Batching events in one endpoint keeps pages fast and cheap. The same pipe can carry safety and device signals, so it is hard to see from outside what each bundle holds.

Where you see it

TypeExampleApps
analyticsLinkedIn measures how far you scroll in the feed and which posts you pause on, and sends that in one batch.LinkedIn
securityA bundle includes device check results that help decide whether a login is suspicious.LinkedIn
gamesA game page reports how long you took on a puzzle, so makers can tune difficulty and spot bot times.LinkedIn Games
liveA live video event page reports buffering and drop offs so the team can fix streaming problems.LinkedIn Live
adsAd viewability, such as whether an ad was on screen, is sent to prove to the advertiser it was seen.LinkedIn Ads
developerError and speed data go out in the same batch, so engineers can fix a slow page.LinkedIn

Risks

  • Hard to know what each batch holds
  • Runs all the time on the page

Good uses and abuse

Legitimate uses

  • Product analytics

Known abuse

  • Carries fingerprint events

Scores

ScoreValueMeaning
Sensitivity3 of 5How revealing the data is
Utility3 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

Endpoint seen in the snapshot; batch numbers from BrowserGate.

Sources

How well checked: Based on official documentation.

On this page