You Run Meta Through Dolphin. Here's How Google, TikTok, Taboola, Snapchat and Outbrain Join the Same Screen.

Most people arrive at the question of how to manage multiple ad platforms in one place from a search that sounds like alternative to the thing I already use. That framing is usually wrong, and it is worth saying why before anything else.

If Meta already runs the way you want it to run — profiles in an anti-detect browser, proxies configured, a team that knows the routine — the thing you are actually missing is not a replacement for any of that. It is the other five platforms, which are currently sitting in five separate tabs with five separate logins and one shared spreadsheet that gets rebuilt on Mondays.

So this is a connection guide. Nothing gets migrated, nothing gets turned off, and Dolphin stays exactly where it is.

What does not change

Worth being explicit, because this is the objection that stops most of these conversations before they start.

Your profiles stay. Anti-detect profiles, fingerprints, proxies, the whole identity layer — untouched. Nothing here reads them, replaces them or asks you to export them.

Your Meta routine stays if you want it to. You can connect Meta through the official API as well, and most people eventually do, but it is not a precondition for adding the other five. The platforms are independent connections.

Nothing gets copied anywhere. A platform connection is a token, not a data migration. There is no import step, no historical export to prepare, no cutover date.

The two layers genuinely do different jobs. A browser profile governs how you reach an account. An API connection governs what happens to the campaigns once you are in. Different layers of the same stack, which is exactly why running both is normal rather than redundant — what a fingerprint layer does and does not touch covers that boundary in detail, and there is a head-to-head write-up if you want the layers side by side.

The five, one at a time

Here is the part that is usually written as "connect in one click" and is not, in fact, one click everywhere. The handshake differs by platform, and knowing which is which in advance saves an afternoon.

Google Ads

How it connects: OAuth redirect. You approve on Google's own screen and come back with a refresh token.

What you need in hand: a Google account with access to the ad accounts you want, and — this is the one that catches people — the manager account structure sorted out first. If your accounts sit under a manager account, connect at the level that actually owns them.

Day one: account sync pulls thirty days of history by default, so the panel has something in it immediately. Longer backfill can be requested afterwards.

Worth knowing: Google reports cost in micros — 1,000,000 to the dollar. That conversion is handled on ingestion, which sounds trivial and is the single most common source of silently wrong cross-platform spend figures in home-made sheets.

What the rules engine can do here: budget changes, pause and activate at campaign level, and CPC changes at ad group level. Google is one of the two platforms where bid changes are supported.

TikTok Ads

How it connects: OAuth code exchange. Redirect, approve, return.

What you need in hand: the advertiser accounts you want visible must be accessible to the account you authorize with. TikTok's business centre structure matters here in the same way Google's manager account does.

Day one: thirty days of history by default on sync.

What the rules engine can do here: budget changes at campaign and ad set level, and pause/activate down to ad set and ad — TikTok is one of only three platforms where that granularity exists, alongside Meta and Snapchat.

Taboola

How it connects: client-credentials flow. There is no OAuth redirect — you supply credentials issued by Taboola rather than clicking through an approval screen. If you are expecting a redirect and do not get one, nothing is broken.

What you need in hand: the API credentials from your Taboola account team. This is the step that is not instant, because it depends on someone at Taboola rather than on you.

Day one: thirty days of history by default on sync.

What the rules engine can do here: budget changes at ad set level, pause and activate at campaign level. Taboola participates in cross-platform comparison conditions — it is one of the four that do.

Snapchat

How it connects: OAuth redirect.

What you need in hand: access to the organisation that owns the ad accounts.

Day one: thirty days of history by default on sync.

Worth knowing: Snapchat does not always return a refresh token when refreshing an existing one. That is a documented quirk of their API and it is handled — worth mentioning only because if you have ever built your own integration against Snapchat, you have met it and you know why it matters.

What the rules engine can do here: budget changes at campaign and ad set level, and pause/activate down to ad set and ad. Snapchat is the third of the three platforms with that depth.

Outbrain — now part of Teads

How it connects: not OAuth. You paste a token. The connection is verified by calling the marketers endpoint and reading back the marketer list, so you know within a second whether the token works.

