Aura · The AI Analyst Layer of Mediaura Signal
The AI Marketing Analyst That Shows Its Work
Aura is the agentic AI layer built into Mediaura Signal. Ask it anything about your marketing performance: channels, locations, campaigns, journey paths, causal lift, anomalies, weather effects, foot traffic. Aura answers in plain English.
But Aura doesn't do the math. Aura calls the tools that do the math.
Every figure comes from the statistical engines, and Aura explains what they found. Aura works inside the platform under the same BAA as everything else. Review its summaries the way you'd review an analyst's.
Every Other “AI Marketing Assistant” Has the Same Problem
You've seen the demos. "Just chat with your data!" A friendly chat panel, a logo in the corner, and a language model that's been pointed at a dashboard. Ask it what your Meta ROAS was last quarter and you get a confident answer in two seconds.
Sometimes the answer is right. Sometimes the answer is off by 30%. Sometimes the answer is a number that doesn't exist anywhere in your database. You can't tell which is which without going to check, which defeats the entire point of asking the AI in the first place.
This is the core problem with bolting a language model onto a marketing dashboard: the model isn't calculating anything. It's pattern-matching against text it was shown in a prompt, and language models trained on the entire internet are extraordinarily good at producing text that sounds like a marketing analytics answer. Whether that text reflects your actual data is a separate question, and most products in this space don't structurally answer it.
Aura was built so the language model doesn't compute your numbers. Not "carefully prompted," not "instructed to be accurate." The engines do the math.
The Architecture
Aura Doesn't Do the Math. Aura Calls the Tools That Do the Math.
The difference between a chatbot and an agent is not the chat interface. The difference is what happens between the question and the answer.
A chatbot reads your question, generates an answer that looks plausible, and hands it back. An agent reads your question, decides what data it needs, calls a tool that runs an actual query against your production database, waits for the real result, and only then formulates an answer based on what came back. The tool is the thing the model can't fake.
Aura is an agent.
How a Question Actually Gets Answered
When you ask Aura "what did Meta contribute to the Fishers location last month?", here's what happens in the seconds before you see a response:
Aura Interprets the Question
Identifies what it doesn't yet know: which location "Fishers" refers to, what date range "last month" means, and what the Mediaura Causal Engine (M-CE) has computed for Meta's causal lift at that location over that period.
Aura Issues Structured Tool Calls
To a tool that lists locations and resolves the name, then to a tool that pulls causal attribution analysis from M-CE for that location and date range. The tool calls are typed: parameters, return shapes, and validation are defined in advance. The model can only call tools that are defined in advance.
The Tools Execute Against Your Production Data
Real SQL queries, real API calls, real M-CE coefficients. Aura builds its answer from what those queries return.
Aura Assembles the Answer
From the real results, in plain English. It might also issue follow-up tool calls if the first round didn't fully answer the question; Aura can chain up to ten tool calls per question to build the context it needs.
You See the Answer
With progress indicators showing which tools ran along the way. "Analyzing performance... Running correlation analysis... Pulling attribution data..." It's not a black box. You can see Aura working.
Why This Matters
The architectural property that matters is this: the model waits for tools to return real data before it makes a quantitative claim. A traditional chatbot can answer "what was Meta's ROAS" without ever consulting a database. It just generates plausible text. Aura is built not to. The tool-use loop is enforced in the architecture. If Aura needs a number and the tool fails, Aura is designed to tell you the tool failed rather than fill the gap. Like any AI output, its narrative can still contain errors, which is why you review it the way you'd review an analyst's.
This is what we mean when we say Aura is built on "agentic AI." The phrase has been diluted into marketing fluff in the last two years, but it has a precise technical meaning: an AI system that uses tools to take actions in the world (in Aura's case, querying real data) rather than generating responses purely from its own parameters. The tools are the difference between an AI that talks about your data and an AI that actually consults it.
The Honest Version of the Trust Story
We want to be precise about what is and isn't enforced, because the honest version is more compelling than overclaiming.
Structurally Enforced
Tool calls are typed and validated. The model can only respond after tools return. Tool execution runs against your production database with no intermediate caching or summarization. The model sees real JSON results before formulating a response.
Prompt-Level Enforcement
Aura's system prompt instructs the model to use tools rather than guessing, to stay on topic, to refuse prompt manipulation, and not to disclose proprietary methodology. These are guardrails, not architectural constraints, and we tell clients exactly which is which.
Not in Place Yet
There is no post-hoc output validator that programmatically checks every number in Aura's response against tool results. The model sees real data and is designed to write from it, but it can still make mistakes, so review its summaries the way you'd review an analyst's. A separate verifier layer is on the roadmap. We think the tool-use architecture is sufficient for the cases Aura is deployed for today, and we'll add the verifier when the cost of an error grows large enough to justify it.
We'd rather be precise about this than overclaim. The trust we're asking for is technical, not vibes-based.
Read-Only by Design
Aura is your analyst. Aura is not your autopilot.
Today, Aura is strictly read-only across every deployment. Every tool Aura has access to is a read query against your data. There are no tools that can push budget changes to Google or Meta, pause campaigns, write to your CRM, or modify any external system. Aura can recommend that you shift $40K from Meta to Google at the Fishers location, and it can show you the M-CE diagnostics that justify the recommendation, and it can write you an action item. But Signal never changes campaigns, budgets, or audiences. Those decisions stay with your team, or with your agency if you've delegated them.
This is deliberate.
An AI agent that can spend money on your behalf is a failure mode we aren't willing to build into a measurement product. The read-only posture is not a limitation we're embarrassed about. The system that measures the spend shouldn't be the one moving it.
Aura reads everything and writes nothing.
Recommendations come with the diagnostics behind them. The decision, and the change, stay with your team.
The Intelligence Layer Across All Four Layers
Aura sits across the entire Mediaura Signal stack, calling into each layer when you ask a question:
Signal Tracker
Captures the signals
Identity Resolution
Stitches them into customer journeys
Revenue Mapping
Ties journeys to booked revenue or admissions
The Mediaura Causal Engine (M-CE)
Runs the causal models
Aura
The layer that lets you talk to all of it in plain English, and that talks back in the form of analysis you can check.
When you ask about lift, Aura calls M-CE. When you ask about a customer journey, it calls the identity layer. When you ask about a transaction, it calls revenue mapping. When you ask why a location is underperforming, it calls all four (plus the weather tool, the foot traffic tool, and the notes layer) and synthesizes the answer.
This is why Aura doesn't have to guess. Every layer beneath it produces real, queryable, structured data, so there's a tool that can answer the question from your data. Aura explains what the tools found, and you review it the way you'd review an analyst's work.
Start With the Fit Check
Free and honest, with no obligation on your side. If your data can support causal conclusions, you'll get a written fixed-fee quote and timeline. If it can't, you'll know that too.