domain: learn.microsoft.com/en-us/linkedin/marketing/conversions · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Create a Conversion Rule in LinkedIn Campaign Manager or via the API (POST to /rest/conversions) to obtain a conversion URN.
Associate the conversion rule with one or more campaigns by POSTing to /rest/campaignConversions.
Build the conversion event payload with eventId (for deduplication), conversionHappenedAt (Unix ms), conversionValue (optional), and user data including hashed email (SHA-256) in the user object.
POST the event to https://api.linkedin.com/rest/conversionEvents with the LinkedIn-Version header and Authorization: Bearer YOUR_TOKEN.
Review the API response for per-event status; a 201 or 200 with accepted status indicates successful ingestion.
Allow 24–72 hours for conversions to appear in LinkedIn Campaign Manager reporting.
Known gotchas
The LinkedIn-Version header is required on Conversions API calls just as with other LinkedIn Marketing API endpoints.
User data must include at least one identifier (hashed email, LinkedIn first-party ad click ID, or mobile device ID) for match resolution; events with no identifiable user are not attributed.
Conversion events must reference a valid conversion URN associated with the ad account; using a URN from a different account results in an authorization error.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?