Mavera DocsOperator's Guide
Checking your Mavera sessionLoading workspace audiences and API keys…
Checking…Use or share this pageSend the page itself, print it, or open its complete context in your AI workspace.
Trackers and alerts
Repeat the same bounded study on a schedule and alert when a computed result moves.
Interactive product walkthrough
Create a tracker
Lock the signal and audience, then set cadence, threshold, and first wave.
Simulation onlyNothing is saved or charged
1
Step 1 of 7Open Intelligence
Choose Intelligence from the sidebar.
Mavera workspace
Good afternoon
Choose a surface from the sidebar to begin.
Demo workspace0 actions completed
Recent workspace activityStatus
Audience comparisonReady to review
Customer interview evidenceGrounded
Campaign pre-flightDraft
- 1Open IntelligenceChoose Intelligence from the sidebar.
- 2Choose TrackersOpen the standing signal workspace.
- 3Name the signalWrite the decision signal to watch.
- 4Lock the audienceChoose the audience that must stay constant.
- 5Pick a cadenceChoose weekly, monthly, or quarterly.
- 6Set the thresholdSet the movement that deserves an alert.
- 7Save the trackerCreate the local tracker and inspect its first scheduled wave.
Name the decision signal
Examples: message preference, switching intent, or price objection prevalence.
Lock the question and audience
Changing either breaks the trend comparison.
Pick a cadence
Daily is expensive and usually noisy. Weekly or monthly fits most decision cycles.
Set the movement threshold
The alert percentage is a code-side threshold, not an LLM judgment.
Review waves
Use the tracker history to distinguish a one-wave spike from sustained movement.
Prompt drop
Prompt4 fields left
Create a monthly tracker for [signal] using [audience] and the exact question “[question].” Alert at [threshold] movement. Keep the audience, sample, and wording fixed. Summarize only after two waves exist.
Unfilled variables remain in brackets.