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

# Target accounts

# Target Accounts

Target accounts are how BoothRev connects event conversations back to the accounts your ABM programme is actually built around — not just "did we get leads," but "did the accounts we planned for show up, and how far did the conversation go."

***

## What a target account is

A target account is a curated record: company name, email domain, territory, and line of business. It's tenant-wide, not tied to a single event — the same list applies across every event your team runs.

Manage your list at **Target Accounts** in the left sidebar (under Org). Field Marketing Managers curate this list. Unlike scorecard templates, it's editable and deletable at any time.

***

## Adding target accounts

* **One at a time** — enter a name, domain, territory, and line of business directly.
* **Bulk upload** — upload a CSV. Rows are matched (upserted) by domain, so re-uploading an updated list is safe: existing accounts get updated, new ones get added.

***

## How matching works

BoothRev matches a lead to a target account automatically, by email domain. You never tag a lead as a target account by hand.

Matching runs the moment a lead's email is confirmed, wherever that happens: a rep confirming on mobile, an event owner confirming on web, a CSV import, or a mobile sync push. Once a lead is matched, it's sticky — later edits to the lead never re-match or clear it.

Free email domains (Gmail, Yahoo, and similar) never match a target account, even if the company name looks right.

If you add or update target accounts after an event already has leads, use **Re-match target accounts** in Event Settings → Event Success (next to Re-score ICP for all leads) to re-run matching against every non-archived lead in that event.

***

## What changes when a lead is on a target account

Rev is told when a lead matches a target account, and it raises that lead's priority one level — Medium becomes High, Low becomes Medium. Target-account status alone is never enough to make a lead High priority; there still has to be a real engagement signal in the conversation.

This means a lead's priority in the inbox can reflect target-account status, not just the conversation itself. See [Reading Rev's output](/rev-ai/reading-rev-output) for the full picture of how priority is set.

***

## Target Account Coverage on the event dashboard

Open an event's dashboard and go to the **Qualification Trends** tab. Target Account Coverage shows your curated accounts side by side with this event's pre-registered invite list, so you can see two different things at once:

* **Curated accounts** — every account on your list, including the ones with zero contact yet. These "not yet engaged" rows are the whitespace: accounts you planned for that haven't shown up.
* **Pre-reg invite-list domains** — domains from this event's own pre-registered attendee import that aren't on your curated list, computed live at report time.

A lead counts as "engaged" once it's past a bare draft or import row — actually captured or confirmed, not just imported.

***

## What target accounts are not

* **Not auto-populated from a pre-registered attendee import.** That's deliberate — a one-off attendee CSV shouldn't silently bloat the curated list you maintain across every event.
* **Not a replacement for ICP.** ICP defines what a good lead looks like in general. Target accounts identify specific named companies you're tracking regardless of ICP fit.

***

## Related

* [Event dashboard and KPIs](/for-field-marketing-managers/event-dashboard)
* [Reading Rev's output](/rev-ai/reading-rev-output)
* [Setting up an event](/for-event-owners/setting-up-an-event)