The platform marks its own homework.
Ad-reported ROAS counts revenue the ads may not have caused, and ignores margin, returns and repeat orders. An account can look healthy while every sale loses money.
Cortex is the platform I built to run Google Ads and Microsoft Ads. It checks every account before the day starts, names the one thing holding growth back, judges spend on profit and can't change a thing without my approval.
Not on general sale yet. The way to have it working for you today is my account management.
Why I built it
After 22 years in Google Ads, the costly mistakes I see are rarely about effort. They come from good work aimed at the wrong problem. Cortex exists to stop three of them.
Ad-reported ROAS counts revenue the ads may not have caused, and ignores margin, returns and repeat orders. An account can look healthy while every sale loses money.
Rewriting every ad won't help if the checkout is broken, the tracking double counts, or the business can't handle more orders. Most tools only look inside the ad account, so they never see it.
A tag stops firing, a data feed goes stale, a report keeps saying nothing is wrong. Cortex treats "couldn't check" as a finding in its own right and says so first.
The method
Every account problem sits in one of five layers, and they come in a fixed order. There's no point tuning keywords while the tracking is wrong. Pick a layer to see what Cortex checks there.
Sometimes the honest answer is that the fix isn't in the ad account at all. Cortex is built to say that plainly, because a Google Ads tweak can't fix a pricing problem.
The platform
Each part feeds the same picture of the account, so a finding in the feed or the tracking changes what gets recommended in the campaigns.
Walks the five layers on fresh data and names the single constraint that matters most, with the numbers behind it.
Joins ad spend to real orders, margins, returns and repeat purchases, so campaigns are judged on new customers and contribution.
Performance breaks, budget pacing, disapprovals and tracking that has stopped firing, caught each morning on every live account.
Finds waste and new keywords, then runs every proposed keyword or negative through a guard that stops it cutting traffic that converts.
Audits Merchant Centre data for errors, weak titles and missing attributes, and builds supplemental feeds to fix what it finds.
Fifty checks across conversion tags, consent, attribution and data quality, so every decision rests on numbers that are right.
Asset groups, channel spend, brand protection and search themes, so automated campaign types get steered instead of left alone.
Tracks monthly budgets, spots campaigns held back by budget and moves bid targets in measured steps, never big swings.
Writes ads in the brand's own voice, runs head-to-head tests and retires tired copy once the data says so.
How a change happens
One negative keyword or a budget move across a whole account, every change takes the same route, and every one can be undone.
Fresh data for the exact period, tied to the constraint the change is meant to fix.
The current value, the new one, the reason and a dry run of what will happen.
Nothing goes live until I approve that exact change. One approval unlocks one change, then the lock re-arms.
Cortex reads the account back to confirm it saved what was asked, logs the undo step and checks the result at 30, 60 and 90 days.
Raise daily budget
Non-brand · High intent
Illustrative example
Safeguards
The rules that protect your account are written into the software, so they hold on a busy day as well as a quiet one.
Nothing automated can change a live account. Each approved change goes through on its own, and the lock re-arms straight after.
Numbers are pulled fresh for the exact period before anything is reported or recommended.
Paused campaigns and ad groups stay out of recommendations, so the advice is about what's actually running.
After every change it confirms the platform stored exactly what was requested, and flags it if not.
Each change is logged with the value it replaced and the exact step to reverse it.
If a check couldn't run, the report says "not checked". It never turns a gap into an all clear.
Cortex signs in to Google with my own account and only reaches the client accounts I've been given access to. It uses that access to report on campaigns, check product feeds and tracking, and apply the changes I approve.
Who built it
"I built Cortex for my own clients first. It had to be good enough for their money."
I've been running paid search for 22 years, for e-commerce brands, B2B firms and agencies. Every tool I used either reported numbers without telling me what to do, or made changes I couldn't see or undo.
So I built the system I wanted. Cortex runs every account I manage, every day. It's where every lesson from those years now lives: each mistake I've seen gets turned into a check, so it can't happen twice.
It isn't on general sale yet. When it opens to other advertisers, it will be the same platform that runs my own clients' money today.
Questions
Get access
Have Cortex working on your account now through my management, or join the waiting list for the public release.
My management service runs on Cortex from day one.