A browser profile is an isolated Chrome instance inside AdsPower, with its own cookies, fingerprint, and IP. In AdFlow, each profile has a 1:1 relationship with a Meta Business Manager.
How profiles appear in AdFlow
AdFlow doesn’t create profiles — it reads profiles that exist in AdsPower via local API. For a profile to appear in /profiles:
- AdsPower must be open on your desktop
- The AdsPower integration must be active at /integrations/adspower
- The profile must have been created in AdsPower and linked to the correct BM
After setting up the integration, click Sync to import the list of available profiles.
Profile status
| Status | Meaning |
|---|---|
| Active | Green proxy, recent last login, no alerts |
| No proxy | No residential proxy linked |
| Slow | Yellow proxy — high latency |
| Blocked | Meta or AdsPower flagged an issue with the account |
A blocked profile doesn’t stop already-published campaigns in Meta — but prevents new publications through that profile.
Profile health checklist
Before publishing a campaign through a profile, confirm:
- Linked proxy with Active (green) status
- Last login in AdsPower less than 30 days ago
- No block alerts in AdFlow or in Meta Business Manager
- Linked BM is the correct one for the campaign
When a profile gets blocked
Don’t access the blocked profile from an IP different than its history. Meta detects IP inconsistency as suspicious access. Wait 24–48h before taking any action. If the block persists beyond 72h, create a new profile with a clean IP.