Skip to main content
Google Ads holds your paid search and display intelligence — search terms, ad performance, keyword opportunities, demographics, placements, RSA assets, and auction insights. These seven jobs pull that data through Mavera’s surfaces (Mave Agent, Focus Groups, Personas, Generate) so your content strategy, ad copy, and competitive positioning are grounded in real campaign data.

API Reference Card

All examples use four environment variables: GOOGLE_ADS_DEVELOPER_TOKEN, GOOGLE_ADS_CLIENT_ID (OAuth client), GOOGLE_ADS_CUSTOMER_ID (10-digit, no dashes), and MAVERA_API_KEY. Python examples use the google-ads client library; JavaScript examples use the REST API directly.

Prerequisites

1

Google Ads API access

Apply for a Developer Token and set up OAuth 2.0 credentials in the Google Cloud Console. You need at least Standard Access for production.
2

google-ads Python client

Install with pip install google-ads. Create a google-ads.yaml config or set credentials via environment variables.
3

Mavera API key

Get your key from Mavera dashboard.
4

Environment variables


Jobs


Rate Limits & Production Notes

Google Ads API uses dynamic rate limiting — QPS adjusts based on your account’s access level and current load. All code should handle RESOURCE_EXHAUSTED (gRPC) or 429 (REST) with exponential backoff. Standard Access accounts have no daily operation limit, but burst capacity varies.
Production checklist:

What’s Next

All Integrations

50+ API integrations with full code

Google Ads API Docs

Official Google Ads API reference

Personas API

Full reference for POST /api/v1/personas

Focus Groups API

Full reference for POST /api/v1/focus-groups

Mave Agent

Full reference for POST /api/v1/mave/chat

Generate API

Full reference for POST /api/v1/generations