What is a campaign?
In AuraGo, a campaign is a behaviour change journey — a designed sequence of interactive touchpoints that moves a person from where they are to where you need them to be.
A campaign is not a single page, a one-off email, or a static funnel. It is the top-level container for everything you design and deploy: the strategic intent, the audience model, the staged experience, and the data you collect along the way.
Most real behaviour change does not happen in one sitting. Someone profiles themselves on day one, receives a follow-up nudge on day three, and converts on day seven — each moment with a different goal, a different tone, and a different set of choices. A campaign holds that full arc together under one name, one aim, and one success signal.
Screenshot — campaign overview in the builder
[Placeholder: screenshot of the campaign editor showing the campaign name, stage list, and Strategic Hub entry point.]
Why stages exist
Before stages, campaign tools tended to collapse everything into one long flow — one page after another, one branching tree, one growing mess. That works for a five-step quiz. It breaks down when the journey spans days, channels, or distinct strategic phases.
Stages solve this by giving each chapter of the journey its own container.
A stage is a self-contained interaction flow — one complete experience a user can enter, move through, and exit. Profile on Monday. Persuade on Wednesday. Convert on Friday. Each is a stage.
Within a stage, AuraGo bundles every mechanical element needed to run that experience in the live world:
Flow
The logic layer. A finite-state machine that decides which step comes next, where branches fork, and when the stage ends.
Views
The experience layer. The interactive screens your audience actually sees — profiling questions, persuasion blocks, offers, and calls to action.
Retrievers
The selection layer. Rules and ranking that pick the right content for this user, this persona, this moment inside the flow.
Packages & contents
The asset layer. Grouped content items — copy blocks, media, profile questions, product cards — that retrievers and flows reference at runtime.
Think of it this way: the campaign is the book; each stage is a chapter; the flow inside a stage is the plot of that chapter. Views, retrievers, packages, and contents are the sentences.
Diagram — stage as a container
[Placeholder: diagram showing one stage box containing Flow at the centre, with Views, Retrievers, and Packages/Contents connected around it. A second diagram level above showing Campaign → Stage 1 → Stage 2 → Stage 3.]
At the campaign level, you orchestrate how stages connect — sequentially, or with dynamic AI routing when the journey has enough depth. The stage itself stays focused: one interaction flow, one exit criteria, one audience slice if needed.
The design principle
One stage, one interaction flow. When you need a genuinely new phase of the journey — a new goal, a new channel, a new strategic beat — add a stage. Do not stretch a single flow into something it was never meant to carry.
Two faces of every campaign
Every AuraGo campaign has two faces that mirror each other. One is the behavioural science face — the theory of change. The other is the implementation face — the mechanics that make the theory runnable with real users.
They are not separate projects. They are two views of the same campaign, designed to stay aligned.
Diagram — strategy vs implementation
[Placeholder: split diagram. Left side: Strategic Hub sections. Right side: Stage canvas with Flow, Views, Retrievers, Packages. A bridge arrow labelled "alignment" connecting Visual Sequence to stage list.]
Face 1 — Campaign Strategy (the science)
This is the work you do in the Strategic Hub. It answers why the campaign exists and who it speaks to before you wire a single node in the Flow Builder.
Foundations
Your campaign aim, value proposition, and success signal. What behaviour are you trying to change, and how will you know it worked?
Persona modeling
Two to four audience archetypes with Jobs-to-be-Done, active hindrances, and interaction style. Personas become live structural inputs — not labels on a spreadsheet.
Creative brief
Tone, narrative angle, big idea, and conversion logic. The voice that should run through every touchpoint in the journey.
Product / service mapping
Capabilities linked to behaviours you want to enable. This grounds AI-generated content in what you actually offer.
Visual sequence
The step-by-step shape of the campaign — which blocks appear in which order, where profiling gives way to persuasion, where persona columns fork. Includes a live alignment score so strategic drift is visible before launch.
This face is the Campaign Strategy. It is behavioural design made structural: the frameworks practitioners use — JTBD, nudge sequencing, persona reframing — encoded as the architecture of the campaign itself.
Screenshot — Strategic Hub
[Placeholder: screenshot of the Strategic Hub showing Foundations, Persona Modeling, Creative Brief, Product/Service, and Visual Sequence sections.]
Face 2 — Implementation (the mechanics)
This is the work you do in the campaign builder — stages, flows, views, retrievers, packages, and deployment. It answers how the strategy becomes a live experience a user can actually enter.
Stages
Execution chapters. Each stage holds one flow and the views, retrievers, and packages that flow needs. Stages have exit criteria, optional audience targeting, and order within the campaign.
Flows
Runtime logic. Wire states, transitions, and branches in the Flow Builder. A flow is always scoped to a stage — it is the engine of that chapter's interaction.
Views
Designed screens. Built in the View Builder with Adaptive Cards, themes, and input/output parameters that connect user choices back to the flow.
Retrievers
Dynamic content selection. Rank and filter packages based on profile signals, persona tags, or campaign context so the right message surfaces at the right step.
Packages & contents
Reusable assets. Bundle copy, media, and profile questions into packages that flows and retrievers reference — shared across stages when it makes sense, scoped to one stage when it does not.
Orchestration & deployment
How stages connect (linear or dynamic routing), bridge messages between stages, and how the campaign reaches users via smart links, web tags, or channel-specific delivery.
This face is where strategy meets the live world. The Visual Sequence you designed in the Hub should map cleanly to the stages and flows you build here. When they diverge, the alignment score tells you — before users do.
Screenshot — stage canvas
[Placeholder: screenshot of the stage editor showing the stage details panel, linked flow, and tiles for retrievers, views, and packages.]
What is an interaction?
If a campaign is the journey and a stage is the chapter, an interaction is the conversation happening inside that chapter — one step, one screen, one choice at a time.
When a user opens your campaign, they enter a stage. The stage's flow loads the first view. The user reads, taps, selects, submits. Their choice travels through the flow — maybe updating their profile, maybe triggering a retriever to rank content, maybe branching them onto a persona-specific path. The next view renders. The loop continues until the stage's exit criteria are met.
Diagram — one interaction cycle
[Placeholder: sequence diagram — User → View → Flow (FSM) → Retriever → Package/Content → next View. Annotate profile data capture on the return path.]
Each interaction is more than a click event. AuraGo captures semantic signals — what the choice implies about motivation, hesitation, and Jobs-to-be-Done — not just that a button was pressed. Those signals accumulate across interactions within a stage and across stages within the campaign, building a profile you can read in the Profile Explorer long after the session ends.
Three terms worth keeping distinct:
- Interaction flow — the full loop inside one stage (flow + views + retrievers + content), from entry to exit.
- Interaction step — a single view rendered at a point in the flow; one beat of the conversation.
- User interaction — the moment a person acts on a step; the input that advances the flow and updates their profile.
How the pieces connect
Here is the hierarchy from top to bottom, and how data flows through it.
Define the Campaign Strategy in the Strategic Hub
Set your aim, model your personas, write the brief, map your product capabilities, and design the Visual Sequence. This is the behavioural science face — the theory of change.
Shape the campaign into stages
Each major phase of the Visual Sequence becomes a stage. A profiling stage, a persuasion stage, a conversion stage — each with its own goal and exit criteria.
Build one interaction flow per stage
For each stage, wire a flow, attach the views it renders, connect retrievers to packages, and populate packages with content. One stage, one self-contained flow.
Orchestrate stage transitions
Choose linear sequencing or dynamic AI routing. Write bridge messages that explain what just happened and what comes next.
Launch and read the interactions
Users enter stages, move through interaction steps, and leave semantic signals behind. The campaign strategy you defined is what gives those signals meaning.
Diagram — full campaign stack
[Placeholder: layered architecture diagram — Campaign Strategy (Hub) on top, Campaign (orchestration) in the middle, Stages below, each stage expanding into Flow / Views / Retrievers / Packages / Content at the bottom.]
| Layer | What it holds | Where you work |
|---|---|---|
| Campaign | Aim, personas, brief, orchestration, deployment | Strategic Hub + campaign editor |
| Stage | One interaction flow and its assets | Stage canvas |
| Flow | Logic, branching, exit | Flow Builder |
| View | Screen design, inputs, outputs | View Builder |
| Retriever | Content selection rules | Retriever editor |
| Package / content | Copy, media, profile questions | Content library |
| Interaction | A user's step through the above | Runtime engine (live) |
Who needs to understand this
Campaign designers
Think in chapters, not pages
Use stages to match the natural phases of your theory of change. Keep each stage focused on one interaction goal.
Flow builders
Scope logic to the stage
Build flows inside stages, not across them. Cross-stage movement is orchestration — not one giant state machine.
Strategists
Keep both faces aligned
The Visual Sequence in the Hub should map to your stage list. If they diverge, fix the drift before launch.
Ready to go deeper?
Start with the entity reference for flows, retrievers, views, and content — or zoom out to the full platform map.
Was this article helpful?
Feedback is saved when Postgres is configured, and logged in local preview mode.