Search campaigns, on accounts we own.

Scope, in one paragraph

Neurad is an internal tool. We use the Google Ads API only to create, manage, and report on Search Network campaigns in Google Ads accounts that we own, all of which sit under our own Google Ads manager account (MCC). We do not access, manage, or report on accounts belonging to anyone else, and we do not offer this tool to outside parties.

What we call the API to do

Campaign creation

When a reviewer approves a brief, the desk creates the campaign, ad groups, keywords, and responsive search ads on the relevant owned account. Templates keep structure consistent; nothing is generated without an approved brief behind it.

Campaign management

Ongoing edits — budgets, bids/CPC targets, status changes, negative keywords, ad rotation — are made through the API after the same review step. Pausing under-performers and shifting budget toward winners is the bulk of day-to-day work.

Reporting

We read performance (impressions, clicks, cost, conversions) across our accounts and consolidate it into one board so the team can decide the next move. Reporting is read-only and runs on a schedule plus on demand.

Where the calls go

• Only our own accounts. Every customer ID we touch is a child of our single manager account.
• No external accounts — ever. The tool has no concept of an outside client; there is nowhere to enter someone else's account.
• One environment. Credentials are scoped to our MCC and live on infrastructure we control.

How a write is authorized

The API is never the first actor. A change is drafted by an operator, reviewed by a second person, and only then does the desk call the API to apply it. There is no autonomous or unattended mutation of live campaigns. Read/reporting calls run automatically; write calls require human approval.

Authentication

We authenticate with OAuth 2.0 using the https://www.googleapis.com/auth/adwords scope against our own Google Cloud project and developer token. Refresh credentials are stored as secrets, never in source control, and are used only by our internal service. Access is limited to the handful of employees who operate the desk.

Respecting limits

We operate within our current access tier and treat the daily operation budget as a hard ceiling, batching reads and backing off on errors. Our volume is modest by design — a small portfolio, reviewed by hand — and we scale calls to what the team can actually review.