Getting started
Knowledge Base
KB contains your company context, ICPs, personas, and exclusions so 1eyeᴬᴵ can evaluate signals, build lists, and target the right companies and contacts.
Knowledge Base is the GTM brain of your 1eyeᴬᴵ workspace. It tells 1eyeᴬᴵ what your company does, which target companies matter, which target contacts to find, and which companies should be excluded from targeting.
1eyeᴬᴵ builds your initial Knowledge Base automatically from your company website, domain, and workspace context. Your team can then review, edit, add, or remove items before launching campaigns.
Before you begin
To review your Knowledge Base, you need:
A 1eyeᴬᴵ workspace
Your company domain added to the workspace
Admin or workspace access
Basic understanding of your target market
For this guide, we’ll use Snowbricks as the example workspace.
Field | Example |
|---|---|
Company | Snowbricks |
Domain | snowbricks.io |
Workspace admin | Matt Bru |
Admin email | |
Company type | B2B AI data company |
Where to find the Knowledge Base

You can access the Knowledge Base from the top-right navigation in your 1eyeᴬᴵ workspace.
Open your 1eyeᴬᴵ workspace
Go to the top-right navigation
Select Knowledge Base
Review the tabs inside the Knowledge Base
The Knowledge Base includes four main tabs:
Workspace Info
ICPs
Personas
Target Pages
Exclusions
Each tab helps 1eyeᴬᴵ understand a different part of your GTM strategy.
What 1eyeᴬᴵ creates for you
When your workspace is created, 1eyeᴬᴵ builds an initial Knowledge Base for your company.
For Snowbricks, 1eyeᴬᴵ may create:
Workspace information based on snowbricks.io
ICPs for companies that are a strong fit
Personas for target contacts inside those companies
Exclusions for companies that should not be targeted
This gives your team a starting point instead of forcing you to build GTM strategy from a blank page.
Why the Knowledge Base matters
The Knowledge Base powers how 1eyeᴬᴵ evaluates signals, builds target lists, and launches campaigns.
When a company signal comes in, 1eyeᴬᴵ evaluates whether the company matches your ICPs.
When a contact signal comes in, 1eyeᴬᴵ evaluates whether the contact matches your personas.
That means your ICPs and personas directly shape which companies and contacts get prioritized, enriched, added to lists, and moved into campaigns.
A strong Knowledge Base helps 1eyeᴬᴵ answer three important questions:
Is this company a good target company?
Is this person a good target contact?
Should this company or contact be added to a target list or campaign?
Workspace Info

The Workspace Info tab contains the core company context for your workspace.
For Snowbricks, this may include:
Field | Example |
|---|---|
Workspace name | Snowbricks |
Domain | snowbricks.io |
Description | Snowbricks is a B2B AI data company that helps teams activate trusted data, automate workflows, and turn business context into actionable intelligence. |
Company logo | Snowbricks logo |
This information helps 1eyeᴬᴵ understand what your company does and how to position your GTM motion.
What to review in Workspace Info
Review the Workspace Info tab for accuracy.
Check:
Company name
Domain
Company description
Logo
Market category
Product description
Value proposition
For Snowbricks, make sure the description clearly explains that Snowbricks is a B2B AI data company.
A strong description could be:
ICPs

