Google Adsv1.0.3

A CRM or marketing ops engineer uses create_customer_list and add_or_remove_to_customer_list to push first-party email and phone identifiers into Google Ads, keeping audiences fresh for retargeting and exclusion. It replaces brittle manual CSV uploads with a repeatable, API-driven pipeline.

An agency media buyer programmatically creates, edits, or pauses campaigns and ad groups across many client accounts using mutate_campaigns and mutate_ad_groups. This removes repetitive UI work and enforces consistent naming, budgets, and targeting.

An analytics team runs search_stream_gaql on a schedule to pull spend, clicks, conversions, and impression share, then loads the rows into a warehouse or dashboard. Scheduled GAQL extracts give stakeholders near-real-time visibility without manual exports.

A growth engineer uses list_accessible_customers, get_campaign_by_id, and get_campaign_by_name to inventory campaigns, detect drift from naming conventions, and audit who manages which accounts. The skill turns ad hoc account checks into automated compliance checks.

An e-commerce team updates campaign budgets and ad group bids around seasonal promotions using mutate_campaigns and mutate_ad_groups. Scripted rotations ensure prices and offers change in Google Ads at the same moment they go live on the storefront.

The skill powers a hosted platform that charges a monthly subscription for Google Ads automation, reporting, and audience management. Customers connect their Google Ads accounts and use the platform's UI instead of building their own API integration.

An advertising agency uses the skill behind the scenes to manage many client accounts efficiently, then bills clients a monthly retainer for campaign management and reporting. The skill lowers delivery costs by replacing manual ad ops work.

A developer-focused product exposes Google Ads operations through its own API, metering each connector run or write action. Customers pay for what they use, aligning cost with automation volume.