Reporting tool & API use
Last updated: June 2026
This page describes the quickByte Marketing Data Pipeline - an internal reporting tool operated by quickByte digital to deliver unified marketing analytics for ecommerce client accounts we manage under contract.
Overview
- Tool name
- quickByte Marketing Data Pipeline
- Operator
- quickByte digital - digital marketing and ecommerce systems agency, New Zealand
- Type
- Internal agency tool - not a public SaaS product and not offered to advertisers outside our contracted client roster
- Users
- quickByte staff operate the pipeline and API connections. Contracted clients may view the reporting dashboards we share with them; clients do not access the APIs directly.
What it does
- A scheduled daily job pulls read-only performance metrics from connected marketing platforms via their official APIs.
- Metrics are joined by date and stored in Google BigQuery - one isolated dataset per client brand.
- Data powers client reporting dashboards built and maintained for accounts we manage under contract.
- No platform data is resold, licensed to third parties, or used for any purpose outside the agreed client reporting described here.
Google Ads API
The pipeline connects to the Google Ads API under the Reporting permissible use. Full terms: Google Ads API Terms of Service.
- Permissible use
- Reporting - read-only only
- API surface used
GoogleAdsServiceSearchStream via GAQL on thecustomerresource- Data pulled
- Daily aggregated metrics: impressions, clicks, cost, conversions, and conversion value
- What we do not do
- No campaign, ad group, ad, budget, or keyword create or edit operations. No Keyword Planner access. No offline conversion uploads. No data sharing or resale.
- Scale
- Approximately 4 contracted client accounts initially; approximately 1 query per account per day
- Authentication
- OAuth 2.0 refresh token per client account; agency developer token with Manager (MCC) access
- Storage
- Agency GCP project; logically isolated BigQuery datasets per client brand - no cross-client data access
Google user data
Use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We do not use Google user data for advertising targeting, profiling, or any purpose beyond the contracted reporting described on this page. We do not sell Google user data.
Meta Marketing API
The pipeline connects to the Meta Marketing API for read-only campaign reporting. Full terms: Meta Platform Terms.
- Permissible use
- Read-only reporting - daily ad account and campaign performance insights
- Metrics
- Spend, impressions, clicks, and purchases (platform-attributed)
- What we do not do
- No ad creation, audience upload, pixel data access, or Conversions API writeback via this pipeline
- Authentication
- Business Manager system user tokens scoped to client ad accounts we manage under contract
- Storage
- Same BigQuery pipeline as other connected platforms; no resale of Meta Platform Data
Meta Platform Data is processed only as described here. To request deletion of data we hold from platform connections, see Data deletion.
Other connected services
The pipeline also connects to the following services in a read-only reporting capacity:
- Google Analytics 4 - read-only channel and session metrics via the Google Analytics Data API
- Google Search Console - read-only query and page metrics via the Search Console API
- Klaviyo - read-only campaign and message performance metrics
- Shopify Admin API - read-only order and revenue data for blended cross-channel reporting
All connections use official, OAuth-authenticated API access scoped to client accounts we manage under contract.
Data flow
Client ad accounts
(Google Ads, Meta, GA4, Search Console, Klaviyo, Shopify)
|
| read-only API pull - daily scheduled job
v
Agency orchestrator
(Node.js, Cloud Run - GCP)
|
v
Google BigQuery
(per-client isolated datasets, agency GCP project)
|
v
Reporting dashboards
(agency-built, shared with contracted clients)
Security & compliance
- All API traffic uses HTTPS/TLS.
- OAuth credentials and API keys are stored in GCP Secret Manager - not in dashboards or source code.
- Client datasets are logically isolated in BigQuery; no cross-client data access.
- Google user data use adheres to the Google API Services User Data Policy including Limited Use requirements.
- Meta Platform Data is processed only as described on this page; deletion requests are honoured within 30 days of a verified request.