> ## Documentation Index
> Fetch the complete documentation index at: https://docs.leadinfo.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Profiles: ICP, Intent and Persona Builder

> Describe who you sell to, which pages signal buying intent and which people you want to reach. Profiles drive the fit, intent and people pillars of the score, and the API drafts them from your own data.

A profile is a named set of rules. An **ICP Builder** profile describes a good-fit account with firmographic rules; an **Intent Builder** profile names the pages that signal buying intent. Up to five profiles of each of those kinds count (`is_active`), the five oldest active ones: each company is scored against every one that counts and keeps its best match, so you can keep one profile per segment you sell to. Inactive profiles are drafts. **Persona Builder** profiles describe the people you want to reach; they have no active switch, and each company is scored against every persona and keeps the best one for the people pillar. Profiles belong to the customer and are shared with the Portal.

## Where profiles are managed

You create, change, switch on and delete profiles in the Portal's ICP Builder, Intent Builder and Persona Builder, or through the [Leadinfo MCP](https://docs.leadinfo.com/product/mcp/overview.md), which saves them after the user confirms. The Data API reads and drafts them:

| Endpoint | Scope | Purpose |
| - | - | - |
| `GET /v1/scoring-model` | `tracker:read` | The scoring model: weights, pillars and the active ICP and Intent profiles with their rules. |
| `GET /v1/profiles/{kind}/suggestions` | `tracker:read` | A draft profile from your own data, with the evidence behind every rule (see below). |

Live scores on company rows pick up a profile change within a minute; stored scores at the next scoring run.

## Rules

| Kind | What a profile holds |
| - | - |
| `icp` | Countries (ISO-2 codes), international sector codes and an employee range, at most one rule each. Sector codes are the full four-digit codes and match exactly. |
| `intent` | Page rules on `url` (the page path, without domain or query string) or `page_title`, each with `contains` or `not_contains` and a list of values; at most 15 rules. |
| `persona` | Job titles (exact, any case), titles that start with, titles to leave out, countries and departments. |

A company matches an ICP only when it matches all of its rules (fit 100, otherwise 0); matching two of three rules is no match, and a company with unknown data for a rule does not match it. Keep each ICP to the rules that define one segment, and create one ICP per segment you sell to.

Intent grows with each page rule matched: one about 50, two about 75, three about 85. Every rule counts the same. With several active profiles a company keeps the highest value, the breakdown names that profile, and stored scores list the value for every profile in `profile_scores`.

### Pages that never count as intent

An Intent rule with `not_contains` is an exclusion: page views it matches never count for the profile's other rules. Exclusions carry no weight and never raise intent; a profile needs at least one `contains` rule. Stored score explanations list a profile's exclusions as `excluded_pages`.

## Suggestions

`GET /v1/profiles/{kind}/suggestions?tracker_code=...&basis=...` drafts a profile from data and returns the evidence behind every rule, so the draft can be reviewed before it is saved in the Portal or through the Leadinfo MCP.

**ICP** drafts describe sectors (SIC major groups, named), company size, home markets and a revenue floor:

* `basis=customers`: the companies tagged customer on the tracker.
* `basis=crm`: the companies linked in the account's connected CRMs.
* `basis=cohort`: for accounts without either, the CRM-linked companies of other Leadinfo customers with the same SIC code prefix. Every customer weighs the same and values held by fewer than five customers are hidden.
* `basis=auto` (default) tries them in that order.

Each evidence row carries the share of the sample and, for the first two bases, the lift against all companies identified on the tracker.

> [!NOTE]
>
> An ICP Builder profile holds four-digit sector codes and no revenue rule. When you save a draft, use the four-digit codes within the drafted sector groups (for example the codes of your customers in them) and leave the revenue floor out.

**Intent** drafts (`basis=pages`) group the pages identified companies viewed in the last 180 days into families: pricing, demo or trial, contact or quote, comparison, integrations, product pages and customer cases. A rule with several values matches any of them. Every draft ends with one exclusion rule for login, account, blog, news, careers and legal pages, so those pages never count as intent.

**Persona** drafts describe the roles that visit: one draft per role family (marketing, sales, customer success, IT, HR, finance, owners and executives) with the exact job titles seen and the countries they came from, from identified visitors at customer-tagged, CRM-linked or all companies (`basis=customers|crm|visitors`), or from the personas of similar customers (`basis=cohort`). Persona drafts come back in `personas`, each with `as_rules` in Persona Builder format.

A `422` means the basis has too little data; the message says which basis to try instead.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.