CONNECTIONS / HubSpot / HubSpot to LinkedIn Leads CAPI
Teach LinkedIn which HubSpot leads became pipeline.
Qualification happens in HubSpot, not on the form. Every lifecycle and deal-stage change you map streams out to LinkedIn's Leads Conversions API, hashed end to end.
- ● hubspot → linkedin.leads_capi :: live
- > event Lifecycle stage to SQL MQL→SQL
- > event Deal closed-won value=58,000 USD
- hash sha256(business_email)
- route linkedin.leads_capi conversion=stage_mapped
- ✓ delivered · stage recorded
WHAT THIS ENABLES
HubSpot to LinkedIn Leads Conversions API
HubSpot to LinkedIn Leads Conversions API streams lifecycle and deal-stage changes from HubSpot to LinkedIn server-side, replacing form-fill counts with qualified pipeline as the signal B2B lead campaigns optimize toward.
- Each mapped stage arriving at LinkedIn as its own named conversion event rather than a generic lead ping.
- Deal value flowing through alongside the stage, so bidding sees more than a bare conversion count.
- A lead signal that reflects whether sales actually qualified the contact, measured past the form fill.
WHAT FLOWS WHERE
HubSpot to Leads CAPI, mapped.
Lifecycle changes and closed-won deals recorded in HubSpot become stage-mapped conversions at LinkedIn's Leads Conversions API, with the business email hashed en route.
Lifecycle changes and closed-won deals recorded in HubSpot become stage-mapped conversions at LinkedIn's Leads Conversions API, with the business email hashed en route.
Built for the teams that own the number.
Accounts where Meta and Google already receive HubSpot stages and LinkedIn is the gap.
From kickoff to verified events.
-
Connect
Token-scoped access to contacts and deals, including the business email property LinkedIn matches on.
-
Map
Lifecycle and deal stages such as SQL and Closed Won mapped to LinkedIn conversion definitions.
-
Deliver
Stages post server-side as HubSpot updates them, and every event carries its own delivery status.
What ships with this use case.
Bids on LinkedIn shaped by what your HubSpot funnel actually did with each lead.
The closed-won amount sitting next to the original lead in one reporting view.
No export step anywhere; the feed moves when HubSpot records move.
What Leads CAPI actually receives.
- ● signals :: event payload
- > POST /conversionEvents source=hubspot.contact
- conversion "urn:lla:llaPartnerConversion:604187"
- conversionHappenedAt 1784133900000
- user.userIds [{ idType: "SHA256_EMAIL", idValue: "c728e0…" }]
- ✓ accepted · conversionValue 58000 USD
Adjacent moves on the same stack.
from HubSpot
HubSpot to Meta Conversion Leads
HubSpot to Meta CAPI for CRM translates lifecycle-stage changes and closed-won deals into…
Learn more
from HubSpot
HubSpot to Google EC for Leads
HubSpot to Google Enhanced Conversions for Leads writes GCLID onto the HubSpot contact at…
Learn more
same use case
ActiveCampaign to LinkedIn Leads CAPI
ActiveCampaign to LinkedIn Leads CAPI: Signals reads your ActiveCampaign contacts and deal…
Learn moregeneric
LinkedIn Leads Conversions API
Datahash sends CRM lead events to LinkedIn server-side, so campaigns optimize toward…
Learn moreAsked on almost every call.
Should lifecycle stages or deal stages drive our LinkedIn conversion events?
Lifecycle stage covers the early read, typically MQL and SQL, while the closed-won deal stage supplies the revenue-bearing event LinkedIn cares about most. Both get set up during onboarding rather than guessed at, and a workspace can add or retire a stage later without opening a new integration project with LinkedIn.
What is the lag between a HubSpot stage change and LinkedIn seeing it?
Small enough to treat as event-driven. Webhook triggers fire when HubSpot saves the change, so delivery runs in near real time rather than on a batch clock, and LinkedIn's bidding sees a qualification long before any weekly pipeline report would surface it. Teams that prefer batching can schedule delivery instead; the connection supports either mode.
Can lifecycle stage and deal stage both feed LinkedIn from the same HubSpot contact?
Yes, and pairing them is common for B2B accounts. Lifecycle stage supplies the qualification signal as a contact moves toward SQL, while the deal record linked to that contact contributes the closed-won value separately, giving LinkedIn two distinct events instead of one signal trying to carry both jobs.
NEXT STEP