server-track-labby Canada Site Ops

LinkedIn Conversions API payload builder

Fill in a conversion and get the LinkedIn conversionEvents request, with email and names normalized and SHA-256 hashed in your browser, plus a pass/warn/fail checklist. Rules come only from these LinkedIn docs: LinkedIn: Conversions API · LinkedIn: Conversions API schema. This is the same logic as the server-track-lab API's LinkedIn dry run, so results match.

Privacy: your entered data never leaves the browser; standard page analytics only. No live send: delivery needs your own LinkedIn access token; this page has none and sends nothing. LinkedIn: dry-run preview (no live delivery yet) in the server-track-lab API too.

Conversion

User

Checklist

Request preview (token redacted)




Version header LinkedIn-Version: 202609 because hashedFirstName/hashedLastName are available starting with that version. Deduplication timing is not described in the fetched docs and is not claimed here.


Related: LinkedIn Conversions API guide · Meta CAPI payload builder · Google Enhanced Conversions builder · hashing tool · CAPI payload validator · event_id generator


Skip this. server-track-lab hashes and sends for you. One POST /api/v1/track call: we normalize, hash, dedupe on event_id and forward to Meta CAPI (Google: dry-run preview (no live delivery yet); LinkedIn: dry-run preview (no live delivery yet)). Free for 1,000 events a month, then CA$2 per 1,000. Get a free API key · Try the playground · API docs


FAQ
Does my data leave the browser?
Your entered data never leaves the browser: email and names are hashed locally with WebCrypto, and form values are never sent to server-track-lab, LinkedIn or Google Analytics. The page uses standard page analytics only (GA4 page views and an anonymous tool_use event).
Can I send this request to LinkedIn?
Delivery needs your own LinkedIn access token and conversion rule. This page has no token and never sends anything; the Authorization header is shown as [REDACTED].
Does server-track-lab forward to LinkedIn?
LinkedIn: dry-run preview (no live delivery yet). The API builds the same request for every event (linkedin_dry_run in the /api/v1/track response) but sends nothing to LinkedIn.
Why are first and last name hashed?
LinkedIn's schema (version 202609 and later) accepts hashedFirstName and hashedLastName, normalized to lowercase with no spaces or punctuation before SHA-256. This builder uses those so plain-text names are not needed.
What time window does LinkedIn accept?
LinkedIn's docs say conversionHappenedAt is epoch milliseconds and must be within the past 90 days.