
Persona tabs split the navigation by audience, so each visitor self-selects into a path built for their role instead of scanning a flat list of links.
Key takeaways
Showing 1–29 of 47 examples
Browse every navbar pattern by UX best practice.
Persona tabs organize the navigation around who the visitor is, not around the product's feature list. Instead of one flat row of links, the bar or its dropdown splits into paths for each audience, so an operations lead and a finance buyer each follow a route built for their role. The navbar does the sorting the visitor would otherwise do in their head.
The pattern takes a few forms:
Most buyers arrive as a specific role with a specific problem. A menu built around the product's structure makes them translate that problem into the company's words before they can move. Persona tabs skip that step: the visitor sees their own job in the navigation and clicks.
The choice also tells the next page who it is talking to. A finance lead and an engineer want different proof, and once they have picked their path, the page can open with what that role cares about instead of a generic pitch.
The best examples below name the actual role instead of hiding it behind a vague label. Parabola splits its menu into a Teams we serve column for Operations, Data and engineering, and Finance, each with one line on what that team gets. Amplitude routes by Team across Product, Data, Engineering, Marketing and Executive. Deel's By Teams column covers HR, Finance, Legal and IT with a one-line benefit each. SignOnSite and Instruqt put a By Role column beside a use-case column, so a director and a project manager can each find their own way in. What repeats is a label that names a job a real person holds, plus a line that confirms the path is theirs.
Persona routing rarely stands alone. The best navbars pair it with use-case tabs that let visitors self-route by the job they came to do and often anchor the dropdown with a featured highlight card that pulls a key story or offer into the menu. The complete navbar gallery shows the full range.


The usual failure is a label so generic it names no one: a bare Teams or Enterprise tab tells a visitor nothing about whether the path is theirs. The second is a list of roles with no value line, so the visitor has to click each one to find out what it holds. The third is too many overlapping segments, where a buyer cannot tell which role fits and stalls on the choice.

Curated by
Gabriel Amzallag , Founder, Web Anatomy
5 years CRO + SEO at Qonto (2021–2025). After advising 15+ SaaS on their websites (Payfit, Pigment…), the same patterns kept breaking, so I decided to build the source of truth on what works on the web: the intelligence layer every tool, builder, and team uses to ship sites that perform.
The common questions about splitting the navbar by audience, with answers drawn from 47 scored examples.
They answer different questions. A persona column answers who are you (Marketing, Sales, Finance). A use-case column answers what are you trying to do (eSignatures, retention, lead generation). An industry column answers what market are you in (Retail, Healthcare, Financial Services). Running them side by side lets each visitor pick the way in that feels natural to them.
Enough to cover the roles that actually buy, few enough to scan in a couple of seconds. Near-identical segments make the choice harder, because the visitor has to work out which one is really theirs. Lead with the most common roles and let use-case or industry columns catch the visitors who do not think of themselves as a job title.