ICPs define the types of target companies that are a strong fit for your product.
1eyeᴬᴵ uses ICPs to evaluate companies, prioritize signals, build target lists, and decide which accounts should move into campaigns.
When a company visits your website or shows activity, 1eyeᴬᴵ evaluates that company against your ICPs. If the company matches one or more ICPs, it can be prioritized as a target company.
For Snowbricks, 1eyeᴬᴵ may create ICPs based on the company website, product category, and market context.
Example ICPs for Snowbricks
Here are example ICPs for Snowbricks as a B2B AI data company.
ICP Name | Short Name | Description |
|---|---|---|
Data-Driven B2B SaaS Companies | B2B-SAAS | B2B SaaS companies that rely on clean company, contact, product, and customer data to power GTM, customer success, analytics, or automation workflows. |
Revenue Operations Teams | REVOPS | Companies with RevOps teams responsible for CRM quality, enrichment, routing, scoring, segmentation, reporting, and GTM data automation. |
AI-Native GTM Companies | AI-GTM | Companies using AI to improve sales, marketing, customer engagement, enrichment, research, routing, or workflow automation. |
Data Infrastructure Companies | DATA-INFRA | Companies building or using modern data stacks, warehouses, reverse ETL, enrichment tools, and business intelligence systems. |
Enterprise Sales Organizations | ENT-SALES | Mid-market and enterprise companies with large sales teams that need better account intelligence, target prioritization, and workflow automation. |
B2B Marketplaces and Platforms | B2B-PLATFORM | Platforms with complex company, vendor, partner, or account data that need enrichment, segmentation, matching, or activation. |
Customer Data and Analytics Teams | DATA-OPS | Teams responsible for organizing customer, account, and behavioral data across tools so the business can act on it. |
How ICPs are used
1eyeᴬᴵ uses ICPs to understand which companies Snowbricks should care about.
ICPs help 1eyeᴬᴵ:
Score companies for fit
Evaluate company signals for ICP match
Prioritize website visitors
Identify target companies
Build target company lists
Recommend campaign audiences
Personalize outreach based on company type
Exclude companies that are not a fit
How to review ICPs
Open the ICPs tab and review each ICP created by 1eyeᴬᴵ.
For each ICP, check:
ICP name
Short name
Description
Company type
Industry fit
Company size fit
Geographic fit
Buying triggers
Use cases
Whether the ICP should be active
A good ICP should be specific enough for 1eyeᴬᴵ to make targeting decisions.
Weak ICP:
Better ICP:
Add or edit ICPs
You can add a new ICP if 1eyeᴬᴵ missed an important target segment.
Use Add ICP to create a new ICP.
Add a new ICP when:
You are entering a new market
You sell to multiple company types
You want to separate enterprise and SMB targeting
You have different messages for different industries
You want to build campaigns for a specific segment
Edit an ICP when:
The description is too broad
The company type is not accurate
The ICP includes companies you do not want
The ICP misses important buying triggers
The ICP needs clearer targeting language
Personas

