Google Ads API — Tool Documentation

Applicant: Wazing Trading Cards

Date: September 1, 2026

Developer Token Customer ID: 153-501-3252

API Access Level Requested: Basic Access

Tool Overview

Wazing Trading Cards — Marketing Analytics Dashboard

Wazing Trading Cards is an e-commerce platform specializing in authentic Pokémon Trading Card Game products. We operate a headless storefront at wazing.com powered by Shopify, supplemented by a public Shopify retail channel. Our business runs daily product "drops" with a scarcity-driven release model and a membership tier system (Insider, Collector, Vault Key).

The tool requesting Google Ads API access is an internal admin dashboard — the "Command Center" — used solely by authorized administrators of Wazing Trading Cards. It is not a public-facing tool, not a resold SaaS product, and not available to any third party. Its purpose is to unify our marketing channel reporting (Google Ads, Meta Ads, Google Search Console, Google Analytics, Instagram organic) into a single view for spend, ROAS, and conversion analysis.

Intended API Usage

Read-Only Performance Reporting

The tool uses the Google Ads API exclusively for read-only reporting. Specifically:

API Resource	Purpose
`campaign`	Fetch campaign names, status, budgets, channel type for dashboard display
`metrics` (cost, impressions, clicks, ctr, conversions, cpc)	Aggregate spend and performance KPIs per campaign and per day
`segments.date`	Time-series breakdown for 7-day / 30-day / 90-day rolling windows
`search_term_view`	Identify which search queries triggered ads (for keyword optimization review)
`customer_client`	Resolve MCC child accounts (our account is under a manager account)

No Write Operations The tool does not create, update, pause, or delete campaigns, ad groups, ads, keywords, budgets, or bids via the API. All campaign management is performed manually in the Google Ads web interface. The API is used purely to pull reporting data into our internal dashboard for analysis.

Technical Implementation

Architecture & Authentication

API Version: Google Ads API v24 (current stable, updated as new versions release)
Authentication: OAuth 2.0 with refresh token stored securely in the platform secrets vault; access tokens refreshed automatically before expiry
Developer Token: Sent as the developer-token header on every request
Account Structure: Our Google Ads account (CID 153-501-3252) is a child of a Manager (MCC) account. We use the login-customer-id header to query the child advertiser account correctly.
Rate Limits: We poll reporting data once daily (scheduled) and on-demand when an admin opens the dashboard. We stay well within the API's rate limits and quota.
Data Storage: Aggregated metrics are cached in our database (ChannelMetricsSnapshot entity) with a per-campaign, per-day granularity for historical trend analysis.

Compliance

Adherence to Google Ads API Terms

No automated bidding: Bidding strategies are managed manually in the Google Ads UI.
No policy circumvention: The tool does not modify ad copy, targeting, or budgets programmatically.
Data retention: Reporting data is retained for internal analytics; no Google Ads data is shared with third parties or resold.
Access control: The dashboard is gated behind admin authentication; only authorized Wazing Trading Cards administrators can access it.
Brand compliance: Our site includes an independent-reseller disclaimer for The Pokémon Company trademarks, satisfying Google's advertising policy requirements for resellers.
Conversion tracking: We use Google Ads conversion tags (gtag) for purchase and add-to-cart events, with transaction_id deduplication, deployed via standard Google Tag architecture.

Business Context

Why We Need API Access

We run Google Ads campaigns (Performance Max and Search) to drive traffic to wazing.com. Currently we can only see Google Ads performance in the Google Ads UI, disconnected from our internal sales data (Shopify orders, traffic attribution, customer acquisition source). The API lets us join ad spend and conversions with our internal revenue data to calculate true ROAS per channel and per campaign — which is essential for allocating our ad budget efficiently.

Without Basic Access, the developer token remains in test mode and every API call returns a 403DEVELOPER_TOKEN_NOT_APPROVED error, blocking all reporting integration.

Contact

Technical Contact

Company:	Wazing Trading Cards
Website:	https://wazing.com
App URL:	https://wazingtcg.base44.app
API Contact:	Site administrator (via Contact Us page on wazing.com)

This document describes the internal tool developed by Wazing Trading Cards that uses the Google Ads API for read-only performance reporting. The tool is not distributed to third parties and is used solely for the company's internal marketing analytics. All Google Ads API usage complies with the Google Ads API Terms of Service.