What you need in hand: the token from your Outbrain account.

What the rules engine can do here — and this is the honest limit: you connect, launch, measure, pause and activate campaigns, and you change budgets by hand or through the assistant. A rule cannot move an Outbrain budget. There is no Outbrain branch in the budget action path, and Outbrain does not appear in cross-platform comparison conditions either.

I would rather you read that here than find it in week three. It is a real gap, it is in the product today, and everything else about Outbrain works.

What day two looks like

Once the connections are in, the things that were previously six separate rituals collapse into one screen.

Insight collection runs on a fifteen-minute cadence across all six platforms. Not on a nightly job, and not when you press refresh.

Cross-channel analytics — channel mix, comparison matrix, top campaigns, budget recommendation, unified export — work across the connected set with no flag to switch on.

Contribution margin sits next to spend. This is the part that changes what you can decide rather than just what you can see. Cost of goods, shipping, processing fees and refunds are scaled back to the campaign, ad set and individual ad, sourced from your commerce data and your tracker rather than from a platform estimate. Ten tracker adapters ship with it — BeMob, Binom, ClickFlare, Everflow, ExoClick, Keitaro, RedTrack, TrafficManager, Voluum and a search feed adapter — which matters mainly because the self-hosted ones are precisely the ones larger reporting suites will never build a connector for.

Rules can read that margin. profit, profit_margin, true_roas and break_even_roas are available as rule conditions, not merely as report columns: 19 universal metrics plus 14 Meta-only ones, 33 in all. A rule that pauses on negative contribution margin behaves very differently from one that pauses on ROAS, and the difference shows up on exactly the campaigns you care about.

Budget pools run across all six. One daily budget, campaigns from different platforms inside it, redistribution every eight hours by default, with a simulation before the move and an allocation log after it.

Creative fatigue scoring runs across all six, with the platform carried as a column in the score, and the baseline taken from the ad's own first days of life rather than from a category average.

The unrounded table

Everyone in this category says "all platforms". Here is the version with the exceptions in it, which is more useful and, I think, more convincing.

Two more that belong in the same list. Duplication is instant on Meta and arrives as a draft to review on the other five — a deliberate choice, because a deep copy across platforms with different object models is a thing you want to look at before it goes live. And no tool, this one included, can guarantee an ad account will never be restricted. Official API and OAuth reduce the surface; they do not remove it.

A realistic sequence

If you want the order that causes the fewest problems:

1. Connect the one platform where you already know the numbers cold. Usually Google or TikTok. Let thirty days of history land, then check the totals against what that platform's own interface says. If they disagree, find out why before adding anything else. Nine times out of ten it is a time zone or an attribution window, and it is much easier to diagnose with one platform connected than with five.
2. Connect the rest of the OAuth ones. TikTok, Snapchat, Google — whichever are left. These are the fast ones.
3. Start the Taboola credentials request early, because it depends on someone else's response time rather than yours.
4. Add Outbrain last, with its limit already understood: everything except rule-driven budget changes.
5. Only then build a rule, and build it on margin rather than on ROAS. The reconciliation problem those rules are meant to end is described at length in the Monday-morning piece. A rule built before the revenue side is connected is a rule reading half the picture, and half a picture is worse than none because it feels authoritative.

And Dolphin stays where it is

Nothing in that sequence touches your profiles.

The identity layer keeps doing what it is good at: isolated profiles, coherent fingerprints, team access without passing passwords around, many accounts on one machine. The API layer does what it is good at: six platforms in one panel, rules on a fifteen-minute cadence, contribution margin next to spend, budget moving on a schedule with a log.

The profile gets you into the account. Then the work starts — and the work is where the other five platforms have been waiting.

---

Connection mechanics and platform coverage described here were verified against the platform's own source on 2026-08-29: the six-platform enum, the per-platform auth providers including Taboola's client-credentials flow and Outbrain's token validation path, the thirty-day default backfill on Google, TikTok, Taboola and Snapchat, the fifteen-minute collection cadence, and the rules-engine action coverage per platform. Third-party API requirements change; check current vendor documentation before planning a rollout.