Personas define the target contacts 1eyeᴬᴵ should find inside target companies.
Personas help 1eyeᴬᴵ understand who to identify, enrich, prioritize, and engage.
When a contact signal comes in, 1eyeᴬᴵ evaluates whether that person matches your personas. If the contact matches one or more personas, 1eyeᴬᴵ can prioritize them as a target contact.
For Snowbricks, personas should focus on the people who own data, revenue operations, GTM systems, analytics, AI adoption, and business automation.
Example personas for Snowbricks
Here are example personas for Snowbricks as a B2B AI data company.
Persona Name | Short Name | Description |
|---|---|---|
Revenue Operations Leader | REVOPS | RevOps leader responsible for CRM data quality, enrichment, routing, scoring, attribution, reporting, and GTM workflow automation. |
Head of Data | DATA | Data leader responsible for data infrastructure, governance, quality, activation, and business intelligence. |
VP Sales | VP-SALES | Sales leader focused on pipeline generation, account prioritization, sales productivity, and better target company intelligence. |
VP Marketing | VP-MKTG | Marketing leader responsible for campaign targeting, account-based marketing, conversion, attribution, and demand generation data. |
GTM Systems Leader | GTM-SYS | Operator responsible for CRM, marketing automation, enrichment tools, routing logic, and sales engagement systems. |
AI Transformation Leader | AI-LEADER | Executive or operator responsible for adopting AI across GTM, data, operations, or customer-facing workflows. |
Business Operations Leader | BIZOPS | Operator focused on process automation, data visibility, reporting, and cross-functional operational efficiency. |
Founder or CEO | FOUNDER | Founder or executive at a fast-growing B2B company looking to scale GTM with better data, automation, and intelligence. |
How personas are used
1eyeᴬᴵ uses personas to find the right target contacts inside target companies.
Personas help 1eyeᴬᴵ:
Identify relevant contacts
Evaluate contact signals for persona match
Enrich work emails and phone numbers when available
Match contacts to target company context
Personalize campaign messaging
Choose the right angle for outreach
Prioritize contacts based on role and relevance
Route contacts into the right campaign workflows
How to review personas
Open the Personas tab and review each persona created by 1eyeᴬᴵ.
For each persona, check:
Persona name
Short name
Description
Seniority
Function
Department
Job titles
Pain points
Buying role
Relevance to your GTM motion
A good persona should describe the person 1eyeᴬᴵ should find, not just a generic department.
Weak persona:
Better persona:
Add or edit personas
Use Add Persona to create a new target contact type.
Add a persona when:
You sell to a new function
You need to target a new seniority level
You want a separate campaign for a specific role
1eyeᴬᴵ missed an important target contact
You want to personalize messaging by job function
Edit a persona when:
The title list is too broad
The function is wrong
The persona is not part of the buying process
The description is unclear
The persona needs sharper targeting language
Build lists from ICPs and personas
You can use ICPs and personas to source and build target lists.
1eyeᴬᴵ can help you build:
Target company lists based on ICP match
Target contact lists based on persona match
Campaign audiences based on company fit and contact relevance
Lists from active signals, such as website visitors or engaged contacts
Lists for specific segments, industries, roles, or use cases
For Snowbricks, you could build a list like:
Or:
This is where the Knowledge Base becomes operational. ICPs define the companies. Personas define the contacts. 1eyeᴬᴵ uses both to help you build sharper lists and launch better campaigns.
Target Pages
arget Pages tell 1eyeᴬᴵ which URLs on your website matter most, so visits to those pages stand out as signals, can be searched and filtered, and can be used to build target lists.
Not every page on your site carries the same intent. A visit to /pricing or /demo usually means more than a visit to /blog. Target Pages let your team mark the URLs that matter so 1eyeᴬᴵ can highlight them wherever signal activity shows up.
For Snowbricks, useful Target Pages could include:
Target Page Name | Target URL | Match Type |
|---|---|---|
Homepage |
| Exact Match |
Pricing page |
| Exact Match |
Demo request |
| Exact Match |
Case studies |
| Starts With |
Blog |
| Contains |
Where to find Target Pages
Target Pages live in the Knowledge Base, alongside Workspace Info, ICPs, Personas, and Exclusions.
Open your 1eyeᴬᴵ workspace
Go to the top-right navigation
Select Knowledge Base
Select the Target Pages tab
The Target Pages tab lists every page you have marked, along with its match type, status, and description.
Add a Target Page
Select Add Target Page to open the form.
The form includes:
Field | Required | Description |
|---|---|---|
URL | Yes | The page path 1eyeᴬᴵ should watch for, e.g. |
Match Type | Yes | How the URL should be matched. See Match Types below. |
Target Page Name | Yes | A human-readable name shown on badges and filters, e.g. "Pricing page". |
Short Name | Yes | A compact identifier used in lists and filters, e.g. |
Descriptions | No | Why this page matters, for your team's context. |
Example for Snowbricks:
Select Save to add the page to your Knowledge Base.
Match Types
Match Type controls how 1eyeᴬᴵ compares a visited URL against the Target Page you defined.
Match Type | What it matches |
|---|---|
Exact Match | Only the exact URL, e.g. |
Contains | Any URL that contains the given string anywhere in the path, e.g. |
Starts With | Any URL that begins with the given path, e.g. |
Ends With | Any URL that ends with the given string, e.g. |
Use Exact Match for single, specific pages like pricing or demo. Use Contains, Starts With, or Ends With for page groups, such as an entire blog, docs, or resources section.
Status: Active and Inactive
Each Target Page has a status.
Status | What it means |
|---|---|
Active | The page is being matched against incoming signal activity. |
Inactive | The page is kept in your Knowledge Base but is not matched against new activity. |
Set a Target Page to Inactive instead of deleting it if you want to pause matching without losing the page's history, description, or short name.
Editing a Target Page
Select a Target Page to open its details drawer.
From the details drawer you can update:
Match Type
Target Page Name
Short Name
Description
Status (Active / Inactive)
The URL cannot be edited once a Target Page is created. If the URL is wrong or needs to change, add a new Target Page with the correct URL and set the old one to Inactive.
How Target Pages are used
Once a Target Page is active, 1eyeᴬᴵ uses it across the workspace:
Signals — page visits that match a Target Page are shown with a Target Page badge on both the company and contact signal cards.
Signal filters — you can filter Signals by one or more Target Pages, with conditions on visit count and total time spent.
Target Lists — the "Signals by Company" sourcing flow can filter for companies that visited specific Target Pages, so you can build a list directly from high-intent page activity.
Exclusions List

