Personas
See how AI engines answer the same question for different audiences
Personas let you see how AI engines answer the same question for different people. Attach a persona to a prompt and GEOflux runs the prompt a second time with a short "about me" description of that person added as context, so you can compare what a mid-market VP of Sales is told with what a solo founder is told, or what a family with young kids sees next to a couple on a tight budget.
Personas are available on Starter, Growth and trial projects. On Free, the Personas page explains the feature and how to upgrade.
Why personas matter
AI answers change with who is asking. A generic prompt such as "what is the best CRM for a small business" tends to return one list; the same prompt asked by a VP of Sales at a 500-person company can return a different set of vendors. Brands that are strong for one audience are often invisible for another, and you will not see that from the base answer alone.
- B2B example: a CRM marketer finds the base prompt favours one vendor, while the "VP of Sales, mid-market" persona surfaces three others, including a competitor they were not tracking.
- B2C example: a travel agency compares a "family with two young children" persona with a "young professional travelling solo" persona and sees which packages and which sites each audience is sent to.
How a persona works
A persona is built from structured attributes, not from free text. When you attach it to a prompt:
- GEOflux writes a short description of the person from those attributes, plus your optional Other details note, and adds it to the question as context about who is asking.
- The prompt runs as a separate answer for that persona, on every engine in the project, on the same schedule as the base prompt (daily on Starter and Growth).
- The prompt's own base answer, without any persona, keeps running too. You always have the generic read to compare against.
- Each prompt and persona pair is tracked on its own, with its own history, Visibility, Share of Voice, Sentiment and Mentions.
Creating a persona
Go to Personas under your project and click Add persona. You can start from a template or build from scratch.
Starter templates
- B2B: CEO (SMB), HR Director (50 to 200 employees), IT Lead (Enterprise)
- B2C: Solo household, Couple (no kids), Family household, Retiree / Senior
Build from scratch
| Type | Attributes |
|---|---|
| B2B | Job role or function, company size, industry, revenue band, decision authority, buying stage, company maturity |
| B2C | Age band, gender (optional), urbanicity, household composition, children, employment, education, spending power, housing type |
Both types can add context toggles (Time-poor, Budget-sensitive, Eco-oriented, Beginner in activity, plus Small living space for B2C) and an Other details note of up to 150 characters. Use the note for the one thing the attributes cannot express ("switching from HubSpot after a price increase", "first time buying a bean-to-cup machine"), not for a paragraph of backstory.
Personas cannot be edited
A persona is part of the definition of the answers collected under it, so changing it would mix two audiences in one history. To change an audience, create a new persona, move your prompts to it, then archive the old one.
The personas table
The Personas page lists every persona with its name, type, a summary of its details, its market (the country it represents), the number of active prompts attached, the date added, and View and Archive actions. It also shows how many included persona slots you have left on your plan, and how many of your credits are in use (Credits: X / Y used, with a Manage credits link).
Attaching personas to prompts
You can attach personas in three places:
- In the Add prompt modal, when creating a prompt.
- From the Prompts page, with the + on a prompt row.
- In bulk, by selecting prompts and choosing Assign personas.
CSV import creates base prompts only. Import first, then attach personas from the prompts table.
Attach personas to the prompts where the audience genuinely changes the answer, not to the whole set. For most brands that is 10 to 15 Evaluate prompts: the comparison and "best X for Y" questions where a buyer's role, budget or household decides which brands come back. Discover prompts and most Buy prompts rarely need a persona. See Build a prompt plan for how personas fit into the wider set.
Reading persona data
- Overview, Personas tab: visibility broken down by audience, so you can see at a glance where your brand is strong for one persona and absent for another.
- Overview, Persona filter: isolate base-only answers or one persona across every other filter (period, engine, topic, tag, Buyer Journey, Brand type). See Filters and periods.
- Prompt detail page: the base answer and each persona side by side for one prompt.
- Answers page: filter by persona to read the actual answers and the sources each engine cited for that audience.
- Shared reports carry the persona filter, so a client report can be scoped to one audience.
Read persona data the same way you read the base set: as a share across prompts and days, not as one answer. A single persona answer differs from the base answer for the same reasons any two AI answers differ; the pattern across a month is what matters.
Credits
Every link between a prompt and a persona is a slot, and each slot holds the same credits as the prompt itself: 1 per answer, so 3 on ChatGPT, Gemini and Perplexity.
| Setup | Credits held |
|---|---|
| Prompt, no persona | 3 |
| Prompt + 1 persona | 6 |
| Prompt + 3 personas | 12 |
| 50 prompts + 3 personas on 10 of them | 150 + 90 = 240 |
| 50 prompts + 3 personas on all of them | 600 |
Credits are allocated, not consumed: a slot holds its credits for as long as it is active. Archiving a prompt returns the credits for the prompt and all its persona links; restoring charges them again. Removing a persona from a prompt returns that link's credits.
Included persona slots: Free 0, Starter 1, Growth 3. The Personas page shows the slots you have left. Additional personas are a paid add-on; each add-on persona also adds 150 credits to your monthly allowance, so the extra audience comes with room to attach it. The price is shown on the Personas page when you add one. During a trial, adding a paid persona needs a payment method on file; your trial keeps running and nothing is charged until it ends. See Billing and credits for the full model.
A worked example on Growth (450 credits): 115 prompts plus 3 personas on the same 10 audience-sensitive prompts is 115 + 30 = 145 slots, or 435 credits, leaving 15 free. The same 3 personas on every prompt would turn 450 credits into about 37 prompts, which is why personas belong on a slice of the set, not all of it.
Archiving a persona
Archiving a persona stops tracking every prompt attached to it for that audience, returns those credits, and frees the persona slot. The base prompts keep running. The persona's history is kept but hidden from stats. Archiving a persona cannot be undone, and if the persona came with bonus credits (an add-on persona), those credits go with it. When you replace an audience, create the new persona and attach the prompts before archiving the old one.
Personas and pitch reports
Pitch reports (for agencies prospecting a new client) run on the Growth package without personas. Attach personas once the pitch converts into a paid project.
Good practice
- Two or three personas that are truly different (role, company size, budget, household) teach more than six that overlap.
- Name personas by the audience, not the campaign ("HR Director, 50 to 200 employees", not "Q4 push").
- Attach personas to the Evaluate prompts first; they are where audience changes the recommendation most.
- Keep the base answer running on every prompt. It is the control you compare each persona against.
- Review persona attachments at the quarterly set review, together with the rest of the prompt set.