Persona Mapping - Framework
How to identify, segment, and target personas within ABM accounts. Mapping personas to their jobs-to-be-done (JTBDs), pain points, and messaging.
The Persona Mapping Principle
ABM targets accounts, but people buy - not companies. Persona mapping answers:
- Who at the target account should see your ads?
- What do they care about? (JTBDs, pain points)
- How should messaging differ by persona?
- When should BDRs reach out to which persona?
Identifying Personas
Step 1: Analyze Your Closed-Won Deals
Look at your CRM data for closed-won deals:
| Question |
What You're Looking For |
Source |
| Who was the primary contact on won deals? |
Most common titles/roles |
CRM deal contacts |
| Who initiated the buying process? |
Champion persona |
CRM first touch data |
| Who signed the contract? |
Economic buyer persona |
CRM deal owner notes |
| Who else was involved in evaluation? |
Buying committee members |
CRM activity log, call notes |
| What was their typical seniority? |
IC vs Manager vs VP vs C-suite |
CRM contact properties |
Step 2: Map the Buying Committee
Most B2B deals involve 6-10 stakeholders. Map the roles:
| Role |
Definition |
Example Titles |
Engagement Priority |
| Champion |
Internal advocate who drives the deal |
Product Manager, Head of Ops, Director of Growth |
Primary - warm them first |
| Economic Buyer |
Controls budget, signs the contract |
VP/C-suite, Finance |
Engage after champion is warm |
| Technical Evaluator |
Assesses product capabilities |
Engineering Lead, Solutions Architect, IT |
Engage during demo/trial stage |
| End User |
Will use the product daily |
Analyst, Designer, Specialist, IC |
Engage with product-focused content |
| Blocker/Gatekeeper |
Can slow or kill the deal |
Legal, Procurement, IT Security |
Address concerns proactively |
Step 3: Define Persona Attributes
For each persona, document:
| Attribute |
What to Capture |
Example |
| Title patterns |
Common job titles |
"Product Manager", "Head of Product", "VP Product" |
| Seniority |
IC / Manager / Director / VP / C-suite |
Manager - Director |
| Function |
Department/team |
Product, Engineering, Marketing |
| JTBD |
Job to be done - what they're trying to accomplish |
"Improve user onboarding to reduce churn" |
| Pain points |
What's frustrating them today |
"Can't see where users drop off", "Manual onboarding flows" |
| Success metrics |
How their performance is measured |
Activation rate, time-to-value, NPS |
| Content preferences |
What content resonates |
Case studies, data/benchmarks, peer recommendations |
| Buying role |
Champion / Economic Buyer / Evaluator / User / Blocker |
Champion |
Persona Enrichment with Clay
Custom Properties to Enrich
When building contact lists in Clay, enrich beyond standard fields:
| Property |
How to Enrich |
Why |
| Persona (custom) |
Map from title using Clay AI/rules |
Enables persona-specific campaigns |
| Seniority (custom) |
Map from title (IC/Manager/Director/VP/C-Suite) |
Different messaging by seniority |
| Function |
Extract from LinkedIn profile |
Department-specific JTBDs |
| LinkedIn URL |
Apollo / Clay |
For LinkedIn outreach + audience matching |
| Verified email |
Email waterfall in Clay |
For outreach sequences |
Persona Assignment Rules
Create rules in Clay to auto-assign personas:
IF title contains "Product Manager" OR "PM" OR "Head of Product" OR "VP Product" OR "CPO":
→ Persona = "Product"
IF title contains "UX" OR "UI" OR "Designer" OR "Design Lead":
→ Persona = "UX/Design"
IF title contains "Marketing" OR "Growth" OR "PMM" OR "Demand Gen":
→ Persona = "Marketing"
IF title contains "CTO" OR "VP Engineering" OR "Engineering Manager":
→ Persona = "Engineering"
IF title contains "CEO" OR "COO" OR "Founder" OR "General Manager":
→ Persona = "Executive"
IF title contains "Customer Success" OR "CX" OR "Support":
→ Persona = "Customer Success"
Persona-Based Messaging
Messaging Matrix
| Persona |
Primary JTBD |
Pain Point |
Messaging Angle |
Ad Content Example |
| Product |
Improve user activation/retention |
Can't see user behavior, manual processes |
"See exactly where users drop off" |
Product analytics screenshots, feature walkthrough |
| UX/Design |
Create better user experiences |
No data on user flows, guesswork |
"Design based on real user behavior" |
Session replay demo, heatmap visuals |
| Marketing |
Drive pipeline, prove ROI |
Can't attribute conversions, poor lead quality |
"Know which campaigns actually drive revenue" |
ROI dashboards, attribution data |
| Engineering |
Ship faster, reduce tech debt |
Too many tools, complex integrations |
"One platform, simple integration" |
API docs, integration showcase |
| Executive |
Hit revenue/growth targets |
Slow growth, high churn, team misalignment |
"Companies like yours grew X% with us" |
Case study with numbers, ROI calculator |
| Customer Success |
Reduce churn, improve NPS |
Can't identify at-risk users proactively |
"Spot churn risk before it's too late" |
Health score dashboards, alert demos |
Messaging by ABM Stage
| Stage |
Product Persona |
Executive Persona |
UX Persona |
| Awareness |
Industry trend / thought leadership about user analytics |
"CEOs at top SaaS companies are investing in..." |
Design community content, UX best practices |
| Interested |
Feature comparison vs competitors |
ROI data, business impact numbers |
Session replay deep-dive, workflow demos |
| Considering |
Product demo, free trial, technical walkthrough |
Case study from peer company, executive briefing |
Design-focused case study, UX workflow example |
LinkedIn Targeting by Persona
Two Approaches
Approach 1: Contact List Upload (More Precise, More Expensive)
- Find specific contacts at target accounts in Clay/Apollo
- Enrich with email
- Upload to HubSpot as marketing contacts
- Sync to LinkedIn via HubSpot Ad Audiences
- Create separate campaigns per persona list
Pros: Very precise targeting
Cons: Expensive (Clay credits + HubSpot marketing contacts cost), complex to manage
Approach 2: Company List + LinkedIn Native Filters (Recommended)
- Upload company list to LinkedIn (via HubSpot company list sync)
- Use LinkedIn Campaign Manager's native filters to target personas:
- Job Function: Product Management, Design, Marketing, etc.
- Seniority: Director, VP, C-Suite
- Job Title keywords: specific titles
Pros: Cheaper, simpler, leverages LinkedIn's data
Cons: Less precise (LinkedIn's job function mapping isn't perfect)
LinkedIn Persona Filters
| Persona |
LinkedIn Job Function |
LinkedIn Seniority |
Title Keywords |
| Product |
Product Management |
Manager, Director, VP |
Product Manager, Head of Product, CPO |
| UX/Design |
Design, Arts and Design |
Manager, Senior, Director |
UX Designer, Design Lead, Head of Design |
| Marketing |
Marketing |
Manager, Director, VP |
Growth, PMM, Demand Gen, Head of Marketing |
| Engineering |
Engineering, IT |
Manager, Director, VP, CTO |
Engineering Manager, CTO, VP Engineering |
| Executive |
General Management |
VP, CXO |
CEO, COO, Founder, GM |
| Customer Success |
Support |
Manager, Director |
CS Manager, Head of CS, VP Customer Success |
Minimum Audience Rules
- Minimum matched audience: 300 LinkedIn members per campaign
- Smaller audiences = higher CPMs (more expensive)
- At later ABM stages (Interested, Considering): persona lists may be too small to run separately
- Solution: Combine personas at later stages, differentiate via ad content instead of targeting
Persona Prioritization
Which Personas to Target First
| Priority |
Persona Type |
Why |
Budget Allocation |
| 1st |
Champions |
They drive the deal internally |
40-50% of budget |
| 2nd |
Economic Buyers |
They approve the purchase |
20-30% of budget |
| 3rd |
End Users |
They validate product fit |
15-20% of budget |
| 4th |
Technical Evaluators |
They assess during demo/trial |
5-10% of budget |
When Budget is Limited
With $10K/month (one campaign group effectively):
- Don't split by persona. Target all personas in one campaign group.
- Differentiate through content. Create ads that speak to different JTBDs within the same campaign.
- Use LinkedIn filters to exclude irrelevant roles (e.g., exclude HR, Finance, Legal from initial campaigns).
- Prioritize by JTBD/intent instead of persona.
Campaign Naming Convention (for Intent Tracking)
Structure
[Campaign Name] - [Persona] - [Ad Type] - [JTBD/Intent] - [ABM Stage]
Examples:
Q1-Analytics - PM - Image - User-Activation - Awareness
Q1-Analytics - UX - Video - Session-Replay - Interested
Q1-Analytics - All - TLA - Industry-Trends - Awareness
Why Naming Matters
When ZenABM/Fibbler pushes engagement data to HubSpot, the campaign name is how you extract:
- Which persona engaged (for outreach targeting)
- Which intent/JTBD they cared about (for message personalization)
- Which ABM stage content resonated (for campaign optimization)
Notion Database for Asset Management
Track all ad assets in a Notion database with properties:
- Persona
- Ad Type (Image, Video, TLA, Carousel, Text)
- Asset Description / JTBD
- ABM Stage (Awareness, Interested, Considering)
- ABM Campaign Name
- Status (Brief Done, Design In Progress, Ready, Launched)
- Owner
- Designer Assigned
- Performance Notes
Use formula fields to auto-generate campaign names from properties, ensuring clean naming that flows through to intent detection.
Project Management: Asset Creation Workflow
Process
1. ABM Manager defines campaign brief
→ Persona, intent, stage, messaging angle
2. Content owner writes ad copy brief
→ Headline, intro text, CTA, visual direction
3. Brief → Notion database (assigned to designer)
4. Designer creates visual assets
→ Follow LinkedIn's current image, headline, and intro-text specs for each ad format
5. ABM Manager reviews + approves
6. Assets uploaded to LinkedIn Campaign Manager
→ Correct campaign group, campaign, naming convention
7. Track in Notion: launched date, performance notes
Volume Expectations
| Campaign Scale |
Ads Needed |
Note |
| First campaign |
~100 ads across personas |
Typical first ABM campaign |
| Mature program |
500+ ads over time |
After 16 months |
| Per campaign cycle |
17-20 ads per intent group |
Based on budget math |
Critical: Volume of ads must follow the budget math - each ad needs enough daily spend to generate 3-4 clicks, so don't create more ads than your budget can effectively serve.
Measuring Persona Effectiveness
Metrics by Persona
| Metric |
What It Tells You |
| CTR by persona |
Which personas engage most with ads |
| CPC by persona |
Cost efficiency per persona |
| Interested-stage conversion by persona |
Which personas move through the funnel |
| Meeting book rate by persona |
Which personas are most receptive to outreach |
| Pipeline generated by persona |
Which personas drive the most revenue |
What to Do with the Data
| Finding |
Action |
| Product personas have 2x the CTR of Engineering |
Shift more budget to Product persona campaigns |
| Executive personas rarely click but deals with exec engagement close faster |
Keep exec campaigns for influence, don't optimize for clicks |
| One persona never progresses past Aware |
Revisit messaging or drop from targeting |
| BDRs get higher reply rates from Champions than Economic Buyers |
Focus BDR outreach on Champions first |
By Ivan Falco - Frontal
1---2name: persona-mapping-framework3description: Use this skill when mapping the buying committee inside ABM target accounts — identifying personas from closed-won data, their jobs-to-be-done and pain points, and how ad messaging and BDR outreach should differ by persona.4---56# Persona Mapping - Framework78How to identify, segment, and target personas within ABM accounts. Mapping personas to their jobs-to-be-done (JTBDs), pain points, and messaging.910---1112## The Persona Mapping Principle1314ABM targets *accounts*, but people buy - not companies. Persona mapping answers:151. **Who** at the target account should see your ads?162. **What** do they care about? (JTBDs, pain points)173. **How** should messaging differ by persona?184. **When** should BDRs reach out to which persona?1920---2122## Identifying Personas2324### Step 1: Analyze Your Closed-Won Deals2526Look at your CRM data for closed-won deals:2728| Question | What You're Looking For | Source |29|---|---|---|30| Who was the primary contact on won deals? | Most common titles/roles | CRM deal contacts |31| Who initiated the buying process? | Champion persona | CRM first touch data |32| Who signed the contract? | Economic buyer persona | CRM deal owner notes |33| Who else was involved in evaluation? | Buying committee members | CRM activity log, call notes |34| What was their typical seniority? | IC vs Manager vs VP vs C-suite | CRM contact properties |3536### Step 2: Map the Buying Committee3738Most B2B deals involve 6-10 stakeholders. Map the roles:3940| Role | Definition | Example Titles | Engagement Priority |41|---|---|---|---|42| **Champion** | Internal advocate who drives the deal | Product Manager, Head of Ops, Director of Growth | Primary - warm them first |43| **Economic Buyer** | Controls budget, signs the contract | VP/C-suite, Finance | Engage after champion is warm |44| **Technical Evaluator** | Assesses product capabilities | Engineering Lead, Solutions Architect, IT | Engage during demo/trial stage |45| **End User** | Will use the product daily | Analyst, Designer, Specialist, IC | Engage with product-focused content |46| **Blocker/Gatekeeper** | Can slow or kill the deal | Legal, Procurement, IT Security | Address concerns proactively |4748### Step 3: Define Persona Attributes4950For each persona, document:5152| Attribute | What to Capture | Example |53|---|---|---|54| **Title patterns** | Common job titles | "Product Manager", "Head of Product", "VP Product" |55| **Seniority** | IC / Manager / Director / VP / C-suite | Manager - Director |56| **Function** | Department/team | Product, Engineering, Marketing |57| **JTBD** | Job to be done - what they're trying to accomplish | "Improve user onboarding to reduce churn" |58| **Pain points** | What's frustrating them today | "Can't see where users drop off", "Manual onboarding flows" |59| **Success metrics** | How their performance is measured | Activation rate, time-to-value, NPS |60| **Content preferences** | What content resonates | Case studies, data/benchmarks, peer recommendations |61| **Buying role** | Champion / Economic Buyer / Evaluator / User / Blocker | Champion |6263---6465## Persona Enrichment with Clay6667### Custom Properties to Enrich6869When building contact lists in Clay, enrich beyond standard fields:7071| Property | How to Enrich | Why |72|---|---|---|73| **Persona** (custom) | Map from title using Clay AI/rules | Enables persona-specific campaigns |74| **Seniority** (custom) | Map from title (IC/Manager/Director/VP/C-Suite) | Different messaging by seniority |75| **Function** | Extract from LinkedIn profile | Department-specific JTBDs |76| **LinkedIn URL** | Apollo / Clay | For LinkedIn outreach + audience matching |77| **Verified email** | Email waterfall in Clay | For outreach sequences |7879### Persona Assignment Rules8081Create rules in Clay to auto-assign personas:8283```84IF title contains "Product Manager" OR "PM" OR "Head of Product" OR "VP Product" OR "CPO":85 → Persona = "Product"8687IF title contains "UX" OR "UI" OR "Designer" OR "Design Lead":88 → Persona = "UX/Design"8990IF title contains "Marketing" OR "Growth" OR "PMM" OR "Demand Gen":91 → Persona = "Marketing"9293IF title contains "CTO" OR "VP Engineering" OR "Engineering Manager":94 → Persona = "Engineering"9596IF title contains "CEO" OR "COO" OR "Founder" OR "General Manager":97 → Persona = "Executive"9899IF title contains "Customer Success" OR "CX" OR "Support":100 → Persona = "Customer Success"101```102103---104105## Persona-Based Messaging106107### Messaging Matrix108109| Persona | Primary JTBD | Pain Point | Messaging Angle | Ad Content Example |110|---|---|---|---|---|111| **Product** | Improve user activation/retention | Can't see user behavior, manual processes | "See exactly where users drop off" | Product analytics screenshots, feature walkthrough |112| **UX/Design** | Create better user experiences | No data on user flows, guesswork | "Design based on real user behavior" | Session replay demo, heatmap visuals |113| **Marketing** | Drive pipeline, prove ROI | Can't attribute conversions, poor lead quality | "Know which campaigns actually drive revenue" | ROI dashboards, attribution data |114| **Engineering** | Ship faster, reduce tech debt | Too many tools, complex integrations | "One platform, simple integration" | API docs, integration showcase |115| **Executive** | Hit revenue/growth targets | Slow growth, high churn, team misalignment | "Companies like yours grew X% with us" | Case study with numbers, ROI calculator |116| **Customer Success** | Reduce churn, improve NPS | Can't identify at-risk users proactively | "Spot churn risk before it's too late" | Health score dashboards, alert demos |117118### Messaging by ABM Stage119120| Stage | Product Persona | Executive Persona | UX Persona |121|---|---|---|---|122| **Awareness** | Industry trend / thought leadership about user analytics | "CEOs at top SaaS companies are investing in..." | Design community content, UX best practices |123| **Interested** | Feature comparison vs competitors | ROI data, business impact numbers | Session replay deep-dive, workflow demos |124| **Considering** | Product demo, free trial, technical walkthrough | Case study from peer company, executive briefing | Design-focused case study, UX workflow example |125126---127128## LinkedIn Targeting by Persona129130### Two Approaches131132**Approach 1: Contact List Upload (More Precise, More Expensive)**1331. Find specific contacts at target accounts in Clay/Apollo1342. Enrich with email1353. Upload to HubSpot as marketing contacts1364. Sync to LinkedIn via HubSpot Ad Audiences1375. Create separate campaigns per persona list138139**Pros:** Very precise targeting140**Cons:** Expensive (Clay credits + HubSpot marketing contacts cost), complex to manage141142**Approach 2: Company List + LinkedIn Native Filters (Recommended)**1431. Upload company list to LinkedIn (via HubSpot company list sync)1442. Use LinkedIn Campaign Manager's native filters to target personas:145 - Job Function: Product Management, Design, Marketing, etc.146 - Seniority: Director, VP, C-Suite147 - Job Title keywords: specific titles148149**Pros:** Cheaper, simpler, leverages LinkedIn's data150**Cons:** Less precise (LinkedIn's job function mapping isn't perfect)151152### LinkedIn Persona Filters153154| Persona | LinkedIn Job Function | LinkedIn Seniority | Title Keywords |155|---|---|---|---|156| **Product** | Product Management | Manager, Director, VP | Product Manager, Head of Product, CPO |157| **UX/Design** | Design, Arts and Design | Manager, Senior, Director | UX Designer, Design Lead, Head of Design |158| **Marketing** | Marketing | Manager, Director, VP | Growth, PMM, Demand Gen, Head of Marketing |159| **Engineering** | Engineering, IT | Manager, Director, VP, CTO | Engineering Manager, CTO, VP Engineering |160| **Executive** | General Management | VP, CXO | CEO, COO, Founder, GM |161| **Customer Success** | Support | Manager, Director | CS Manager, Head of CS, VP Customer Success |162163### Minimum Audience Rules164165- **Minimum matched audience:** 300 LinkedIn members per campaign166- **Smaller audiences = higher CPMs** (more expensive)167- **At later ABM stages (Interested, Considering):** persona lists may be too small to run separately168- **Solution:** Combine personas at later stages, differentiate via ad content instead of targeting169170---171172## Persona Prioritization173174### Which Personas to Target First175176| Priority | Persona Type | Why | Budget Allocation |177|---|---|---|---|178| **1st** | Champions | They drive the deal internally | 40-50% of budget |179| **2nd** | Economic Buyers | They approve the purchase | 20-30% of budget |180| **3rd** | End Users | They validate product fit | 15-20% of budget |181| **4th** | Technical Evaluators | They assess during demo/trial | 5-10% of budget |182183### When Budget is Limited184185With $10K/month (one campaign group effectively):1861. **Don't split by persona.** Target all personas in one campaign group.1872. **Differentiate through content.** Create ads that speak to different JTBDs within the same campaign.1883. **Use LinkedIn filters to exclude irrelevant roles** (e.g., exclude HR, Finance, Legal from initial campaigns).1894. **Prioritize by JTBD/intent** instead of persona.190191---192193## Campaign Naming Convention (for Intent Tracking)194195### Structure196197```198[Campaign Name] - [Persona] - [Ad Type] - [JTBD/Intent] - [ABM Stage]199```200201**Examples:**202- `Q1-Analytics - PM - Image - User-Activation - Awareness`203- `Q1-Analytics - UX - Video - Session-Replay - Interested`204- `Q1-Analytics - All - TLA - Industry-Trends - Awareness`205206### Why Naming Matters207208When ZenABM/Fibbler pushes engagement data to HubSpot, the campaign name is how you extract:209- Which **persona** engaged (for outreach targeting)210- Which **intent/JTBD** they cared about (for message personalization)211- Which **ABM stage** content resonated (for campaign optimization)212213### Notion Database for Asset Management214215Track all ad assets in a Notion database with properties:216- Persona217- Ad Type (Image, Video, TLA, Carousel, Text)218- Asset Description / JTBD219- ABM Stage (Awareness, Interested, Considering)220- ABM Campaign Name221- Status (Brief Done, Design In Progress, Ready, Launched)222- Owner223- Designer Assigned224- Performance Notes225226Use formula fields to auto-generate campaign names from properties, ensuring clean naming that flows through to intent detection.227228---229230## Project Management: Asset Creation Workflow231232### Process233234```2351. ABM Manager defines campaign brief236 → Persona, intent, stage, messaging angle2372382. Content owner writes ad copy brief239 → Headline, intro text, CTA, visual direction2402413. Brief → Notion database (assigned to designer)2422434. Designer creates visual assets244 → Follow LinkedIn's current image, headline, and intro-text specs for each ad format2452465. ABM Manager reviews + approves2472486. Assets uploaded to LinkedIn Campaign Manager249 → Correct campaign group, campaign, naming convention2502517. Track in Notion: launched date, performance notes252```253254### Volume Expectations255256| Campaign Scale | Ads Needed | Note |257|---|---|---|258| **First campaign** | ~100 ads across personas | Typical first ABM campaign |259| **Mature program** | 500+ ads over time | After 16 months |260| **Per campaign cycle** | 17-20 ads per intent group | Based on budget math |261262**Critical:** Volume of ads must follow the budget math - each ad needs enough daily spend to generate 3-4 clicks, so don't create more ads than your budget can effectively serve.263264---265266## Measuring Persona Effectiveness267268### Metrics by Persona269270| Metric | What It Tells You |271|---|---|272| **CTR by persona** | Which personas engage most with ads |273| **CPC by persona** | Cost efficiency per persona |274| **Interested-stage conversion by persona** | Which personas move through the funnel |275| **Meeting book rate by persona** | Which personas are most receptive to outreach |276| **Pipeline generated by persona** | Which personas drive the most revenue |277278### What to Do with the Data279280| Finding | Action |281|---|---|282| Product personas have 2x the CTR of Engineering | Shift more budget to Product persona campaigns |283| Executive personas rarely click but deals with exec engagement close faster | Keep exec campaigns for influence, don't optimize for clicks |284| One persona never progresses past Aware | Revisit messaging or drop from targeting |285| BDRs get higher reply rates from Champions than Economic Buyers | Focus BDR outreach on Champions first |286287---288289> By Ivan Falco - Frontal