GrowingAlgo Campaign Builder · Attract
Audience Persona Builder
A persona that cannot change an ad is a poster. This one is five fields: job, trigger, objection, channel, and proof they trust. Use it when “SMBs” is still the audience line.
The tool
Try it here
Use this when the brief’s audience line is still “SMBs” or “gen z.” Those are not people you can write an RSA for (RSA = Google’s multi-headline search ad).
Why it helps
Why you need an Audience Persona Builder
Twenty-page persona decks sit in Drive. Nobody opens them in creative review. The ad still says “grow your business.”
The useful persona is operational: what just happened that makes them click, what they will not believe, where they already scroll.
If two campaigns share a persona, they should share proof and CTA. If they do not, you do not have one persona. You have a compromise.
When
When to use it
- Before the brief, if the market is still fuzzy.
- When paid and organic are writing to different people.
- When CAC (cost to acquire a customer) is fine on one segment and terrible on “everyone 25–54.” Split the persona, split the campaign name.
How
How to use it
- 1Job: title plus the work they are measured on. “Performance lead, weekly ROAS slide.”
- 2Trigger: the event last week. Missed pipeline. Agency overage. A truncated RSA in auction.
- 3Objection: why they will not book. “Another tool to log into.” Answer it in the ad or do not spend.
- 4Channel: where they will actually see this. LinkedIn for B2B job titles. Google for problem queries. Not both with the same line.
- 5Proof they trust: a peer, a number, a constraint. Generate. Paste the persona into the brief’s audience field.
Example
Example: the in-house lead who inherited messy UTMs
Not “marketers 25–40.” The person who opens GA4 on Monday and sees twelve sources for one Facebook campaign.
You put in
- Job
- In-house performance lead, 8-person team
- Trigger
- Board asked for channel CAC; the export would not roll up
- Objection
- Will not adopt a stack that needs another login
- Channel
- Google Search (“utm builder”, “campaign naming convention”)
- Proof
- Free, no account, same name in ads and UTM
You get
Job: In-house performance lead, 8-person team Trigger: Board asked for channel CAC; export would not roll up Objection: No another login Channel: Google Search for UTM / naming queries Proof: Free, no account, same string in UI and URL
The RSA can say “UTMs that match the campaign name.” That is the trigger, not a brand adjective. The CTA is Book a demo, or just use the free builder - the objection was login, so the product answer is no account to browse.
Result
What this changes for you
Headlines name a job and a trigger. Media picks the channel they already use. You stop buying reach against a made-up age band.
Common mistakes
- Made-up names and stock photos. They do not change a headline.
- Five personas for one campaign. You will write mush to please all five.
- Channel = “everywhere.” Then you buy everywhere.
- Objection left blank. The landing page will not answer it either.
FAQ
Audience Persona Builder FAQ
How is this different from a marketing persona template?
It drops hobbies, quotes and day-in-the-life. It keeps the five fields that change the ad, the channel and the CTA.
How many personas should a campaign have?
One. If you need two, you need two campaign names and two UTMs. That is allowed. Mixing them in one RSA is not.
Should personas include age and gender?
Only if the channel targeting requires it. They rarely write the line. Job and trigger do.
Can I use this persona builder for B2C?
Yes. Job becomes the role in the household or the task (“parent booking a class”). Trigger is still an event, not a vibe.