Dolphin + Wevion: The Profile Gets You In. Then the Work Starts.

There is a question that comes up in every conversation about using Dolphin with Wevion, and it is never the one people ask out loud. The question they ask is "which one is better". The question they mean is "how much of my setup do I have to tear down". The answer to the second one is none of it, and that is worth explaining properly, because the fear of migration keeps more teams on a half-working stack than any feature comparison ever has.

If you want the argument behind this rather than the procedure, it is in what Dolphin solves and what stays open. This piece is the procedure.

The Order of a Normal Day

Written out in sequence, so you can see where the handover actually happens.

1. Open the profile in Dolphin, as you always have. Fingerprint, proxy, cookies, session — untouched. If the profile is shared with a colleague, that stays true too.
2. Land in Business Manager inside that profile. This is the moment the browser layer has finished its job: the right identity is in the right account.
3. Connect the ad account once, by OAuth. A consent screen lists what is being requested, you approve it, and a scoped token is stored. This happens one time per ad account, not once per session.
4. Repeat for the other networks you buy on. Google, TikTok, Taboola, Snapchat and Outbrain each have their own connect flow, each takes minutes, and none of them requires a profile.
5. Connect the tracker and the store. This is the step most people skip and then miss, because it is the one that puts revenue and cost of goods next to the spend.
6. Stop opening the profile to check numbers. Open it to do the things only a browser can do. Everything else now has a panel.

Step 6 is the whole return on the exercise. The profile stops being the place you go to look and goes back to being the place you go to enter.

What OAuth Connects, and What It Leaves Alone

This is the part worth being precise about, because "connecting an account" sounds heavier than it is.

An OAuth connection issues a token scoped to the permissions you approved, held by a registered application. Wevion is a Meta Business Partner and talks to the Marketing API as a registered app — no cookies are copied, no session is replayed, and no browser profile is uploaded anywhere. Your campaigns, ad sets, creatives, audiences and pixels never leave the platform: they were always on Meta's servers, and they stay there. When you want the connection gone, you revoke it from the platform's own settings and nothing else in your setup notices.

Contrast that with what the browser layer holds, which is a genuinely different set of things: fingerprint configuration, cookies, local storage and session state, synced to Dolphin's cloud when the profile is closed rather than continuously. (Dolphin help centre, Profile Cloud Sync, checked 29 August 2026.) We wrote that mechanism up in detail in how Dolphin Anty cloud profiles work, and reading the two paragraphs side by side is the fastest way to see why neither tool can absorb the other.

Wevion is an ad operations platform that connects Meta, Google, TikTok, Taboola, Snapchat and Outbrain through their official APIs with OAuth, syncing insights roughly every fifteen minutes, so bulk launch, rules, budget allocation and contribution margin all sit in one panel instead of six.

Nothing Migrates. That Is the Whole Point.

Say it plainly, because it is the sentence that unblocks the decision: there is no migration.

• No profiles to export.
• No cookies to move.
• No campaign history to rebuild — it lives on the platform and the API reads it, including a historical backfill on all six networks.
• No parallel period where half the work is in one tool and half in the other.
• No cancellation of anything you are currently paying for, unless you decide later that you want to.

The realistic first week is: connect one ad account, connect the tracker, look at the numbers for a few days, and only then decide whether to bring the rest across. If the panel is not telling you something the browser could not, you have lost an hour.

Day Two: What Is Different on the Panel

Once the accounts are connected, four things become possible that were structurally impossible from inside a tab.

Bulk launch from a grid. One row per campaign, the platform as a column, published across all six. This is the difference between a launch afternoon and a launch coffee — the mechanics are in launching many campaigns at once.

Rules on a cadence rather than on your attention. The engine evaluates every fifteen minutes, day and night. It carries a detail worth knowing: when you hit the stop switch, it halts activations, budget increases and relaunch, but it deliberately keeps running pauses and budget decreases. The brakes stay live when the accelerator is cut.

One daily budget across platforms. A budget pool holds N campaigns from N networks under a single daily figure and redistributes toward performance every eight hours by default, inside per-member floors and ceilings, with a simulation before the move and an allocation log after it.

Margin instead of a revenue proxy. With the tracker and store connected, contribution margin is computed down to the single ad — spend, gross and net revenue, refunds, cost of goods, shipping, processing fees, contribution profit, true ROAS and break-even ROAS. There is no tax column, so this is contribution margin rather than net profit. A rule can then act on profit_margin or break_even_roas directly.

The Numbers Before the Demo, Not After

(Wevion internal data, August 2026, read from the platform registry and the rule worker.)

Publishing the limits in the same table as the strengths is not a rhetorical move. It is what makes the strengths believable, and it is cheaper than having a prospect find the fourth row on their own during a trial.

What Stays in Dolphin, and Should

Three jobs, permanently:

• Identity. One account, one device signature, no cross-contamination. Nothing at the API layer provides this, and nothing at the API layer should.
• Sites with no API. Panels, networks and back offices that exist only as websites. A session is the only way in, and that is exactly what a profile is for.
• Handover without passwords. Sharing a working profile with a colleague, or transferring it outright, beats pasting credentials into a chat window. The roles and the share-versus-transfer distinction are built for that. (Dolphin help centre, Teamwork, checked 29 August 2026.)

On our side the equivalent control is a different shape: organisation, team, workspace and access groups, with an audit log you can question in plain language about who changed which budget and when. That is account-level accountability rather than device-level identity — the same instinct applied one layer up, and the way to set it up is in agency team roles for ad accounts.

One Agency Week, Concretely

A team running client accounts through profiles opens Monday the way it always has: profile, Business Manager, eyes on the account. What changes is everything after that first look.

The Monday reconciliation across networks is already done, because the sync has been running since Friday. The campaign that went under break-even on Saturday was paused by a rule at 03:40, and the log says which condition fired. Tuesday's launch of nine campaigns across three platforms is a grid, not nine sequences of clicks. And when a client asks why their budget is different from last week, the answer is an allocation log entry, not a reconstruction. The example is written out at length in an in-house team running six platforms in one workspace.

The profile did not disappear from that week. It just stopped being asked to answer questions it was never built to answer.

Key Takeaways

• There is no migration: OAuth connects an account, it does not move one. Profiles, cookies and campaign history all stay exactly where they are.
• The handover point is precise — the browser gets you into the account, the API layer takes over once you are inside.
• Connect the tracker and the store on day one, not month two. Margin is the reason the panel is worth having.
• Know the counts before the demo: six for launch and sync, five for rule-issued budget changes, four for cross-network conditions, Meta only for relaunch and rollback.
• Keep the profile layer for identity, for handover, and for every service that never published an API.

Want to test the second half without touching the first? Start on the free plan, connect one ad account from inside the profile you already have open, and give it a week.