Sherlock Pro Scraper: 3 Practical Use Cases & Identity Resolution

Direct answer

Sherlock Pro Scraper searches for handles across 400+ social platforms, narrows queries to chosen target networks, and resolves whether target accounts match a known profile despite squatters or lookalikes. Operating in broadSearch or identityResolution modes, the Actor evaluates candidates using transparent, multi-signal scoring models including bio backlinks, display name similarity, avatar matching, follower counts, and verified status. Organizations deploy this tool for influencer verification, brand protection, and OSINT investigation workflows. By configuring parameters like targetNetworks, sourceProfile, sourceOverrides, and candidateHandles, researchers generate structured, decision-ready output containing bestMatch candidates and ranked confidence breakdowns while avoiding unverified guesses.

Align username search with key intelligence goals

Automated cross-platform handle detection requires moving beyond naive string matching. Squatters, fan accounts, and brand impersonators frequently claim identical handles on newly emerging platforms, creating noise for intelligence analysts, marketing teams, and brand safety personnel. Sherlock Pro Scraper addresses this problem by separating simple discovery from full identity resolution.

When executing identity resolution, the Actor evaluates candidates across independent criteria rather than relying solely on handle similarity. Bio backlinks, display name alignment, avatar visual similarity, relative follower counts, and platform verification badges are weighted individually. For instance, bio backlinks and profile details carry heavy weight because squatter profiles rarely link back to a genuine primary account. Furthermore, when no candidate clears the minimum confidence threshold, the Actor returns an honest negative result rather than forcing a low-confidence match.

Practical use cases

These use cases come from Sherlock Pro Scraper's published documentation. Each is expanded into an operating pattern so the Sherlock Pro Scraper output has a purpose beyond collection.

Use case 1: Influencer verification

Outcome: confirm which TikTok/Instagram/Twitter account genuinely belongs to a known creator before running a partnership or ad spend.

Question to answer: Which candidates fit the brief on both reach and content, and what would a reviewer need to see before approving one?

