AdsPower: map one account, one 2FA setup and one IP to each Profile
Use AdsPower to manage Profiles and proxy environments, then keep the account, 2FA, IP and BM workflow correctly mapped for each Profile.
Read guideLocate environment, permission, payment and verification issues by the actual page result, then preserve the next action for every Profile.
Use AdsPower to manage Profiles and proxy environments, then keep the account, 2FA, IP and BM workflow correctly mapped for each Profile.
Read guideSeparate ready, failed, rerunnable and manually pending accounts after a BM workflow, and record the exact step where each exception stopped.
Read guideA login issue, ad restriction, disabled ad account, BM restriction and payment decline require different responses. Start with the first object that failed.
Read guideSeparate an unavailable payment entry point, cardholder verification, issuer decline and account restriction before deciding whether a card needs replacing.
Read guideWhen Business Manager requires two-factor authentication, pause payment and permission changes until the account owner completes the official verification flow.
Read guideAdmins provide access and continuity. They do not repair a restricted personal account or BM, so stop adding people after a restriction appears.
Read guideRun environment checks, BM access, payment binding and approved admin cleanup in order, then separate ready, failed, rerunnable and pending outcomes.
Read guideDo not rely on a fixed warm-up period. Verify identity, assets, permissions, payment and environment before changing another relationship.
Read guide