In English

• E-commerce store build, optimisation and day-to-day operation (Shopify)
• Paid advertising management and reporting (Google Ads, Meta Ads) for client accounts
• CRM and email/LINE marketing (Klaviyo, LINE Official Account)
• Branding and creative production
• Reporting automation and internal tooling for the accounts we operate

All of our revenue comes from agency service fees paid by the clients whose accounts we operate. We are not a software vendor: we do not sell, license, resell or distribute any software product, and we have no software end users.

How we use the Google Ads API

We use the Google Ads API for a single purpose: an internal productivity tool for our own staff, used only on the Google Ads accounts of clients who have granted us access. It is a set of Python command-line scripts run manually on a staff workstation. There is no server, no hosted service, no web interface, no public endpoint, no sign-up and no client-facing UI. The tool is never distributed, licensed or sold to anyone.

1. Daily reporting (read only)

Instead of copying figures out of the Google Ads UI by hand every day, we query GoogleAdsService.SearchStream for cost, impressions, clicks and conversions, print them to the terminal for a staff member to sanity-check, and then write those four columns into the private Google Sheets workbook we review with each client. A second read-only mode prints a per-campaign breakdown for client meetings and writes nothing.

2. Campaign creation (write)

Campaign structure, budget, ad copy and images are decided by our team and approved with the client before the tool is used. The approved plan is written into a JSON specification, validated locally (character limits, image ratios, required asset counts), and then submitted through the campaign, budget and asset group services. Campaigns and asset groups are always created with status PAUSED. The tool contains no code path that can set a campaign to ENABLED and no code path that can raise the budget of an existing campaign — every delivery decision stays a manual human action inside the Google Ads UI.

3. Keyword research (read only)

When we propose a campaign structure to a client, we retrieve keyword ideas, average monthly search volume and bid estimates to present that research to the client. No plans are stored in the account and no automated bidding decisions are derived from it.

Data handling

Google Ads data retrieved through the API is used solely to report to, and improve results for, the client that owns the account. It is never combined across clients, never provided or resold to any third party, and never used to build or offer a product to anyone outside the client relationship. Credentials are held by the individual staff member who authorised them (OAuth2 installed-application flow, refresh token in a local file with 0600 permissions). The tool is used by 1–3 internal staff members.