Redbit Ads Manager

Who operates this tool

What the tool does

Redbit Ads Manager is a private, server-side application. It is not a product: it is not sold, licensed, published, or made available to anyone outside the company, and it has no public sign-up, no customer accounts and no external users. It exists to let our own team analyse and manage the advertising accounts that Redbit S.r.l.s. owns and pays for.

The tool runs on our own server and is operated by our internal staff. It authenticates to the Google Ads API with a Google Cloud service account that has been granted access to our advertising accounts from within the Google Ads interface.

Accounts it operates on

How the Google Ads API is used

Permissible use: ad creation / management and reporting.

Reporting (read)

• Account overview: currency, time zone, status and period totals
• Campaign, ad group, ad and keyword performance over a chosen date range
• Search terms report, used to identify wasted spend and new keyword opportunities
• Campaign budgets and conversion actions
• Performance broken down by day, week, month, device and network
• Account change history

All reporting is performed with GoogleAdsService.SearchStream using GAQL queries.

Management (write)

• Pause, enable or remove campaigns, ad groups and keywords
• Adjust daily campaign budgets
• General campaign structure changes through GoogleAdsService.Mutate

Every write operation requires an explicit confirmation from the operator and supports a validate-only dry run before it is applied.

How our staff interact with it

The tool runs as a local server on our own machine and exposes its reporting and management operations to the internal operator's console, which is an AI coding assistant (Claude, by Anthropic). Our staff ask for a report or a change in plain language; the assistant calls the corresponding operation, and the tool performs the Google Ads API request.

This is an implementation detail of how one company operates its own accounts, not a service offered to anyone:

• The server listens on the loopback interface (127.0.0.1) only. It is not published on any domain, has no public endpoint, and cannot be reached from the internet.
• It additionally requires a bearer token that exists only on our server.
• No agency, end advertiser or other third party has access to it, directly or indirectly, and it is never used to give anyone access to our developer token.

Data handling

• Google Ads data retrieved through the API is used only for internal analysis and optimisation of our own campaigns.
• It is never sold, published, or combined with data belonging to other advertisers.
• Because our operators work through an AI assistant, the report data returned by the API is transmitted to that assistant's provider (Anthropic) as part of the operator's working session, under that provider's terms. No Google Ads data is sent anywhere else.
• Service account credentials are stored on our own server, outside the public web root, readable only by the system account that runs the tool.

Technical summary