Adset.ProAdset.ProKnowledge base
To app
Home/Meta / TikTok/Dev Token, Chrome Plugin or Antidetect Agent: How to Connect Meta to Adset.Pro

Dev Token, Chrome Plugin or Antidetect Agent: How to Connect Meta to Adset.Pro

Facebook spend without manual exports, ROI for every funnel, auto-rules that cut losing ad sets on their own. It all starts with one decision: how to connect your Meta ad accounts.

Adset.Pro offers three methods, each built for a different audience. A solo media buyer just starting out needs speed. A team with a hundred antidetect profiles needs scale without manual routine. Teams working through Business Manager need maximum automation and stability. Below we break down how the methods differ, what each can do, and how to pick yours in a couple of minutes.

Key point: every method gives you the same data: spend, impressions, clicks, the "ad account → campaign → ad set → ad" structure and creatives. The methods differ in how automated the process is and which tools you get on top of the data.

In short: which method to choose

  • You have Business Manager access and want "set it and forget it" → Dev Token. Fully automatic server sync, the most frequent updates, auto-rules that take action.

  • You want to see numbers today, with no setup in Meta → Chrome plugin. Install the extension, paste the token, click "Sync".

  • Your accounts live in an antidetect browser (AdsPower, Dolphin Anty, Multilogin, Vision) → antidetect agent. One archive for all profiles, server sync through the profile's proxy, auto-rules and the comment cleaner.

Comparison

Dev Token

Chrome plugin

Antidetect agent

How it works

The Adset.Pro server calls the Meta Marketing API with your System User token

The extension reads your logged-in Ads Manager session and sends the data to Adset.Pro

The agent takes the session from the antidetect profile; sync then runs on the server through that profile's proxy

What you need

Business Manager access, a Meta app and a System User token

Just Chrome and a Facebook login

An antidetect browser and a proxy on the profile

Time to start

15–30 minutes when issuing the token for the first time

5 minutes

10 minutes to install, then profiles connect themselves

Browser must stay open

No

Yes, the Ads Manager tab

Not all the time: sync runs on the server while the profile session is alive

How often spend updates

On schedule: 15 / 30 / 60 minutes (depends on your plan)

On click or on the plugin timer, while the browser is open

Automatically, every 30 minutes

Auto-rules: notifications

✅

✅

✅

Auto-rules: pause, start, budgets in live

✅

—

✅

Comment cleaner (Beta)

—

✅

✅

Proxy

Optional

Not needed, your browser does the work

Required: the agent picks it up from the profile

Scale

All ad accounts the System User can access

Ad accounts of one logged-in account

Dozens or hundreds of profiles with one archive

Best for

Teams and agencies on Business Manager

Solo buyers, tests, quick start

Teams on antidetect browsers and farms

You can mix methods: some ad accounts on a Dev Token, some on the plugin, some on the agent. All stats still land in one Meta section.

Dev Token: maximum automation

This is the official route through the Meta Marketing API. You issue a System User token in Business Manager once, paste it into a social profile, and Adset.Pro takes it from there: on schedule, on the server, without your browser.

Pros

  • Fully automatic. Sync runs on schedule even when your computer is off.

  • The most frequent sync. Up to every 15 minutes (depends on your plan). Today's spend is visible almost in real time.

  • Auto-rules that act. Rules pause, start and change budgets of campaigns, ad sets and ads on their own. If an ad account is connected through several profiles, rules pick the Dev Token first for changes.

  • Stability. A System User token doesn't care whether you got logged out in the browser.

  • All ad accounts with one token. You see every ad account the System User has access to.

Limitations

  • You need Business Manager access and permission to create a Meta app. Not suitable for accounts without a BM.

  • For auto-rules that act, the token needs the ads_management permission. To pull Business Manager info for ad accounts, it also needs business_management.

  • The comment cleaner is not available: it works through the profile's own session.

Best for: teams and agencies working through Business Manager who want to forget about manual sync.

👉 Guide: How to Get a Facebook Dev Token

Chrome plugin: start in 5 minutes

The "Adset.pro Cost Sync" extension takes data straight from your open Ads Manager tab. No Meta token, app or System User needed: if you can see an ad account in Ads Manager, the plugin can sync it.

Pros

  • The fastest start. Create a profile, generate a token, paste it into the extension. Five minutes later your spend is in Adset.Pro.

  • Nothing to set up in Meta. No Business Manager, app or System User required.

  • Precise sync scope. Pick ad accounts and campaigns: all, active only, active and paused, or hand-picked with checkboxes.

  • Comment cleaner (Beta) is available for plugin profiles.

