Seven LinkedIn intent signals worth acting on — profile viewers, job changes, content engagement, hiring motion, event attendance, and company growth — and where a LinkedIn API fits.
LinkedIn is unusually rich for B2B intent because professional actions on the platform are explicit. People change roles in public. They engage with content in their feed. They post open jobs. They view profiles. They attend events. Every one of those actions is a signal that — in aggregate — tells you who is moving, what they care about right now, and whether timing favors outreach.
That's what intent data is: evidence of buying context. Not a vanity score. Not a static lead database. The question every B2B team is asking right now is the same: how do we stop spraying messages at cold lists and start reaching people when the signal says it's time?
This guide walks through what counts as LinkedIn intent, which signals matter, how to turn them into plays, and where a LinkedIn intent API fits — specifically versus scraping or databases that were accurate two months ago.
LinkedIn intent data is the structured record of behavior on LinkedIn that correlates with buying activity. Who viewed your profile. Who changed jobs. Who engaged with which post. Which companies posted which roles. Which accounts are growing fast.
None of those, taken alone, is a purchase signal. Together, they're the sharpest first-party intent graph in B2B — because the actions are taken by the people who would buy from you, on a platform where their professional identity is the whole point.
Two things make LinkedIn intent different from generic B2B intent data:
That combination is the reason LinkedIn intent data has become a foundational input for modern GTM stacks.
Not every action on LinkedIn is intent. Distinguish between noise and signal.
When someone views your (or a rep's) LinkedIn profile, they've raised their hand. It's the most direct intent signal on the platform — closest in shape to a pixel hit on your website, but with identity attached.
Most profile visits are noise: recruiters, friends, randos. The ones worth acting on are the ones from target accounts, decision-makers, or people who matched an ICP filter. The play is: filter visits against your target list, enrich the visitor, and route the match into sequencing or ABM.
Whose employees are looking at your company page? The company-level version of profile viewers. If a CMO at a target account views your LinkedIn page, that's a warmer first-touch than most outbound lists you'll ever buy.
Company viewers surface account-level interest — often before a single form gets filled out on your website.
A new CMO or VP of Engineering almost always means new tool evaluations. A Head of Growth who left your competitor six weeks ago is a different conversation than a random cold lead.
Job-change signal has a short half-life — the first ninety days after a transition is the high-intent window. Tracked at scale, job changes are the single highest-leverage signal most B2B teams under-use.
Who liked, commented on, or reposted content in your category? Someone who commented on a post about the exact problem your product solves has already declared interest — they just did it publicly.
Post-level intent is noisy at the population level (likes happen for lots of reasons) but very sharp when filtered to posts that match your category and to reactors who match your ICP.
Job posts reveal priorities. A company hiring three data engineers is building a data platform. A sales team that just posted six AE roles is scaling outbound. Hiring motion surfaces both capacity (the team is growing) and intent (the team is solving a specific problem).
Searchable at scale through LinkedIn's jobs surface, structured enough to be useful in a prospecting query.
Attendees of a LinkedIn event about your category are actively exploring the topic. It's a narrower signal than content engagement, but a stronger one — attending takes more commitment than clicking.
For niche verticals, event attendees can be the highest-intent list you build all quarter.
Headcount and team composition over time. A company that doubled its RevOps team in six months is either buying tools or about to. A company that just posted a VP of Data is building a data stack.
Growth signals are lagging versus job changes and content engagement, but they're durable — useful for segmenting account lists and for triggering account-based plays on a longer cadence.
Having the data isn't the play. Routing it into the right motion is.
For ABM, rank accounts by signal recency. Job changes in the last thirty days, profile visits this week, content engagement this month — each bucket scores differently and each routes differently. Fresh intent gets a rep; stale intent gets a campaign.
For lead scoring, treat intent as a multiplier, not a factor. An ICP-match account with zero recent signal is a lower priority than a lower-match account that's been engaging daily. The best scoring models weight intent recency heavily.
For outreach, let the signal shape the message. "Saw you commented on X" is a different cold open than "Saw you joined Y." Match the opener to the signal; don't send the same template to every source.
For retention, watch intent from existing customers. Your biggest churn risks are the accounts whose champions just left. Job-change signal on your customer base is a leading indicator of churn — and an opportunity to land a second champion before they do.
The old way of getting LinkedIn intent data was one of three options: browser extensions (fragile, per-rep, tied to one session), homegrown scrapers (maintenance forever, break every time LinkedIn ships a UI change), or static B2B databases with intent enrichment bolted on (aggregated, delayed, sometimes inferred rather than observed).
The new way is an API. A LinkedIn intent API exposes the signal surface as structured endpoints: you call it, you get profile viewers, company viewers, job changes, activity, and Sales Navigator metrics as JSON. No scraper to maintain. No account-specific extension. No waiting for a third-party intent vendor to refresh their feed.
For teams building on top of LinkedIn data — product companies, RevOps teams, ABM platforms — an intent API removes the infrastructure problem so the team can focus on the plays.
Edges is a LinkedIn automation API. One key, documented actions, consistent JSON across LinkedIn core, Sales Navigator, and Recruiter Lite. Four surfaces:
For LinkedIn intent specifically, the Signals & Intent API is the surface you'd build against. Pull profile viewers, filter by ICP, enrich with profile fields, and hand the matched rows to whatever sequencing or routing system your team uses.
To be explicit about what Edges is not: it's not a workflow builder, a no-code canvas, a CRM connector, an email finder, a phone lookup service, a contact database, or a multi-provider waterfall. It's the LinkedIn layer — the pipe other tools in your stack call through.
That scope is the point. You get reliable LinkedIn intent primitives behind one key, and you compose them into your GTM stack the way your roadmap demands.
Knowing a prospect exists is table stakes. Acting while intent is visible is the edge.
LinkedIn is the richest, sharpest, most identity-resolved intent surface in B2B. A LinkedIn intent API — versus scrapers, extensions, or stale databases — is what makes that surface usable at product scale.
Book a demo and we'll walk through the Signals & Intent API on your ICP and your specific signals.