Evidence first
An insight links to the records it used and the time they were last updated.

The auditor looks for drops, anomalies, high frequency, missing new creatives and misallocated spend, and explains each finding with figures you can open and check.

Floating cards and figures are examples on sample data, not a customer account.
Sample data, fictional brand. This is how AI insights shows a figure: the value, where it came from, the formula behind it and when it was last updated.
Rule: every number shows its source, formula and update time. A missing source reads "not measured", never 0.
One of four areas of the product, sharing the same client record, roles and log.
An insight links to the records it used and the time they were last updated.

Comments, documents and web pages are read as data and never followed as instructions.
A suggested change goes through preview and approval like any other change.
Connections start read-only. Writing is switched on per account, only after you grant the rights.
Lines draw as you scroll. Platforms on the left are read-only first, AI insights sits on the one client record, and each output keeps its receipt.
Sources are read first, the numbers are stored once per client, and every output shows its source, formula and update time.
The same four moves apply to every module in this area.
From first connection to the number a client sees.




Daily metric snapshots, rules and tasks form the evidence.

Scheduled checks compare against history with a minimum sample.

Each finding states what changed, by how much and where to look.

Open a task or a proposed change with the evidence attached.

Photos are stock images that show the kind of business this is built for. They are examples, not customers.




Stock photos and example labels, not customers.
General practice for this kind of work, not a claim about any one tool.
A summary is a starting point written from numbers that may be incomplete. Open the source rows and check the figure before it reaches a client.
A question like 'what is going on?' gets a confident answer that may not fit the data. Name the metric, the period, the segment and the decision the answer will feed.
Without a record, nobody can tell later whether the insight helped. Log the insight, the change it caused and the result read back after the change.
Your ticks stay in this browser only.
Connections are read-only first and go live only after the platform access is approved.
Built: the connector exists in the product and goes live per account once access is granted. Planned: not built yet.
Teams often use tools such as Madgicx for this. Our comparison pages are drafts being verified.
Modules that share this client record, these roles and this log.
Short guides on the numbers and routines behind this module.
No. An insight can propose a change, and the change then needs a preview, an approval, a single send, a read-back and a log entry.
The finding says what is missing and does not guess. A disconnected source is shown as not measured.
Models are swappable behind an adapter, so the product is not tied to one provider.
We open one agency at a time, with your own accounts connected read-only first.