Fix Security OAuth Reconnect Required
Fix path for security oauth reconnect required in AdsDoneEasy — product layers first, not inventing auto-bid.
Symptom security oauth reconnect required: check OAuth, customer ID, tier ceilings, then sync/Optimize credits.
- ✓Checklist for security oauth reconnect required: (1) OAuth scopes and correct customer ID, (2) Starter/Growth/Enterprise campaign or sync limits, (3) whether empty sync is a credit or tracking issue, (4) MCP PAT vs OAuth mismatch if using hosted MCP.
- ✓Fix the AdsDoneEasy path; do not invent auto-bid or live Meta workarounds.
- ✓Re-test after one change; avoid stacking MCP, OAuth, and bid edits.
- ✓Publish stays PAUSED; AdsDoneEasy does not auto-bid; Google bills media spend.
Why this matters
Credits check fix-security-oauth
Verify sync/Optimize credits when diagnosing security oauth reconnect required.
Support packet fix-security-oauth
Record customer ID, tier, and last sync for security oauth reconnect required.
Layer isolate: fix-security-oauth
Split auth, limits, sync, and publish when fixing security oauth reconnect required.
Steps
Apply one fix
Repair OAuth, credits, structure, or MCP auth for security oauth reconnect required.
Verify
Re-sync or re-test, then document the fix for security oauth reconnect required.
Reproduce
Capture UI state and customer ID for security oauth reconnect required.
Check product constraints
Verify PAUSED publish, tier limits, and no-auto-bid expectations.
Frequently asked questions
Is Google media spend inside the SaaS price for security oauth reconnect required?
Can I use Meta Ads for security oauth reconnect required inside AdsDoneEasy today?
Is auto-bid included when running security oauth reconnect required?
What should I capture when security oauth reconnect required fails?
Related guides
Ready for profitable Google Ads?
Build verified Search campaigns and keep 100% control in your own Google Ads account.