Pandorium Ads Hub is the in-house operations platform our team uses to manage client Google Ads accounts under our Manager Account (MCC). It connects to the Google Ads API for reporting, campaign creation, campaign management, account auditing, and keyword planning — entirely operated by Pandorium Agency staff.
Pandorium Ads Hub is an internal-use tool built and operated by Pandorium Development (doing business as Pandorium Agency). It is not a SaaS product. It is not sold or licensed to third parties. There is no public sign-up, no client login, and no external API exposure. The tool is used exclusively by Pandorium Agency employees and contracted operators to manage paid advertising campaigns on behalf of our clients under our authorised Manager Account (MCC 363-097-5998).
The Hub is built on Anthropic's Claude Code agent CLI together with custom Python scripts and Model Context Protocol (MCP) servers. These components call the Google Ads API on behalf of our operators. Every API write operation is reviewed and explicitly approved by a human operator before execution against a live account.
These match exactly the capabilities declared in our Google Ads API token application. Every action is initiated and approved by a Pandorium operator.
Pull campaign, ad group, ad, keyword, and search-term reports for client dashboards.
Audit account structure, conversion actions, and settings across the MCC.
Build new Search, Performance Max, Shopping, Display, Video, and Demand Gen campaigns from approved briefs.
Adjust budgets, bids, keywords, negatives, RSAs, assets, and audience targeting.
Pull search volume, competition, and forecast data via the Keyword Plan Service.
Pandorium Ads Hub runs locally on operator workstations — not on a public server. Operators authenticate against the Google Ads API using OAuth 2.0 with the developer token tied to MCC 363-097-5998. Anthropic's Claude Code agent orchestrates the calls; custom Python scripts and MCP servers provide the API client layer.
Below is a representative session showing how a Pandorium operator pulls performance data and proposes optimizations. The agent never executes write operations without explicit operator approval.
Daily pulls of campaign, ad group, keyword, and search-term reports across all client accounts under our MCC. Data feeds internal weekly review documents and end-of-month client reports.
Quarterly account-health audits: conversion action setup, GCLID linking, account-level negatives, broken ad assets, RSA strength, and PMax asset coverage.
From an approved client brief, the Hub builds Search, PMax, Shopping, Display, Video, and Demand Gen campaigns in draft state. An operator reviews the structure before enabling.
Weekly bid & budget adjustments, negative keyword additions, RSA pinning, asset rotation, and audience refinement — all logged and reviewable.
Search-volume and forecast pulls via the Keyword Plan Service to size opportunities before recommending budget changes to clients.
MCC-wide policy enforcement: ensure conversion tracking, brand safety negatives, geo-exclusions, and budget pacing rules are consistent across the portfolio.
Access is restricted to Pandorium Development employees and contracted operators bound by NDA and a Data Processing Agreement. There is no public sign-up, no client login portal, and no external developer access.
| Who | What they can do | How they authenticate |
|---|---|---|
| Pandorium employees | Full reporting + write operations under MCC | OAuth 2.0 to MCC manager login |
| Contracted operators | Read access by default; write access scoped per client engagement | OAuth 2.0 with operator-tier role + NDA + DPA |
| Clients | None — receive PDF/dashboard reports only; never log in to the Hub | Not applicable (no login) |
| Third parties | None — the Hub is not licensed, sold, or shared | Not applicable |
| Data accessed | Campaign configuration, ad groups, ads, keywords, conversions, change history, and reporting metrics for accounts linked to MCC 363-097-5998. No end-user PII beyond what is exposed by the Google Ads API itself. |
| Storage | Performance data is cached locally on encrypted operator workstations for the duration of analysis. Aggregated reports are stored in encrypted Google Workspace for the active engagement. No raw account data is replicated to a third-party warehouse. |
| Retention | Operational cache: rolling 30 days. Report archives: duration of the client engagement plus 90 days for backup recovery, after which raw data is deleted. |
| Sharing | Google Ads API data is shared only with the client whose account the data belongs to. We do not sell, transfer, or otherwise disclose data to third parties. We do not use Google Ads API data to train, fine-tune, or augment any machine-learning models, including foundation models accessed via Anthropic's API. |
| Encryption | All API traffic over TLS 1.2+. Credentials and refresh tokens stored encrypted at rest using OS-native key stores. |
| Revocation | OAuth grants are revocable by the account holder at any time via myaccount.google.com → Third-party access. Upon revocation, the Hub immediately loses the ability to read or write to that account. |
| Off-boarding | When a client engagement ends, that account is unlinked from MCC 363-097-5998, and all cached data for the account is deleted within 30 days. |
Pandorium Ads Hub's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We use Google Ads data only to manage the advertising accounts of clients who have explicitly authorised Pandorium Development to do so under their existing engagement.
For questions about our Google Ads API integration, data practices, or compliance, please reach out:
MCC ID: 363-097-5998 · Operator: Pandorium Development (DBA Pandorium Agency)