The Dolphin{cloud} Browser Extension: What It Adds, and Where It Stops

If you search for "dolphin cloud extension", you get results about Dolphin Cloud in general and almost nothing about the extension itself. That is a small gap in the internet, and it is easy to close.

The extension is a real, specific, documented component with one job. It is also the clearest illustration in this whole product family of where browser-level tooling ends and server-level tooling begins — which is a useful thing to understand whatever you end up buying.

---

What it is

Dolphin ships two products. Dolphin{anty} is an anti-detect browser: it holds browser profiles, each with its own fingerprint and proxy, and inside those profiles live your Facebook logins. Dolphin{cloud} is a separate cloud panel that works on Facebook ad accounts in bulk without opening Ads Manager. (If those two are still blurry, start with the difference between Dolphin{anty} and Dolphin{cloud}.)

The extension is the handshake between them.

From Dolphin's own help centre, read 29 August 2026:

And on what it moves:

Source: docs.dolphin-anty.com/en/dolphin-cloud-and-parser/dolphin-anty-integration-with-dolphin-cloud.

That is the whole job. It is a courier. It takes an account that currently exists as a logged-in session inside a browser profile and hands it to a panel that can act on it at volume.

---

Where it comes from, and why yours might be missing

This is the single most common source of confusion, and the answer is one sentence: it depends on the profile type.

The extension is attached automatically to profiles created with the "FB" type. Create a profile with a different type and the extension is not there. The documentation covers this case explicitly — it publishes a link to install the extension manually, and points at its standard instructions for adding an extension to a profile.

Two practical consequences worth knowing before you have thirty profiles:

If you create profiles by hand, pick the type at creation. Retro-fitting is possible but it is thirty manual steps instead of zero.

If you create profiles through the API, the profile type is a field in the creation payload, alongside platform, browserType, useragent and the rest of the fingerprint description. Set it in your template and the problem never occurs. The Dolphin{anty} API article walks the creation call in detail.

---

The token setup, in two fields

The extension needs to know which Dolphin{cloud} account to hand things to. That is the token.

In Dolphin{cloud}: log in, open Settings from the left menu, and copy the value in the field labelled "Access token to your Dolphin".

In Dolphin{anty}: open Settings. Near the top there is a block called "Integration with Dolphin". Paste the token there and save.

The reason to do it in the browser's own settings rather than in each extension instance is the obvious one: you do it once, and every "FB"-type profile inherits it. Doing it per profile is the version of this that eats an afternoon.

(Both steps as documented on docs.dolphin-anty.com, read 29 August 2026. Interfaces move; open the help centre the day you set this up.)

---

What happens after the handover

The extension's job ends the moment the account lands in Dolphin{cloud}. It is worth knowing what it lands into, because that is the whole reason for the trip.

Dolphin{cloud} describes itself as a "Multitool for FB" and works on Facebook advertising objects in bulk (cloud.dolphin.tech, read 29 August 2026). Once an account is inside, the panel offers:

Bulk campaign creation. Create, duplicate and launch ad sets across any number of accounts, against objectives their page lists as clicks, conversions, target views, fan page promotion, app installs and in-app events, with deep links. Their own phrasing for this is automated ad creation, or "auto-fill", and their pricing table places it on the Pro tier.

Creative uniqueness at launch. The page states that creatives are uniqued automatically during the launch, also a Pro-tier item on their comparison table.

Business Manager and fan page plumbing. Creating BMs and invite links, confirming BM email, creating pixels and linking them to accounts, creating and auto-publishing fan pages, uploading avatars, sharing and switching pages, linking and unlinking Instagram.

Account and billing operations. Card binding in three ways, changing billing country, setting spending limits, moving accounts between teammates, renaming and deactivating accounts.

Auto-rules and comment moderation. Rules on accounts and rules on campaigns, plus filtering, hiding or deleting comments under ads by stop-word or by hand.

Tracker integrations. Keitaro and Binom, with export of unique clicks and GEO to Keitaro, import from either, and postbacks from trackers and servers to attribute revenue to leads.

Read that list and the shape of the trip becomes obvious: the extension carries a credential from a browser profile into a panel that can act on it hundreds of times. It is a small component doing a load-bearing job, and its scope is exactly one hop wide.

---

Four things that go wrong, and what each one means

The extension is not in the profile. Almost always the profile type. It is attached automatically only to "FB"-type profiles; anything else needs the manual install. If it keeps happening, the fault is in your profile template, not in the extension.

The token field is empty in every profile. You pasted the token into one extension instance instead of into the browser's own Settings. The "Integration with Dolphin" block in Dolphin{anty} Settings is what propagates it; per-profile entry is the version that has to be repeated forever.

Nothing transfers and there is no error. Check that Dolphin{cloud} is a live, authorised session on your side — the token is issued from a logged-in Cloud account, and a token copied from a session that has since ended is a string that looks correct and does nothing.

It worked last month and now there is no extension anywhere. Look at the Dolphin{anty} homepage feature list before assuming a fault: the newer under-the-hood transfer is advertised as replacing the extension route entirely, and a build that has it may simply not install the old component any more.

None of these are exotic. They are all the same failure in different clothes — a two-product handshake has two sides, and the side that is misconfigured is rarely the side you are looking at.

---

The newer path, and a small divergence worth flagging

There is a wrinkle, and it is better to name it than to pretend the documentation is monolithic.

