Interesting individuals
What would you like to know about them?
Saved searches
Your searches, ready to run.
Click a search to open it in Advanced search with everything filled in. Save new ones from Advanced search.
Audiences
Searches turned into LinkedIn audiences.
Audiences are built from your Contacts — a list, or the contacts you pick — with Build LinkedIn audience there. Each file lists their valid work and personal emails with name, country, company and title — LinkedIn’s contact-list format.
How to use it on LinkedIn — and share it with a client
- Download CSV here. LinkedIn needs at least 300 rows; up to 300,000 per list.
- In Campaign Manager (your ad account): Plan › Audiences › Create audience › Upload a list › Contact list, and upload the file. Matching takes up to 48 hours.
- To give a client the audience: in Business Manager (you need to be an admin), add the client’s Business Manager as a partner, then Partners › the client › Matched Audiences › Share audiences. The client shares it with their ad account and uses it in campaigns.
- The client sees the audience and its size, never the list. They can’t edit, delete, copy or reshare it; Rebuild + re-upload here refreshes it for everyone using it.
Check that your data license allows ad targeting for clients. The files contain emails — keep them on this drive and delete them from your computer after uploading.
Advanced search
Find records by who they are, what they do, and where they work.
placed by ZIP or town county centre (approximate) · size = number of records · hover for details, click to open
Single lookup
Find a record by email, phone, or both.
Any format works — case, spaces, dashes and brackets are ignored. With both, records matching both come first.
Count by county
How many records are in a county?
Records are placed by ZIP code, or — when there's no ZIP — by town, if that town lies clearly in one county.
Enhance
Upload a list. Find the people behind it.
Stats
What’s in the data.
Earn credits
Share data we don’t have — get credits for future enhancements.
Your uploads
Columns
Choose which columns are available in queries. Unchecked columns stay in the data but won't be offered.
Index
Lookup indexes for fast queries: email and phone → record, record filters (location, company, job, contact quality), and company → records. Built from the Parquet files and stored next to the app in index\.
- Built
- —
- Records
- —
- Email keys
- —
- Phone keys
- —
- Records with a company
- —
- Size on disk
- —
Claude
Claude answers questions about the data by running counts and breakdowns on this computer. It only ever sees those numbers and your question — never names, emails, phones or addresses.
Claude connector Claude Desktop · claude.ai · Claude apps — uses your Claude plan
Claude Desktop on this computer Uses your Claude plan · needs the data on this computer
Dashboard chat Anthropic API · billed per token
- Model
- —
- Key file
- —
- Get a key
- console.anthropic.com → API keys. Usage is billed to that Anthropic account.
Outlook
Lets users sync their Contacts with Outlook (a test feature — turn it on per user in Settings › Users). It needs an app registration in your Microsoft account; no password or secret is stored here, and each user signs in to Microsoft themselves.
- Open the Microsoft Entra admin center — entra.microsoft.com — and sign in as an admin of your Microsoft 365 tenant.
- Go to Identity › Applications › App registrations (or Entra ID › App registrations in the newer menu). Open your existing app — or New registration to make one just for ID Dash.
- Authentication › Add a platform › Mobile and desktop applications, and add this custom redirect URI:
—(an existing Web platform for another app can stay as it is). - Still in Authentication › Advanced settings: Allow public client flows → Yes, then Save.
- API permissions › Add a permission › Microsoft Graph › Delegated permissions: Contacts.ReadWrite, User.Read and offline_access. Then Grant admin consent for your tenant (so users aren’t asked one by one).
- From the app’s Overview, copy the Application (client) ID and Directory (tenant) ID into the fields below. No client secret is needed — ID Dash signs in with PKCE.
If ID Dash runs on a different port on another computer, add that computer’s redirect URI to the app registration too.
Fees
What an enhancement costs (admins pay no fees). Charged when it finishes, for each uploaded record it links to a record (at the confidences the user chose). A rerun only pays for records it adds. Credits are used first.
Credits by user
Users
Everyone who can sign in to ID Dash on this drive. Each user has their own Contacts; admins also manage users, settings and the validation queue.
Add a user
Photos
Most photo_url values can’t be shown: LinkedIn photo links are signed, and the source stored them in lowercase, so LinkedIn refuses them — they can’t be repaired, only replaced. Links on static.licdn.com are LinkedIn’s generic silhouette. Replacement photos are kept on this drive by LinkedIn profile URL and shown instead, wherever that person appears; the source data is never changed.
- Replacement photos
- —
- Stored in
- —
Import refreshed photo URLs
A CSV with a LinkedIn profile column and a photo column — e.g. linkedin_url, photo_url or linkedin_profile_url, new_photo_url (a refreshed file from your data provider). Each photo replaces that person’s old one; importing again updates them.
One person at a time: in a record, the Photo line has Replace photo… — open their LinkedIn profile, right-click the photo, Copy image address, and paste it.
Data source
Where ID Dash reads from. Paths are resolved relative to the app folder, so the drive letter can change. Edit config.json to point elsewhere.
- Parquet folder
- —
- Files
- —
- Columns
- —
- Settings file
- —