Actionist·LinkedIn Conversions
LinkedIn Conversions

LinkedIn Conversions

· #122 most-used

Send offline conversions back to LinkedIn Ads

CRMSalesMarketingAnalyticsLead Generation

LinkedIn Conversions is the Conversions API that lets you send offline and server-side conversion events — form fills, CRM deals, purchases, webinar sign-ups — directly to LinkedIn Campaign Manager so your ad attribution stays complete even when pixels miss. Connect it to Actionist and your agents can fire conversion events from your CRM, payment processor, or webinar platform, map lead quality data back to ad campaigns, and keep your LinkedIn ROAS reporting accurate without any manual data uploads.

Try LinkedIn Conversions with ActionistVisit LinkedIn Conversions
Average time saved
14 hours
per person · per month
≈ 2 workdays back

Eliminates manual work. Agents eliminate manual CRM export, LinkedIn upload template formatting, batch upload submissions, pixel monitoring, and weekly attribution reconciliation across sales, marketing, finance, and ops.

Schedule

What your LinkedIn Conversions agent runs on autopilot

A week of scheduled jobs your Actionist agent will execute on your behalf.

28Scheduled jobs
7Agents at work
24/7Always on
Agents
Mon–Wed
Mon
Tue
Wed
7a
8a
9a
10a
11a
12p
1p
2p
3p
4p
5p
6p
Multi-app workflows

LinkedIn Conversions × every other app you use

End-to-end automations that span multiple apps — each one a real business outcome.

6Workflows
10Apps spanned
~28 hrsSaved / week
5Personas served
For sales
Featured3 apps

CRM closed-won fires LinkedIn purchase conversion

When a deal moves to Closed Won in HubSpot, the agent reads the contact's email, deal value, and currency, then sends a Send Purchase Conversion Event to LinkedIn Campaign Manager. Within about a minute, the revenue is attributed to the original LinkedIn ad campaign — value-based bidding now has real revenue signals to optimise toward.

~8 hrs

Time saved for your team — every week, on autopilot

The flow
Trigger·When a deal is moved to Closed Won in HubSpot
Trigger
Step 1
HubSpot
Deal stage changes to Closed Won
read
Step 2
HubSpot
Fetch associated contact email and deal value
read
Step 3
LinkedIn Conversions
List Conversions to confirm 'Closed Won' rule is active
write
Step 4
LinkedIn Conversions
Send Purchase Conversion Event with email and deal amount
write
Step 5
Google Sheets
Log conversion event ID and deal metadata to attribution tracker
Result
Send Purchase Conversion Event with email and deal amountLog conversion event ID and deal metadata to attribution tracker
The win
Saved per run
15 min
Runs / week
~30×
Every closed deal is attributed back to LinkedIn — no revenue falls out of ROAS reporting
Driven bySales Agent
ROI

Savings

What your team gets back — two angles: what you stop doing manually, and what that's worth.

Without Actionist

What you do manually today

With Actionist

