Knowledge Base

Your Knowledge Base contains your company context, ICPs, personas, and exclusions so 1eyeᴬᴵ can evaluate signals and build lists with the right buyers.

Knowledge Base is the GTM brain of your 1eyeᴬᴵ workspace. It tells 1eyeᴬᴵ what your company does, which target companies matter, which buyers to find, and which pages to exclude from tracking.

Your Knowledge Base contains your company context, ICPs, personas, and exclusions so 1eyeᴬᴵ can evaluate signals and build lists with the right buyers. Keeping it accurate is one of the highest-leverage things you can do in your workspace.

Where to find the Knowledge Base

1. Open your 1eyeᴬᴵ workspace
2. Select Knowledge Base from the left-hand nav

What’s in the Knowledge Base

Tab	What it holds
Workspace Info	Your company profile — name, domain, and the context 1eyeᴬᴵ uses to understand your business
ICPs	The company profiles 1eyeᴬᴵ uses to evaluate fit — see ICPs
Personas	The contact profiles 1eyeᴬᴵ uses to match people — see Personas
Target Pages	The pages on your website that signal buying intent when visited
Exclusions	URLs to exclude from tracking, and pages to include for form tracking

Workspace Info

Workspace Info holds the company-level context 1eyeᴬᴵ uses to understand your business — your company name, domain, and description. Keep this accurate. 1eyeᴬᴵ uses it as background context alongside your ICPs and personas when evaluating fit.

ICPs and Personas

ICPs and personas are the strategy layer behind targeting — ICPs define which companies matter, personas define which people inside those companies matter. There’s no separate setup step here beyond what’s covered on their own pages. See ICPs and Personas for how to review, edit, and add new ones.

Target Pages

Target Pages are the pages on your website that indicate stronger buying intent when a contact visits them — for example, a pricing page, a demo request page, or a specific product page. Add or edit Target Pages so that 1eyeᴬᴵ can surface visits to these pages as higher-signal activity in Website Signals and on a contact’s timeline.

For Snowbricks, examples could include:

https://snowbricks.io/pricing
https://snowbricks.io/demo
https://snowbricks.io/product

Exclusions

Use Exclusions to control which pages the Vision pixel tracks and which pages are eligible for form tracking.

Excluded URLs — Add pages you don’t want 1eyeᴬᴵ tracking at all — for example, login, account, admin, careers, or internal pages. For Snowbricks, examples could include:

https://snowbricks.io/login
https://snowbricks.io/careers
https://app.snowbricks.io/*

Form tracking — Add the pages where a form submission should count as a signal — typically demo, contact, trial, or newsletter pages. For Snowbricks, examples could include:

https://snowbricks.io/demo
https://snowbricks.io/contact
https://snowbricks.io/trial

Only add forms where a submission is meant to identify a business contact for GTM purposes. See Install Vision Pixel for the privacy and compliance checklist to ### Target Forms

Target Forms are the specific form URLs on your website — like a contact form, demo request, or trial signup — where 1eyeᴬᴵ identifies submissions as high-intent signals. Add a Target Form with its domain, URL, and a short name so 1eyeᴬᴵ can recognize submissions on that page and surface them in Website Signals and on a contact’s timeline.

For Snowbricks, an example could be:

Field	Example
Domain	snowbricks.io
URL	https://snowbricks.io/contact
Short Name	Contact

review before turning form tracking on.

Best practices

• Keep Workspace Info current — If your company description or domain changes, update it here so fit evaluation stays accurate.
• Review ICPs and personas together — They’re evaluated together on every buyer — a stale ICP or persona affects fit scoring across the whole workspace.
• Add Target Pages that reflect real intent — Pricing, demo, and product pages are usually stronger signals than generic content pages.
• Exclude internal and sensitive pages — Keep login, admin, and internal tooling out of tracking.
• Scope form tracking intentionally — Only track forms meant to identify a business contact — not every form on your site.

Troubleshooting

• A company isn’t matching my ICP the way I expect — Review the ICP definition on the ICPs page — check for criteria that may be too narrow or too broad.
• A contact isn’t matching a persona — Review the persona definition on the Personas page, or check the persona match explanation on the contact’s record.
• A page visit isn’t showing as high-signal — Confirm the page is added under Target Pages, and that the Vision pixel is installed and tracking on that URL — see Install Vision Pixel.
• A page I excluded is still showing activity — Confirm the URL pattern under Excluded URLs matches the actual page URL, including any trailing slashes or query parameters.

FAQ

Do I need to set up my Knowledge Base before using 1eyeAI?

Yes. 1eyeᴬᴵ creates an initial ICP, persona, and workspace context during onboarding, but reviewing and tuning them improves match quality from day one.

How often should I update my Knowledge Base?

Whenever your ideal company profile, target roles, or website structure changes. Many teams review it quarterly or after a positioning change.

Can I have more than one ICP or persona?

Yes. See ICPs and Personas for how multiple profiles are evaluated together.

What's the difference between Excluded URLs and Target Pages?

Excluded URLs stop 1eyeᴬᴵ from tracking a page at all. Target Pages do the opposite — they flag a page as a stronger buying-intent signal when visited.

Next step

Next, go to ICPs to review or refine the company profiles 1eyeᴬᴵ uses to evaluate fit.