Verification status
Google verification is in progress. Ordinary production users cannot start the unverified Google Ads OAuth flow. Demonstration access is limited to the restricted review environment and allowlisted reviewer accounts.
Google Ads reporting. Clear access boundaries.
Review the account selection, campaign reporting and user-controlled management scope. Google verification is in progress; general OAuth access is not enabled.
For verification reviewThe restricted demonstration uses a dedicated reviewer environment and approved test account.
For reportingConnected account data is used for the disclosed reporting features, not sent to AI providers.
For user controlSupported management actions require a deliberate user action and the applicable permissions.
Zavyra’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Google Ads API scope
Performance visibility with explicit, user-controlled changes.
Zavyra requests the Google Ads scope https://www.googleapis.com/auth/adwords. This scope is required by the Google Ads API for both reporting and supported account changes; Zavyra limits its use to the features described below and the accounts a user explicitly connects.
Connection and control path
- 01In the restricted review environment, an explicitly allowlisted reviewer can start Google authorization and review the requested Google Ads access. This unverified flow is not enabled for ordinary production users.
- 02Select an accessible customer account; manager-account context is supported where Google requires a login customer ID.
- 03Import campaign configuration and performance, then review reporting views in the Zavyra workspace.
- 04The review covers existing user-facing campaign, budget and status controls. Any live write demonstration requires separate owner approval and an approved test account; no paid campaign spend is part of the review.
- 05Disconnect in Zavyra to remove the local connection and trigger a best-effort Google token revocation.
Google Ads access and purpose
| Access | Why Zavyra uses it | What the user sees or controls |
|---|---|---|
| Accessible customer accounts | Let the user choose the Google Ads account to connect. | Customer and manager-account selection. |
| Campaign configuration | Read campaign identity, status, type, currency and time-zone context. | Campaign list, state and account context. |
| Performance metrics | Read cost, impressions, clicks, conversions and conversion value. | Campaign reports, trends, comparisons and ROAS context. |
| Campaign mutations | Create supported campaigns or change budgets and status after an explicit user action. | A reviewable action initiated by the user; no hidden automatic edit. |
Limited Use
Zavyra’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Token protection
Access and refresh tokens are stored encrypted and are used only for the connected workspace and supported Google Ads operations.
Google data and AI
Google API data is not sent to AI model providers. Google Ads reporting remains separate from other AI-assisted commerce features, as described in the current Privacy Policy.
Disconnect and deletion
Disconnecting removes the local connection and attempts provider revocation. A verified deletion request can be submitted from the Data deletion page.
Google Ads integration
Built for clear, connected operations.
Explore the workflows described below. Available actions depend on the connected service, account permissions and selected plan.
Account selection
Choose the accessible Google Ads account during the restricted review flow.
- Google authorization
- Customer account selection
- Workspace-bound connection
Campaign reporting
Read supported cost, impressions, clicks, conversions and conversion value.
- Campaign comparisons
- Date-based reports
- Account context
User-controlled management
Review supported campaign, budget or status changes before an explicit action.
- Review before action
- No hidden campaign edits
- Permission-bound operations
Restricted availability
The unverified OAuth flow is not available to ordinary production users.
- Dedicated review environment
- Allowlisted reviewer access
- No Google API data sent to AI providers
How teams use it
From source data to a clear next move.
- 01For verification review
The restricted demonstration uses a dedicated reviewer environment and approved test account.
- 02For reporting
Connected account data is used for the disclosed reporting features, not sent to AI providers.
- 03For user control
Supported management actions require a deliberate user action and the applicable permissions.
Frequently asked questions
Clear answers before you connect.
Can ordinary users connect Google Ads now?
No. Verification is in progress, and the unverified OAuth flow remains disabled for ordinary production users.
Does Zavyra send Google Ads data to AI providers?
No. Under the current Privacy Policy, information received from Google APIs is not sent to AI providers.
Why is the adwords scope described here?
The Google Ads API uses https://www.googleapis.com/auth/adwords for the disclosed reporting and management operations. Zavyra does not add unrelated Google scopes for this integration.
Your next step
Explore the options for your workspace.
Review availability, choose the capabilities you need and keep provider access under your control.