What your agent runs for you

  • Sales
    60 min / week
    Manual CRM-to-LinkedIn attribution upload

    Sales ops exports a CSV of closed deals from the CRM, manually formats it to LinkedIn's upload template, and uploads it through Campaign Manager UI — an hour-long task done weekly, meaning the algorithm runs 5 days without real revenue signals.

    Sales Agent
    0 min
    Agent sends conversion events the moment deals close

    Every time a deal moves to Closed Won, the agent reads the contact email and deal value and sends a purchase conversion event to LinkedIn within about a minute — ROAS reflects real revenue in near-real-time without any spreadsheet exports.

  • Marketing
    45 min / week
    Manual pixel and UTM tracking for content campaigns

    Marketing relies on pixel fires and UTM parameters to attribute content downloads and webinar registrations — ad blockers, CORS errors, and page refreshes mean 20–30% of conversions are never counted, and cost-per-download looks worse than it really is.

    Marketing Agent
    0 min
    Agent attributes every conversion server-side

    Content downloads and webinar registrations fire as server-side conversion events — pixel coverage gaps are irrelevant because the event is sent from the CRM, not the browser. Every registration counts.

  • Customer Support
    30 min / week
    No post-sale attribution to LinkedIn campaigns

    Renewals and onboarding completions are never attributed back to LinkedIn campaigns. Retargeting ads that drive existing customers to renew or expand are invisible in ROAS reporting — their value is not measured or credited.

    Customer Support Agent
    0 min
    Agent sends post-sale milestones as LinkedIn conversions

    Onboarding completions, renewals, and NPS promoter scores are fired as custom conversion events — LinkedIn retargeting campaigns show lifetime-value ROAS, not just new-logo ROAS.

  • Human Resources
    20 min / week
    Recruitment ad ROAS measured in clicks, not hires

    Recruitment campaigns are measured by click-through rate because no one converts application or hire data back into LinkedIn. Cost-per-click is the proxy metric — but it doesn't correlate with cost-per-hire.

    Human Resources Agent
    0 min
    Agent attributes applications and hires to LinkedIn campaigns

    Job applications and accepted offers fire as conversion events — recruitment teams see cost-per-application and cost-per-hire in LinkedIn Campaign Manager, and budget flows toward the creatives that produce real hires.

  • Finance
    90 min / week
    Weekly manual revenue reconciliation export

    Finance exports a payment report from Stripe, cross-references it with the CRM, formats a LinkedIn upload CSV, and submits it weekly — 90 minutes per week, and the data is always at least 7 days stale in LinkedIn.

    Finance Agent
    0 min
    Agent runs nightly revenue attribution batch automatically

    Each night the agent reads completed payments from Stripe and sends a bulk conversion event batch to LinkedIn — revenue is attributed by the next morning, and finance never touches a spreadsheet for this task.

  • Operations
    30 min / week
    No systematic conversion rule health monitoring

    Conversion rules fail silently — a misconfigured or paused rule means campaigns run for days or weeks without attribution data. The problem is usually discovered when someone notices LinkedIn ROAS has dropped unexpectedly.

    Operations Agent
    0 min
    Agent audits every conversion rule every week

    Every Monday the agent lists all conversion rules and checks their status — paused or zero-event rules are flagged before the week's campaign spend begins, preventing silent attribution blackouts.

  • Legal
    25 min / week
    Manual consent audit for ad tracking data

    Legal reviews ad tracking data compliance manually each quarter — by the time opted-out contacts are identified, their data may have been sent to LinkedIn in multiple conversion batches over months.

    Legal Agent
    0 min
    Agent checks consent before every conversion batch

    Before each conversion event batch, the agent cross-references contacts against the marketing consent database and excludes opted-out contacts automatically — compliance is enforced at transmission time, not discovered in a quarterly audit.

+ 100s of other LinkedIn Conversions automations
Average time saved
30 hrs / person / month
Calculator

Calculate what your team saves

Team size
5 people
Hourly rate
$45 / hr
Hours saved / week
18
Hours saved / year
875
Annual ROI
$39,375

Based on LinkedIn Conversions's typical team usage — the visible tasks plus a few other automations the agent runs: ~3.5 hrs / person / week of admin work automated.

Connect

How to plug LinkedIn Conversions into Actionist

Pick the connection method that suits your environment.

Connect via LinkedIn OAuth 2.0. Actionist opens a LinkedIn authorisation window — you approve Campaign Manager access and the agent is ready to send conversion events and list your conversion rules.

1
Open the Apps tab

Find LinkedIn Conversions in the Apps library and click Connect. OAuth is the recommended and only supported connection method.

2
Authorise in LinkedIn

A LinkedIn OAuth window opens. Sign in with the account that has advertiser or above access to your Campaign Manager account and grant Actionist permission to read ad accounts and send conversion events.

3
Select your ad account

After authorisation, Actionist calls List Ad Accounts to confirm the connection is working. Select the ad account you want to send conversion events to.

4
Create or select a conversion rule

In LinkedIn Campaign Manager, ensure you have at least one active 'Conversions API' type conversion rule. Actionist will list your available rules when configuring a conversion event workflow.

Actions

15 actions your agent can call

Read and write operations available to your Actionist agent.

Triggers

0 events your agent can react to

Events your agent watches for, and the actions it kicks off in response.

This app has no triggers yet.
FAQs

Questions about LinkedIn Conversions + Actionist

