Skip to main content
Target accounts are the companies you are trying to reach. You can type them in, paste them, or import a CSV, each with its LinkedIn company page and its own tier. You can also point a list in your CRM at them, so the CRM stays the source of truth and Clustr follows it.

A LinkedIn company page is required

Every new target account needs the company’s LinkedIn page, like linkedin.com/company/acme, however it is added: typed in, pasted, from a CSV, through the API or MCP, or from a CRM list. A row without one is refused with the reason, and the rest are added. The LinkedIn company URL field links to a LinkedIn search for the name you typed, so you can copy the page’s address from there. Accounts you added before this rule stay as they are, with or without a URL.

When the LinkedIn page cannot be found

Clustr looks up a LinkedIn page it does not know yet in the background, at most twice, a week apart. When neither lookup finds it, the row on Targeting > Accounts shows LinkedIn page not found: it may be a wrong or outdated URL, so check it. The LinkedIn page not found filter above the list shows only those rows. Meanwhile the account is matched by its name when exactly one company carries that name. Correcting the URL clears the warning and starts the lookups again for the new page. The API and MCP report it as linkedin_lookup: not_found (List Target Accounts). Set this up on Targeting > Accounts, on the row for the CRM you have connected.

What each CRM calls it

The picker says which kind each one is, and puts the filter driven ones first. Binding a list that somebody maintains by hand is allowed, and it means what it says: the list moves when they move it. Attio offers saved views and not Attio Lists. A List is a set of entries somebody or an automation adds records to; a saved view is a stored filter, and a filter is what keeps a target account list in step without anyone tending it. A Salesforce list view that Salesforce will not hand over as a query appears in the picker, greyed out, with the reason on the row.

Your target list is the sum of its sources

Your target accounts are everything you added by hand or by file, plus every CRM list you link. Link lists one at a time; each one adds to the others.
  • An account you added by hand stays, with its tier, owner and tags, whatever any list does.
  • A company that is in a list and also added by hand, or in two lists, appears once, with every source that holds it.
  • You can filter the table by source: one list, or the accounts added by hand.

Companies with no LinkedIn page in the CRM

A company in the list becomes a target account only with its LinkedIn company page. Clustr takes it from the CRM record’s LinkedIn URL field and, when that is empty or is not a company page, from the company Clustr matched the record to. A company with neither is skipped, and the sync counts it as skipped. Fill in its LinkedIn URL in your CRM and it arrives with the next sync. An account the list added before this rule stays, with or without a URL.

Unlinking

Unlinking a list removes the accounts only that list held, and tells you how many go first. An account another list holds, or that you added by hand, stays.

When it updates

The list is pulled nightly, or when you press Sync now. There are no live updates: a company added to the list in your CRM at 10am appears in Clustr after the next sync. The list is the source of truth. A complete sync makes the accounts from that list match it exactly: a company that left the list in your CRM leaves your target accounts, however many leave at once. Two cases remove nothing:
  • a sync that stops before the end
  • a list that has been deleted in your CRM, or that your connection can no longer see. The row says the list is gone and offers to unlink it or link another one.

If the row says to reconnect

Reading lists needs a permission that Clustr did not ask for in earlier versions of the HubSpot connection. If yours was connected before that, the row says so and links to Settings, where reconnecting takes one click. Nothing else about your connection changes, and no data is re-imported. Salesforce and Attio connections already have what they need.

Through the API

There is no public API for the binding. It is available to agents through the MCP server, as three tools:
  • list_crm_account_lists shows the lists you could bind, and whether the CRM decides their membership from a filter
  • bind_target_accounts_to_crm_list binds one and pulls it now
  • unbind_target_accounts_from_crm_list stops following it and says how many accounts were removed
The target accounts themselves, from every source, are on List target accounts.