Create a LinkedIn Insight Tag event conversion and retrieve performance data via the Conversions API
domain: learn.microsoft.com/en-us/linkedin/marketing · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate with the LinkedIn Marketing API using OAuth 2.0 with the rw_conversions and r_ads_reporting scopes, and include the LinkedIn-Version header set to the current YYYYMM version (e.g. 202601)
POST to the /conversionRules endpoint to create a conversion rule, specifying the name, type (e.g. PURCHASE or LEAD), attribution window, and the associated Campaign Group or Account
Retrieve the conversion rule URN from the response and attach it to a Campaign by POSTing to the campaign's conversion association endpoint
Send server-side conversion events to the Conversions API endpoint by POSTing to /conversionEvents with the conversion rule URN, event time, and hashed user identifiers (email, LinkedIn first-party ID, or click ID)
Query the Analytics Finder endpoint (/adAnalytics) with the conversion rule URN and a date range to retrieve attributed conversions, cost-per-conversion, and conversion value metrics
Cross-reference with the Insight Tag pixel data in Campaign Manager to validate server-side vs. client-side deduplication rates
Known gotchas
The LinkedIn Conversions API requires the LinkedIn-Version header on every request; omitting it defaults to an older behavior that may not support all conversion fields
User matching for server-side events relies on hashed email or LinkedIn click ID (li_fat_id); if neither is available the event will not be attributed to a campaign member
Conversion rules must be explicitly associated with campaigns or campaign groups before they appear in reporting; creating the rule alone does not enable attribution
Give your agent this knowledge — and 15,600+ 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?