Personas

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 contact lists, personalizes outreach, and helps your team decide which people are worth engaging.

A clear persona helps 1eyeᴬᴵ separate relevant target contacts 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 target contact inside the company

Is this person the right target contact inside the company

Is this person the right target contact inside the company

That is what a persona helps answer.

Without personas, your team may see contacts visiting, clicking, replying, or engaging, 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:

1. Which contacts are relevant

2. Which contacts should be prioritized

3. Which contacts should be ignored

4. Which contacts should be enriched

5. Which contacts should be added to target lists

6. Which contacts should move into campaigns

7. 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 target contact type.

A good persona may include:

1. Job title

2. Seniority

3. Function

4. Department

5. Target departments

6. Keywords

7. Buying role

8. Pain points

9. Responsibilities

10. Use cases

11. Goals

12. Buying triggers

13. Common objections

14. Example titles

15. 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

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

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

Sales

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 target contact types 1eyeᴬᴵ uses to evaluate and source contacts.

What you can see in the Personas tab

The Personas table may include:

1. Persona name

2. Short name

3. Description

4. Created by

5. Created date

6. Updated date

When you open a persona, you may see:

1. Name

2. Short name

3. Description

4. Target departments

5. Keywords

6. Example contacts when available

7. Created date

8. Updated date

Example:

Persona name

The persona name should clearly describe the target contact type.

Good persona names are specific and easy to understand.

Examples:

1. Revenue Operations Leader

2. Head of Data

3. VP Sales

4. VP Marketing

5. GTM Systems Leader

6. AI Transformation Leader

7. Founder or CEO

8. Chief Operating Officer

9. IT Leader

10. Finance Leader

Avoid names that are too broad.

Weak persona names:

Sales
Marketing
Data
Executive
Operations

Sales
Marketing
Data
Executive
Operations

Sales
Marketing
Data
Executive
Operations

Better persona names:

VP Sales
Revenue Operations Leader
Head of Data
GTM Systems Leader
Chief Operating Officer

VP Sales
Revenue Operations Leader
Head of Data
GTM Systems Leader
Chief Operating Officer

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 signal views.

Examples:

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:

1. What the person owns

2. What team or function they sit in

3. What responsibilities they have

4. What pain points they care about

5. What buying role they may play

6. What use cases are relevant

7. 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

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

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

RevOps

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 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

Directors and senior leaders in revenue operations, sales operations, marketing operations, GTM systems, or business operations

Directors and senior leaders in revenue operations, sales operations, marketing operations, GTM systems, or business operations

Use target departments when:

1. The persona can appear under multiple job titles

2. The same title means different things in different departments

3. You need to target a specific buying group

4. You want cleaner contact sourcing

5. You want better persona matching from signals

Keywords

Keywords help 1eyeᴬᴵ understand the language, responsibilities, and themes connected to a persona.

Keywords may include:

1. Job title keywords

2. Department keywords

3. Responsibility keywords

4. Pain point keywords

5. Use case keywords

6. 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

revops, revenue operations, sales operations, marketing operations, GTM operations, CRM, Salesforce, HubSpot, routing, enrichment, attribution, scoring, segmentation, pipeline, forecasting, GTM systems

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:

1. VP Revenue Operations

2. Head of Revenue Operations

3. Director of Revenue Operations

4. Sales Operations Leader

5. GTM Systems Leader

6. Marketing Operations Leader

7. CRM Operations Manager

8. 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:

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:

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:

1. Accuracy

2. Specificity

3. Role relevance

4. Seniority

5. Function

6. Department

7. Target departments

8. Keywords

9. Buying role

10. Use case

11. Segment priority

How personas are used across 1eyeᴬᴵ

Personas are used throughout the platform.

They help power:

1. Contact signal evaluation

2. Website contact prioritization

3. LinkedIn contact prioritization

4. Conversation signal context

5. View by Contact filtering

6. Target contact sourcing

7. Target list building

8. Campaign audience quality

9. Outreach personalization

10. 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 Signals

When contact signals come in, 1eyeᴬᴵ evaluates those contacts against your personas.

A contact signal may come from:

1. Website activity

2. LinkedIn activity

3. Form activity

4. Email activity

5. iMessage activity

6. Conversation activity

7. Response activity

When the contact matches a persona, 1eyeᴬᴵ may show a persona badge.

Example:

REVOPS

REVOPS

REVOPS

This helps your team understand that the contact is not just active, they may also be the right person.

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

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

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 View by Contact

In View by Contact, personas help you focus on people who matter.

You can use:

1. Show Personas Only
   Shows only contacts that match your personas.