Configure: Start with sourceProfile (The known account to resolve against (identityResolution mode). Example: {"platform": "instagram", "handle": "xyz"}.), mode (broadSearch: check usernames across networks (optionally filtered). identityResolution: disambiguate which candidate account on a target network matches a source profile.), sourceOverrides (Optional manual displayName/bio/avatarUrl for the source profile, used when the source platform can't be auto-scraped (e.g. Instagram) or to supplement missing data.). Use the narrowest Sherlock Pro Scraper values that represent the real task, keep the first result set small, and record why each selected input matters to the Sherlock Pro Scraper outcome.

Working method: Convert every brief requirement into something checkable in the collected data, evaluate candidates against that checklist one item at a time, and keep the risk assessment separate from the reach number so neither hides the other.

Deliverable: Create a creator shortlist with fit evidence, content examples, open questions, and explicit reasons not to select a candidate. Include the Sherlock Pro Scraper source identifier and the collected fields behind every Sherlock Pro Scraper decision.

Stop condition: Pause when a checklist item cannot be verified from the collected data, or a candidate's recent activity is too sparse to judge fairly. Fix the Sherlock Pro Scraper question, comparison rule, or configuration before expanding the Sherlock Pro Scraper run.

Use case 2: Brand protection

Outcome: find squatter and impersonator accounts across networks and see exactly why they were flagged as low-confidence.

Question to answer: Which records satisfy the decision rule clearly enough to act on, and which need a second look?

Configure: Start with mode (broadSearch: check usernames across networks (optionally filtered). identityResolution: disambiguate which candidate account on a target network matches a source profile.), targetNetworks (Limit the search/resolution to these networks. Optional filter in broadSearch (omit to search all 400+). Required (1+) in identityResolution; exactly one network required when candidateMode is 'verify'. The list covers every network Sherlock supports plus Reddit (resolved via its own public search API for identityResolution).), usernames (Usernames to search for (broadSearch mode). Supports {?} wildcard (e.g. 'john{?}doe' expands to 'johndoe', 'john-doe', 'john.doe').). Use the narrowest Sherlock Pro Scraper values that represent the real task, keep the first result set small, and record why each selected input matters to the Sherlock Pro Scraper outcome.

Working method: Write the acceptance rule down before the first record is reviewed, apply it consistently across the batch, and change only one rule or input between batches so any shift in the result has a clear cause.

Deliverable: Create a decision-ready review queue that preserves each raw record and its inclusion or exclusion reason. Include the Sherlock Pro Scraper source identifier and the collected fields behind every Sherlock Pro Scraper decision.

Stop condition: Pause when the same record gets a different classification on a second pass, or a required field is missing often enough to change the outcome. Fix the Sherlock Pro Scraper question, comparison rule, or configuration before expanding the Sherlock Pro Scraper run.

Use case 3: Recruiting / vendor vetting

Outcome: cross-check a candidate's or vendor's professional and social presence before engaging.

Question to answer: Which opportunities actually satisfy the hard constraints, and which ones only look promising from the title?

Configure: Start with mode (broadSearch: check usernames across networks (optionally filtered). identityResolution: disambiguate which candidate account on a target network matches a source profile.), sourceOverrides (Optional manual displayName/bio/avatarUrl for the source profile, used when the source platform can't be auto-scraped (e.g. Instagram) or to supplement missing data.), candidateMode (discover: auto-generate candidates via search + username-variation heuristics. verify: score only the candidateHandles you supply.). Use the narrowest Sherlock Pro Scraper values that represent the real task, keep the first result set small, and record why each selected input matters to the Sherlock Pro Scraper outcome.

Working method: Apply the hard constraints as a first pass filter before reading any description closely, then rank only the survivors by preference fit, flagging anything with missing required fields instead of guessing.

Deliverable: Create an opportunity watchlist grouped by strong fit, possible fit, and missing-information review. Include the Sherlock Pro Scraper source identifier and the collected fields behind every Sherlock Pro Scraper decision.

Stop condition: Pause when a listing cannot be confirmed as still open, or the constraint check is relying on the title instead of a documented field. Fix the Sherlock Pro Scraper question, comparison rule, or configuration before expanding the Sherlock Pro Scraper run.

Step-by-step identity resolution workflow

1. Select the operational mode based on operational objectives: choose broad search for wide handle discovery across 400+ sites, or identity resolution to match a candidate against a known source profile.
2. Configure input parameters in the Apify console, specifying target networks, wildcard handle expansions using {?}, or explicit candidate handle lists.
3. Run the Sherlock Pro Scraper Actor and inspect the dataset for bestMatch candidates, transparent signal breakdowns, and non-fatal platform warnings.
4. Export decision-ready results as JSON, CSV, or XLSX files for integration into brand safety dashboards, creator databases, or investigative reports.

Parameter reference and schema configuration

Sherlock Pro Scraper provides structured controls across search modes:

• mode (string, required): Controls execution behavior. Options are broadSearch (searches handles across 400+ networks) or identityResolution (scores candidates against a source profile). Default: broadSearch.
• usernames (array of strings): Handles to search in broadSearch mode. Supports {?} wildcard expansion (e.g., john{?}doe expands to john_doe, john-doe, and john.doe).
• targetNetworks (array of strings): Limits searches to designated networks. Optional in broadSearch; required in identityResolution (exactly one network required when candidateMode is verify).
• sourceProfile (object): Known account to resolve against in identityResolution mode (e.g., {"platform": "instagram", "handle": "xyz"}).
• sourceOverrides (object): Optional manual attributes (displayName, bio, avatarUrl) for source profiles that cannot be auto-scraped.
• candidateMode (string): Controls candidate generation in identityResolution mode. Options are discover (auto-generates candidates via heuristics) or verify (scores provided handles). Default: discover.
• candidateHandles (array of strings): Specific candidate handles to score when candidateMode is set to verify.
• maxCandidatesToDiscover (integer): Caps auto-discovered candidates per target network in discover mode (range 1-60, default 20).

Data structure and output signal evaluation

Sherlock Pro Scraper returns clean JSON records without null values or empty placeholder strings.

Output fields for broadSearch mode:

• username: The exact username string queried during the run.
• links[]: Array containing profile URLs where the handle was found (omitted if no profile exists).

Output fields for identityResolution mode:

• sourceProfile: Source account details including platform, handle, profileUrl, displayName, and verified status.
• targetNetwork: The designated platform evaluated during the run.
• candidateMode: Indicates whether discover or verify mode was utilized.
• candidatesEvaluated: Integer count of candidate accounts scored.
• bestMatch: Highest confidence match object containing handle, profileUrl, confidenceScore, confidenceLabel, and signals (omitted if no candidate clears the confidence bar).
• candidates[]: Array of all evaluated candidate profiles ranked by confidence, complete with individual signal breakdowns.
• warnings[]: Array of non-fatal execution notes (omitted if empty).

Quality controls and error mitigation

• Validate candidate handles on platforms like TikTok using candidateMode: "verify" rather than discover, because TikTok existence checks flag random handles as active.
• Use sourceOverrides when analyzing source profiles on platforms that restrict public automated scraping (such as Instagram or Twitter) to ensure scoring algorithms receive valid display names and bios.
• Always review individual signals breakdowns inside bestMatch objects rather than relying solely on aggregate confidence scores.
• Rely on honest no-match outputs: if bestMatch is omitted, do not force an unverified match into production workflows.
• Utilize wildcard {?} expansions to catch punctuation variations without submitting separate manual batch jobs.

Frequently asked questions

How does identity resolution distinguish genuine profiles from impersonators?

The Actor evaluates candidates across independent weighted signals including bio backlinks to the source profile, display name similarity, profile picture visual match, platform verification status, relative follower count, and case-insensitive handle similarity. High-weight signals like bio backlinks and display name matches prevent squatter handles from achieving false positive matches.

Why is candidate discovery disabled on TikTok?

TikTok public endpoints report virtually all searched handles as existing user pages. To prevent generating false candidate accounts, auto-discovery is disabled for TikTok. Verification mode (candidateMode: "verify") remains fully functional when you provide explicit candidate handles.

How does the username wildcard expansion work?

Including {?} within a handle string inside the usernames array automatically expands the query into three standard separator variations. For example, entering john{?}doe searches for john_doe, john-doe, and john.doe in a single run.

Can target network queries be restricted to specific platforms?

Yes. Setting targetNetworks limits searching strictly to selected platforms from the supported list of 400+ networks. This speeds up run times and eliminates unnecessary platform checks.

Does Sherlock Pro Scraper require user account credentials or API keys?

No. The Actor operates entirely using publicly accessible web data and search endpoints, eliminating the need for platform logins, cookies, or external API keys.

Resources

• Sherlock Pro Scraper on Apify