Paminga IQ: ICP Classification Agent
When this action fires, a Paminga IQ agent crawls the Account's website, weighs what it finds against your ICPs, and records the Account's ICP for the Brand you chose in the action's settings — or, with no Brand chosen, the Account's ICP for All Brands.
From there, the ICP classification is yours to use:
- When using Paminga IQ to draft emails, landing pages, and CTAs
- Segment on it anywhere Paminga's Segment Builder appears.
This means you can score, customize content, trigger alerts, and more based on ICP - It's visible in the ICPs section of Account Details
This agent classifies Accounts against the ICPs you've defined. Until at least one ICP exists, there is nothing to classify against — the action's settings will point you there.
Choosing a Brand
The action has a Brand setting, and it decides two things: which ICPs the agent chooses among, and where the verdict is recorded.
- With a Brand chosen — the agent considers that Brand's ICPs plus the ICPs shared by every Brand, and records the result as the Account's ICP for that Brand.
- With no Brand chosen — the agent considers shared ICPs only, and records the result as the Account's ICP for All Brands.
An Account holds one ICP per Brand, so the same company can be classified differently for each brand you market to it. Two actions, one per Brand, classify the same Account twice — independently, and neither overwrites the other. If you market a single brand and haven't created any Brands, leave the setting empty. ICPs and Brands covers how shared and Brand-specific ICPs relate.
How the Agent Finds the Website
The agent uses the Account's Website field when it has a value.
When it doesn't, the agent infers the company's domain from the business email addresses of the Account's contacts — and writes the inferred website back to the Account's Website field, so the Account is more complete than it was before the agent ran.
Re-Classification
Companies change, and so do your ICPs. The action gives you two modes:
- Do not re-classify Accounts that have already been classified — each Account is classified once per Brand. This is the default.
- Re-classify if the Account's ICP classification is older than (days) — an Account becomes eligible again once its last classification for that Brand is older than the window you set. Use this when the action runs on recurring triggers (CRM sync, workflows) and you want classifications to stay current.
Both modes work per Brand. An Account classified for one Brand last month is still due its first classification for another Brand today, and one Brand's re-classification clock has no bearing on the other's.
"None of My ICPs" Is a Real Answer
The agent doesn't force a match. When it reads an Account's website and concludes that none of the candidate ICPs fit, it records that verdict: the Account's row for that Brand in the ICPs section reads No ICP matched. That counts as a classification — in "do not re-classify" mode the Account won't be re-evaluated for that Brand; with a re-classification window, it gets another look once the window passes.
This matters for segmentation: an Account with no ICP for a Brand is either "not yet classified" or "confidently no match," so segment on specific ICPs rather than on the absence of one when you want to target classified Accounts.
One Classification Per Account, Per Brand
The action is triggered by contacts — a form submission, an import, a CRM sync — but it operates on Accounts. When many contacts from the same company trigger the action at once (a large import, say), the Account is classified once for that Brand, not once per contact.
What the Agent Skips
The agent declines to classify Accounts where the result would be noise:
- Anonymous-visitor Accounts — Accounts resolved by IP lookup (internet service providers like Comcast) are skipped. The agent only classifies an Account once an identified contact belongs to it.
- The "-" placeholder Account — the catch-all for contacts with no company.
- Websites with too little readable content — if a site yields almost no text, the agent skips the Account rather than guessing. The Account stays eligible and will be picked up the next time the action fires for one of its contacts.
A Useful Side Effect
While reading an Account's website, the agent notices the company's social profiles. Any it finds — LinkedIn, X, Facebook, Instagram, YouTube — are written to the Account's matching fields, but only where those fields are empty. Values you've already curated are never overwritten.
Where You Can Trigger It
Like all Paminga Actions, this one is available everywhere actions are: form submissions, contact imports, CRM sync, workflows, lead scoring thresholds, Action Sets, and more — including as a Conditional Action, so you can classify only the Accounts that meet conditions of your choosing.
