Public app overview

Zbang Google Ads Audit

Zbang connects to a Google Ads account selected by the user, reads performance and account-structure data, and turns it into a private audit with dashboards, recommendations, and exportable planning outputs.

Primary use Audit search, Shopping, and retail Performance Max accounts

Google Ads access Used in a read-only workflow for analysis, not campaign edits

User control Each user explicitly connects Google, picks the account, and starts each audit

Public documentation Privacy, retention, and scope usage are documented below

Create account Sign in Read app privacy policy Read app terms

What the app does

Lists the Google Ads accounts the connected user can access.
Retrieves reporting and configuration data needed to build audits, dashboards, and recommendations.
Highlights wasted spend, measurement gaps, asset issues, bid-readiness, segmentation problems, and product-feed opportunities.
Generates private in-app dashboards and downloadable outputs for the connected user.

What the app does not do

It does not use the Google Ads connection to create, edit, pause, or delete campaigns.
It does not sell Google Ads data or use it for unrelated advertising.
It does not make a Google Ads connection public to other customers.

Google data used for audits

Basic Google identity data needed for sign-in and account linking.
Accessible-account metadata such as customer IDs, account names, and currency.
Google Ads reporting, campaign, asset, conversion, and product/feed diagnostics needed for analysis.

Privacy and retention

If AI recommendations are enabled for a job, relevant Google Ads analysis data is sent to the configured AI provider to generate campaign recommendations.

Generated files and workspace artifacts are retained in the workspace database for up to 7 days before cleanup.

For the detailed policy used on the Google OAuth consent screen, see the app privacy policy.

For service scope and provider disclosures, see the app terms and the subprocessors page.