Exclusion Lists help prevent 1eyeᴬᴵ from targeting companies or contacts that should not be included in campaigns.
You can create and manage multiple Exclusion Lists for different purposes, making it easier to organize and control who is excluded from outreach. Lists can be edited, archived, or reused across campaigns as your requirements change.
When creating a campaign, you can choose which Exclusion Lists to apply. By default, all active Exclusion Lists are selected.
Common Exclusion Lists
You may create separate lists for:
Existing customers
Competitors
Unsubscribed contacts
Partners
Vendors
Investors
Agencies
Students or academic organizations
Companies outside your target market
Strategic accounts
Any custom exclusion segment
Managing Exclusion Lists
You can:
Create multiple Exclusion Lists
Add or remove companies and contacts
Import exclusions in bulk
Rename lists as your needs evolve
Archive lists that are no longer required
Reuse lists across multiple campaigns
Well-maintained Exclusion Lists help ensure campaigns remain relevant, compliant, and focused on the right audience.
For Snowbricks, example exclusions could include:
Company | Reason |
|---|---|
Snowbricks | Own company |
Existing customers | Already customers |
Direct competitors | Do not target competitors |
Current vendors | Not part of outbound targeting |
Implementation partners | Partner relationship, not prospecting |
Recruiting agencies | Not a target company |
Universities | Not a priority ICP unless intentionally targeted |
Consumer apps | Not a B2B AI data target |
Small local businesses | Not a fit for Snowbricks’ B2B AI data motion |
How exclusions are used
1eyeᴬᴵ uses exclusions to avoid targeting the wrong companies.
Exclusions help 1eyeᴬᴵ:
Keep target lists clean
Avoid contacting competitors
Avoid contacting customers
Avoid wasting credits
Improve campaign quality
Reduce irrelevant outreach
Keep GTM workflows focused
How to review exclusions
Open the Exclusions tab.
Review the companies that 1eyeᴬᴵ added automatically.
Check:
Company name
Domain
Reason for exclusion
Whether the company should stay excluded
Whether any important companies are missing
If a company should not be targeted, keep it in exclusions.
If a company was excluded by mistake, remove it from the list.
Add a Company to exclusion list
Use Add Company in List details when you want 1eyeᴬᴵ to avoid a specific company.
Add an exclusion when:
The company is already a customer
The company is a competitor
The company is a vendor
The company is a partner
The company is not a fit
The company should not receive outreach
Your team has a strategic reason to avoid it
For example:
Keep your Knowledge Base current
Your Knowledge Base should evolve as your business grows. As Snowbricks enters new markets, tests new segments, learns which companies convert, or changes positioning, your team should continue fine-tuning ICPs, personas, and exclusions. A stale Knowledge Base creates noisy signals and weak campaigns. A sharp Knowledge Base helps 1eyeᴬᴵ keep improving target quality over time.
Best practices
Review the Knowledge Base before launching campaigns
Make sure the workspace info, ICPs, personas, and exclusions are accurate before engaging target contacts.Keep ICPs specific
Broad ICPs create noisy target lists. Specific ICPs help 1eyeᴬᴵ prioritize the right companies.Separate ICPs by market segment
If Snowbricks sells to B2B SaaS, data infrastructure companies, and enterprise sales teams, keep those as separate ICPs.Make personas role-specific
Avoid generic personas like “marketing” or “sales.” Use specific personas like Revenue Operations Leader, Head of Data, or VP Marketing.Use exclusions aggressively
Exclusions prevent wasted credits and low-quality outreach.Build lists from ICP and persona match
Use ICPs to source target companies and personas to source target contacts. This keeps lists focused and campaign-ready.Use signals to validate your strategy
Company signals should be evaluated against ICPs. Contact signals should be evaluated against personas. Use what you learn to improve the Knowledge Base.Update the Knowledge Base as your GTM motion changes
Add, edit, or remove ICPs and personas as you learn which segments convert.Check generated content for accuracy
1eyeᴬᴵ creates the initial Knowledge Base, but your team should review it before relying on it for campaigns.Align ICPs and personas
ICPs define the target companies. Personas define the target contacts inside those companies. Both need to work together.Use short names carefully
Short names make ICPs and personas easier to scan in lists, filters, and campaigns.Mark your highest-intent pages first
Pricing, demo, and signup pages are usually the strongest signal.Use Exact Match for single pages
Reserve Contains, Starts With, and Ends With for page groups like blog or docs sections.Keep names and short names clear
Short names show up in filters and badges, so keep them scannable, e.g.pricing_page,demo_request.Write a short description
A one-line description helps teammates understand why a page was marked without asking.Deactivate instead of deleting
Set outdated pages to Inactive so you keep the history without matching future activity.Review Target Pages as your site changes
Add new Target Pages when you launch new high-intent pages, and update match types if your URL structure changes.Keep exclusions current
Add customers, competitors, partners, and strategic no-contact companies as your business changes.Can I archive an Exclusion List?
Yes. Lists that are no longer needed can be archived and excluded from future campaign configurations.Can I create multiple Exclusion Lists?
Yes. You can create separate lists for customers, competitors, unsubscribes, partners, or any custom segment and apply them selectively to campaigns.
Example Snowbricks Knowledge Base
Here is what a strong Snowbricks Knowledge Base could include.
Workspace Info
Field | Example |
|---|---|
Workspace name | Snowbricks |
Domain | snowbricks.io |
Description | Snowbricks is a B2B AI data company that helps teams unify company data, automate enrichment, and activate trusted business intelligence across GTM workflows. |
ICPs
ICP | Short Name |
|---|---|
Data-Driven B2B SaaS Companies | B2B-SAAS |
Revenue Operations Teams | REVOPS |
AI-Native GTM Companies | AI-GTM |
Data Infrastructure Companies | DATA-INFRA |
Enterprise Sales Organizations | ENT-SALES |
B2B Marketplaces and Platforms | B2B-PLATFORM |
Personas
Persona | Short Name |
|---|---|
Revenue Operations Leader | REVOPS |
Head of Data | DATA |
VP Sales | VP-SALES |
VP Marketing | VP-MKTG |
GTM Systems Leader | GTM-SYS |
AI Transformation Leader | AI-LEADER |
Founder or CEO | FOUNDER |
Exclusions
Exclusion Type | Example |
|---|---|
Own company | Snowbricks |
Customers | Existing Snowbricks customers |
Competitors | Direct AI data competitors |
Vendors | Current vendors |
Partners | Implementation or data partners |
Not a fit | Companies outside Snowbricks’ target market |
Troubleshooting
ICPs look too broad
If 1eyeᴬᴵ creates ICPs that feel too broad, edit the descriptions to include more specific company types, industries, size ranges, use cases, and buying triggers.
Instead of:
Use:
Personas do not match your target contacts
If personas are missing important roles, add new personas manually.
For Snowbricks, you may want to add:
RevOps Leader
Head of Data
GTM Systems Leader
VP Sales
VP Marketing
AI Transformation Leader
Company signals are not matching ICPs correctly
If active companies are not being evaluated the way you expect, review your ICP descriptions.
Check whether your ICPs include:
Clear company types
Relevant industries
Company size ranges
Use cases
Buying triggers
Exclusions for poor-fit companies
Contact signals are not matching personas correctly
If active contacts are not being evaluated the way you expect, review your personas.
Check whether your personas include:
Relevant job titles
Function and department
Seniority
Buying role
Pain points
Use cases
A page visit is not showing a Target Page badge
Check:
The Target Page is set to Active
The Match Type is correct for the visited URL
The URL was entered without typos
The visit happened after the Target Page was created
I created the wrong URL
The URL field cannot be edited. Set the incorrect Target Page to Inactive and add a new one with the correct URL.
Too many pages are matching
Your Match Type may be too broad. Switch from Contains or Starts With to Exact Match if you only want one specific page to match.
Target lists are too noisy
If your target lists include too many poor-fit companies or contacts, tighten your ICPs, personas, and exclusions.
Noisy lists usually come from:
ICPs that are too broad
Personas that are too generic
Missing exclusions
Weak company description
Old workspace context
Exclusions are missing important companies
Add exclusions for:
Your own company
Existing customers
Competitors
Partners
Vendors
Companies your team should not contact
A company was excluded by mistake
Remove it from the Exclusion list so 1eyeᴬᴵ can evaluate it as a possible target company.
Knowledge Base was generated from old website copy
Update the Workspace Info description and refine your ICPs and personas manually.
If your website changes, review the Knowledge Base again to make sure it still reflects your current positioning.
Campaigns are targeting the wrong companies
Check your ICPs and exclusions first.
Poor targeting usually comes from:
ICPs that are too broad
Personas that are too generic
Missing exclusions
Weak company description
Old workspace context
FAQ
Does 1eyeᴬᴵ create the Knowledge Base automatically?
Yes. 1eyeᴬᴵ creates an initial Knowledge Base for your workspace using your company website, domain, and available context.
Can I edit the Knowledge Base?
Yes. You can edit workspace info, ICPs, personas, and exclusions.
Do I need to review it before launching campaigns?
Yes. Review the Knowledge Base before launching campaigns so 1eyeᴬᴵ targets the right companies and contacts.
What is the difference between an ICP and a persona?
An ICP defines the target company. A persona defines the target contact inside that company.
How does 1eyeᴬᴵ use ICPs with signals?
When a company signal comes in, 1eyeᴬᴵ evaluates whether the company matches your ICPs. This helps prioritize the right target companies.
How does 1eyeᴬᴵ use personas with signals?
When a contact signal comes in, 1eyeᴬᴵ evaluates whether the contact matches your personas. This helps prioritize the right target contacts.
Can I build lists from ICPs and personas?
Yes. You can use ICPs to source target companies and personas to source target contacts. You can also combine fit and signal activity to build focused campaign lists.
Can I edit the URL after creating a Target Page?
No. All other fields (Match Type, Target Page Name, Short Name, Description, Status) can be edited from the details drawer, but the URL cannot be changed.
What is the difference between the four Match Types?
Exact Match matches one specific URL. Contains, Starts With, and Ends With match a group of URLs based on where the string appears in the path.
What happens if I set a Target Page to Inactive?
1eyeᴬᴵ stops matching new signal activity against it, but the page and its history stay in your Knowledge Base.
Do Target Pages affect ICP or persona matching?
No. Target Pages are separate from ICPs and personas. ICPs evaluate company fit and personas evaluate contact fit. Target Pages flag which URLs were visited.
What are exclusions?
Exclusions are companies 1eyeᴬᴵ should not target.
Can I add my own ICPs?
Yes. Use Add ICP to create a new target company profile.
Can I add my own personas?
Yes. Use Add Persona to create a new target contact profile.
Can I add my own exclusions?
Yes. Use Add Exclusion to prevent 1eyeᴬᴵ from targeting specific companies.
How often should I update the Knowledge Base?
Update it whenever your positioning, target market, product, ICP, personas, customers, competitors, or GTM strategy changes.
Next step
After reviewing your Knowledge Base, go to Invite Users so the right teammates can help review signals, build target lists, launch campaigns, and manage conversations.