Skip to main content
Leadinfo identifies companies. People enter the picture in three distinct ways, and telling them apart is what keeps outreach honest.

Identified visitors

GET /v1/trackers/{tracker_code}/visitors lists people who identified themselves on the website: through Persona Insights, a form, an email-campaign link or an integration. Each row carries company_id, company_name, email, first_name, last_name, job_title, phone, linkedin_url, country, first_event_at, last_event_at, source_confidence and matched_personas. Filter by company_id or persona_id. This is the only place where a named person is known to have visited. Form submissions (/form-submissions) and Leadbot conversations (/leadbot-submissions) return the captured field values per company and are the other two signals that a person acted.

Personas

Personas are the Persona Builder rules, the same ones the Portal shows: job titles, titles that start with, titles to leave out, countries and departments. They are managed in the Portal’s Persona Builder or through the Leadinfo MCP (see Profiles). Company rows count identified visitors matching any persona in persona_visitors. The people pillar of the score weighs what people at a company did, in full when they match a persona and at half otherwise (see Scoring), and persona_id on visitors, opportunities and contacts restricts results to matches. The API can also draft personas from your data (see Profiles).

Contacts

GET /v1/trackers/{tracker_code}/companies/{company_id}/contacts returns people who work at a recognised company according to Leadinfo’s contact database: name, position, position_category, departments, country, linkedin_url, leadership_score, seniority_score, has_email, email_verified and matched_personas. Persona matches come first; department and dmu (the decision makers of a department) and position_keyword narrow the list when a persona finds nobody, which happens at small companies where titles are informal. Contacts did not necessarily visit the website. Email and phone are not returned on the public API.

Writing to people

Whether you reach out yourself or let an assistant draft the message, the same rules apply:
  • The website identified the company, not the person. Never say or imply that a specific person visited.
  • Do not quote page-by-page behaviour in a message. Describe the topic the company showed interest in as a possible need.
  • Before outreach, check in_crm, crm_integrations and tags: existing customers, partners and open conversations belong to Sales, not to a prospecting sequence.