A post about a problem you solve is a useful place to begin prospect research. The next step is to identify the right people, rather than collect everybody who clicked a reaction. This guide starts with one post and one usable profile file. The optional example below shows how to review that audience again later.

Find posts about the problem you solve

Use LinkedIn's native Posts search. For an onboarding consultant, the aim might be to find teams struggling with the sales-to-customer-success handoff.

  1. Search the problem. Try customer onboarding handoff, need help with onboarding or looking for CRM consultant as separate keyword searches. Adapt these examples to the service you sell.
  2. Choose Posts, then narrow the results. Under All filters, use Sort by and Date posted to pick a review window. For a known source, use From member or From company. Author industry and Author company describe the author, not everyone in the replies.
  3. Read the post and replies. Check the problem, the author's responsibility and the participants' current roles. Save the post link and a short reason for choosing it. If you only need the author, that research may be enough.
Four fictional posts: which deserves a closer look?
Illustrative postWhat it tells youWhat to do next
Can anyone recommend help fixing our sales-to-onboarding handoff?A request for help; scope and purchasing process are still unknown.Check the author's responsibility and relevant replies.
We fix your onboarding. Book a demo with our CRM consultancy.A provider promoting a service.Use it as market context; inspect participant discussions before choosing an audience.
Starting my new job in HR onboarding today!Employee onboarding, outside this customer-onboarding brief.Skip it for this offer.
How does your team hand closed deals over to customer success?A relevant problem discussion, without a confirmed project.Review participants' responsibilities and company fit.

These are fictional teaching examples. A comment or reaction gives you context, not confirmed buying intent or permission to contact.

Turn a selected post into a profile audience

If you need several relevant participants in a file, follow the post-commenter export guide for your selected post. The free profile allowance lets you try a supported source before choosing a larger extraction or a paid workflow.

  1. Set up your free account. Confirm your email and install the extension from the link in the app.
  2. Collect into an audience. Follow the selected source's import steps, choose or create an audience, and review the quantity and credit display before confirming.
  3. Export from the app. Open that audience and choose Export to CSV. Check the profile URLs, current roles and company values against your brief. Keep the post link beside the file so you know why you selected those people.

Check the chosen source in your account: post visibility affects who is available, and company or other profile fields may be blank. The file is profile data, not a verified email or phone list. Free profile sampling is separate from automatic post monitoring.

Build your first profile audience.

Start with the 100-profile, no-card offer. Try the source you need, open your audience in the app and inspect its CSV.

Get my 100 free leads

No card · Signup allowance released in batches of 20 · Current account terms apply

Choose which audience to revisit

Write down the roles, companies and geography you need, then keep posts whose topic and participants fit. For a recurring brief needing hundreds of profiles, count relevant people who are still missing from your audience. Students, peers, providers and company Pages can participate without being your buyers.

If your current tool already collects the right audience, keep it. HeyReach's LinkedIn Post (Reactors) source uses a logged-in LinkedIn account and excludes commenters. Dripify has separate likes and direct-comment lists, skips comment replies, and includes Evergreen collection on Advanced. Its collection report explains initial and Evergreen uploads and skipped records. A separate CSV is useful when you want to compare files or check contact history; it is optional when the native route already finishes the task.

Save a dated snapshot of the same post

  1. Keep the post link, interaction type, capture date, account/access context and filename together.
  2. Collect the profiles available to you, or keep a manually reviewed list. Preserve the original file.
  3. For the comparison, align the field meanings in both files. Keep changing capture dates in the filenames or source log, rather than a shared column that would make every row look changed.
  4. Choose when to review again. Weekly is a practical operating choice, not a promised collection schedule.

Comment ordering and restrictions and post visibility can change the set you can observe. A person missing from an export has not necessarily stopped engaging.

Ready to repeat the review? The optional exercise below compares two files, checks older contacts and separates people to keep from people to hold. It does not collect live posts or run an automatic monitor.

Fictional dated post snapshots lead to a seven-row candidate queue, historical exclusions and a separate two-row approved demonstration
Original workflow diagram · Leadsforlinked

Optional: practise a weekly review with the worked CSV example

All people, URLs, companies and dates in the exercise are fictional. The snapshots are labelled 5 and 12 October 2026. Contact-row files retain synthetic=TRUE and do_not_contact=TRUE. Changed fields has a report schema without contact flags and describes the same fictional keys. No example file is a production prospect payload.

Example files and expected results
StageDownloadData rows
SnapshotsPrevious: 5 October
Current: 12 October
7 / 13
ComparisonMain comparison
New key candidates
Missing keys
Changed fields
Identity review
12 / 7 / 2 / 1 / 5
Historical referencesIncomplete reference
Authored reviewed reference
4 / 4
Incomplete-reference runRemaining Main
Excluded
5 / 2
Reviewed-reference runRemaining Main
Excluded
4 / 3
Authored final decisionsApproved net-new demonstration
Held demonstration
2 / 2

The example manifest contains the mappings, counts and file hashes. The supplied history corrections and final decisions are part of the fictional example. The workbench compares files; you still decide which real people fit your brief.

Compare the two snapshots

Open Compare snapshots in the free workbench. Load the previous and current files. Select public_profile_url [2] in both matching selectors and keep LinkedIn profile URL as the identifier type. Leave Excel-safe downloads off to reproduce the supplied files, then choose Compare snapshots.