How does Actionist connect to the LinkedIn Conversions API?
Go to the Apps tab in Actionist, find LinkedIn Conversions, and click Connect. The connection uses LinkedIn OAuth 2.0 — Actionist opens a LinkedIn authorisation window and you grant permission to the ad account and Campaign Manager scope. Once authorised, Actionist can list your ad accounts and conversion rules, and send conversion events to any Conversions API rule you have configured. You need a Campaign Manager account with advertiser or above permissions to connect.
What is the LinkedIn Conversions API and why is it better than the LinkedIn Insight Tag pixel?
The LinkedIn Conversions API (CAPI) is a server-to-server integration that sends conversion event data directly from your CRM, payment system, or server to LinkedIn's Campaign Manager — bypassing the browser entirely. The LinkedIn Insight Tag fires from the visitor's browser, which means ad blockers, cookie restrictions, CORS errors, and single-page-app navigation can prevent it from firing. CAPI events are sent from your server and are not subject to those losses. Most advertisers see 15–30% higher conversion counts after adding CAPI on top of their existing pixel.
What identity signals can I send with a LinkedIn conversion event, and which is strongest?
LinkedIn accepts up to four identity signals in a single conversion event: email address (SHA-256 hashed or plain), LinkedIn First-Party Cookie ID (li_fat_id from the URL parameter), LinkedIn Lead Gen Form lead_id, and first/last name with company and country. The strongest signal is the lead_id — it is a direct LinkedIn identifier that guarantees a match without hashing. The first-party cookie ID is the second strongest for web-originated leads. Email is the most broadly available signal and is strong enough for most CRM-to-LinkedIn workflows. You can send multiple signals in one event for the best match rate.
How do I create a LinkedIn Conversions API rule so I can start sending events?
In LinkedIn Campaign Manager, go to Analyse → Conversion Tracking → Create Conversion and select 'Conversions API' as the type. Give it a descriptive name that matches the CRM event you'll be sending (e.g. 'Closed Won Deal', 'Webinar Registration'). Set the attribution window — 90-day click and 30-day view are standard for B2B. Once created, the rule appears in the List Conversions action in Actionist so you can select it as the target when configuring your conversion event workflow.
Can I send conversion events with a monetary value for LinkedIn value-based bidding?
Yes. The Send Purchase Conversion Event and Send Conversion Event actions both accept a monetary amount and an ISO currency code (e.g. USD, EUR, GBP). When you send value alongside events, LinkedIn Campaign Manager can optimise for revenue rather than conversion count — budget flows toward the audience segments and ad creatives that generate the highest revenue per click, not just the most clicks. Value-based bidding requires at least 30 purchase conversion events with values in the past 30 days to activate.
What happens if the same conversion event is sent twice to LinkedIn?
If you send the same event twice, LinkedIn will deduplicate it using the event_id field if you provide one. Set the event_id to a unique, stable identifier from your source system — the CRM deal ID, payment transaction ID, or database record ID works well. When LinkedIn receives two events with the same event_id for the same conversion rule within 24 hours, it counts only the first. If you do not provide an event_id, duplicate events will be counted as separate conversions, which inflates your reported conversion numbers.
How far back can I upload historical conversion events to LinkedIn?
LinkedIn accepts conversion events up to 90 days in the past. When you create a new Conversions API rule, you can backfill up to 90 days of historical events from your CRM or payment system — this gives LinkedIn's algorithm historical data to learn from on day one rather than starting cold. Events older than 90 days are rejected by the API. For a new rule, send the maximum 90-day backfill using the Send Bulk Conversion Events action before your next campaign launches.
Do I need a LinkedIn Lead Gen Form to use LinkedIn Conversions API, or does it work with my own website forms too?
LinkedIn Conversions API works with any conversion source — your website forms, CRM deals, payment events, ATS applications, or event registrations. LinkedIn Lead Gen Forms are not required. The API uses email address matching (or the first-party cookie ID if your LinkedIn Insight Tag with enhanced tracking is active) to match your conversion data to LinkedIn member profiles. Lead Gen Form leads are the easiest to match because they come with a lead_id, but the API is designed to work across all your lead and customer data sources.