Stream conversion events to LinkedIn Ads via the Conversions API
domain: learn.microsoft.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Create a conversion rule with POST /conversions, setting conversionMethod to CONVERSIONS_API for each conversion type you plan to stream server-side rather than relying on the insight tag.
Ensure the access token carries rw_conversions and r_ads scopes before making conversion event calls.
POST conversion events to the events endpoint with a userIds array containing at least one identifier (SHA256_EMAIL, LINKEDIN_FIRST_PARTY_ADS_TRACKING_UUID, ACXIOM_ID, or ORACLE_MOAT_ID).
To send events in bulk, set the X-RestLi-Method header to BATCH_CREATE and include up to 5,000 conversion events in a single request.
Send events in near real time and include multiple user ID types per event where available to maximize match rate, since only matched events count for attribution and optimization.
Known gotchas
Only matched events (successfully tied to a LinkedIn member) are usable for attribution/optimization — a high send volume with low match rate won't improve campaign performance.
conversionMethod must be explicitly set to CONVERSIONS_API on the conversion rule; conversion rules created for the insight tag won't accept server-side events.
rw_conversions is a distinct OAuth scope that must be separately granted, not bundled automatically with standard rw_ads Marketing API access.
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?