Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.gradial.com/llms.txt

Use this file to discover all available pages before exploring further.

Audiences add a targeting layer on top of personas for CX Optimizer. Instead of selecting personas one by one for every run, teams can save named audiences, organize personas inside them, and reference those groups directly from chat when launching CX Optimizer. Think of it as:
  • Persona — one simulated buyer or user
  • Segment / tag — metadata used to narrow personas
  • Audience — a saved group of personas that can be reused across runs
This makes CX Optimizer more repeatable for demos, account planning, and post-launch validation because the target audience definition can be reused instead of rebuilt every time.

​
What you can do

When the Audiences feature is enabled, teams can:
  • Group existing personas into named audiences such as Enterprise Buying Committee, Healthcare Prospects, or Trial-to-Paid Evaluators
  • Keep audiences at the organization level for broad reuse, or scope them to a workspace for team-specific or deal-specific testing
  • Move or copy personas between audiences as the target scenario changes
  • Reference an audience directly in chat with the Journey Agent when launching a CX Optimizer flow
  • Layer segment or tag filters on top of an audience when you want a narrower slice inside the saved group
Creating and editing audiences is limited to Admin and Design roles.

​
How it works with CX Optimizer

1

Create personas

Build personas that represent real customer types in your organization.
2

Group into audiences

Organize those personas into one or more saved audiences.
3

Reference in chat

Ask CX Optimizer to run against a named audience directly in chat.
4

Agent resolution

The Journey Agent resolves the audience, pulls the matching personas, and launches persona-based journey analysis.
5

Review the report

The final report reflects the selected audience rather than a generic user.
If the audience has 5 or fewer personas, CX Optimizer runs against all of them. If it has more than 5, the agent samples up to 5 for a single run so the analysis stays manageable and comparable.

​
Where segments fit

Use audiences when you want a stable, reusable group. Use segments or tags when you want to filter within that group. Example:
  • Audience: Enterprise Buying Committee
  • Segments inside it: security, marketing-ops, web-owner, executive
That lets a team run:
  • The full audience for a broad journey review
  • Only the security and web-owner segments for a technical evaluation flow
  • A narrower sub-group without rebuilding the saved audience

​
Use cases

Group the personas involved in one deal cycle, then run CX Optimizer against that audience to show where different stakeholders experience friction across the same journey.Example audience: Enterprise Buying Committee — Marketing lead, web manager, compliance reviewer, procurement stakeholderThis tells a stronger story than a single generic persona and shows how one site experience lands differently across roles.
Create vertical audiences such as Healthcare, Financial Services, or Higher Ed and test whether the site’s messaging and flows work for that industry’s expectations.Useful for industry landing pages, ABM campaigns, and vertical demos — and helps position CX Optimizer as persona-aware rather than one-size-fits-all.
Group personas by journey stage such as First-Time Evaluators, In-Market Buyers, or Existing Customer Expansion.Lets teams test whether pages support discovery, evaluation, and conversion differently — a good fit for pricing, demo request, onboarding, and support journeys.
Create a workspace-scoped audience for a live opportunity and run CX Optimizer against the exact stakeholder mix that matters for that account.Keeps the analysis relevant to one prospect or account team. Useful for SE-led workshops and pre-demo prep.
Reuse the same audience after a redesign, launch, or content update to compare how the journey changed for the same target group.Makes CX Optimizer runs more consistent over time and makes it easier to show before-and-after improvement to customers.
Use a broad audience, then narrow it with segments in chat for a more focused read.Example: Audience: SMB Prospects + Segment filter: mobile-firstGives teams a clean way to tailor the story without rebuilding personas every time.

​
Sample chat prompts

  • “Run CX Optimizer on our pricing flow for the Enterprise Buying Committee audience.”
  • “Audit the signup journey for the Healthcare audience, using only the security and compliance segments.”
  • “Run a mobile CXO pass against the SMB Prospects audience.”
  • “Use the Existing Customer Expansion audience to review our support-to-upsell journey.”

​
Things to keep in mind

The Audiences feature must be explicitly enabled for your organization. Contact your Gradial team to get access.
  • Audiences are built from existing personas — they are not a replacement for persona design.
  • A single CX Optimizer run still caps persona fanout at 5 personas per run.
  • Segment or tag filters can be layered onto an audience, but if the filter removes every persona, broaden the selection or run a generic-user analysis instead.