Google Ads API Use

Last updated: May 26, 2026

Who we are

Kivolaro is a custom software and AI-automation studio. We help our clients (and ourselves) replace spreadsheet-driven operations with integrated tooling. The Kivolaro Studio is our internal admin application at studio.kivolaro.com, used only by Kivolaro staff — there is no public sign-up and no third-party access.

How we use the Google Ads API

The Studio integrates with the Google Ads API for one purpose only: to read the daily performance metrics of Google Ads campaigns we run on our own ad account (impressions, clicks, cost, conversions, lead counts), and to push back first-party offline conversions when a lead generated through a Google Ads campaign closes into a paying customer.

The integration does NOT:

OAuth scopes requested

Data we read

From our own Google Ads account, on a daily schedule:

Nothing personally identifying about end-users is requested. Lead-level attribution lives in our own first-party CRM (Firestore) keyed by anonymous gclid / wbraid / gbraid identifiers that Google provides for measurement.

Data we write

Where the data lives

Security

User rights

The Studio is operated exclusively by Kivolaro staff. Any data subject rights (access, deletion, correction) over campaign metrics that originate from Google Ads are governed by Google's own platform terms; over leads or business contacts stored in our CRM, by our Privacy Policy and the GDPR/CCPA rights enumerated there.

Compliance contact

Questions about this integration: hello@kivolaro.com.

Privacy Policy · Terms of Service

WhatsAppProblem
Google Ads API Use