The Dolphin{anty} homepage advertises a feature flagged as new: "Integration with dolphin{cloud} — Transfer profiles to Dolphin{cloud} in a couple of clicks", with the explicit note "No more need to manually transfer profiles or use extensions. Profile transfer to Dolphin{cloud} works under the hood." (dolphin-anty.com, read 29 August 2026.)

The help centre article still describes the extension route in full.

Both pages were live on the same day. The most likely reading is that the newer transfer is being rolled out and the docs have not caught up, which is normal for a product that ships fast. The practical advice: open your own build, look for the "Integration with Dolphin" block, and see which mechanism it offers you before you plan a workflow around either.

---

Where it stops — and this is the interesting part

Nothing below is a complaint about the extension. It is a description of what an extension is, and it applies equally to every browser extension ever written, ours included if we had one.

An extension runs inside a tab. It needs a browser process. It needs that browser to be open, on a machine that is powered on, with the profile launched. Close the laptop and the extension is not doing anything, because there is nothing for it to run inside.

An extension sees one page at a time. It has the scope the browser gives it: the document in front of it, and whatever the profile can reach. It does not have a warehouse of historical spend, and it has no reason to — that is not what page-level code is for.

An extension does not aggregate. Six ad platforms in three currencies do not add up inside a browser tab. That summation happens somewhere that can hold state and run on a schedule.

Which gives you the actual dividing line in this market, and it is not about quality:

Those are two different pieces of infrastructure for two different problems, and neither one is a worse version of the other.

---

What "on a schedule" means, with real numbers

Since we are being specific: cadence is a published, checkable property of rules engines, and it is worth knowing the range before anyone quotes you a number.

TheOptimizer — a direct competitor of ours, and the fastest published cadence we could verify — states in its own FAQ that rules "can be configured to execute as frequently as every 10 minutes", with available intervals of every 10, 20 or 30 minutes, then hourly steps, then daily and weekly (theoptimizer.io, read 29 August 2026).

Wevion runs its automation rules on a 15-minute cadence. That is five minutes slower than theirs, we know it, and we would rather you heard it here than found it in a demo.

Dolphin{cloud} offers auto-rules on accounts and on campaigns across its four paid tiers, plus automated review of rejected ads on the top two (cloud.dolphin.tech, read 29 August 2026). Its rules operate on Facebook, which is the platform it covers.

The point of listing all three is that "does it run without me" is a real question with a real answer per product, and the extension is simply not in this category. It was never trying to be.

---

What sits on the server side of the line

This is the part where we describe our own product, so you can weigh it.

Wevion talks to ad platforms through their official APIs with OAuth — no cookies, no browser sessions, no profile to keep alive. What that buys, in the vocabulary of this article:

It runs when you do not. The rules engine evaluates every 15 minutes on the server. Your machine's state is irrelevant.

Six platforms, connected the same way. Meta, Google, TikTok, Taboola, Snapchat and Outbrain — connect, launch, sync and measure across all six.

And the numbers underneath, stated up front. Budget moves driven by rules run on five of them (Outbrain has no branch). Rules that compare one platform against another run on four: Meta, Google, TikTok, Taboola. Pause and activate at ad-set and ad level: three — Meta, TikTok, Snapchat. Launch rollback and relaunch: Meta only.

Rules that read margin. 33 condition metrics, and among them profit, profit_margin, true_roas and break_even_roas. A rule can act on contribution margin rather than on the platform's own return figure.

An asymmetric brake. Pull the handle on autonomy and activations, budget increases and relaunches stop — while pause and budget decrease keep running. The direction that can only reduce exposure stays available.

Budget Pools. One daily budget across campaigns from several platforms, redistributed every eight hours, with a simulation before it acts and a log after.

Ten tracker adapters — BeMob, Binom, ClickFlare, Everflow, ExoClick, Keitaro, RedTrack, SearchFeed, TrafficManager, Voluum — so the revenue that lives in your tracker can sit next to the spend that lives in the ad platform.

And the limits, in the same breath:

• No creative uniqueization at launch. Dolphin{cloud} advertises it on its Pro tier. We do not have it.
• Launch rollback is Meta-only. The other five platforms have no undo for a bulk launch.
• No identity layer, ever. No fingerprints, no proxies, no profiles. If your problem is keeping accounts apart on one machine, an anti-detect browser is the answer and we are not it.
• Seats on the entry plan are our harshest pricing step — on Starter, additional seats cannot be purchased at all.

---

The practical summary

• The Dolphin{cloud} extension is a courier between Dolphin{anty} profiles and the Dolphin{cloud} panel. It moves Facebook accounts. That is its job and it does it.
• It appears automatically only in profiles created with the "FB" type; otherwise install it manually or fix the profile template.
• The token comes from Cloud → Settings → "Access token to your Dolphin" and goes into Anty → Settings → "Integration with Dolphin".
• A newer transfer without the extension is advertised on the Anty homepage; check your own build.
• Anything that must keep watching a campaign after you close the browser belongs on a server, not in a tab. That is not a shortcoming of the extension — it is the shape of the two layers.

---

Next steps

• Confused about which Dolphin you have: Dolphin{anty} vs Dolphin{cloud}, side by side.
• Automating profile creation: what the Dolphin{anty} API can and cannot reach.
• Want the layer that runs while the browser is closed: try Wevion on the free plan. It is an OAuth authorisation, not a migration — Dolphin stays exactly where it is.