
Define
who matters.
Aura turns an opportunity into an audience you can review: inclusion criteria, exclusions, eligibility and the reason each person belongs. Observed behavior stays separate from interpretation and unknowns.
“Who are we really talking to?”How it works
Curious and human, attentive to behavior. Aura asks what people did, not just which label they carry, and keeps the unknowns visible.
- The problem it solves
- Segments get built from a hunch or a demographic label, and nobody can say later who was included, who was left out or why.
- What it produces
- An audience you can review: inclusion criteria, exclusions, eligibility by channel and the reason each rule exists.
What Aura can do.
- Build audiences from behavior. First-party data, behavior and context tied to the decision.
- Define eligibility and exclusions. Supported identity links, channel permissions and suppression rules.
- Version the audience. Revise the definition as behavior and results change.
- You
Define an audience of eligible customers who have not upgraded.
AuraI’ll use the eligibility rules and exclude recent upgrades and customers who can’t receive this communication. Review the criteria before I prepare the audience.
- You
Why exclude customers with an open support ticket?
AuraAn upgrade offer during an unresolved issue tends to read as tone-deaf. It’s a judgment call: keep it or drop it, and I’ll record the decision with the audience.
Why it holds: Rules come from your eligibility and consent data. Customers without a confirmed match stay unresolved; they are not guessed.
| Rule | Criterion |
|---|---|
| Include | Postpaid plan eligible for upgrade |
| Include | 12 or more months of tenure |
| Exclude | Upgraded in the last 90 days |
| Exclude | No consent for this channel |
| Exclude | Open support ticket (to confirm) |
Illustrative script with fictional data. It shows how the work feels; it is not a transcript or a product screenshot.
Try Aura in a simulation.
Interactive simulation · illustrative data · not a product screenshot

A person-shaped understanding.

City explorers
One example,
five stages.
A retailer asks why repeat purchases fell in the North region. The same question, region and period travel through every stage. Illustrative workflow; the numbers are not client results.
- 01 · Understand
NexusRepeat purchases fell 11.8%, concentrated among customers whose last order was 35–60 days ago. - 02 · Define
Aura42,380 customers match. Prioritize frequent buyers with no purchase in 45+ days. - 03 · Create
PrismThree retention concepts from your brand rules and product catalog. - 04 · Activate
RadianMeta customer audience, push and email. 80% test, 20% holdout. Ready for review. - 05 · LearnShared systemIllustrative result: 7.4% relative lift in repurchase rate versus holdout. Back to Understand.↺ Returns to Understand