Campaign and ad group management
Create, edit and organise campaigns, ad groups, keywords and budgets inside the accounts we own, instead of repeating the same setup account by account.
An internal application our team uses to run our own Google Ads manager accounts through the Google Ads API: creating and editing campaigns and ads, checking status and performance, updating tracking parameters, and pausing or resuming delivery.
What it is, who operates it, and how it connects to Google.
CampaignOps Manager is software built and operated in house by the Nellamuse team. It connects to our own Google Ads manager account (MCC) and the client accounts linked to it, and gives our staff a single place to carry out routine advertising operations that would otherwise be repeated account by account.
It is not a public product. 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.
The tasks our staff perform with it on the accounts our organisation manages.
Create, edit and organise campaigns, ad groups, keywords and budgets inside the accounts we own, instead of repeating the same setup account by account.
Build responsive search ads and update headlines, descriptions, display paths and final URLs for the campaigns our team runs.
Read campaign, ad group, ad and keyword status together with cost, click and conversion metrics pulled from Google Ads reporting.
Apply final URL suffixes, UTM parameters and custom parameters consistently across selected campaigns and ad groups.
Pause or re-enable campaigns, ad groups, ads and keywords when a promotion ends, stock runs out or a budget needs to be held back.
Review what changed, when it changed and which staff account requested it, using the change history Google Ads returns for our accounts.
The application never acts on its own initiative outside the access granted by a member of our team.
Someone on our team with existing access to our Google Ads manager account starts the authorisation flow and grants the application OAuth 2.0 access.
The application requests the Google Ads API scope and can only act on manager accounts and linked client accounts that our organisation owns.
Routine checks pull current status and performance. Creation, editing, tracking and pause or resume actions run when a staff member asks for them.
The application keeps an internal log of the actions it performs and the account that authorised them.
Stated plainly, because it matters for anyone reviewing this application.
Advertising data is used to operate our own campaigns and for nothing else.
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, keywords, performance metrics and change history, together with the identity of the authorising user.
That information is used only to operate, monitor and report on our own advertising. Access is limited to authorised team members, transferred over HTTPS and stored in encrypted form. Authorisation can be withdrawn at any time from the Google Account permissions page, and the stored credentials stop working immediately afterwards.
The full detail, including retention and deletion, is in thePrivacy Policy and the Terms of Service.
Questions about the application, this website, or a data request can be sent to our team.
[email protected]