Your Monday: Six Panels, Three Currencies, and the Campaign That Was Losing Money Since Thursday

The ritual has a shape, and if you run campaigns on multiple ad platforms you already know it.

You open the laptop at nine. Meta first, because Meta is where most of the money is. Then Google, because Google is where the weekend usually did something strange. Then TikTok, then Taboola, then Snapchat, then Outbrain — or whichever four to six of those you actually run. Six tabs, six sign-ins, six different ideas of what a week is.

Somewhere in the second half hour you find it: a campaign that has been underwater since Thursday afternoon. Not catastrophically. Just quietly, at maybe forty euro a day, in a currency that is not the one your P&L is kept in, on a product whose real margin lives in a spreadsheet nobody has opened since the last cost update.

This article is about where those ninety minutes go, and about which part of the problem tooling can actually take off your desk.

The part that gets misdiagnosed

There is a common instinct, when Monday is painful, to reach for the account layer. More profiles. Cleaner separation. Better fingerprints. A tidier way for four people to share forty ad accounts without emailing each other passwords.

That instinct is not wrong — it is just aimed at a different problem. Anti-detect browsers, Dolphin Anty and its neighbours included, are built for access and identity. Each profile carries its own fingerprint, so a site sees a separate device. Sessions do not leak into each other. A new buyer gets a profile instead of a password. That is genuinely hard engineering, and the tools that do it well are worth what they cost — we have written separately about what a fingerprint layer actually protects and what it never touches, and about the cloud side of that category.

But none of it touches Monday. The profile got you into the account on Thursday. What went wrong on Thursday happened inside the account, in a currency conversion, in an attribution window, in a cost-of-goods figure that changed when the supplier raised prices. A browser cannot see any of that, and has never claimed to.

Different layers of the same stack. It is worth being precise about which layer your Monday problem lives on, because buying more of the wrong one is the most expensive kind of tidy.

Where the ninety minutes actually go

1. Units, and the decimal that survives to the end of the sheet

Google Ads reports cost in micros — 1,000,000 to the dollar. Meta reports dollars with decimals. If whoever built your cross-platform spend sheet did not know that, you will never see the error: you will see a number, very confident, off by six orders of magnitude or corrected by a hard-coded divisor that someone will eventually forget to update.

Add the ad account currency, which is set per account and does not have to match your books. Add the exchange rate, which needs to be the rate on the day of the spend rather than the rate this morning, or a strong week in a weak currency quietly becomes a weak week. Add time zones: an ad account's day boundary is a property of the account, not of your calendar, and two accounts in the same campaign can disagree about when Thursday ended.

None of this is intellectually difficult. It is arithmetic. It is just arithmetic done six times, by hand, at nine on a Monday, under the specific pressure of knowing something is already bleeding.

2. The revenue is not where the spend is

This is the structural one.

Spend lives in the ad manager. Revenue — the revenue you actually believe, the one net of refunds — lives somewhere else: a tracker, a shop back office, a payment processor, a CRM. Affiliates keep it in Keitaro or Binom. Dropshippers keep it in Shopify or WooCommerce. Agencies keep it in whatever the client uses, which is frequently something self-hosted that no business-intelligence vendor will ever build a connector for.

So the reconciliation is a join, done by a human, across systems that were never designed to be joined. And because it is manual, it happens once a week. Which is the real answer to why did nobody notice on Friday: nobody noticed on Friday because the only place the two halves meet is a sheet that gets built on Mondays.

3. Nobody owns the weekend

Rules exist on most platforms. They are also per-platform, which means a rule that knows Meta is doing well cannot use that fact to take money off Google. Each engine sees its own island.

So the practical state of most weekends is: the campaigns that were fine on Friday keep running, and the ones that turned are still running too, because the thing that would have caught them is a person, and the person was not there.

4. Six tabs is six mental models

The tax nobody counts. Meta calls it an ad set; Google calls it an ad group; TikTok calls it an ad group and means something closer to an ad set; Taboola thinks in campaigns and site blocks. Objectives do not map cleanly. Bid strategies do not map at all. Switching between them costs a real, if unmeasured, amount of attention, and attention is what you are short of at the exact moment you need to make a budget decision. The same tax shows up inside a single platform once the account count grows, which is a problem with its own set of habits.

What actually removes the work

Three specific things, and it is worth naming them at the level of what they do rather than as features.

A rule that reads margin instead of ROAS

The metric that matters is the one that survives cost of goods, shipping, payment fees and refunds. On a product with a 22% gross margin, a 2.4 ROAS campaign and a 2.9 ROAS campaign can sit on opposite sides of break-even once returns are scaled back to the ad that produced them.

