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.
How It Works
Configure the analysis scope
Navigate the site like a real user
Evaluate the experience at every step
Discover issues proactively
Generate a prioritized report
Analysis Modes
Single Page Audit
A deep-dive on any specific URL. The agent evaluates content quality, CTA effectiveness, visual hierarchy, accessibility, and sentiment for the target page and captures a structured observation before exiting. Best for focused reviews of high-traffic or high-value pages.Journey Analysis
End-to-end evaluation of a complete user flow — onboarding, checkout, a campaign landing sequence, or any multi-step path. The agent navigates the site pursuing a persona’s goals through the natural flow, logging every step: page visited, action taken, observation, sentiment annotation, and pain points. When personas are configured, one thread runs per persona in parallel, and findings are synthesized across audience segments.Full Site Exploration
The agent autonomously discovers and audits pages across your entire digital property. This mode leverages crawl infrastructure to surface broken links, navigation issues, and structural problems site-wide — covering ground that would take a UX team weeks to complete.Persona Simulation
Personas are first-party audience definitions — your actual customer segments with their demographics, goals, and pain points. When personas are enabled, CX Optimizer creates one analysis thread per persona and evaluates the experience from each audience’s perspective. What counts as “clear” or “effective” shifts based on who the audience is. A flow that works for a power user may confuse a first-time visitor. Persona simulation surfaces those gaps by running every persona in parallel and synthesizing cross-persona findings in the final report. Configure personas in Settings → Personas. Each persona record includes name, description, target role, geography, goals, and pain points.Sentiment Scoring
Sentiment is captured at the journey step level — not aggregated into a single pass/fail score at the end. Each step in a persona’s journey is annotated with one of four values:| Sentiment | Meaning |
|---|---|
| Positive | Action completes smoothly; user is satisfied |
| Neutral | Action completes without friction but without delight |
| Negative | User encounters delays, unclear navigation, or minor usability issues |
| Frustrated | User hits blockers, dead ends, or significant confusion |
Report Output
Every CX Optimizer run produces a structured report with the following components:- Overall journey health score — A 0–10 score summarizing the experience across all tested journeys and personas.
- Per-persona breakdown — CX score, goal completion rate, sentiment curve, and session replay for each configured persona.
- Actionable insights — Recommendations organized into four categories:
| Category | What it covers |
|---|---|
| Tactical Updates | Quick wins — copy tweaks, CTA adjustments, minor content improvements |
| Bug Fixes | Broken functionality and UX issues that block or confuse users |
| New Content | Missing information or guidance that users are clearly looking for |
| Moonshots | Strategic, higher-effort improvements with significant CX impact |
Live Observation
While CX Optimizer runs, you can watch the agent navigate your site in real time. The dashboard streams live screenshots and journey step observations with sentiment indicators, showing active thread status and current step. This is especially useful for demos and stakeholder reviews — decision-makers can see the agent clicking, scrolling, and evaluating their actual site as it happens.Pre-Publish Simulation
CX Optimizer can run against any URL that loads in a browser — including staging environments. The agent treats staging and production identically, capturing the full experience including page state, interactive elements, and form behavior. Run CX Optimizer on a staging URL before launch to catch experience issues before they reach customers. Results are stored separately from production data, enabling side-by-side comparison.AEM Preflight
AEM Preflight is a dedicated pre-launch mode that lets you run a CX analysis on a single AEM page — published or unpublished — before a full campaign goes live. Unlike standard Pre-Publish Simulation, which requires a publicly accessible staging URL, AEM Preflight connects directly to your AEM environment using browser-to-AEM authentication. This means the agent can access and evaluate pages that haven’t been published yet — draft content, launch copies, and staged variants that are invisible to any external URL. When to use AEM Preflight:- Validate a new page or campaign landing experience before promoting from a launch copy to live
- Catch CX issues in unpublished content before it reaches QA or stakeholder review
- Run a targeted single-page analysis without spinning up a full site or journey audit
- In CX Optimizer, select Single Page Audit as your analysis mode.
- Enter the AEM page path or author URL for the page you want to evaluate.
- Confirm your AEM connection is authenticated — Preflight uses your connected AEM integration credentials.
- Run the analysis. The agent accesses the page directly through AEM and produces the standard CX report.
The Closed Loop
CX Optimizer is designed to connect directly to Gradial’s content execution layer. When the optimizer surfaces an issue, you can create a Gradial task directly from the finding — and the performance context travels with the task. The agent executing the fix understands what it’s optimizing and why, not just what to change.Surface the signal
Understand the gap
Create the task
Frequently Asked Questions
How long does a CX Optimizer run take?
How long does a CX Optimizer run take?
What does the report include?
What does the report include?
How accurate is the AI agent?
How accurate is the AI agent?
How is this different from analytics tools like GA or Adobe Analytics?
How is this different from analytics tools like GA or Adobe Analytics?
How is this different from session replay tools like FullStory or Hotjar?
How is this different from session replay tools like FullStory or Hotjar?
Will this replace our UX team?
Will this replace our UX team?
Can we test pages before they go live?
Can we test pages before they go live?
Is our data safe?
Is our data safe?