Google Ads API access and Read-only user enforcement
- Google Ads API scope vs. Read-only Google Ads user role: Google’s official Google Ads API provides a single OAuth scope (
https://www.googleapis.com/auth/adwords), so Google’s OAuth consent screen always displays "See, edit, create, and delete your Google Ads accounts and data". Karsa.ai’s connector executes only read-only Google Ads Query Language (SELECT) requests and contains zero campaign, bid, or budget mutation calls. Because Google Ads API tokens inherit the permissions of the authorizing Google user, connecting a dedicated user account granted only the Read-only role in Google Ads (Admin → Access and security, without higher inherited MCC permissions) enforces read-only access on Google’s servers: any mutate request fails with an authorization error from Google. - Pull-only supplemental XML source in Google Merchant Center: Karsa.ai does not require write access to your Merchant Center account or online store database. Karsa.ai hosts a tokenized HTTPS XML file containing only
<g:id>and<g:custom_label_X>, which Google Merchant Center fetches on schedule.
Data inventory: what Karsa.ai processes — and what it never touches
| Data Category | Processed by Karsa.ai? | Details |
|---|---|---|
Product Catalog XML (id, title, price, category, brand, availability) |
Yes | Used for nightly statistical prediction and cluster diagnostics |
| Aggregated Google Ads SKU & Campaign Metrics | Yes | Impressions, clicks, cost, conversions, conversion value, impression share |
| Optional Wholesale COGS / Margin % | Optional (Encrypted) | Used server-side for net profit & break-even ROAS; never exported in public feeds |
| End-Customer PII (Names, Emails, Phones, Addresses, IPs) | Never | Zero shopper personal data is collected, transmitted, or stored |
| Storefront Checkout / Browser Cookies | Never | Zero storefront JavaScript tags or checkout pixels |
EU hosting, encryption, and vulnerability disclosure
All Karsa.ai application servers and databases run in European Union data centers with TLS 1.2/1.3 encryption in transit, encrypted credential storage at rest, and tenant isolation. Security researchers can reach our security team directly via our security contact form (see /.well-known/security.txt).
Frequently asked questions
Why does Google’s OAuth consent screen show edit permissions, and how does Karsa.ai enforce read-only access?
Google’s official Google Ads API defines a single OAuth scope (https://www.googleapis.com/auth/adwords), which displays the standard prompt 'See, edit, create, and delete your Google Ads accounts and data' because Google offers no separate read-only OAuth scope. First, Karsa.ai’s connector executes only read queries (GAQL SELECT) and contains zero mutate calls. Second, if you authorize Karsa.ai with a dedicated Google user that holds only the Read-only access level in Google Ads (and no higher inherited permissions via a Manager / MCC account), Google’s API servers reject any mutate call with a permission error.
Does Karsa.ai process customer names, emails, IP addresses, or order addresses?
No. Karsa.ai never ingests shopper PII, browser cookies, or customer order records. It processes only product catalog identifiers, SKU prices/margins, and aggregated Google Ads performance metrics.