Advertising, in the same admin as the site it points at.

Three reasons, and they are the reasons the tool exists at all.

• The numbers exist nowhere else. Campaign, keyword and search-term performance can only be read from Google Ads. There is no export, no feed and no scrape that produces them; a reporting screen that cannot reach the API has nothing to put on it.
• Reporting without acting is just a second screen. Seeing that a search term wasted £186 is only useful if you can add it as a negative keyword there and then. If the tool showed the numbers and sent you elsewhere to act, we would have built two systems to keep in sync by hand, which is the exact problem our clients came to us with.
• The advertising has to meet the enquiry. The website, the enquiry inbox and the order history are already in this admin. Joining what was spent to the lead it produced is the whole point of putting them together, and it can only be done by reading the advertising data programmatically.

It reads campaign performance, keyword performance and search-term reports for the linked account, plus the account’s own change history.

It changes three things, each written back to Google Ads and each recorded in the change log with its previous value:

• Pause or resume a campaign.
• Pause or resume a keyword.
• Add a negative keyword to a campaign.

Nothing else is written. A change made in the tool is a change made in the account, and it is attributable to the person who made it.

It does not create Google Ads accounts, does not create campaigns, and does not offer keyword planning or forecasting. It works with Search campaigns only — the keyword and search-term reporting it is built around does not exist for Performance Max or Display.

We would rather the tool did less and said so than claim a surface we have not built.

Both sides of the engagement, under one permission model.

• Our own staff, managing campaigns for clients who have asked us to run their advertising.
• The client’s own people, signing in to their own installation. Reporting is read-only by default. Where a client has advertising capability in-house, the same screens are handed over with management rights, decided per client rather than by a fixed rule.

Advertising engagements run through Circus Consulting Limited’s Google Ads manager account, with each client’s own account linked to it. The client keeps their account.

• Separate installations. Every client runs on their own codanomiq installation with its own database and its own system user. There is no shared tenant table, so there is no query that could return another client’s advertising data.
• Separate permissions. Reaching the Google Ads tool and reaching the credentials behind it are two different permissions. Someone can be given the reports without being given the account.
• Write-only credentials. Credential fields are stored write-only: once saved, the value is never sent back to any browser, ours or the client’s.