Google Ads PMax Action Console

Safe PAUSED launches for agent-driven ad ops.

The console and MCP tools share one Action Gateway. In mock mode, Phase 1 simulates PAUSED non-retail PMax writes without calling Google Ads mutate.

Google OAuth requests the Google Ads scope to list accessible accounts, run readiness checks, and prepare PAUSED PMax actions through this console and MCP gateway. OAuth tokens are stored encrypted; production live writes remain blocked until Google Ads readiness and approval gates are complete.
Sign in to app
Checking account context

Readiness And Reporting

Choose a campaign resource name from a selected client customer before building an optimization plan.

Google Ads Management

Full Workflow v2

Optimization Console

Release Readiness

These fields prepare a plan only. Merchant readiness checks the Google Ads product link against the exact Merchant Center ID; it does not verify feed contents or create a Shopping/Retail campaign.

Execution

PMax Plan JSON

Ready

Idle
{
  "message": "Run a check or validate the sample plan."
}

Remote MCP

Public MCP endpoint: /mcp. Local compatibility mode uses a short-lived static token only on localhost. Public deployments must switch to WorkOS OAuth.