Limitations

  • Works while the browser is open with a logged-in Ads Manager tab. Timer-based auto-sync also runs only while the browser is open.

  • Auto-rules only notify. The plugin can't pause campaigns or change budgets. If you need actions, connect the same ad account with a second profile on a Dev Token or the agent.

  • One browser, one Facebook account. Inconvenient for dozens of accounts.

Best for: solo media buyers, anyone trying out Adset.Pro, and those without Business Manager access.

👉 Guide: Pulling Costs from Facebook into Adset.Pro

Antidetect agent: scale without routine

The agent is built for those who keep accounts in an antidetect browser. It is installed once as a global extension and works in every antidetect profile. Supported: AdsPower, Dolphin Anty, Multilogin and Vision, plus regular Chrome.

When a profile starts, the agent figures out where it is running, sees the Facebook login and creates the social profile in Adset.Pro by itself, with the right traffic source and proxy. From then on, sync runs on the server, through that profile's proxy. Facebook sees the same IP and fingerprint as during normal work.

Pros

  • One archive for all profiles. No token per browser: one install instead of 30 manual connections for 30 profiles.

  • Profiles connect themselves. Pick a traffic source when downloading, and the agent adds new profiles without asking.

  • Server-side sync. No need to keep every profile open: Adset.Pro updates spend on its own every 30 minutes.

  • Auto-rules that act. Pause, start and budget changes go the same way as sync: through the profile's session and proxy.

  • Comment cleaner (Beta) under ad posts.

  • Team mode. A team lead or tech installs one team extension for the whole team, and each buyer picks themselves the first time a profile starts. Connections and profile transfers are logged.

  • Access control. The agent key is revoked with one button: all previously downloaded archives stop working.

Limitations

  • The profile must have a proxy. Without one, server sync and auto-rule actions don't run.

  • Sessions don't last forever. If Facebook logged the profile out or the session expired, open the profile in the antidetect browser and the agent will send a fresh one.

  • Sync no more than every 30 minutes. For near-real-time updates, the Dev Token is a better fit.

  • Vision requires its X-Token at download. AdsPower needs a key only if verification is enabled in its Local API.

Best for: teams and buyers running dozens of accounts from an antidetect browser who want to see spend and ROI and manage campaigns without manual routine.

👉 Guides: Facebook Spend Sync via the Antidetect Agent · Global installation of the agent · Team extension

Ready-made scenarios

"I work solo and want to see how it works."
Start with the plugin: in five minutes you'll see spend and ROI for your funnels. When you need auto-rules that act, add a Dev Token or the agent.

"We have 50+ profiles in AdsPower / Dolphin Anty."
The agent, no question. The team lead downloads the team extension, installs it in the antidetect browser once, and the whole team's profiles connect themselves.

"We work through our own Business Managers and want full automation."
Dev Token. One token, all ad accounts, sync every 15–30 minutes, auto-rules in live.

"The buyer uses the plugin, but the team lead wants auto-rules."
Connect the same ad account with a second profile on a Dev Token or the agent and enable auto-rule permission on it. The buyer keeps working as usual, and rules change campaigns through the "action" profile.

"Some accounts are in a BM, some in an antidetect browser."
Mix them: Dev Token for BM ad accounts, the agent for the antidetect browser. Stats still end up in one place.

What all methods have in common

For spend not just to sit in the Meta section but to match clicks, deposits and revenue in tracker reports, every method needs two things:

  1. A traffic source on the social profile.

  2. FB macro mapping for {{campaign.id}}, {{adset.id}}, {{ad.id}} in the source and in the click link.

Without the mapping, spend shows up in the Meta tables but won't reach the campaign report. Five minutes of setup gives you ROI for every ad.

What about the official Meta login (OAuth)?

Connecting through a Meta app is in development: it is marked "Soon" in the list of methods. Once it's live, you'll connect an ad account in a couple of clicks without issuing a token by hand. Follow the news in the Changelog.

FAQ

Can I change the method of an existing profile?
No, the method is chosen when the profile is created. To switch, create a new profile. Historical spend stays in analytics.

Is it secure?
Tokens and sessions are stored encrypted. The plugin token is shown once and can be reissued. The agent key is revoked with one button. The antidetect API key is not stored on the Adset.Pro server: it only goes into your archive.

Which method is the most resilient?
The Dev Token: it doesn't depend on the browser or login. The agent comes second: sync runs on the server, and the session occasionally needs a refresh by opening the profile. The plugin works while the browser is open.

Not sure where to start? Create a social profile in Meta → Social profiles and pick a method using the table above. Still unsure? Ask Adset AI right in your account: the assistant will suggest a method for your setup.