Skip to main content
BitsWeave
Guides

Google Ads

Connect a Google Ads account with OAuth, then report with GAQL and pause campaigns from BitsWeave tools.

A signed-in Google user connects their own Google Ads account to BitsWeave. Authorized people and agents in that organization can then report on and manage campaigns they already own. Advertisers never receive BitsWeave's developer token and do not call Google Ads as a raw API.

Live docs

This page is the public design document for the Google Ads connector. Product URL: bitsweave.com. Install: Connect Google Ads.

Company

Bitsweave. Product: bitsweave.com.

Business model

Bitsweave is a software product. Organizations sign in, connect the tools they already use, and run work through signed-in agents. We are not an advertising agency. We do not resell the Google Ads API. We do not give third parties a pass-through of our developer token.

Tool access and use

  1. An organization admin starts Google Ads from Brokers.
  2. Google OAuth asks for the https://www.googleapis.com/auth/adwords scope.
  3. The user allows access. Bitsweave stores that user's refresh and access tokens on that install only.
  4. Authorized members and connected agents call Bitsweave tools. Those tools call the Google Ads API for that account.

We start with Bitsweave-owned advertiser and manager accounts (internal use). The same product is for customers who sign in with Google and connect their own Ads accounts. We will file a tool-change / permissible-use update before we offer full campaign creation to other advertisers.

Tool design

Google user  --OAuth-->  Bitsweave install  --tools-->  googleads.googleapis.com
                              |                              ^
                     encrypted OAuth tokens                  |
                     (per organization)                      |
                                                             |
              Bitsweave developer token (platform env)  -----+
  • Install is OAuth only. No form fields. No developer token on the install.
  • Every Ads API call sends Authorization: Bearer <user OAuth token> and developer-token: <Bitsweave token>. The developer token is one Bitsweave credential. It is not shown to advertisers. We do not send login-customer-id.
  • OAuth access tokens refresh from the stored refresh token when they expire. Reconnect is not required after an hour.
  • Dedicated product tools:
    • brokers.google-ads.search — GAQL read (GoogleAdsService.Search)
    • brokers.google-ads.listCampaigns — list campaigns for a customer
    • brokers.google-ads.listAccessibleCustomers — customer ids the user can access
    • brokers.google-ads.pauseCampaign — set a campaign to PAUSED

API services called

ServiceUse
GoogleAdsService.SearchPerformance reads and campaign list (GAQL)
CustomerService.ListAccessibleCustomersCustomer ids the signed-in user can access
CampaignService.MutatePause a campaign the advertiser already owns (status = PAUSED)

Host: googleads.googleapis.com (Ads API v25). Scope: https://www.googleapis.com/auth/adwords.

How to connect

Start install

Open Connect Google Ads or call brokers_installations_startInstall with definitionId google-ads. Bitsweave returns a Google OAuth redirect.

Allow access

Sign in as a Google user who can access the Ads account. Approve the Ads scope.

Confirm

brokers_installations_list should show the install as active. Then run brokers.google-ads.listAccessibleCustomers, then listCampaigns or pauseCampaign with the client customerId.

On this page