Manager account administration
Keeps one registry of our Google Ads manager account (MCC) and the client accounts linked to it, together with the per-account settings the automation reads before it runs.
AdsFlow Manager
An internal application our team uses to run our own Google Ads manager accounts through the Google Ads API: managing accounts and campaigns, queueing advertising tasks, reading ad status, maintaining tracking links and parameters, and pausing, resuming or automating delivery.
Internal tool, authorised staff only Google Ads API over OAuth 2.0
Application overview
What AdsFlow Manager is
The application in one page: what it does, who operates it, which Google service it uses and who is allowed to sign in.
AdsFlow Manager is advertising operations software built and operated in house. It connects to our own Google Ads manager account (MCC) and the client accounts linked to it, so that routine work which would otherwise be repeated account by account is carried out from one place: campaign and ad task handling, status checks, tracking parameter maintenance, and pausing, resuming and rotating delivery.
It is not a public service. There is no sign-up, no subscription and no way for anyone outside our organisation to create an account, submit information or reach advertising data through it. The only people who can sign in are members of our team who already hold access to the Google Ads accounts our organisation owns.
- Application
- AdsFlow Manager, described at adsflow.beautyedithub.com
- Operated by
- the AdsFlow Manager team. Contact: [email protected]
- Purpose
- Internal advertising operations on our own Google Ads manager account
- Google services
- Google Ads API, authorised by the account holder with OAuth 2.0, from the Google Cloud project Google Ads Automation AD
- Who may use it
- Authorised team members only. No public registration and no self-service access.
- This website
- A static information site with three pages. No login, no forms and no tracking scripts of our own.
Capabilities
What the application does
The work our team carries out with it on the Google Ads accounts our organisation owns and manages.
Campaign and ad task management
Records campaign and ad work as tasks in our internal queue: create, edit, pause, resume or retire, each carrying an owner, a reason and a state that can be audited later.
Advertising status queries
Reads the serving status of campaigns, ad groups and individual ads, plus daily cost, click and conversion figures, and shows where what Google Ads reports differs from what we asked for.
Tracking links and parameters
Holds the tracking links, final URL suffixes and custom parameters used by each campaign, applies them consistently across selected campaigns, and checks that a link resolves before it is used.
Pause, resume and scheduled operations
Runs pause, resume and tracking-link rotation on a schedule, and writes a receipt for every change so that an action is either confirmed by Google Ads or reported as unresolved.
Internal task queue and run status
Shows the state of the automation service: what is queued, dispatched, waiting for a receipt or failed, with a heartbeat and a status view for the team on duty.
Development status
Available now, and not yet in use
Advertising tools change often, so the difference between what is running today and what is still being built is stated plainly here.
Available now
- Manager account registry. Account configuration for the manager account and its linked client accounts is read from our workspace and used to route every task.
- Advertising task queue. Campaign, ad and link operations are queued in our own workspace, with states, owners and an append-only record of what was requested.
- Final URL suffix and parameter updates. Tracking parameters and campaign URL suffixes are applied to selected campaigns through the manager account scripts.
- Scheduled tracking-link rotation. Live links are replaced on a schedule after a pre-flight check that the replacement link and its redirect chain resolve.
- Pause and resume with receipts. Pause and resume requests are executed, then read back from Google Ads, and a signed receipt is stored for each one.
- Daily performance readback. Daily cost, click and conversion figures are read from Google Ads into the workspace for the accounts we manage.
- Service health and run status. A heartbeat, queue state and health view are produced for every processing cycle so the team can see whether the automation is running.
- Retention and archiving. Finished tasks and rotation history are archived with checksums, and the detailed rows are cleared only after archiving is verified.
Planned or not yet enabled
- Automated ad removal and retirement. The pause and resume path runs in production. The removal path is written and covered by isolated tests, but it has not yet been exercised against a live Google Ads account.
- Profit and loss analysis with loss alerts. Implemented behind a switch that is off by default. It stays off until the business thresholds, currency settings and reporting windows it depends on have been agreed.
- Further affiliate network connections. Order and revenue data is imported from the affiliate networks that are already connected. Additional networks will be added only as they are approved.
How it works
From authorisation to recorded change
The application never acts on accounts we do not own, and it does not act outside the access a member of our team has granted.
Step 1
A team member authorises the application
A member of our team signs in with the Google Account that already holds access to our Google Ads manager account, and grants OAuth 2.0 access on Google's consent screen.
Step 2
Access is limited to our own accounts
The application requests the Google Ads API scope only. It can act on the manager account and the client accounts our organisation owns, and on nothing else.
Step 3
Work is queued, then executed
A queued task is dispatched to the manager account scripts, which make the requested change in Google Ads and return the result.
Step 4
The result is read back and recorded
The application reads the account back to confirm what actually changed, stores a receipt, and reports anything that could not be confirmed instead of assuming success.
Boundaries
What the application is not
Stated plainly, because these limits matter to anyone reviewing the application.
- It is not a public advertising platform, a commercial product or a paid service. Access is never sold, resold or offered to anyone outside our organisation.
- It is not a Google product and it is not certified, endorsed or sponsored by Google. Google Ads is a trademark of Google LLC, and the name is used here only to describe the service the application connects to.
- It never reads or changes a Google Ads account that our organisation does not own or manage. It holds no access to other advertisers' accounts.
- It does not collect information from visitors to this website. These pages have no sign-up, no login form and no advertising or profiling tag of our own.
- It does not sell, rent or share Google Ads data, and it does not use that data for advertising, profiling or credit assessment.
Data and privacy
Advertising data is used to run our own campaigns
Access runs through Google's OAuth 2.0 consent screen, and only for the accounts our organisation controls.
When a member of our team authorises the application, it receives access to Google Ads data for the accounts we manage: account and campaign structure, ads, budgets and keyword settings, status and performance figures, change history, and the identity of the authorising user. That access is used only to operate our own advertising.
Operational records live in our own workspace and on our own infrastructure, and access is limited to authorised team members. Authorisation can be withdrawn at any time from the Google Account permissions page.
The full detail, including what is stored, how long it is kept and how to ask for deletion, is set out in the Privacy Policy and theTerms of Service.
Contact
Questions about the application or this website
Questions about the application, these pages, or a request concerning stored data can be sent to the address below.
[email protected]