Skip to main content
Bounty customers can authorize Google Ads and choose which accessible advertiser accounts belong to their Bounty organization. The native connection currently covers OAuth, credential storage, account discovery, and account selection.
The native Google Ads connection does not yet power Bounty reporting queries. Reporting remains dependent on the data paths activated for the customer. This page distinguishes the shipped connection flow from later data use.

​
What the current connection does

The current connection can:
  • Start Google OAuth from the authenticated Bounty Connections page.
  • Request the Google Ads scope required to list and access advertiser accounts.
  • Exchange the authorization code on Bounty’s server.
  • Store the access and refresh credential in encrypted Supabase Vault storage.
  • Discover advertiser accounts available to the authorizing Google user.
  • Let the user select one or more active advertiser accounts.
  • Save those selections as organization-scoped direct-query connection records.
  • Disconnect the credential and native selections from Bounty.
It does not currently create, edit, pause, or otherwise modify campaigns. The native selection is also not yet consumed by Bounty reporting or analysis queries.

​
Before you connect

You need:
  • An authenticated Bounty account.
  • Access to the Bounty organization receiving the connection.
  • Google access to at least one Google Ads advertiser account.
  • The Google Ads connector enabled for the Bounty organization.
Bounty owns the OAuth client, Google Ads developer token, and callback. Customers do not provide a developer token or OAuth client secret.

​
Connection workflow

  1. Open Connections in Bounty and select Connect Google Ads.
  2. Review Bounty’s disclosure describing the requested data, AI processing, and organization isolation.
  3. Select Continue to Google.
  4. Review Google’s consent screen and authorize the Google Ads permission.
  5. Google returns the authorization code to Bounty’s server callback.
  6. Bounty stores the resulting credential in Vault and lists advertiser accounts available to the Google user.
  7. Select the accounts to associate with the current Bounty organization.
  8. Bounty saves the selected account identifiers and shows Google Ads as connected.
Bounty never asks for the user’s Google password. OAuth access and refresh credentials are not returned to the browser after authorization.

​
Data requested and intended use

The Google Ads OAuth scope can provide access to Google Ads account and advertising data. The native flow initially uses it to discover account identifiers and metadata so the user can select the correct advertiser accounts. When Bounty activates a data workflow using the selected connection, it may process account, campaign, ad group, ad, keyword, configuration, spend, impression, click, conversion, and related performance data to provide customer-requested reporting, analysis, recommendations, and automation. The product will identify that activated behavior separately; completing OAuth alone does not imply that native reporting is active.

​
AI use and model isolation

Bounty may use de-identified Google-derived data with OpenAI and Anthropic as contracted processors to produce customer-visible analysis, summaries, recommendations, chat responses, and workflow outputs. Bounty does not allow those providers to train their general models with submitted customer data. Where a customer enables model personalization, Google-derived data may be used only for a customer-specific model or model artifact belonging to the authorizing Bounty organization. The data retains organization provenance and is never pooled, commingled, or used to train a generalized, foundational, or cross-customer model.

​
Security and organization isolation

  • Credentials are encrypted at rest in Vault and used only by server-side Bounty services.
  • The stored secret name includes the Bounty organization ID.
  • Account selections are stored against the same organization ID.
  • A user can select only accounts returned for that user’s Google authorization.
  • Selecting an account for one Bounty organization does not expose it to another organization.
  • Bounty’s OAuth client secret and developer token remain server-side.

​
Disconnect and delete

Use Disconnect Google Ads on the Bounty Connections page to remove the organization’s native Google Ads credential and account selections. Disconnect is idempotent: repeating it does not affect another organization or another connector. You can also revoke Bounty through your Google Account permissions. Disconnecting stops future access through the native connection. To delete Google-derived data previously processed through another configured data path, contact Bounty as described in the Privacy Policy. Deletion removes the data from future training inputs and deletes or rebuilds an affected customer-specific model.

​
Privacy, security, and support

For connection support, email arran@bountygrowth.com.