The engine · five stages · one loop

A loop that remembers what it did.

Most tools react. The Ad Spend ingests, understands, detects, explains, and recommends — every ~3 hours — and writes down every step, so the account accumulates judgment instead of resetting every morning.

The loop

Five stages, one loop, every ~3 hours.

Step through each stage, or watch the loop run on its own. Whatever it does, it writes down — so the next pass starts from everything the last one learned.

Back to the top — every ~3 hours
01 — Ingest

Every setting and change, at the most granular level.

The engine captures every campaign structure, budget, bid, audience and creative — and every change to them, by whom and from what to what. Nothing sampled, nothing rounded off. The account starts remembering itself the moment you connect.

01 / 05

Everything in the platform

Three pillars. One continuous loop.

Memory keeps the record, Signal reads it for what changed and why, and Action closes the loop. Here is every capability across the three — what is live today, and what is on the way.

Memory

Every change, kept permanently.

Explore Memory
Historylive

A permanent, timestamped record.

Captures which field changed, from what value to what value, by whom and when — manual or platform-automated. Never expires.

Chatprivate beta

Your accounts, answerable in plain English.

“Why did CPA jump on Brand in March?” returns the answer with the decision that caused it — in the web app and in Slack.

Signal

Detection with the cause attached.

Explore Signal
Trendslive

1,900+ detection algorithms, every ~3 hours.

More than 1,900 detection algorithms run against the full record — context, setup, metrics — every ~3 hours, and connect each finding to its cause via causal inference.

Alertslive

Forecast-backed monitoring.

A model trained on the account's own history sets the baseline; pacing, spend and conversion alerts arrive in Slack, bundled as digests.

Reportslive

Stakeholder-tailored rundowns, on schedule.

Executive summaries, platform-by-platform analysis, audience and creative insights — with recommendations attached.

Action

Approve the fix. Close the loop.

Explore Action
Optimizerprivate beta

Approve a recommendation; it executes.

Budget reallocation first (targeting, pause/reactivate next), with projected impact shown — every change logged back into History.

Attributionprivate beta

Ad decisions mapped to closed revenue.

Connects through CRM (HubSpot, Salesforce) to tie touchpoints — and the specific decisions behind them — to revenue.

Intentroadmap

True intent, not a guessed pixel.

Flips the pixel-vendor model — instead of guessing who's in-market, it reads real targeting choices and real response rates.

Why a record

The reasoning is the product.

A number tells you what happened. A record tells you why someone decided what to do about it. When the reasoning is written down, the account stops depending on whoever happened to be watching the dashboard that day.

See how memory works

Change record

Recommendation
Shift 18% of budget to Prospecting
Reason
Retargeting CPA up 31% over 9 days
Expected
Blended CPA down 8–12%
Result, once approved
CPA down 11% over 14 days

Questions

Answers, not gestures.

How is this different from automated rules?
Rules fire blindly when a threshold is crossed. The Ad Spend ingests context first, detects against your own baseline, explains the cause, and recommends a fix. A rule cannot explain itself; this record can.
Does it change my campaigns on its own?
No. The system recommends; you decide. Nothing executes without your approval, and every approved change — budget, bid, status — is written straight back into the record.
Can I see why a recommendation was made?
Yes. Every finding is traced to the specific change that caused it through causal inference, with projected impact attached. The reasoning is part of the record, not a footnote.
How long until it has enough memory to be useful?
It starts with whatever history you connect and keeps everything from the moment you connect onward. The more the account runs, the deeper the memory — but it is useful from the first read, not after a long training period.

See it on your account

Watch the loop run on your own spend.

Connect an account and the engine starts building its record from day one.