> ## Documentation Index > Fetch the complete documentation index at: https://docs.1eye.ai/llms.txt > Use this file to discover all available pages before exploring further. # Personas > Personas define the types of buyers 1eyeᴬᴵ should find, evaluate, prioritize, and engage inside your target companies. A persona describes the people inside your target companies who matter for your GTM motion. These are usually the roles involved in buying, evaluating, influencing, using, or approving your product. In 1eyeᴬᴵ, personas are not just labels in your Knowledge Base. They power how 1eyeᴬᴵ evaluates contact signals, sources contacts, builds target lists, and helps your team decide which people are worth engaging. A clear persona helps 1eyeᴬᴵ separate relevant buyers from noisy contact activity. ## Why personas are critical Every B2B business needs clear personas. Your ICP tells 1eyeᴬᴵ which companies are a good fit. Personas tell 1eyeᴬᴵ which people inside those companies are worth finding and engaging. For example, a company may be a great fit, but not every person at that company is relevant. The important question is: is this person the right buyer inside the company? That is what a persona helps answer. Without personas, your team may see contacts visiting your website, but you will not know who actually matters. ## Why 1eyeᴬᴵ relies on personas 1eyeᴬᴵ uses personas as the contact-level strategy layer across your GTM workflow. Personas help 1eyeᴬᴵ understand: which contacts are relevant; which contacts should be prioritized; which contacts should be ignored; which contacts should be enriched; which contacts should be added to target lists; which contacts should move toward a Destination; which contacts should receive specific messaging. Signals tell 1eyeᴬᴵ that activity happened. Personas tell 1eyeᴬᴵ whether that activity came from a person who matters. ## What a persona contains A persona describes a buyer type. A good persona may include: job title, seniority, function, department, target departments, keywords, buying role, pain points, responsibilities, use cases, goals, buying triggers, common objections, example titles, example contacts when available. For example: "Revenue operations leaders responsible for CRM quality, routing, enrichment, attribution, reporting, segmentation, and GTM workflow automation. These contacts usually sit between sales, marketing, and operations and care about clean data, better account prioritization, accurate reporting, and improving sales team productivity." That is much stronger than: "Sales." The stronger version gives 1eyeᴬᴵ enough context to understand the role, department, responsibility, buying relevance, and likely fit. ## Where to find personas You can find personas in the Knowledge Base. 1. Open your 1eyeᴬᴵ workspace 2. Go to Knowledge Base 3. Select the Personas tab 4. Review the personas created for your workspace 5. Open a persona to view details, description, target departments, keywords, and related context The Personas tab shows the buyer types 1eyeᴬᴵ uses to evaluate and source contacts. ## What you can see in the Personas tab The Personas table may include: Persona name, Short name, Description, Created by, Created date, Updated date. When you open a persona, you may see: Name, Short name, Description, Target departments, Keywords, Example contacts when available, Created date, Updated date. Example: | Field | Example | | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------- | | Persona name | Revenue Operations Leader | | Short name | REVOPS | | Description | RevOps leaders responsible for CRM data quality, routing, enrichment, attribution, reporting, segmentation, sales process, and GTM workflow automation. | | Target departments | Revenue Operations, Sales Operations, GTM Operations, Marketing Operations, Business Operations | | Keywords | revops, sales operations, marketing operations, CRM, routing, enrichment, attribution, scoring, GTM systems | ### Persona name The persona name should clearly describe the buyer type. Good persona names are specific and easy to understand. Examples: Revenue Operations Leader, Head of Data, VP Sales, VP Marketing, GTM Systems Leader, AI Transformation Leader, Founder or CEO, Chief Operating Officer, IT Leader, Finance Leader. Avoid names that are too broad. Weak persona names: Sales, Marketing, Data, Executive, Operations. Better persona names: VP Sales, Revenue Operations Leader, Head of Data, GTM Systems Leader, Chief Operating Officer. ### Persona short name The short name is a compact label used in the product. Short names help personas appear cleanly in badges, tables, filters, and on contact cards across Website Signals and Buyers. | Persona name | 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 | | Chief Operating Officer | COO | Use short names that your team can recognize quickly. ### Persona description The description is the most important part of the persona. 1eyeᴬᴵ uses the persona description to understand what kinds of contacts should match. A strong persona description should explain: what the person owns; what team or function they sit in; what responsibilities they have; what pain points they care about; what buying role they may play; what use cases are relevant; what titles should be included or excluded. Example: "Revenue operations leaders responsible for CRM quality, lead routing, enrichment, attribution, segmentation, forecasting, reporting, and GTM workflow automation. These contacts usually sit between sales, marketing, and operations and care about data quality, process efficiency, and pipeline visibility." This gives 1eyeᴬᴵ much better context than: "RevOps." ### Target departments Target departments help 1eyeᴬᴵ understand which parts of an organization the persona belongs to. A persona is stronger when it includes both the person's role and the department or function they are tied to. For example, a Revenue Operations Leader persona may include target departments such as: | Target department | Why it matters | | -------------------- | --------------------------------------------------------------------------------------- | | Revenue Operations | Owns GTM process, routing, reporting, enrichment, attribution, and pipeline operations. | | Sales Operations | Supports sales process, territories, sequencing, account routing, and rep productivity. | | Marketing Operations | Owns campaign operations, attribution, segmentation, lead flow, and marketing systems. | | GTM Operations | Connects sales, marketing, data, systems, and workflow execution. | | Business Operations | May own cross-functional process, data quality, and operational scale. | Target departments help 1eyeᴬᴵ avoid matching only by job title. They give the system more context about where the person sits inside the organization. For example, the title "Director" by itself is too broad. But this is much clearer: "Directors and senior leaders in revenue operations, sales operations, marketing operations, GTM systems, or business operations." Use target departments when: the persona can appear under multiple job titles; the same title means different things in different departments; you need to target a specific buying group; you want cleaner contact sourcing; you want better persona matching from signals. ### Keywords Keywords help 1eyeᴬᴵ understand the language, responsibilities, and themes connected to a persona. Keywords may include: job title keywords, department keywords, responsibility keywords, pain point keywords, use case keywords, industry-specific terms. For example, a Revenue Operations Leader persona may include keywords such as: revops, revenue operations, sales operations, marketing operations, GTM operations, CRM, Salesforce, HubSpot, routing, enrichment, attribution, scoring, segmentation, pipeline, forecasting, GTM systems. Keywords help 1eyeᴬᴵ recognize relevant contacts even when job titles vary. For example, the following titles may all fit the same persona depending on the department and context: VP Revenue Operations, Head of Revenue Operations, Director of Revenue Operations, Sales Operations Leader, GTM Systems Leader, Marketing Operations Leader, CRM Operations Manager, GTM Operations Lead. Use keywords to make persona matching more accurate, especially in industries where titles are inconsistent. ### Example contacts Example contacts help make a persona more concrete. When you open a persona, you may see contacts associated with that persona. Example contacts help your team and 1eyeᴬᴵ understand what "good fit" looks like. For example, a persona for Revenue Operations Leader might include example contacts such as: | Contact | Why it fits | | --------------------------------------------- | ----------------------------------------------------------------- | | Jordan Lee, VP Revenue Operations | Owns GTM systems, routing, reporting, and sales process. | | Avery Morgan, Head of Revenue Operations | Responsible for CRM quality, enrichment, and pipeline operations. | | Taylor Brooks, Director of Revenue Operations | Manages GTM data quality and workflow automation. | Examples should represent the kinds of people you actually want 1eyeᴬᴵ to find and prioritize. ### Example persona: industry-specific buyer Personas can also be specific to a vertical or industry. For example, a healthcare, corrections, education, hospitality, or financial services company may need personas that reflect the language of that market. Example: | Field | Example | | ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Persona name | Correctional Leadership | | Short name | Corrections Execs | | Description | Senior leaders responsible for oversight, safety, rehabilitation, and behavioral health outcomes within adult and juvenile correctional systems. This persona includes probation chiefs, custody leaders, rehabilitative services leaders, and medical or mental health decision-makers. | | Target departments | Custody & Operations, Rehabilitative Services, Medical & Mental Health, Juvenile Justice Services, Training & Staff Wellness, Probation & Parole | | Keywords | corrections, custody, probation, parole, rehabilitation, behavioral health, juvenile justice, reentry, safety, staff wellness | This gives 1eyeᴬᴵ a clear definition of who to look for, what departments they belong to, and which keywords should help identify relevant contacts. ## How personas are created 1eyeᴬᴵ can create initial personas for your workspace based on your company website, domain, ICPs, and available business context. Your team should review the generated personas before using them for targeting. 1eyeᴬᴵ gives you a starting point, but your team should make sure the personas reflect your actual buyer personas and GTM strategy. Review each persona for: accuracy, specificity, role relevance, seniority, function, department, target departments, keywords, buying role, use case, segment priority. ## How personas are used across 1eyeᴬᴵ Personas are used throughout the platform. They help power: website signal evaluation; contact prioritization within Website Signals; buyer sourcing; target list building; credit efficiency. Personas are one of the most important inputs in 1eyeᴬᴵ. If your personas are weak, your targeting will be noisy. If your personas are sharp, 1eyeᴬᴵ can help you find and prioritize much better contacts. ## Personas and Website Signals When website activity comes in, 1eyeᴬᴵ evaluates the contact against your personas. Activity may come from: website visits, tracked form activity, Target Page matches. When the contact matches a persona, 1eyeᴬᴵ shows a persona badge on their card in Website Signals. Example: `REVOPS`. This helps your team understand that the contact is not just active — they may also be the right person. You can also filter Website Signals directly by persona. See Website Signals for the full filter walkthrough. ## Persona match explanations When a contact matches a persona, 1eyeᴬᴵ may provide an explanation. Example: "Jordan Lee leads revenue operations and is responsible for CRM quality, enrichment, routing, reporting, and GTM workflow automation. This aligns with the Revenue Operations Leader persona." Use the explanation to understand why 1eyeᴬᴵ matched the contact. If the explanation does not make sense, update the persona description, target departments, keywords, or review the contact's company fit. ## Personas and Buyers Personas are used to define and source Buyers. Personas define the type of person. Buyers are the real people — at real companies — your team may want to engage. | Layer | Example | | --------- | -------------------------------------------------------- | | Persona | Revenue Operations Leader | | Buyer | Jordan Lee, VP Revenue Operations at Northstar Analytics | | Signal | Pricing page visit | | Next step | Add to RevOps SaaS Pipeline list | Personas help 1eyeᴬᴵ move from strategy to real people. ## Personas and Target Lists Personas are one of the best ways to build Target Lists. A target list can include contacts sourced by persona. For example: ```text theme={null} Target List: RevOps SaaS Pipeline ICP: B2B SaaS Companies Persona: Revenue Operations Leader Goal: Build a list of active SaaS company contacts in RevOps roles ``` You can use ICPs to filter for contacts at matching companies, then use personas to narrow to the right person at each one. ## Personas and ICPs Personas and ICPs work together. ICPs define the companies. Personas define the people inside those companies. | Strategy layer | Example | | -------------- | -------------------------------------------------------- | | ICP | B2B SaaS Companies | | Persona | VP Revenue Operations | | Buyer | Jordan Lee, VP Revenue Operations at Northstar Analytics | | Destination | Pushed to HubSpot for outreach | A company can match an ICP, but you still need the right person inside that company. A person can match a persona, but the company may not be a good fit. The best targets usually have both: company ICP fit and contact persona fit. ## Personas and buying roles Personas can represent different roles in a buying process. Some personas are decision-makers. Others are influencers, users, evaluators, blockers, or champions. | Buying role | What it means | | -------------- | ------------------------------------------------------ | | Decision-maker | Has authority to approve or buy. | | Influencer | Shapes the buying process or recommends vendors. | | Champion | Feels the pain and may push internally for change. | | Evaluator | Reviews the product, data, security, or technical fit. | | User | Uses or benefits from the product. | | Approver | Signs off on budget, legal, security, or procurement. | A target list may focus on one persona or a full buying group. For example, Snowbricks may care about: RevOps leaders as champions; Heads of Data as technical evaluators; VP Sales as business decision-makers; Founders or CEOs as executive sponsors. ## Personas and prioritization Personas help 1eyeᴬᴵ and your team prioritize the right buyers. Different personas care about different outcomes. | Persona | Likely cares about | | ------------------------- | ----------------------------------------------------------------- | | Revenue Operations Leader | CRM quality, routing, reporting, enrichment, workflow automation. | | Head of Data | Data quality, governance, pipelines, activation, reliability. | | VP Sales | Pipeline, account prioritization, team productivity, conversion. | | VP Marketing | Campaign targeting, attribution, conversion, audience quality. | | Founder or CEO | Growth, efficiency, revenue, team leverage, strategic execution. | The more specific the persona, the better 1eyeᴬᴵ can prioritize. ## Example personas for Snowbricks For Snowbricks, a B2B AI data company, example personas may include: | Persona | Short name | Description | | ------------------------- | ---------- | ----------------------------------------------------------------------------------------------------------------------------------- | | Revenue Operations Leader | REVOPS | RevOps leaders responsible for CRM quality, enrichment, routing, attribution, reporting, segmentation, and GTM workflow automation. | | Head of Data | DATA | Data leaders responsible for data infrastructure, governance, quality, activation, analytics, and trusted business intelligence. | | VP Sales | VP-SALES | Sales leaders focused on pipeline generation, account prioritization, sales productivity, and better target company intelligence. | | VP Marketing | VP-MKTG | Marketing leaders responsible for campaign targeting, audience quality, attribution, conversion, and demand generation data. | | GTM Systems Leader | GTM-SYS | Operators responsible for CRM, marketing automation, enrichment tools, routing logic, and sales engagement systems. | | AI Transformation Leader | AI-LEADER | Executives or operators responsible for adopting AI across GTM, data, operations, or customer-facing workflows. | | Founder or CEO | FOUNDER | Founders or executives looking to scale GTM with better data, automation, signal intelligence, and workflow execution. | These personas help 1eyeᴬᴵ understand which contacts Snowbricks should care about. ### Example persona detail Here is what a strong persona detail could look like. | Field | Example | | ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Name | Revenue Operations Leader | | Short name | REVOPS | | Description | Revenue operations leaders responsible for CRM quality, enrichment, routing, attribution, segmentation, reporting, and GTM workflow automation. These contacts usually sit between sales, marketing, and operations and care about clean data, better account prioritization, improved sales productivity, and accurate pipeline visibility. | | Target departments | Revenue Operations, Sales Operations, Marketing Operations, GTM Operations, Business Operations | | Keywords | revops, revenue operations, sales operations, marketing operations, CRM, routing, enrichment, attribution, scoring, segmentation, forecasting, GTM systems | | Example contact | Jordan Lee, VP Revenue Operations | | Example contact | Avery Morgan, Head of Revenue Operations | | Example contact | Taylor Brooks, Director of Revenue Operations | This gives 1eyeᴬᴵ a clear definition of what to look for. ## Strong persona vs weak persona A weak persona is too broad. Weak persona: "Sales." Better persona: "VP Sales or sales leaders responsible for pipeline generation, account prioritization, sales team productivity, conversion, and revenue execution at B2B companies." Another weak persona: "Data." Better persona: "Heads of Data, data leaders, or analytics leaders responsible for data quality, governance, activation, business intelligence, and trusted data workflows across GTM and operations." A weak persona creates noisy matches. A strong persona gives 1eyeᴬᴵ enough context to make better decisions. ## How to review personas Review each persona before relying on it for signals, sourcing, or lists. For each persona, check: is the name specific? Is the short name easy to understand? Is the description detailed enough? Does it describe the right job function? Does it include the right seniority? Does it mention relevant responsibilities? Does it mention relevant pain points? Does it reflect your actual buyer persona? Are target departments accurate? Are keywords specific enough? Are example contacts accurate? Would your team agree this is a real buyer type? Also review the persona's target departments and keywords. Check: do the target departments match where this persona usually sits? Are the keywords specific enough? Are there missing job title keywords? Are there industry-specific terms 1eyeᴬᴵ should know? Are there departments that should be removed because they create noisy matches? If the answer is no, edit the persona. ## When to create a new persona Create a new persona when you want to target a distinct type of contact. Add a new persona when: you are entering a new market; you sell to multiple departments; you need different messaging by role; you want separate target lists for different seniority levels; you want to test a new buyer group; you need to separate decision-makers from users; 1eyeᴬᴵ did not create a persona your team needs. For example, Snowbricks may create separate personas for: Revenue Operations Leader, Head of Data, VP Sales, VP Marketing. Each persona may need different messaging and different targeting logic. ## When to edit a persona Edit a persona when it is creating poor matches or missing good contacts. Edit a persona if: the description is too broad; the persona includes people you do not want; the persona misses people you do want; the seniority is wrong; the function is wrong; the department context is wrong; the keywords are too generic; the buying role is unclear; the persona overlaps too much with another persona; the example contacts are misleading; your GTM motion has changed. Personas should improve over time. ## How to write a strong persona description Use this structure: "\[Role type] responsible for \[responsibilities] who care about \[pain points or goals]. These contacts typically sit in \[function or department], influence \[buying area], and are a fit because \[reason]." Example: "Revenue operations leaders responsible for CRM quality, enrichment, routing, attribution, segmentation, reporting, and GTM workflow automation. These contacts typically sit between sales, marketing, and operations, influence GTM systems and data decisions, and care about improving pipeline visibility, sales productivity, and account prioritization." This gives 1eyeᴬᴵ clear targeting context. ## Persona quality checklist A strong persona should include: clear role type; seniority guidance; function or department; target departments; responsibilities; pain points; goals; buying role; example titles; example contacts; keywords; distinction from other personas. A weak persona usually has: generic wording; no seniority guidance; no clear function; no department context; no responsibilities; no pain points; no buying role; no keywords; no examples; too much overlap with another persona. ## Best practices * **Keep personas specific** — Broad personas create noisy contacts and poor target lists. * **Use personas as strategy, not just labels** — Personas should define real people your team wants to engage. * **Create separate personas for separate messages** — If the role, pain point, or message is different, use a separate persona. * **Use target departments** — Departments help 1eyeᴬᴵ understand where the person sits in the organization. * **Use keywords carefully** — Keywords help identify relevant contacts when job titles vary. * **Add example contacts** — Examples make the persona easier to understand and validate. * **Review persona matches regularly** — If matches look wrong, update the persona. * **Connect personas to ICPs** — Know which personas matter inside each target company segment. * **Use personas to build target lists** — Personas should help you source and prioritize contacts, not just sit in the Knowledge Base. * **Use persona fit before enrichment** — Enrich contacts that match your personas and belong to strong target companies. * **Use signals to improve personas** — If certain roles engage but never convert, tighten the persona. If unexpected roles convert, create or update a persona. * **Keep personas current** — As your product, market, and GTM strategy change, your personas should evolve. ## Troubleshooting * **Persona matches are too broad** — Your persona may be too generic. Try adding seniority guidance, function or department, clearer responsibilities, buying role context, target departments, specific keywords, example job titles, or example contacts. * **Persona matches are too narrow** — Your persona may be too restrictive. Try adding adjacent job titles, broadening seniority, expanding responsibilities, adding related departments, more keywords, or more example contacts. * **The wrong contacts are matching** — Review the persona description. Check whether it includes wording that could match poor-fit contacts. Also check whether target departments are too broad, keywords are too generic, the contact belongs to a company that should be excluded, or the persona overlaps with another persona. * **Good contacts are not matching** — Check whether your persona description is missing important titles, responsibilities, seniority levels, functions, departments, or keywords. Add more detail about the role type, department, use case, buying role, and common title variations. * **Personas overlap too much** — If two personas match the same contacts, clarify the difference. For example, VP Sales may own pipeline and sales team performance; RevOps may own routing, CRM quality, attribution, and GTM systems; Head of Data may own data infrastructure, governance, and activation. Each persona should represent a distinct targeting or messaging angle. * **I do not know how many personas to create** — Start with 3-5 personas. Create enough personas to cover your main buying group, but not so many that your team cannot manage them. * **I do not know whether something is a persona or ICP** — Use this rule: ICP = company type, Persona = person type. | If you mean | Use | | -------------------------- | ------- | | B2B SaaS companies | ICP | | Revenue Operations Leaders | Persona | | Hospitals and Clinics | ICP | | Chief Operating Officers | Persona | ## FAQ A persona defines the types of buyers your team wants to find, evaluate, prioritize, and engage. Yes. In 1eyeᴬᴵ, personas represent the buyer personas your team wants to engage. 1eyeᴬᴵ uses personas to evaluate contact signals, source contacts, build target lists, and prioritize buyers. Yes. 1eyeᴬᴵ can create initial personas based on your company website, domain, ICPs, and workspace context. Yes. Always review and refine personas before using them for targeting or lists. Personas define buyers. ICPs define target companies. Yes. Use multiple personas for different roles, departments, seniority levels, buying groups, or messaging needs. Yes. You can edit persona name, short name, description, target departments, keywords, and example contacts when available. The short name is the compact label used in badges, filters, and tables. Target departments describe where the persona usually sits inside an organization, such as Revenue Operations, Sales Operations, Data, IT, Marketing, Finance, or Operations. Keywords are job title, department, responsibility, pain point, and industry terms that help 1eyeᴬᴵ understand and match the persona. Example contacts are people who represent the persona. They help make the persona easier to understand and validate. When a contact shows website activity, 1eyeᴬᴵ evaluates the contact against your personas. If it matches, the contact may show a persona badge and explanation. You can source contacts by persona and build target lists around specific buyer types. Personas help target lists focus on the right people and support more relevant messaging based on role, responsibility, pain point, and buying context. Make personas specific, include responsibilities and buying roles, add target departments, use relevant keywords, add example contacts, define seniority, and keep personas updated as your GTM strategy changes. ## Next step Next, go to Buyers to see how 1eyeᴬᴵ finds, organizes, and prioritizes the people your team should pursue.