A woman in a dark suit reading a newspaper in front of venetian blinds

For enterprise

Governance, built into the record.

Many markets, many accounts, in-house teams and agency partners on the same spend. The Ad Spend keeps one record of who changed what, and routes every change through approval.

HistoryAll markets · This week

Example

Changes
3
By people
2
Auto-applied
1
  1. North AmericaGoogle Ads

    Tue 8:40 AM

    Location targeting on Search / Brand

    12 metros3 metros

    Changed by Sam R., agency partner.

  2. APACMeta

    Mon 4:12 PM

    Daily budget cap on Prospecting

    $400$500

    Changed by Maya T., APAC team.

  3. EMEAGoogle Ads

    Mon 9:02 AM

    Bid strategy on Search / Non-brand

    Manual CPCMaximize conversions

    Changed by an auto-applied recommendation.

Example History timeline across three markets: three settings changes this week, two made by people and one auto-applied. In North America an agency partner narrowed location targeting from 12 metros to 3, in APAC the regional team raised a daily budget cap from 400 to 500 dollars, and in EMEA an auto-applied recommendation changed a bid strategy.

Who this is for

Built for enterprise teams.

At enterprise scale, the question is never just performance. It is who decided, when, and why.

See how it works

The quarter, as it happens

The moments every enterprise team knows.

  • Finance asks why spend changed last quarter

    History answers with a dated list of every budget change, who made it, and what it replaced.

  • A change needs sign-off

    The Optimizer proposes one specific change and routes it to an admin. Nothing runs before approval, and the approval is on the record.

  • Audit week

    Review ad copy and targeting as they stood on any date, with disapproval reasons and budget changes checked against approvals.

  • Regions report differently

    The same alerts and the same report template run in every market, so standards stay consistent and each market's data stays separate.

  • An agency partner hands over

    The change history stays with the account through agency and team changes, so the next owner starts with the record.

Two colleagues in shirts and ties standing before venetian blinds, one adjusting his tie

Optimizer

Approved before it runs.

Who proposed it, who approved it and when it ran, on one record.

OptimizerChange record

Example

APAC · Meta · Prospecting

Return the daily budget cap to $400

$500 / day$400 / day

Why
Since Monday's change, the month is pacing $2,300 over the $12,400 in Strategy.
Expected
Month-end spend back on plan.

On the record

  1. Proposed

    By the Optimizer, from a Trends finding

    Fri 7:30 AM

  2. Approved

    By Dana W., admin

    Fri 9:15 AM

  3. Applied

    Meta shows $400 / day. Written to History.

    Fri 9:16 AM

Example Optimizer change record: return the Prospecting daily budget cap in APAC from 500 to 400 dollars a day, with its rationale and expected effect. Proposed by the Optimizer on Friday at 7:30 AM, approved by Dana W. at 9:15 AM, applied at 9:16 AM and written to History.

Projected impact attached. Nothing executes without approval; the approved change logs back to the record.

Explore Action
An analyst in a grey jacket staring past a monitor in a dark office at night

Your own tools

The record, inside your own stack.

An authenticated, hosted MCP endpoint lets your tools query the record.

MCP endpointYour agent

Example

The question

Who changed Search / Brand spend last quarter?

  1. North America

    14 changes

    Latest Sep 24, by Sam R., agency partner

  2. EMEA

    9 changes

    Latest Sep 18, by an auto-applied recommendation

  3. APAC

    6 changes

    Latest Aug 30, by Maya T., APAC team

29 changes in 3 markets · Signed in with OAuth as Dana W.

Example query from a company's own analytics agent through the hosted MCP endpoint: who changed Search / Brand spend last quarter. The answer lists 14 changes in North America, 9 in EMEA and 6 in APAC, 29 in all, each market with its latest change and who made it. The call ran as Dana W., signed in with OAuth.

Your agents ask the record the way your team does. Every call runs with your own access, and the warehouse stays where it is.

Read data handling

What you use

The same record, pointed at your problem.

Time-stamped settings changes, and who made each one. No reconstruction from memory.

  • History Change history across every market, with before-and-after values and who made each change.
  • Reports Regional and global rundowns on one cadence, with the evidence attached for anyone who asks.
  • Optimizer Proposed changes routed for approval, executed with granted permissions, written back to History.
  • Attribution Salesforce and HubSpot closed revenue alongside spend, kept distinct from platform-reported conversions.

Setup

Start with one market.

Connect one market, read its record, then bring every other market onto the same one.

Free to start. Plans are on the pricing page.

See pricing
  1. Connect one market's ad accounts.

    Two years of performance history load on connection, and History keeps every settings change.

  2. Choose who approves.

    Approvals stay with admins. Nothing changes in an ad account until one of them approves it.

  3. Set the standard once.

    The same alerts and the same scheduled reports run in every market.

  4. Connect your own tools.

    Your tools sign in to the hosted MCP endpoint with OAuth or a personal API key.

  5. Add the next market.

    Each market joins the same record, in its own currency.

Questions

Questions enterprise teams ask.

How does this hold up when leadership asks what happened?

Open History, filter to the period, and read it. Every change has its time, its before and after, and who made it. Approved Optimizer actions carry their rationale.

Does anything change campaigns automatically at scale?

No. Every account change is proposed and approved before it runs, with the permissions you have granted. Execution results write back to the record.

Can we connect our own tools?

Yes. An authenticated, hosted MCP endpoint lets your tools query the record. Data handling, retention, and subprocessors are documented on the data-handling page.

We already have a data warehouse.

The warehouse stays. It answers what happened to the numbers; The Ad Spend keeps who changed what and what followed. The record is queryable through a hosted MCP endpoint so your existing stack can read it rather than replace it.

Three colleagues standing together; one holds a mug, one looks at a phone.

See the record on your own accounts.

Scope a single-market pilot.