Q

QUK Ads Manager

An internal desktop tool for managing Google Ads campaigns and keyword research.

What this application is

QUK Ads Manager is a desktop application used by the in-house performance marketing team at QUK. It connects to Google Ads accounts that the team is directly responsible for, and helps the team build, review and publish search advertising campaigns without repeatedly working through the Google Ads web interface.

The application is not a public product. It is installed locally, is used only by authorised members of our own advertising team, and is not distributed to, or made available to, the general public.

What it does

AreaFunction
Campaign setup Creates search campaigns, ad groups, responsive search ads, keyword lists and initial bids in a single batch, based on an internal product sheet.
Inventory review Reads back the current state of campaigns, ad groups, ads and keywords, so the team can verify what was actually published and correct any discrepancies.
Keyword research Collects keyword suggestions and monthly search volumes for our own product categories, so the team can decide which terms to bid on.
Reporting Exports daily spend, clicks and conversion figures for the accounts the team manages, for internal performance review.

Why it requests access to your Google Account

The application requests a single OAuth scope: https://www.googleapis.com/auth/adwords.

This scope is required because the Google Ads API has no narrower alternative — the same scope covers both reading campaign statistics and creating campaigns. The application uses it only to:

The application cannot access any Google Ads account that the signed-in user does not already have permission to view in the Google Ads web interface. It does not request access to Gmail, Google Drive, Calendar, Contacts or any other Google service.

Data handling in one sentence: advertising data retrieved through the Google Ads API is stored only on the operator's own computer, is used only for the team's internal advertising decisions, and is never sold, published, or shared with third parties.

How credentials are handled

Authorisation uses Google's standard OAuth 2.0 installed-application flow. The resulting refresh token is written to a configuration file on the operator's local machine only. No credentials are transmitted to, or stored on, any server operated by us — the application has no backend service.

Contact

Questions about this application, or requests relating to data held by it, can be sent to support@pixead.com.