Devices and identities together
Review device names, versions, Facebook identities and recent connections. Select a browser by actual availability. Plugin allowances apply per user according to the subscription.
Open cloud workspaceProducts / NADSX
NadsX Cloud control and remote devices
Connect execution browsers to one web workspace for Facebook identities, ad assets and remote tasks, with a clear source and result for each operation.
Open cloud workspaceInstall the NadsX Cloud execution extension- Web management workspace
Choose scope · Submit tasks · Review receipts
- NadsX Cloud
Coordinate tasks and store business records
- Remote execution browsers
NadsX Cloud extension + Facebook session
NadsX Cloud
Bring separate browsers into one workflow
Use defined business actions while preserving each identity’s and device’s actual permissions.
Assets across sources
Shared ad accounts are deduplicated by ID while retaining identity and browser sources. Check permissions and sync time for accounts, BMs, Pages and Pixels.
Open cloud workspaceAd creation and reusable settings
Create or update ads through selected devices and reuse cloud presets, audience templates, media and copy. Batch creation currently supports on-Facebook lead forms; new objects default to paused.
Open cloud workspaceContinuous lead-to-group monitoring
Connect leads, WhatsApp join evidence and ad spend. The server coordinates monitoring. Automatic pauses or budget increases require separate activation, complete data, cooldowns and allowances.
Open cloud workspaceRemote reports and team spend
Bind report settings to an execution source and review account-level history and downloads. Administrators see authorised team spend; review each currency separately.
Open cloud workspaceReceipts and unresolved operations
Track the original request and its results. A timeout is not proof of failure. Verify unknown writes in Facebook rather than resending through a different device.
Open cloud workspaceDistributed extension connections
One workspace, browsers in different places
Install the cloud extension on office, operator or remote devices and choose sources from the web. Each execution browser keeps its own Facebook session.
Manage and execute separately
Manage from a web workspace on any computer. The selected execution browser carries out remote operations.
Separate identities and permissions
Different browsers on one computer can connect separately. Asset access still depends on each Facebook identity’s permissions.
Results from the original source
The cloud coordinates tasks and the original extension returns results. Verify unresolved operations before resending through another device.
Distributed extension connection diagram
Web cloud workspace
Choose sources · Submit tasks · Review results
NadsX Cloud
Task coordination · Asset directory · Receipts
Tasks go to the selected sourceResults return from the execution browser
- Browser 01
Office computer
NadsX Cloud extensionFacebook identity AAd accounts · BMs · Pages
- Browser 02
Operator computer
NadsX Cloud extensionFacebook identity BAd accounts · BMs · Pages
- Browser 03
Remote device
NadsX Cloud extensionFacebook identity CAd accounts · BMs · Pages
Check online, identity and executable separately
The device directory shows connection and identity information; every operation still requires current business conditions.
- 01
Device online
The device recently connected to NadsX. This does not prove a usable Facebook session or permission for every action.
- 02
Identity reported
The last read Facebook identity is shown. During checks or read failures, an old name does not prove the current session is valid.
- 03
Currently executable
Identity, login, extension capabilities, allowance and asset access meet this operation’s requirements. Submission and execution still recheck them.
What continues after the web workspace closes?
Management and execution are separate, but tasks advance differently. Every Facebook step still depends on its execution browser and services remaining available.
| Task | Web page requirement | Execution conditions |
|---|---|---|
| Continuous lead-to-group monitoring | The management page may close after activation. | The server coordinates monitoring; reads and actions need the original device session and available WhatsApp services. |
| Submitted bulk-pause batches | Close the dialog or reload the web and return to the original batch. | Administrator only. Pauses enabled campaigns in the scanned scope and needs online execution devices. |
| Batch ad creation | Keep the web open for subsequent scheduling. | Selected devices and sessions must stay online. Check steps already sent; closing the page does not revoke them. |
| Remote ad reports | Supported background single-file runs can continue; merging needs the original report page open. | The execution device and authorisation must remain valid. Check download location and historical file availability against settings and source. |
| Operations tool analysis | Start refresh, analysis or checks manually. Supported timed refresh runs only while the page is visible. | Reads selected remote sources. Suggestions are not continuous background monitoring or automatic ad updates. |
Product facts
- Suitable for
- Teams and individual operators managing multiple Facebook identities, browser environments or media buyer devices.
- Before you start
- A NadsX Cloud account with active access. Execution devices need running browsers, extensions, network access and usable Facebook sessions with asset permissions. The web workspace can run on a separate computer.
- Scope and limits
- Cloud control does not host or replace Facebook login or grant asset permissions. Online, reported identity and executable are separate states. Offline asset directories can remain visible; each task has its own web and device availability requirements.
Questions about this feature
Does the management computer need an extension?
Remote management does not. Install NadsX Cloud in execution browsers and sign in to the product and Facebook separately. Public ad collection, local collection sync and local extension downloads still require the extension in that browser.
Will tasks continue after closing the workspace or execution computer?
Continuous lead-to-group monitoring, submitted bulk-pause batches and reports that support background execution can continue after the web closes while their execution browsers and services remain available. Batch creation needs the web open for subsequent scheduling. A closed execution computer cannot keep reading or writing.
Are plugin allowances counted per team or per user?
Each signed-in plugin user has a separate allowance, including administrators and each media buyer, as specified by the subscription. Temporarily offline devices still occupy a slot. Sign-out, revocation or session expiry releases it while preserving historical assets.
Can an online device operate every synced asset?
No. Online describes the product connection. Operations also require a usable Facebook session, asset permissions and an eligible source. Historical entries can come from offline devices. Check unknown writes before retrying; do not resend them through another device.
NadsX product documentationContent reviewed
How it fits into your workflow
Know where a task runs and what actually happened.
- 01
Install NadsX Cloud in the execution browser, sign in to the product and Facebook separately, and open Ads Manager.
- 02
Verify the device, Facebook identity and access in the cloud workspace; sync assets and explicitly select the execution source.
- 03
Confirm scope before submitting and review receipts afterward. Recover sessions in the original browser and verify unknown operations first.
Connected capabilities
NADSX / Your next step
Start with your first execution device.
Install and sign in to NadsX Cloud in the execution browser, then sync assets in the cloud workspace. Open the workspace from another computer if needed.