AdPilot Troubleshooting

Use this guide when an AdPilot plan, launch, daily monitor, or weekly report is blocked.

Quick Checks

Before changing campaign settings, confirm:

• The provider account is connected and not showing an auth banner.
• The selected ad account is still visible to the connected user.
• The daily and monthly budget caps have not been exhausted.
• The conversion event and landing URL still match setup.
• The latest approval card was approved before it expired.
• No provider or compliance rejection is blocking launch.

Auto-Pause Triggered

AdPilot can pause spend-reducing entities when a guardrail trips. Pause actions can run automatically because they reduce risk; reactivation requires approval.

Recovery:

1. Open the pause notification or monitoring row.
2. Review the provider, ad account, campaign ID, trailing spend, conversions, target CPA/ROAS, and pause reason.
3. Fix the underlying issue, such as tracking, creative, landing page, targeting, or budget configuration.
4. Ask AdPilot for a reactivation recommendation.
5. Approve the new reactivation card if you want spend to resume.

Do not reconnect auth just to clear an auto-pause. Re-auth only helps if the pause reason mentions provider access.

No Conversions Yet

Zero conversions is not always a failure. New campaigns can need time to exit learning, and low-budget campaigns can take longer to collect signal.

Check:

• CAPI setup verification passed for the configured event.
• The landing page fires the same event name configured in AdPilot.
• Pixel and server-side CAPI events share a dedupe event_id.
• Consent rules allow the event to be published.
• The campaign has spent enough and run long enough to evaluate.
• Provider reporting is not delayed.

Recovery:

1. Verify the conversion event before changing bids or budgets.
2. Confirm the configured learning window and minimum spend threshold.
3. Review search terms, audience size, placements, and landing page load issues.
4. Ask AdPilot for a diagnostic plan instead of approving a budget increase by default.
5. Approve changes only after the plan explains why tracking is healthy or what needs to be fixed.

If CAPI verification fails, fix tracking first. Optimizing against a missing event can make daily monitoring and CPA/ROAS reports misleading.

Budget Exhausted

AdPilot stops or blocks spend-changing work when the configured daily or monthly budget cap is exhausted.

What remains active:

• Read-only reporting when provider auth is healthy.
• Weekly report generation from available data.
• Draft recommendations for future budget changes.

What is blocked:

• Campaign launch.
• Budget increase.
• Bid-strategy change that can increase spend.
• Ad-set or ad-group reactivation.

Recovery:

1. Check whether the exhausted cap is daily, monthly, or provider-side.
2. Wait for the next budget reset if no increase is needed.
3. Ask AdPilot for a revised plan if you want to reduce scope.
4. Use Spend approval and safety if you want to increase a cap.
5. Approve only the new budget cap you are comfortable spending.

Rejected or expired budget approvals do not resume spend. AdPilot must issue a fresh approval card.

Compliance Rejection

AdPilot runs pre-launch compliance checks, and providers can still reject ads after submission.

Common causes:

• Restricted category or special ad category mismatch.
• Unsupported personal-attribute language in ad copy.
• Landing page claims that do not match the ad.
• Missing disclosures, privacy language, or consent handling.
• Targeting that violates provider policy.

Recovery:

1. Open the rejection detail.
2. Identify whether it came from AdPilot’s pre-launch scan or the provider.
3. Edit the claim, creative, targeting, landing page, or disclosure.
4. Ask AdPilot to regenerate the plan or provide a narrower compliant alternative.
5. Approve a new plan only after the compliance issue is resolved.

If the provider rejected an already submitted ad, AdPilot can keep monitoring read-only status but should not resubmit the same rejected asset without a revised approval.

Customer Rejected Plan

Rejecting a plan is safe. It prevents the proposed spend-changing action from running and records the rejection for audit.

After rejection:

• No campaign launch, budget increase, bid-strategy change, or reactivation runs from that approval.
• The rejected approval cannot be resumed.
• Existing live campaigns remain unchanged unless a separate pause or provider event affects them.
• AdPilot can draft a revised plan using your rejection reason.

Recovery:

1. Add a rejection reason when possible, such as budget too high, wrong audience, weak creative, or tracking not ready.
2. Ask AdPilot to revise the plan, narrow scope, or stop the campaign.
3. Review the new approval card before any spend-changing action runs.

Auth Or Account Problems

If troubleshooting shows provider access is the blocker, use the provider-specific runbook:

• Google Ads re-auth
• Meta Ads re-auth
• LinkedIn Ads re-auth

Provider auth recovery preserves configuration, monitoring history, conversion settings, and approval history. It does not revive rejected, expired, or stale approvals.

When To Stop Instead Of Fix

Stop the campaign plan instead of trying to recover when:

• The landing page or offer is not ready.
• You cannot confirm consent for the conversion event.
• The provider account owner cannot grant the required permissions.
• Compliance issues require product, legal, or policy changes.
• The remaining budget is not enough to reach a useful test window.

Return to AdPilot.