LinkedIn OAuth Signup Enrichment: The Login Button That Hands You a Profile

Most teams treat "Sign in with LinkedIn" as a login option, not a data source

Google and Microsoft OAuth get all the attention in signup enrichment write-ups, mostly because they show up more often in the logs. LinkedIn sign-in is rarer, but when a B2B SaaS product offers it, the people who choose it are telling you something: they have a LinkedIn account open, they're comfortable sharing their professional identity, and they skipped the option to sign up with a personal Gmail address. That's not nothing.

The irony is that LinkedIn is the single best-documented identity source available to a growth team, and most products that offer "Sign in with LinkedIn" do nothing with the connection beyond pulling a name and email for the account record. The profile URL, which is the one piece of information most enrichment vendors have to go find through search and scraping, is handed to you directly during the OAuth handshake.

What the LinkedIn OAuth flow actually returns

LinkedIn's OpenID Connect implementation (the current standard; the older r_liteprofile/r_emailaddress scopes are deprecated) returns a userinfo response after authorization that typically includes:

• sub: a stable LinkedIn member ID, unique per user
• email and email_verified: the address tied to the account, verified by LinkedIn
• given_name, family_name
• picture: a profile photo URL
• locale

That's the baseline token response, and on its own it's not much richer than Google OAuth. What it gives you is a reliable starting point: the member ID and name let you resolve the person's full public LinkedIn profile URL, which is the anchor most B2B enrichment runs are built around. Once you have that, you can pull current title, company, tenure, and the rest of the profile data your enrichment pipeline already knows how to process for any other LinkedIn-sourced record.

A caveat worth stating plainly: LinkedIn's API does not hand third parties someone's full profile (experience history, connections, headline) through the basic OpenID Connect scopes. Getting there means resolving the public profile from the verified identity and running it through the same LinkedIn-profile enrichment path you use for teammates found some other way, not pulling extra fields out of the OAuth token itself.

Why the email domain still does most of the early work

Before touching any LinkedIn profile lookup, run the email through the same personal-email-domain check you'd apply to any other signup. LinkedIn sign-in doesn't require a work email. Plenty of people connect LinkedIn to a Gmail or Outlook.com address because that's what they used to create their LinkedIn account years ago.

So the sequence that actually works:

1. Check the email domain against your personal email resolution list.
2. If it's a work domain, you likely already have company context before you've even looked at the LinkedIn data.
3. If it's a personal domain, the LinkedIn profile becomes your primary path to the person's current employer, since the email alone tells you nothing useful about where they work.

This flips the usual enrichment order. With most signup sources, email domain resolution comes first and profile lookups are a fallback for personal addresses. With LinkedIn OAuth, the profile lookup is often the more reliable signal, because people update their LinkedIn job title the day they change roles and update their account email a lot less often.

Turning the profile into ICP and teammate data

Once you've resolved the LinkedIn profile tied to the OAuth login, treat it the same way you'd treat any profile your enrichment engine finds through search: pull current title, company name and domain, seniority, and tenure, then run it through your existing ICP scoring model.

The part that's genuinely different from other signup sources is teammate discovery. A LinkedIn-authenticated user has already proven they're comfortable with their professional identity being visible to your product. That makes the signup itself a reasonable seed for a teammate discovery pass against their current company: if the signup came through LinkedIn, you can search LinkedIn's public company pages for the same employer with higher confidence than you'd have starting from an email domain guess alone, because you're not inferring the company, you're reading it off a current, user-confirmed profile.

A few specifics worth building into the scoring:

• Tenure at current company. Someone three months into a new role is more likely to be evaluating new tools for their team than someone who's been there five years and has an established stack.
• Title changes since their last signup. If this isn't a first-time signup and the LinkedIn title has changed since their last login, that's an expansion or re-engagement signal worth routing differently than a cold new account.
• Company size and industry from the profile's current employer, scored against your ICP the same way you'd score any other company record.

A routing example

Say a mid-market project management tool adds "Sign in with LinkedIn" as a signup option. Someone signs up, the OAuth token resolves to a LinkedIn profile showing "Head of Operations" at a 150-person logistics company, six months into the role.

That one signup, properly enriched, gives you:

• A verified work identity (title, company, tenure) without a single form field
• An ICP score run against company size and industry
• A teammate discovery pass seeded from a confirmed current employer, not a guessed one
• A routing decision: a Head of Operations at a 150-person company six months into the role is a stronger product-qualified lead than an anonymous free-tier signup, and should probably skip the generic onboarding sequence in favor of a sales-assist touch

None of that required asking the user anything. It required treating the LinkedIn OAuth response as enrichment input instead of a login shortcut.

Mistakes worth avoiding

Assuming the OAuth email is a work address. It frequently isn't. Run it through personal-domain detection like any other signup before you draw conclusions from the domain.

Stopping at the token response. The given_name/family_name/picture fields from the basic scopes are not the valuable part. The valuable part is the LinkedIn profile you can resolve once you have a verified identity to anchor the search.

Treating LinkedIn sign-in users as a monolith. People choose this login option for different reasons: some are comfortable sharing professional identity, some just don't want to create another password, some only have LinkedIn open in a tab. Score the resolved profile, not the fact that they picked this particular button.

Ignoring returning users. LinkedIn profiles change more often than most signup data. A returning user's title change is a cheap, high-signal re-enrichment trigger that costs nothing beyond a periodic profile refresh.

What to measure

• Share of signups using LinkedIn OAuth versus other methods, and how that share trends after you add or promote the option.
• Conversion rate of LinkedIn-authenticated signups to paid, compared against email/password and other OAuth sources.
• Percentage of LinkedIn OAuth signups where the email domain is personal (expect this higher than you think).
• Teammate discovery hit rate for LinkedIn-seeded searches versus domain-seeded searches.
• Re-enrichment events triggered by title changes on returning LinkedIn-authenticated users.

If LinkedIn-authenticated signups convert better or route to sales-assist more accurately than your average signup, that's the case for promoting the login option higher on your signup screen, not just leaving it as a secondary choice buried under Google and email/password.

Where this fits into the rest of your enrichment stack

LinkedIn OAuth is one signup path among several, and it won't be your highest-volume one. Google and Microsoft will usually bring in more users. What it brings instead is higher-confidence professional data at the moment of signup, which is exactly the kind of signal PLG signup enrichment is built to use instead of discard.

Groful can wire LinkedIn-authenticated signups into the same enrichment, ICP scoring, and teammate discovery pipeline you already run for every other signup source, so a login choice turns into a routing decision instead of just a session. Check the blog for the rest of our signup-source playbooks, see how it fits your onboarding personalization flow, review pricing, or get in touch if you want help mapping LinkedIn sign-in into your existing scoring model.