Skip to main content
Bounty integrations connect systems selected and authorized by a customer. Each credential, account selection, and property selection is scoped to the customer’s Bounty organization.

​
Native Google connections

  • Google Ads supports Bounty-owned OAuth, advertiser-account discovery, account selection, encrypted credential storage, and disconnect.
  • Google Analytics supports Bounty-owned OAuth, GA4 property discovery, property selection, encrypted credential storage, and disconnect.
  • Google Search Console supports read-only OAuth, domain and URL-prefix property selection, encrypted credential storage, daily search-performance Datasets, and disconnect.
The native Google Ads and Google Analytics connections currently establish authorization and save the selected provider resources; they do not yet feed Bounty reporting queries. Google Search Console can create organization-scoped daily Datasets for selected properties.

​
Other connection types

Bounty also supports Meta Ads, Microsoft Advertising, HubSpot, Snowflake, Tinybird, Customer.io, Apple Search Ads, and Criteo connections. Availability and setup depend on the organization’s configuration. An integration never grants access beyond the accounts and resources available to the authorizing user. See Data Hierarchy for the relationship between connectors, connections, tables, data sources, and fields.

​
AI processing

When a customer requests an AI-backed feature, Bounty may send de-identified customer data to OpenAI or Anthropic as contracted processors to return the requested result. Google-derived data may personalize a model only for the authorizing Bounty organization. It is never used for generalized, foundational, pooled, or cross-customer model training. See the operative Privacy Policy and the Subprocessors list for details.