Six concepts that appear everywhere in AdFlow. Understanding each one prevents the most common operational mistakes.
Browser profile
An isolated Chrome instance inside AdsPower, with its own cookies, fingerprint, and IP — invisible to all other profiles. In AdFlow, each profile has a 1:1 relationship with a Meta Business Manager.
Isolation depends on three layers: AdsPower browser (cookies + fingerprint) + linked residential proxy (IP) + associated Meta account. If any layer fails, Meta can associate accounts.
Campaign in AdFlow
In AdFlow, “campaign” = Ad Set in Meta Ads Manager. Meta’s structure: Campaign (objective) → Ad Set (audience + budget + placement) → Ad (creative). AdFlow manages at the Ad Set level.
Proxy status
Every proxy has a traffic light updated on each connectivity test: Active (green, ≤500ms), Slow (yellow, >500ms), Failed (red, no connection), Not tested (gray). Slow doesn’t mean unusable — residential proxies fluctuate at peak hours.
Budget vs Bid strategy
Budget = spending cap (daily or lifetime for the Ad Set). Bid strategy = how Meta competes in auctions (Lowest Cost, Bid Cap, Cost Cap). Independent settings. Confusing them is the most common cause of Ad Sets with zero delivery.
Audit Log
Chronological and immutable record of every action in the organization — by members or by the system. Each entry has: who, what, when, on which resource, before/after data. Append-only: no entry can be edited or deleted.
Webhooks
HTTP POST sent to your server when something happens in AdFlow. Each POST includes the X-AdFlow-Signature header (HMAC-SHA256 of the body) for authenticity validation. Retry policy: 3 attempts after failure.