Business Model
We are a performance marketing operator. We run Google Ads campaigns for our own brands and for a limited set of client accounts that we are authorized to manage. Revenue comes from managed service fees and, where applicable, affiliate commissions from partner networks. This API tool is used internally to support reporting, ROI/ROAS analysis, and budget safety controls.
How we use the Google Ads API
- Reporting: Retrieve spend, clicks, impressions, and campaign performance metrics for accounts under our MCC and authorized accounts.
- ROI/ROAS analytics: Reconcile Google Ads spend with partner/affiliate order and commission data (from affiliate network APIs) to compute daily ROI/ROAS.
- Monitoring & alerts: Detect anomalous spend (e.g., spend spikes, overspend vs. daily caps) and notify internal operators (e.g., WeCom) via webhook.
- Safety controls (internal approval): Provide recommendations and optional actions (pause/enable campaigns, adjust budgets) after internal review/approval.
- Scope limitations: No public access, no data resale/sharing, no account creation; only accounts we own or are authorized to manage.
Architecture (Summary)
A scheduled internal service (Node.js) pulls Google Ads reporting data via the Google Ads API and pulls partner/affiliate order data via partner APIs. Data is stored in a secure database (PostgreSQL) for aggregation. A daily job computes ROI/ROAS and generates internal dashboards and alerts. Optional budget safety actions are queued and executed with audit logging.
Screenshot (Internal Tool)
Contact for Google Ads API matters
Email: beldnbmwoendbg@gmail.com
We currently use beldnbmwoendbg@gmail.com as the developer contact email and will migrate to a role-based email address on our domain as soon as it is available.