LinkedIn Offline Conversions
AdvertisingStream server-side conversion events to LinkedIn Ads through the official Conversions API, creating rules and associating campaigns. Agents report closed revenue back to the ad platform that sourced it.
What This Integration Enables
A LinkedIn campaign optimizes against whatever you tell it a conversion is. If the only signal it ever receives is a form fill, it will get very good at producing form fills, including from the people least likely to buy. This connector is the return path: server-side conversion events streamed back through the official Conversions API so the platform learns which clicks became revenue that landed somewhere else entirely, in a CRM, weeks later, after a sales cycle it never saw. Agents create conversion rules with the method fixed to the Conversions API, set the click and view attribution windows, associate the campaigns whose conversions should be attributed to a rule, and stream events singly or in batches of up to 5,000 with hashed identifiers and a deduplication event id that keeps a server-side event from double counting against one already recorded by the Insight Tag. What the connector cannot do is decide what a conversion is worth, and that number is what the bidding engine spends against for as long as the campaign runs. Note the gating: this requires an approved LinkedIn app admitted to the Marketing Developer Platform with the Conversions API enabled, and a member role above VIEWER on the ad account.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Closed-won deals reach the campaign that sourced them
An opportunity flips to Closed Won in Salesforce. The agent reads the amount and the close timestamp, converts the timestamp to epoch milliseconds, gathers every identifier available on the contacts attached to the account, hashes the email and IP identifiers exactly as documented, and calls Stream Conversion Event against the enabled rule for that pipeline. An event id derived from the opportunity ID travels with it, so if the Insight Tag already recorded something for the same person, LinkedIn deduplicates instead of counting the deal twice. The campaign that produced the click three months ago now has the outcome attached to it. Pair this with LinkedIn Matched Audiences, which handles the outbound half: the audience goes out, the revenue comes back.
Standing up the rule and wiring the campaigns to it
Before any event can be streamed, a rule has to exist and campaigns have to be associated with it, because conversions are only ever attributed to campaigns attached to their rule. The agent calls Create Conversion Rule for the conversion type being tracked, sets the click and view attribution windows against the sales cycle rather than the default, and either auto-associates All Active Campaigns at creation, which covers up to 200 of them, or calls Batch Associate Campaigns to backfill an existing rule across a large account. The 365-day window is only accepted for the Submit Application, Purchase, Add To Cart, Qualified Lead and Lead types, which is worth knowing before a long enterprise cycle gets truncated to 90 days by a setting nobody chose deliberately.
Backfilling 90 days of history
Turning this on for the first time means catching the platform up. The agent pulls every deal closed inside the 90-day window from the CRM, joins the recognized amount from Stripe or QuickBooks Online where invoiced revenue is the agreed basis, and assembles batches for Batch Stream Conversion Events. Batching matters here: 5,000 events per request is the recommended way to avoid throttling, and the endpoint allows 600 requests per minute and 500,000 per day per token. It also has a sharp edge that shapes how the flow is built, since a validation failure anywhere in the payload fails every record in it. The agent validates locally first, then on rejection reads the batchIndex from the error, corrects that one element, and resubmits the whole payload rather than assuming the rest went through.
Human-in-Loop Highlight
The gate is on the value, not on the send. Streaming a conversion is reversible in the sense that a wrong event is one bad row; reporting the wrong basis for every conversion is not, because LinkedIn's bidding rebalances against it and keeps doing so for as long as the attribution window runs, which on a Purchase or Qualified Lead rule can be 365 days. Total contract value, first-year value, and monthly recurring value are three defensible answers that produce three different campaign strategies, and choosing between them is a pricing decision rather than a data-mapping one. So before the first backfill streams, the agent stops and puts the specifics in front of the revenue owner in Slack: "Rule Enterprise Closed Won, 214 events ready for the window 2026-05-06 to 2026-08-04. Value basis: first-year contract value. Total 4.1M reported. Top five deals attached. Confirm the basis before I stream?" The same gate fires again when Update Conversion Rule would switch the value type, since that changes what every event already sent is taken to mean. FlowRunner's human-in-the-loop is designed for exactly this shape of decision: the agent has assembled everything and is entirely capable of sending it, and the one input it does not own is what the number means.
Agent Capabilities
9 actionsConversion Rules
4- Create Conversion Rule Creates a rule on an ad account for one kind of conversion, with the method fixed to the Conversions API so events can be streamed to it. Attribution windows control how long after a click or a view a conversion still counts, and 365 days is only accepted for the Submit Application, Purchase, Add To Cart, Qualified Lead and Lead types. Campaigns can be auto-associated at creation, with All Active Campaigns covering up to 200. Events cannot stream until at least one campaign is associated.
- Find Conversion Rules Lists the rules on an ad account with id, name, type, attribution windows, method and enabled flag. Filter to rules whose method is CONVERSIONS_API and whose enabled flag is true, since those are the only ones events can stream to. Request Owned And Shared to also surface rules shared from other accounts under the same Business Manager.
- Get Conversion Rule Retrieves one rule by id with its full configuration: name, owning account, tracked type, method, attribution model and windows, and whether it is enabled. Streaming to a disabled rule is rejected, so this is the pre-flight check before a batch run.
- Update Conversion Rule Applies a partial update to a rule: rename it, change the attribution model or windows, switch the value type, or disable it so it stops matching conversions. Sent as a Rest.li partial update, so fields left empty are untouched. Switching the value type changes how already-reported history reads, which makes it worth a person.
Campaign Association
2- Associate Campaign Attaches one campaign to a conversion rule. Only associated campaigns are eligible to have the rule's conversions attributed to them, so associate as many applicable campaigns as possible. Do this before streaming, unless the rule was created with auto-association.
- Batch Associate Campaigns Attaches several campaigns to one rule in a single batch update. The response reports the outcome per campaign, so a partially rejected batch still associates the rest. Used when backfilling an existing rule across a large account after the fact.
Conversion Events
2- Stream Conversion Event Sends one offline conversion against a rule. The timestamp must be epoch milliseconds within the past 90 days, since a seconds value is rejected. Supply as many user identifiers as you hold to raise the match rate, with email and IP identifiers hashed exactly as documented. The request needs at least one valid identifier, a lead URN, an external id, or a first and last name. An event id enables deduplication against events sent by the Insight Tag.
- Batch Stream Conversion Events Sends up to 5,000 conversions in one request, which is the recommended way to avoid throttling at volume. Each element carries its own rule URN, millisecond timestamp within the past 90 days, optional value, event id and user object. A validation failure anywhere in the payload fails every record, so correct the element named by batchIndex and resubmit the whole batch. The endpoint allows 600 requests per minute and 500,000 per day per member token.
Ad Accounts
1- Find Ad Accounts Lists the sponsored ad accounts the connected member can reach with each account's id, name, type and status. Used to resolve the sponsoredAccount URN a conversion rule must be created against. The member needs a role above VIEWER for the conversion endpoints to work at all.
Frequently Asked Questions
What can FlowRunner do with LinkedIn Offline Conversions?
FlowRunner agents can run Create Conversion Rule, Find Conversion Rules, and Get Conversion Rule in LinkedIn Offline Conversions, plus 6 more actions.
Does connecting LinkedIn Offline Conversions to FlowRunner require OAuth?
Yes. LinkedIn Offline Conversions connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials.
Can LinkedIn Offline Conversions trigger a FlowRunner workflow automatically?
LinkedIn Offline Conversions doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with LinkedIn Offline Conversions
$100 in credits. No card required. Connect in minutes.