2. Persona filter
   Shows contacts that match a specific persona.

Use these controls when you want to reduce noise and focus on target contacts.

For example, you can filter for:

Persona - REVOPS

Persona - REVOPS

Persona - REVOPS

Then review only contacts who match that role.

Personas and Target Contacts

Personas are used to define and source Target Contacts.

Target Contacts are the actual people your team may want to engage.

Personas define the type of person.

Target Contacts are the real people who match or get added.

Example:

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:

Target List: RevOps SaaS Pipeline
ICP: B2B SaaS Companies
Persona: Revenue Operations Leader
Goal: Build a list of active SaaS companies and relevant RevOps contacts

Target List: RevOps SaaS Pipeline
ICP: B2B SaaS Companies
Persona: Revenue Operations Leader
Goal: Build a list of active SaaS companies and relevant RevOps contacts

Target List: RevOps SaaS Pipeline
ICP: B2B SaaS Companies
Persona: Revenue Operations Leader
Goal: Build a list of active SaaS companies and relevant RevOps contacts

You can use ICPs to source companies, then use personas to source contacts inside those companies.

Personas and Campaigns

Personas improve campaigns by making sure the right people enter the audience.

A strong campaign usually starts with a specific role or buying group.

For example:

Campaign: RevOps Workflow Automation Campaign
ICP: B2B SaaS Companies
Persona: Revenue Operations Leader
Message angle: Clean account data, routing, enrichment, and GTM workflow automation

Campaign: RevOps Workflow Automation Campaign
ICP: B2B SaaS Companies
Persona: Revenue Operations Leader
Message angle: Clean account data, routing, enrichment, and GTM workflow automation

Campaign: RevOps Workflow Automation Campaign
ICP: B2B SaaS Companies
Persona: Revenue Operations Leader
Message angle: Clean account data, routing, enrichment, and GTM workflow automation

This gives the campaign better context than a generic list of contacts.

Personas and ICPs

Personas and ICPs work together.

ICPs define the companies.

Personas define the people inside those companies.

Example:

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:

1. Company ICP fit

2. 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.

Common buying roles include:

A campaign may target one persona or a full buying group.

For example, Snowbricks may care about:

1. RevOps leaders as champions

2. Heads of Data as technical evaluators

3. VP Sales as business decision-makers

4. Founders or CEOs as executive sponsors

Personas and messaging

Personas help 1eyeᴬᴵ and your team create more relevant outreach.

Different personas care about different outcomes.

Example:

The more specific the persona, the better the message can be.

Example personas for Snowbricks

For Snowbricks, a B2B AI data company, example personas may include:

These personas help 1eyeᴬᴵ understand which contacts Snowbricks should care about.

Example persona detail

Here is what a strong persona detail could look like.

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

Sales

Sales

Better persona:

VP Sales or sales leaders responsible for pipeline generation, account prioritization, sales team productivity, conversion, and revenue execution at B2B companies

VP Sales or sales leaders responsible for pipeline generation, account prioritization, sales team productivity, conversion, and revenue execution at B2B companies

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

Data

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

Heads of Data, data leaders, or analytics leaders responsible for data quality, governance, activation, business intelligence, and trusted data workflows across GTM and operations

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, lists, or campaigns.

For each persona, check:

1. Is the name specific?

2. Is the short name easy to understand?

3. Is the description detailed enough?

4. Does it describe the right job function?

5. Does it include the right seniority?

6. Does it mention relevant responsibilities?

7. Does it mention relevant pain points?

8. Does it reflect your actual buyer persona?

9. Are target departments accurate?

10. Are keywords specific enough?

11. Are example contacts accurate?

12. Would your team agree this is a real target contact type?

Also review the persona’s target departments and keywords.

Check:

1. Do the target departments match where this persona usually sits?

2. Are the keywords specific enough?

3. Are there missing job title keywords?

4. Are there industry-specific terms 1eyeᴬᴵ should know?

5. 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:

1. You are entering a new market

2. You sell to multiple departments

3. You need different messaging by role

4. You want separate campaigns for different seniority levels

5. You want to test a new buyer group

6. You need to separate decision-makers from users

7. 1eyeᴬᴵ did not create a persona your team needs

For example, Snowbricks may create separate personas for:

1. Revenue Operations Leader

2. Head of Data

3. VP Sales

4. VP Marketing

Each persona may need different messaging and different campaign logic.

When to edit a persona

Edit a persona when it is creating poor matches or missing good contacts.

Edit a persona if:

1. The description is too broad

2. The persona includes people you do not want

3. The persona misses people you do want

4. The seniority is wrong

