How NegativeFinder uses the Google Ads API

Our API surface is intentionally small. We request a single Ads scope (https://www.googleapis.com/auth/adwords) and act only on the accounts the signed-in user already manages. There is no autonomous mode; a human approves every write.

ReadWhat we read

Accessible accounts. To show you which Google Ads accounts you can connect.
Search terms. For the date range you scan (last 30 days by default), with cost, clicks, and conversions, so the classifier can spot waste.
Campaigns, ads & keywords. To scope a scan, skip terms you're deliberately targeting, and draft the account's business context from its own campaign signals.
Existing negative keywords. To flag suggestions that duplicate something you already block.
Shared negative lists. So you can pick where a new negative is added.

WriteWhat we write

Negative keywords only. Added at the campaign, ad-group, or shared-list level.
One write per approved suggestion. Never in the background, on a timer, or by confidence alone. If you undo or move an applied negative, we remove only the negative we created.
Every write is audit-logged. Timestamp, user, account, and the suggestion that justified it.
We never create, pause, or edit campaigns, ads, budgets, or bids. The only thing we write is a negative you approved.

Human-in-the-loop, always. NegativeFinder only reads and writes data the authenticated user is already authorized to access in Google Ads. We never share or aggregate data across customers. You can revoke access at any time from your Google Account, and your stored credentials are deleted on revocation. Our use of Google user data complies with the Google API Services User Data Policy, including the Limited Use requirements.