Google Bid Manager Python API Docs | dltHub
Build a Google Bid Manager-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.
Last updated:
Google Bid Manager is a platform for managing programmatic advertising queries and reports through a REST API. The REST API base URL is https://doubleclickbidmanager.googleapis.com and all requests require an OAuth 2.0 Bearer token.
dlt is an open-source Python library that handles authentication, pagination, and schema evolution automatically. dlthub provides AI context files that enable code assistants to generate production-ready pipelines. Install with uv add "dlt[hub]" and start loading Google Bid Manager data in under 10 minutes.
What data can I load from Google Bid Manager?
Here are some of the endpoints you can load from Google Bid Manager:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| queries | v2/queries | GET | queries | Lists queries created by the current user. |
| queries | v2/queries/{queryId} | GET | Retrieves a query. | |
| queries.reports | v2/queries/{queryId}/reports | GET | reports | Lists reports generated by the provided query. |
| queries.reports | v2/queries/{queryId}/reports/{reportId} | GET | Retrieves a report. | |
| queries | v2/queries | POST | Creates a new query. |
How do I authenticate with the Google Bid Manager API?
All API requests must include an Authorization header with the format 'Bearer {access_token}', where the access token is obtained via the OAuth 2.0 flow.
1. Get your credentials
To access the Google Display & Video 360 (Bid Manager) API, you must use OAuth 2.0; API keys are not supported for data access. Follow these steps in the Google Cloud Console: 1. Create or select a Google Cloud project. 2. Navigate to the API Library and enable the 'Display & Video 360 API'. 3. Go to the 'Credentials' page and click 'Create Credentials' > 'OAuth client ID'. 4. Choose your application type (e.g., 'Desktop app' for local scripts). 5. Configure the OAuth consent screen if prompted. 6. Once created, download the credentials as a JSON file, which will contain your 'client_id' and 'client_secret'. Use these to authenticate via an OAuth 2.0 flow.
2. Add them to .dlt/secrets.toml
[sources.google_bid_manager_source] access_token = "REPLACE_ME"
dlt reads this automatically at runtime — never hardcode tokens in your pipeline script. For production environments, see setting up credentials with dlt for environment variable and vault-based options.
How do I set up and run the pipeline?
Set up a virtual environment and install dlt:
uv init uv add "dlt[hub]"
1. Install the dlt AI harness:
uv run dlthub ai init --agent <your-agent> # <agent>: claude | cursor | codex
This installs project rules, a secrets management skill, appropriate ignore files, and configures the dlt MCP server for your agent. Learn more →
2. Install the rest-api-pipeline toolkit:
uv run dlthub ai toolkit install rest-api-pipeline
This loads the skills and context about dlt the agent uses to build the pipeline iteratively, efficiently, and safely. The agent uses MCP tools to inspect credentials — it never needs to read your secrets.toml directly. Learn more →
3. Start LLM-assisted coding:
Use /find-source to load data from the Google Bid Manager API into DuckDB.
The rest-api-pipeline toolkit takes over from here — it reads relevant API documentation, presents you with options for which endpoints to load, and follows a structured workflow to scaffold, debug, and validate the pipeline step by step.
4. Run the pipeline:
uv run python google_bid_manager_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline google_bid_manager_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset google_bid_manager_data The duckdb destination used duckdb:/google_bid_manager.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
uv run dlthub show
This opens the Pipeline Dashboard where you can verify pipeline state, load metrics, schema (tables, columns, types), and query the loaded data directly.
Python pipeline example
This example loads advertisers.campaigns and queries from the Google Bid Manager API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:
import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def google_bid_manager_source(access_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://doubleclickbidmanager.googleapis.com", "auth": {"type": "bearer", "token": access_token}, }, "resources": [ {"name": "queries", "endpoint": {"path": "v2/queries", "data_selector": "queries"}}, {"name": "queries_reports", "endpoint": {"path": "v2/queries/{queryId}/reports", "data_selector": "reports"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="google_bid_manager_pipeline", destination="duckdb", dataset_name="google_bid_manager_data", ) load_info = pipeline.run(google_bid_manager_source()) print(load_info)
To add more endpoints, append entries from the resource table to the "resources" list using the same name, path, and data_selector pattern.
How do I query the loaded data?
Once the pipeline runs, dlt creates one table per resource. You can query with Python or SQL.
Python (pandas DataFrame):
import dlt data = dlt.pipeline("google_bid_manager_pipeline").dataset() sessions_df = data.queries.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM google_bid_manager_data.queries LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("google_bid_manager_pipeline").dataset() data.queries.df().head()
See how to explore your data in marimo Notebooks and how to query your data in Python with dataset.
What destinations can I load Google Bid Manager data to?
dlt supports loading into any of these destinations — only the destination parameter changes:
| Destination | Example value |
|---|---|
| DuckDB (local, default) | "duckdb" |
| PostgreSQL | "postgres" |
| BigQuery | "bigquery" |
| Snowflake | "snowflake" |
| Redshift | "redshift" |
| Databricks | "databricks" |
| Filesystem (S3, GCS, Azure) | "filesystem" |
Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.
Next steps
Continue your data engineering journey with the other toolkits of the dltHub AI harness:
data-exploration— Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.dlthub-platform— Deploy, schedule, and monitor your pipeline in production.
uv run dlthub ai toolkit install data-exploration uv run dlthub ai toolkit install dlthub-platform
Was this page helpful?
Community Hub
Need more dlt context for Google Bid Manager?
Request dlt skills, commands, AGENT.md files, and AI-native context.