Load Google Bid Manager data to DuckDB

Google Bid Manager is a platform for managing programmatic advertising queries and reports through a REST API. Everything needed to build a working Google Bid Manager → DuckDB pipeline is on this page: the API's base URL, authentication, endpoints, pagination and incremental field — plus a prompt that hands the whole job to your coding agent.

---

Build your Google Bid Manager to DuckDB pipeline

Paste this prompt into Claude, Codex, or Cursor. The agent does the rest.

PromptCopy prompt
Run uvx dlthub-init@latest to build a pipeline from Google Bid Manager to DuckDB and run it on dltHub

That scaffolds a dltHub workspace and installs the dltHub AI harness — the project rules, the secrets-management skill, and the dlt MCP server your agent needs to work safely. From there it reads the Google Bid Manager API, proposes the endpoints to load, then writes, runs and validates the pipeline while you review rather than type. Credentials are inspected through MCP tools, so your agent never reads secrets.toml itself. How the LLM-native workflow works →

Prefer to write it yourself? Every fact the agent uses is below.

---

Google Bid Manager API at a glance

These values come from the Google Bid Manager API reference — the authoritative source if anything here looks out of date.

---

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

Copy
[sources.google_bid_manager_source]
access_token = "REPLACE_ME"

dlt reads this file automatically at runtime. With the harness, the setup-secrets skill prompts you for the values and never handles the raw credential in chat. For production, see setting up credentials with dlt.

---

What Google Bid Manager data can I load into DuckDB?

These are the Google Bid Manager endpoints dlt can load into DuckDB:

---

How do I load only new Google Bid Manager records?

Google Bid Manager exposes pageToken on v2/queries, so dlt can request only the records that changed since the last run. Set it as the cursor_path and dlt tracks the high-water mark for you between runs.

Copy
{"name": "queries", "endpoint": {
    "path": "v2/queries",
    "data_selector": "queries",
    "incremental": {"cursor_path": "pageToken", "initial_value": "2024-01-01T00:00:00Z"},
}}

On the first run dlt loads everything from initial_value; on every run after that it requests only what changed and appends with write_disposition="merge" if you set a primary key. See incremental loading.

---

What does the generated Google Bid Manager pipeline look like?

A standard dlt REST API pipeline — the same code you would write by hand, loading advertisers.campaigns and queries from the Google Bid Manager API into DuckDB:

Copy
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 load_google_bid_manager_to_duckdb() -> 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)


if __name__ == "__main__":
    load_google_bid_manager_to_duckdb()

Run it with python google_bid_manager_pipeline.py. The agent iterates on this until it loads cleanly — you review and approve, rather than write it from scratch.

---

How do I query Google Bid Manager data in DuckDB?

dlt creates one table per resource. Query the loaded data with Python or SQL — or ask your agent to, through the MCP server's execute_sql_query tool.

Python (pandas DataFrame):

Copy
import dlt

data = dlt.pipeline("google_bid_manager_pipeline").dataset()
df = data.queries.df()
print(df.head())

SQL:

Copy
SELECT * FROM google_bid_manager_data.queries LIMIT 10;

See querying your data with dataset and exploring it in marimo notebooks.

---

How do I deploy the Google Bid Manager to DuckDB pipeline in production?

The pipeline runs locally, which is ideal for prototyping and one-off analysis. When you need it on a schedule, monitored on every load, and shared with your team, deploy the same dlt code on the dltHub platform — no infrastructure to maintain. The prompt above already ends with "run it on dltHub", so your agent can take it there directly.

• Deploy & schedule — run the pipeline as a managed job with automatic retries.
• Monitor — observable job queues, alerting, and load metrics for every run.
• Transform — promote raw Google Bid Manager loads into governed, documented models.
• Visualize & share — explore data in notebooks and publish live dashboards instead of static screenshots.

Book a demo →

---

What other destinations can I load Google Bid Manager data to?

dlt loads into any of these — only the destination argument changes:

Set dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. On the dltHub platform the same pipeline runs against a managed Iceberg lakehouse. See the full destinations list.

---

Next steps

• Ready for production? Book a demo of the dltHub platform →
• dlt LLM-native workflow docs
• REST API source reference
• Join the dlt community on Slack