Skip to main content
Start with the exact failed step. A connection problem, an old report, and an ad change with an unknown outcome need different recovery.

​
I cannot see an account

Confirm the AutoAdy identity, Facebook profile, selected business and accounts, and workspace account grants. Reconnect only when connection permissions needs correction. A client mapping alone does not grant access. Follow Connect Meta, Connect Google Ads, or Team access.

​
The numbers are empty or different

Confirm account, dates, timezone, currency, filters, attribution, and result definitions. Read fetch time and coverage warnings. A quiet period is different from a report that failed to load or partial report. Follow Freshness and Metric definitions.

​
An action is disabled

Read the reason beside the control. Check role, provider permissions, plan, credits, selected account, and availability. Coming soon or setup-unavailable states do not become enabled by reconnecting or creating a key. For Autopilot, check the saved mode and daily caps. For a scheduled task, resolve the preview blocker and review the corrected revision.

​
A change or job has an unknown outcome

Keep the original attempt visible and inspect its receipt, provider state, and offered recovery. A timeout does not prove that a provider made no change. Retry unresolved entities or reconcile the existing job as offered before starting new work. See Delivery changes, Budget changes, and Credit reservations.

​
Website ownership is verified but no events arrive

Check the published script, website key, consent, environment, actual visitor action, and reporting period. An ownership proof and a received event are separate checks. Follow Install tracking.

​
Payment succeeded but Billing is unchanged

Refresh and keep the Stripe receipt reference. Use a pending purchase or plan-change recovery when offered; do not purchase again to force a state update. Automatic top-up has its own paused and pending-payment states. See Subscriptions and Top-ups.

​
Prepare a useful support request

Record the failed step, exact message, account or site ID, period, relevant job/receipt reference, and expected result. Include a redacted screenshot only if it clarifies the state. Contact support with those details; never include passwords, API keys, provider tokens, or card details.