A security lead, a product manager, and a procurement analyst from the same 3,000-person company open your website in the same week. They sit on the same buying committee and are evaluating the same product, and they get the same homepage, the same case studies, and the same demo form. The security lead wants your SOC 2 report, the product manager wants to know whether the team will actually use the thing, and procurement wants the price. To personalize a website by job title is to give each of them the page that answers their question first.
It is also harder than it sounds, and most guides skip the hard part. Industry and company size come almost for free from an IP lookup on the first pageview. Job title does not: it belongs to a person, and on most B2B sites the person is anonymous. This guide is about doing role-based personalization honestly. It covers which roles to use, how to map messy titles into them, where role data actually comes from (and where it does not), what to change on each page, and how to tell if any of it worked.
Why Role Matters, and Why It Gets Skipped
B2B purchases are group decisions. Forrester's 2024 buyers' journey survey found that on average 13 people are involved in a purchasing decision. Each of those people reads your site with a different question. Account-level personalization can recognize that someone from a logistics company in Germany is visiting, but it treats everyone from that company as the same reader. Role is the layer that separates the CFO from the engineer.
Teams skip it for a practical reason: the data is thin. Reverse IP lookup identifies companies, not people. You only know someone's title when they are already in your CRM, when they arrived through a campaign aimed at that title, or when their behavior gives them away. So role personalization will always reach a minority of sessions, and the program has to be designed around that fact rather than pretending every visitor can be tagged.
Our position: role is worth adding once industry or size personalization is already running, and it is most valuable on three pages (homepage, pricing, demo form). Do not start with it, and do not build twenty personas.
The Four Roles Worth Segmenting by First
Four groups cover how buying committees split the work. More than that and each segment gets too little traffic to measure.
| Role | Typical titles | Wants to know | Reads | Right CTA |
|---|---|---|---|---|
| Economic buyer | CEO, CFO, VP with budget | What it costs, what it returns, what the contract looks like | Pricing, ROI content, case studies with outcomes | Pricing and ROI worksheet, call with a senior rep |
| Technical evaluator | CTO, security lead, architect, engineering manager | Architecture, integrations, security, data handling | Docs, API reference, security and trust pages | Architecture overview, technical briefing without a sales pitch |
| Practitioner | Analyst, ops manager, specialist | Will this make my week easier, how long to learn it | Feature pages, tutorials, screenshots, help center | Product tour, sandbox or recorded demo |
| Champion | Director, senior manager, team lead, product manager | Can I sell this internally, what will my team get | Comparison pages, peer case studies, ROI material | Internal pitch pack, reference call |
The champion is the role most sites under-serve. That person is not signing the contract, but they are writing the internal email that gets it signed. Giving them something to forward (a one-page summary, a comparison, a security FAQ) is often the cheapest win in the whole program.
Job Title to Category Mapping Table
The hard part is not writing rules. It is mapping the free-text job titles you actually receive from your CRM, form fills, and data providers (ZoomInfo, Apollo, 6sense and similar) into the four categories above. Use the table below as a starter taxonomy and tune it to your market.
| Category | C-Level & VP | Director & Head of | Manager & Lead | Individual contributor |
|---|---|---|---|---|
| Economic buyer | CEO, CFO, COO, CRO, Chief Revenue Officer, President, VP Finance, VP Operations, VP Procurement | Director of Finance, Director of Procurement, Director of Operations, Head of Finance, Head of Procurement | Finance Manager, Procurement Manager, Buyer, Category Manager | Procurement Specialist, Finance Analyst (with buying authority) |
| Technical evaluator | CTO, CIO, CISO, Chief Architect, Chief Data Officer, VP Engineering, VP Technology, VP Security, VP IT, VP Data, VP Platform | Director of Engineering, Director of Platform, Director of Infrastructure, Director of Security, Head of Engineering, Head of Platform, Head of Security | Engineering Manager, Tech Lead, Architect, Solutions Architect, Security Engineering Manager | Senior Engineer, Staff Engineer, Principal Engineer, Security Engineer, DevOps Engineer, SRE |
| Practitioner / end user | (rare at this level) | (rare at this level) | Marketing Manager, Operations Manager, Sales Operations Manager, RevOps Manager | Analyst (Marketing, Sales, Business, Data), Specialist, Coordinator, Associate, Researcher, Junior / Mid-level Engineer |
| Champion / influencer | VP Marketing, VP Product, VP Customer Success (when not the economic buyer) | Director of Marketing, Director of Product, Director of Demand Generation, Director of Growth, Head of Marketing, Head of Product, Head of Growth | Senior Manager, Product Manager, Senior Product Manager, Program Manager, Team Lead | (rarely starts here) |
One caveat on the table: the same title means different things in different products. If you sell marketing software, the VP Marketing is your economic buyer, not a champion. Before using the table, re-sort the rows for the function your product serves.
How to Handle Ambiguous Titles
Plenty of titles will not fit cleanly. These defaults cover the common cases:
- "Director of X" with no clear function: default to champion. A director with a generic title is more often pitching internally than signing.
- "Head of X" or "VP" at a company under 50 people: treat as economic buyer. At that size the function lead usually holds the budget.
- Senior and staff engineers or analysts: practitioner, unless the company is under about 30 people, where authority is flat enough to treat them as technical evaluators.
- Product managers: champion. They rarely hold budget but often run vendor evaluations.
- Consultants and contractors: map by the function in the title ("Marketing Consultant" goes to practitioner). They influence but rarely buy.
- Owner or founder at a small company: economic buyer.
- Empty or generic titles ("Employee", "Member of Technical Staff", "Engineer"): put them in an unmapped bucket and rely on behavior for those sessions.
Keep the mapping as one lookup table in your personalization tool or CDP, not as logic repeated inside every page rule. Then marketing can change a category in one place, and switching data vendors does not mean rewriting the taxonomy.
Where Role Data Actually Comes From
Avoid "choose your role" pop-ups. Most visitors close them, some click a different role out of curiosity, and you have added friction for everyone. Use these sources instead, roughly in order of how much you can trust them:
| Source | How it works | Reliability | Watch out for |
|---|---|---|---|
| CRM record of a known contact | Returning visitor matched by cookie after a form fill or an email click | High: the title is on file | Titles go stale; refresh from your data provider at least yearly |
| Campaign targeting | UTM shows the visitor came from an ad or email aimed at one role (for example a LinkedIn campaign targeted by job function) | Medium to high | Targeting leaks; colleagues forward links |
| On-site behavior | Pages read in the session reveal the question the visitor is asking | Medium, improves with more pages | Needs two or more pageviews before it says anything |
| Person-level identification vendors | Third parties claim to match anonymous visitors to individuals | Varies widely, mostly US coverage | Under GDPR this is personal data processing and needs a lawful basis; check before you switch it on for EU traffic |
Company-level visitor identification fits alongside these: it will not tell you the person's title, but it tells you the company, which lets you combine role with industry and size. Our post on connecting website personalization data to your CRM covers how to pass known contact titles back to the website.
Behavioral rules for inferring role
For anonymous visitors, behavior is the main signal. Simple rules beat a complicated model at the start, because you can explain them and check them:
- Two or more views of pricing or ROI content in one session: economic buyer.
- Two or more views of docs, API reference, or security pages: technical evaluator.
- Two or more views of feature pages, tutorials, or product tours: practitioner.
- A case study plus a comparison or alternatives page: champion.
- Anything else: no role. Show the default.
When sources disagree, use a precedence order rather than averaging them: a CRM title beats campaign context, which beats behavior. Behavior should only override a CRM title when it is strong and recent (a known "Marketing Manager" who has read four API pages this week is acting as a technical evaluator for this purchase). Our post on behavioral segmentation for B2B websites covers the scoring side in more depth.
Before launch, check your rules against reality. Take the contacts who filled in a demo form last quarter, look up the pages they viewed before converting, and see what role your rules would have assigned compared with their real title. If the rules get the role wrong for many of them, fix the rules before anyone sees a personalized page.
What to Change on Each Page by Role
Role personalization does not mean writing every page four times. On each page, change two to four elements and leave the rest alone.
Homepage
Change the hero headline, the featured proof, and the primary CTA. Example copy (illustrative, for a fictional analytics product):
| Role | Hero headline | Proof shown | Primary CTA |
|---|---|---|---|
| Default | Know which accounts are ready to buy | Logo bar | Book a demo |
| Economic buyer | See which pipeline your website is already creating | Quote from a finance or revenue leader about outcomes | See pricing and ROI worksheet |
| Technical evaluator | One script tag, no changes to your stack | Security certifications, integration logos | Read the architecture overview |
| Practitioner | Build your first segment in an afternoon | Screenshot of the daily workflow | Take the product tour |
| Champion | What your team can ship this quarter | Case study from a similar team | Get the internal pitch pack |
Our homepage personalization playbook covers the rest of the homepage. Add role on top of elements you already personalize rather than opening up new ones.
Pricing page
This is where the roles diverge most. The economic buyer wants total cost over the contract term and a way to justify it, so lead with an annual view and an ROI worksheet. The technical evaluator wants to know what each tier includes: API limits, SSO, data residency, support levels. The practitioner wants to know what they can actually do on each plan. The champion wants something to take to finance: a one-page summary with the business case and two reference customers.
Keep the prices themselves identical for every role. Changing framing is fine; showing different numbers to different people from the same company is a fast way to lose trust once they compare notes. More on this page in our post on B2B pricing page personalization.
Product and feature pages
Product pages need the least rewriting. Change what sits above the fold: architecture diagrams and integration lists for technical evaluators, workflow screenshots and tutorials for practitioners, outcome-led case studies from similar companies for economic buyers and champions. Leave the feature list itself static on the first pass.
Demo form
The form is where a mismatch costs most. An economic buyer wants to know who will be on the call and how long it takes. A technical evaluator often wants a technical session or documentation, not a sales call. A practitioner wants to see the product without a meeting. Offering a role-appropriate alternative next to the standard demo request (for example a "technical briefing" option for evaluators) keeps the people who would otherwise leave.
Worked Example: One Account, Three Visitors
Illustrative example. A 600-person logistics software company is evaluating a reporting tool. Over two weeks, three people from the company visit:
- Visitor A arrives from a LinkedIn campaign targeted at finance roles and reads pricing twice. Role: economic buyer (campaign plus behavior agree). The pricing page leads with the annual cost view and the ROI worksheet.
- Visitor B is anonymous, reads the API reference, the security page, and the integration list. Role: technical evaluator (behavior). The homepage hero switches to the "no changes to your stack" variant on the next visit, and the demo form offers a technical briefing.
- Visitor C is a known contact (filled in a webinar form a year ago) with the title "Senior Product Manager". Role: champion (CRM title). They see the peer case study and the internal pitch pack CTA.
Meanwhile, company-level identification shows three people from the same account in two weeks, which is a buying-group signal sales should hear about regardless of role. Role changes what each person sees; the account view decides when sales gets involved. Our post on account scoring covers that second half.
A 60-Day Rollout Plan
- Days 1 to 10: role inference. Load the title mapping table, connect CRM titles, write the behavioral rules, and back-test them against last quarter's demo requests.
- Days 11 to 25: homepage. One hero, proof, and CTA variant per role, plus a holdout group that keeps seeing the default. Use an A/B test plan to fix the success metric before launch.
- Days 26 to 40: pricing page. Change framing and the primary CTA only. Pricing copy has commercial consequences, so keep the first iteration small.
- Days 41 to 55: product pages. Above-the-fold emphasis and the case studies below the feature list.
- Days 56 to 60: review. Compare each role segment with its holdout. Keep variants that win with a sample you trust, retire the rest, and decide which role gets new content next.
If your traffic is small, cut the plan down: one role, one page, one month. The technical evaluator on the homepage is a good first test because the behavioral signal is clear and the content usually exists already in your docs.
Mistakes That Sink Role-Based Personalization
Too many roles. Persona documents often list ten or more. Each extra role splits traffic further until nothing is measurable. Four is plenty for the first quarter.
No default experience. Most sessions will never get a role tag. The default page has to be good on its own; role variants add to it, they do not replace it.
Changing copy but not the CTA. A finance-flavored headline followed by "Start building now" undoes the work. The call to action has to match what that role does next.
Treating every visit as the first. A CFO on their fourth visit has already seen your pitch. Adjust by visit count as well as role, for example by moving from the ROI worksheet to a direct meeting offer.
Role without company context. A CFO at a 50-person startup and a CFO at a 5,000-person enterprise have different concerns. Combine role with at least one firmographic dimension; our guide to company size personalization is a natural base layer.
Ignoring privacy. Showing a visitor "Welcome, Jane from Finance" is creepy and, in the EU, may be unlawful depending on how you got the data. Personalize by role quietly: change what is emphasized, never announce what you know.
How to Measure It
Measure at the segment level. Site-wide conversion moves for many reasons unrelated to role variants. Track these each week:
- Conversion rate per role segment against its own holdout. A role with no lift needs a new variant.
- Role coverage: the share of sessions that receive a role tag. Low coverage limits impact; a sudden jump usually means a rule has become too loose.
- Tag accuracy, checked monthly by comparing inferred roles with titles of people who later convert.
- Downstream quality: whether leads from personalized sessions become qualified opportunities at a higher rate than leads from the holdout.
Markettailor's segmentation lets you define role segments from CRM fields, campaign parameters, and page behavior, and report conversion per segment against a holdout. Whatever tool you use, the measurement design matters more than the tool.
Start With One Role and One Page
Pick the technical evaluator, write one homepage hero for them, and run it against the default for a month. If it wins, add the pricing page or a second role. If it does not, you have learned which question that audience is not asking, at the cost of one headline.
To see how role segments combine with company-level identification on your own traffic, book a walkthrough from our pricing page.