Data usage & Google Ads API

A plain-language description of AdIntelivo’s business model, Google Ads API use case, data separation and customer controls.

Last updated 3 September 2026

Google Ads API purpose: AdIntelivo uses the Google Ads API to provide reporting for Google Ads accounts that an authenticated agency user is already authorized to access. The integration is reporting-only by product design and is not used to retrieve private competitor account data.

1. Business model

AdIntelivo is subscription software for marketing agencies. Agencies use the product to review first-party advertising performance for connected client accounts and to monitor separately sourced competitive activity in the markets those clients serve.

AdIntelivo charges the agency a software subscription. We do not resell Google Ads inventory, act as a media buyer, take a percentage of client ad spend, or sell connected Google Ads data to third parties.

2. Two separate categories of data

CategorySourcePurpose
First-party Google Ads dataA Google Ads account connected by an authorized agency userClient account reporting, monitoring and agency/client reporting workflows
Competitive intelligencePublic search observations, public landing pages and separately licensed market dataUnderstand public competitor advertising and search visibility

These sources are kept distinct. AdIntelivo does not present publicly observed competitor activity as if it came from a competitor’s Google Ads account, and it does not use the Google Ads API to access competitor spend, conversions, settings or other private account information.

3. Google Ads API — intended and implemented product use

A user connects Google Ads through Google OAuth. The user must already have permission to access the Google Ads account being connected. Once connected, AdIntelivo uses the Google Ads API for reporting/read operations so the user can review that account’s performance inside the AdIntelivo workspace.

Reporting data we may retrieve

  • customer/account identity needed to show and distinguish authorized accounts;
  • campaign, ad group, ad and keyword structure that is included in a reporting view;
  • search-term reporting where that reporting view is enabled;
  • status fields needed to label active, paused or removed entities when displayed;
  • performance fields such as impressions, clicks, cost, conversions and all conversions;
  • campaign budget information used for budget reporting and pacing views;
  • other read-only reporting fields required to render a selected account report.

API operations

AdIntelivo is designed to use Google Ads reporting and read-only operations, including GoogleAdsService reporting queries. The product does not provide a Google Ads campaign editor and does not use mutate operations to change advertiser accounts.

We do not use the Google Ads API to

  • create, edit, pause, enable or remove campaigns, ad groups, ads, keywords or budgets;
  • place advertising or manage media spend on behalf of an advertiser;
  • obtain private data from a competitor’s Google Ads account;
  • show one customer’s connected account data to another customer;
  • sell, license or syndicate connected Google Ads account data;
  • represent public competitor observations as Google Ads API metrics.

4. Authorization and account selection

Google OAuth is initiated by an authenticated AdIntelivo user. The user authorizes Google access and then connects only an account the user is permitted to access. AdIntelivo does not ask users to provide their Google password and does not receive the user’s Google password.

Google Ads uses its required OAuth authorization scope for API access. AdIntelivo limits what it does with that authorization at the application level to the reporting/read-only product behavior described on this page.

5. How connected data appears in the product

First-party Google Ads data is displayed in clearly labelled connected account, portfolio and reporting views. Public competitor observations appear in separate competitive intelligence views. Where a report places the two categories near each other, the source remains labelled so an agency user can tell which figures are first-party account metrics and which are market observations.

The public Google Ads integration page and the product demo contain representative mock-ups of this workflow using illustrative sample data.

6. Access control and customer isolation

  • Connected account data is associated with the agency workspace that authorized the connection.
  • One agency cannot use AdIntelivo to browse another agency’s private Google Ads account data.
  • Application access is restricted to authenticated users of the relevant workspace.
  • Google access tokens are treated as sensitive credentials and are not exposed in the public client interface.

7. Retention, disconnection and deletion

AdIntelivo retains connected advertising reporting data only for the period needed to provide historical reporting, up to 13 months while the account remains connected. If the account is disconnected or the workspace is closed, the connection is disabled and stored connected account data is scheduled for deletion within 30 days, except records we are legally required to retain.

8. Competitive intelligence sources

Competitor monitoring uses public or separately licensed sources such as publicly displayed search ads, organic search positions, map results, publicly reachable landing pages and aggregate keyword-market data. This process is independent of the client’s Google Ads API connection.

9. Contact

API and developer questions: api@adintelivo.com
Privacy and data requests: privacy@adintelivo.com

See also the Privacy policy, Terms of service, and Google Ads integration overview.