The example compares nine non-key fields. It produces seven unmatched current keys, two missing keys, one changed profile with one changed field, two unchanged profiles and five original observations for identity review. Main contains twelve rows. The reports overlap across the two files; adding their counts would not give you a prospect count.

  • W01 matches despite a host spelling and tracking suffix difference.
  • W02 has different role text. Check the change; it does not prove a promotion.
  • W05 has one previous row and two current rows with the same key. All three need review. W13 has an unresolved Sales Navigator path.
  • W04 appears as both missing and new because its slug case differs. LinkedIn's custom public URLs are case-insensitive, but this conservative matcher preserves slug case and encoding. Hold the possible alias.
  • W06 had a blank key in the old file. Its current usable key appears as New, although an earlier observation exists.

The matcher compares identifiers; it does not open profiles or verify identity. Use the comparison guide for the matching rules.

Remove people you already know or must exclude

Open Exclude existing contacts. Load the expected New file as New prospect list and the incomplete reference as Existing contacts or exclusions. Select the public-profile columns, keep the same identifier type and choose Compare lists.

The first run removes W08, an earlier accepted contact absent from last week's file, and W09, a suppressed contact. Five candidates remain. The report has no candidate Review rows, but the reference still contains a blank key and an invalid opaque key. Those reference warnings matter: an incomplete identifier cannot exclude a matching person.

Repeat with the supplied reviewed reference. Its fictional corrections include W06's historical public URL. Three candidates are excluded and four remain. In your own files, investigate missing reference identifiers and hold uncertain matches. Keep earlier accepted contacts and current suppression records together; last week's export alone is not the full history. The CRM exclusion guide explains that check.

Choose which remaining people fit the brief

Four rows remain, but only two fit this fictional brief. Hold W04 for the possible identity alias and W10 because its student role is outside the brief. W11 and W12 are the two approved demonstration rows: one commenter and one manually observed reactor. Their roles and the brief drive that decision, rather than the interaction alone.

Where the thirteen current records finish
DecisionCurrent recordsExamples
Already in the previous snapshot, including the changed observation3W01, W02, W07
Identity review3Both W05 originals, W13
Historical exclusion3W06, W08, W09
Manual hold2W04, W10
Approved demonstration2W11, W12

The count is 3 + 3 + 3 + 2 + 2 = 13. Comparison Review contains five observations because it also includes two previous originals.

For a real list, record the source row, snapshot date, history version, decision, reason and reviewer. Then prepare the fields your destination requires. The Clay guide and n8n CSV workflow cover those separate handoffs. The fictional approval columns here are not a production import schema.

Repeat the useful part, then choose your plan

Keep the original files, comparison results, history and decisions together. On your next review date, check the current audience against both the previous snapshot and the full history. A returning profile is not necessarily a new person.

Need more profile extraction? Basic is €4.99 monthly for extraction, CSV export and audiences. Starter is €29 monthly with one connected LinkedIn account, campaigns, inbox, Kanban and analytics. Pro adds auto-sourcing and AI tools; Plus lists Signal Radar, Post Spy and three connected accounts. For monitoring, confirm the source coverage and collection schedule available in your account, especially if you need keyword discovery across new posts.

The free offer includes 100 profile leads without a card, released in batches of 20. Use your sample and remaining audience requirement to choose further extraction; the offer planner can compare your one-time and recurring choices. You can choose a subscription directly when you need its workflow. Profile counts do not predict how many people will fit your brief.

LinkedIn restricts unauthorized scraping and automation. Neither a manual review nor a cloud or browser tool guarantees protection from account restrictions.

Sources and further reading

Frequently asked questions

Does post monitoring discover new posts by keyword?

Start with native LinkedIn Posts search to find discussions by keyword. This guide then uses a profile CSV and a later snapshot comparison to review a selected audience. Plus lists Signal Radar and Post Spy; confirm its source coverage and collection schedule in your account. The free profile allowance does not include automatic keyword monitoring.

Does new mean this person engaged during the last seven days?

No. New means the selected usable identifier is in the current file and absent from the previous one. It does not establish when someone interacted or whether they have appeared before. Visibility changes, incomplete capture and URL aliases can change the result.

Which Leadsforlinked plan includes automatic post monitoring?

The published Plus plan lists Signal Radar and Post Spy. Check the sources, quotas and collection schedule available in your account before choosing it. Basic covers extraction and CSVs; the free allowance and the manual comparison in this guide do not include scheduled monitoring.

Can I use a native post source instead?

Yes. HeyReach supports post reactors and excludes commenters. Dripify supports separate likes and direct-comment lists, skips comment replies and includes Evergreen collection on Advanced. Keep the native route when its audience and limits meet your task; you do not need an extra CSV step just to use another tool.

Why can exclusion show no Review rows when history is incomplete?

Review rows flag unusable candidate identifiers. Blank or invalid identifiers in your history are counted separately, so they can leave known contacts unmatched even when Review is empty. Resolve those history warnings before treating the remaining people as new.

Are the approved downloads safe to upload to a production CRM?

No. The people and profile-shaped URLs are fictional. The contact-row files retain synthetic=TRUE and do_not_contact=TRUE, including the approved demonstration. Those labels do not enforce a destination blocklist. Use the files for the exercise; do not contact, enrich or import them into production.

Make the next export useful.

Choose one relevant source, review the people and keep a profile file you can build on.

Get my 100 free leads

No card · Signup allowance released in batches of 20 · Current account terms apply