Sensing and control belong in one app
Traffic monitoring and paid-spend control across an estate of sites, built as one application over one schema rather than two dashboards that disagree.
Client: HW Legacy Group.
Once you run more than three web properties you need to know what each is doing, and you need a way to stop spending money on the ones that are not working. Those are usually two products. Here they are tabs over one schema.
The reason is that a sensing dashboard and a control panel built separately will eventually disagree about the state of the world, and when they do, the one holding the credit card wins the argument by spending. One schema means the number you are looking at and the number the spend rule acts on are the same number.
Spend rules carry a hard ceiling set outside the application, in the provider's own console, and the application is not permitted to raise it. An automated system that can increase its own budget is not a control, it is a hazard with a dashboard. The ceiling is the real constraint; the app only moves within it.