5. The function is wrong

6. The department context is wrong

7. The keywords are too generic

8. The buying role is unclear

9. The persona overlaps too much with another persona

10. The example contacts are misleading

11. 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]

[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]

[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

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

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

Use this checklist when reviewing personas.

A strong persona should include:

1. Clear role type

2. Seniority guidance

3. Function or department

4. Target departments

5. Responsibilities

6. Pain points

7. Goals

8. Buying role

9. Example titles

10. Example contacts

11. Keywords

12. Distinction from other personas

A weak persona usually has:

1. Generic wording

2. No seniority guidance

3. No clear function

4. No department context

5. No responsibilities

6. No pain points

7. No buying role

8. No keywords

9. No examples

10. Too much overlap with another persona

Best practices

1. Keep personas specific
   Broad personas create noisy contacts and poor target lists.

2. Use personas as strategy, not just labels
   Personas should define real people your team wants to engage.

3. Create separate personas for separate messages
   If the role, pain point, or message is different, use a separate persona.

4. Use target departments
   Departments help 1eyeᴬᴵ understand where the person sits in the organization.

5. Use keywords carefully
   Keywords help identify relevant contacts when job titles vary.

6. Add example contacts
   Examples make the persona easier to understand and validate.

7. Review persona matches regularly
   If matches look wrong, update the persona.

8. Connect personas to ICPs
   Know which personas matter inside each target company segment.

9. Use personas to build target lists
   Personas should help you source and prioritize contacts, not just sit in the Knowledge Base.

10. Use persona fit before enrichment
    Enrich contacts that match your personas and belong to strong target companies.

11. Use signals to improve personas
    If certain roles engage but never convert, tighten the persona. If unexpected roles convert, create or update a persona.

12. 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:

1. Adding seniority guidance

2. Adding function or department

3. Adding clearer responsibilities

4. Adding buying role context

5. Adding target departments

6. Adding specific keywords

7. Adding example job titles

8. Adding example contacts

Persona matches are too narrow

Your persona may be too restrictive.

Try:

1. Adding adjacent job titles

2. Broadening seniority

3. Expanding responsibilities

4. Adding related departments

5. Adding more keywords

6. Adding 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:

1. Target departments are too broad

2. Keywords are too generic

3. The contact belongs to a company that should be excluded

4. 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:

1. VP Sales may own pipeline and sales team performance

2. RevOps may own routing, CRM quality, attribution, and GTM systems

3. 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

ICP = company type
Persona = person type

ICP = company type
Persona = person type

Example:

FAQ

What is a persona?

A persona defines the types of target contacts your team wants to find, evaluate, prioritize, and engage.

Are personas the same as buyer personas?

Yes. In 1eyeᴬᴵ, personas represent the buyer personas or target contact types your team wants to engage.

Why does 1eyeᴬᴵ need personas?

1eyeᴬᴵ uses personas to evaluate contact signals, source contacts, build target lists, personalize outreach, and prioritize target contacts.

Does 1eyeᴬᴵ create personas automatically?

Yes. 1eyeᴬᴵ can create initial personas based on your company website, domain, ICPs, and workspace context.

Should I review the generated personas?

Yes. Always review and refine personas before using them for targeting, lists, or campaigns.

What is the difference between personas and ICPs?

Personas define target contacts. ICPs define target companies.

Can I create multiple personas?

Yes. Use multiple personas for different roles, departments, seniority levels, buying groups, or campaign messages.

Can I edit a persona?

Yes. You can edit persona name, short name, description, target departments, keywords, and example contacts when available.

What is a persona short name?

The short name is the compact label used in badges, filters, and tables.

What are target departments?

Target departments describe where the persona usually sits inside an organization, such as Revenue Operations, Sales Operations, Data, IT, Marketing, Finance, or Operations.

What are keywords?

Keywords are job title, department, responsibility, pain point, and industry terms that help 1eyeᴬᴵ understand and match the persona.

What are example contacts?

Example contacts are people who represent the persona. They help make the persona easier to understand and validate.

How does 1eyeᴬᴵ use personas with signals?

When a contact signal comes in, 1eyeᴬᴵ evaluates the contact against your personas. If it matches, the contact may show a persona badge and explanation.

How does 1eyeᴬᴵ use personas with target lists?

You can source contacts by persona and build target lists around specific target contact types.

How do personas affect campaigns?

Personas help campaigns target the right people and support more relevant messaging based on role, responsibility, pain point, and buying context.

How do I improve persona quality?

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 Target Companies to understand how 1eyeᴬᴵ finds, organizes, and prioritizes the companies your team should pursue.