What ProAIE does with Google Ads data
ProAIE is a campaign reporting platform. When a business ("tenant") connects their Google Ads account, ProAIE reads the spend and performance metrics for their selected customer and combines those numbers into a monthly performance report alongside data from their other ad platforms (Meta, TikTok, LinkedIn), their booking calendar (GoHighLevel), and their payment processors (Stripe, CardPointe).
The reader of the report sees Google Ads spend on the same page as revenue and can answer "did Google pay off this month?" without switching tabs.
Scopes ProAIE requests
Read-only. Only one Google OAuth scope is requested:
https://www.googleapis.com/auth/adwords— read campaign spend and performance for the customer accounts the tenant explicitly picks. Google Ads API additionally requires an approved developer token, which ProAIE holds at the platform level for its verified Cloud project.
ProAIE does not request Analytics, Search Console, Merchant Center, Drive, Calendar, or any other Google scope.
What ProAIE reads (endpoints)
The integration calls exactly these Google Ads API endpoints, all read-only:
GET /{version}/customers:listAccessibleCustomers— list the Google Ads customer accounts the tenant granted access to, so the tenant can pick which one feeds the report.POST /{version}/customers/{cid}/googleAds:searchwith the querySELECT customer.descriptive_name, customer.currency_code, customer.time_zone FROM customer— resolve the customer's display name for the report header.POST /{version}/customers/{cid}/googleAds:searchwith the querySELECT campaign.id, campaign.name, campaign.status, campaign.advertising_channel_type FROM campaign— list campaigns for the picker and campaign ledger.POST /{version}/customers/{cid}/googleAds:searchwith a metrics query pullingmetrics.cost_micros,metrics.impressions,metrics.clicks,metrics.ctr,metrics.average_cpcfor the report window (typically last 30 days). This is the only data-reading call per report.POST /oauth2/token(Google identity endpoint) — refresh the short-lived access token using the tenant's stored refresh token.
Present integration scope
The current Google Ads integration is limited to the single
adwords scope and the read-only endpoints listed
above. It does not call any campaign-mutation, audience, keyword,
or budget-write endpoint, and does not access any other Google
product (Search Console, Analytics, Merchant Center, Drive,
Calendar, etc.). Data handling posture:
- ProAIE does not access audience demographics or user-level data — only aggregated per-campaign performance metrics.
- ProAIE does not sell or share Google Ads data with third parties.
- ProAIE does not use Google Ads data to train machine learning models.
If a future version adds any additional scope or campaign- management endpoint, this page will be updated to name it and the tenant will be re-prompted to authorize the added scope before it takes effect.
What ProAIE stores
- Access token and refresh token. Encrypted at rest. Only used server-side to call the endpoints above.
- Customer ID and display name. Shown in the report and the tenant's Settings page so they can see which Google Ads account is wired up.
- Aggregated performance snapshot. The per- campaign spend/impressions/clicks numbers so past reports render consistently. No user-level or audience data.
How the tenant revokes access
- In-app. Open the report's Settings page, find the Google Ads source row, click Disconnect. ProAIE deletes the encrypted credential and stops calling the Google Ads API for that source.
- On Google's side. Revoke the app at myaccount.google.com/permissions. ProAIE detects the invalidated refresh token on the next fetch and surfaces a "reconnect required" state in the report.
- Delete the whole ProAIE account. Every connector is removed at once. Instructions on Data deletion.
Contact
Questions about the Google Ads integration, or requests to delete specific Google Ads data: sales@proaie.com.
General policy: Privacy Policy.