google-ads-manager

What This Skill Does

The google-ads-manager skill is a powerful automation interface for OpenClaw agents to interact with the Google Ads API. It bridges the gap between natural language requests and complex ad management workflows. This skill empowers your AI agent to monitor campaign performance, analyze key metrics such as CTR, clicks, and impressions, and execute administrative changes like adjusting daily budgets or toggling campaign statuses (ENABLE/PAUSED) directly from the command line or via agent dialogue. By abstracting the Google Ads API complexities, it allows users to focus on strategic decisions rather than technical implementation.

Installation

To integrate this skill into your environment, use the OpenClaw CLI: clawhub install openclaw/skills/skills/3824108-cell/claw-google-ads

Ensure that you have generated a OAuth2 credentials file. The skill expects a configuration file named google-ads.yaml located at ~/.google-ads.yaml or within the root directory of your project. This file must contain your Developer Token, Client ID, Client Secret, and Refresh Token.

Use Cases

• Proactive Campaign Monitoring: Automatically pull daily or weekly performance reports to identify underperforming ads.
• Budget Optimization: Dynamically adjust daily spend limits based on current market conditions or target ROAS.
• Emergency Controls: Quickly pause high-spending campaigns that have encountered technical issues or reached a threshold during off-hours.
• Reporting Integration: Feed live advertising data into other analytics dashboards managed by your OpenClaw agent.

Example Prompts

1. "Check the current performance of all active campaigns and list any with a CTR below 2%."
2. "Increase the daily budget for campaign 123456 to $50 and confirm the change."
3. "Pause the seasonal summer sale campaign immediately as the promotion period has ended."

Tips & Limitations

• Validation First: The agent is programmed to seek confirmation before executing destructive or financial actions (like changing budgets). Always provide clear, explicit instructions to avoid accidental spend spikes.
• Credentials Management: Keep your google-ads.yaml file secure. Since this file contains access tokens, it should never be committed to public repositories.
• Latency: API requests to Google are subject to rate limits. If you have thousands of campaigns, avoid performing massive batch updates within a single loop to prevent API throttling.