LinkedIn Conversions
Stream server-side conversion events to LinkedIn and manage Conversions API conversion rules and their campaign associations.
About
LinkedIn Conversions ships in the w6w first-party pack. It declares 7 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.linkedin-conversions- Version
- 0.1.0
- Author
- w6w
- Licence
- MIT
- Categories
- Marketing · Analytics & BI
Overview
The LinkedIn Conversions API lets an advertiser stream conversion events from its own server to LinkedIn, so campaign performance can be measured and optimized regardless of where the conversion actually happens (server-side purchases, CRM-qualified leads, offline events) rather than only what a client-side pixel can see.
This app covers the three steps LinkedIn’s own docs lay out for that flow: create a Conversion Rule (the named, typed target conversion events attribute against), associate it with the campaign(s) that should get credit for it, then stream the conversion events themselves — singly or in a batch of up to 5,000 per request.
It is a separate product surface from this pack’s linkedin-ads app: same host and the same Rest.li versioned-REST transport, but a distinct API family, a distinct pair of OAuth scopes (rw_conversions, r_ads — not linkedin-ads’s rw_ads/r_ads_reporting), and a distinct approval gate. A health check tracks LinkedIn’s own developer-API status page.
Build with LinkedIn Conversions
Three routes to the same 7 actions. The Workflow tab is generated from LinkedIn Conversions's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
Associate Campaign with Conversion Rule
campaign-conversion-associate Associate a Campaign with a Conversion Rule so conversions can be attributed to it. Only associated campaigns are eligible for attribution.
Remove Campaign / Conversion Rule Association
campaign-conversion-delete Remove the association between a Campaign and a Conversion Rule. Does not delete the Conversion Rule.
Report Conversion Event(s)
conversion-event-report Stream one or more conversion events to a Conversion Rule. Send a JSON array with one or more events; a single event uses the plain create shape, two or more use a batch create (up to 5,000 per call).
Create Conversion Rule
conversion-rule-create Create a Conversion Rule for streaming server-side conversion events via the Conversions API.
Update Conversion Rule
conversion-rule-update Partially update a Conversion Rule's name, enabled state or attribution settings. Only the fields you set are changed. Set Enabled to false to stop new conversions from matching this rule — LinkedIn documents no separate delete for a Conversion Rule.
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying LinkedIn Conversions's real ids.
{
"manifestVersion": "2",
"name": "linkedin-conversions-example",
"steps": [
{
"id": "campaign-conversion-associate",
"uses": {
"app": "io.w6w.linkedin-conversions",
"action": "campaign-conversion-associate",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"campaignId": "<campaignId>",
"conversionId": "<conversionId>"
}
}
]
}Here are some of the things you can do
-
Associate Campaign with Conversion Rule
performcampaign-conversion-associate -
Report Conversion Event(s)
performconversion-event-report -
Create Conversion Rule
performconversion-rule-create -
Get Conversion Rule
readconversion-rule-get -
List Conversion Rules
searchconversion-rule-list
+2 more actions available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for LinkedIn Conversions, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to LinkedIn Conversions. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "campaign-conversion-associate",
payload: {
campaignId: "<value>",
conversionId: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action campaign-conversion-associate --payload '{"campaignId":"<value>","conversionId":"<value>"}'Give an AI agent LinkedIn Conversions — without giving it LinkedIn Conversions's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.linkedin-conversions#campaign-conversion-associate",
"input": {
"campaignId": "<campaignId>",
"conversionId": "<conversionId>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's LinkedIn Conversions connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
What the agent gets
Credentials it can't read
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
A tool surface scoped to the caller
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
A durable workflow in one call
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Health-aware discovery
LinkedIn Conversions's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. LinkedIn Conversions itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
LinkedIn Conversions declares its own checks, so its health is a property of the app rather than something the host guesses at.
LinkedIn API platform status
Atlassian Statuspage rollup for www.linkedin-apistatus.com, LinkedIn's official developer API status page, with per-component detail when the vendor publishes any. Unauthenticated and unsigned.