In Wevion, profit, profit_margin, true_roas and break_even_roas are available as rule conditions, not just as report columns — 19 universal metrics plus 14 Meta-only ones, 33 in total. A rule can therefore say pause when contribution margin goes negative over a rolling three-day window rather than pause when ROAS goes under 2. Those two rules disagree often, and the second one is the one that lets a Thursday problem live until Monday.

The margin figure is not a platform estimate. It is assembled from your commerce data and your tracker: cost of goods frozen at the order, shipping, processing fees, refunds scaled back to the ad ID. Ten tracker adapters ship with the platform — BeMob, Binom, ClickFlare, Everflow, ExoClick, Keitaro, RedTrack, TrafficManager, Voluum and a search feed adapter — which matters mostly because the self-hosted ones are exactly the ones larger reporting suites never integrate.

The engine evaluates on a fifteen-minute cadence. So does insight collection. That is the interval that decides whether "since Thursday" is a sentence you ever have to write again.

One daily budget across platforms, moved on a schedule

This is the piece that does the Monday morning reallocation without you.

You declare one daily budget. You put campaigns from different platforms into the same pool. You choose the optimization metric and the scoring window, and you set a floor and a ceiling per member so nothing gets starved or runaway. Every allocation cycle — eight hours by default — the pool redistributes toward what is performing.

Two details make it usable rather than alarming. It runs a simulation before it moves anything, so you can see the proposed allocation as a proposal. And it writes an allocation log afterwards, so the question why is this campaign on 340 instead of 200 has a recorded answer rather than a shrug.

Budget pools run across all six platforms.

An asymmetric brake

When you stop autonomy — because you are on a plane, because a client is nervous, because it is Black Friday and you want hands on the wheel — the sensible thing is not to stop everything.

So it does not. Stopping autonomy blocks activate, increase_budget_pct and relaunch, and deliberately leaves pause and decrease_budget running. The brake is one-directional: the system can still spend less on your behalf, it just cannot spend more. That asymmetry is written into the engine rather than being a setting you have to remember to configure, and it is the design decision I would look for first in any tool that is allowed to touch a live budget.

Alongside it: a per-action ceiling of EUR 50 and a per-team daily ceiling of EUR 200 on autonomous spend moves, on by default. Not a marketing number — a default you can raise, lower, or leave exactly where it is.

The numbers, said before the demo rather than after it

Every platform in this category rounds up. Here is the unrounded version, which is more useful to you and, frankly, more persuasive.

On Outbrain you connect, launch, measure, pause and activate campaigns, and change budgets by hand or through the assistant — but not from a rule. That is a real limit, it is in the product today, and you would rather hear it now than discover it in week three.

Two more, in the same spirit. Duplication is instant on Meta and arrives as a draft to review on the other five. And no tool, this one included, can promise an ad account will never be restricted — official API and OAuth reduce the surface, they do not eliminate it.

What Monday looks like when the layer is doing its job

Not empty. You still open the panel, because judgement is not automatable and you are being paid for judgement.

But the ninety minutes become twenty, and the shape of the twenty is different. You are not rebuilding the sheet; the sheet built itself on a fifteen-minute cadence over the weekend. You are not discovering the Thursday problem; it was paused on Thursday evening by a margin rule, and there is a line in the execution log saying so. You are not doing currency arithmetic; it was done at the day's rate, per account, by something that knows what a micro is.

What is left is the work you actually wanted: which angle to push, which audience is saturating, what to test this week. The part a browser profile was never going to hand you, and the part the reconciliation ritual was quietly eating.

If you already run an anti-detect browser

Keep it. Genuinely — this is not a migration argument, and there is nothing to move.

The profile gets you into the account. The OAuth connection is a separate, one-time thing that happens on the platform side, so the two live side by side without touching each other: one governs how you reach the account, the other governs what happens to the campaigns once you are in. Teams running Dolphin Anty, AdsPower or Multilogin for identity, and an API layer for campaign operations, are not running a redundant stack. They are running two halves that were designed for different problems.

If the Monday in this article is recognisable, the half you are missing is probably not the one you are already paying for — and the practical version of adding it is connecting the other five platforms without leaving the browser you already use.

---

Product capabilities described here were verified against the platform's own source on 2026-08-29: the six-platform enum, the margin metrics available as rule conditions, the asymmetric autonomy brake, the budget pool simulation and allocation log, the ten tracker adapters and the fifteen-minute evaluation cadence. Platform behaviour changes; check the current state when it matters to a decision.