What ProAIE does with Meta Ads data
ProAIE is a campaign reporting platform. When a business ("tenant") connects their Meta Ads account, ProAIE reads the spend and performance metrics for their selected ad account and combines those numbers into a monthly performance report alongside data from their other ad platforms (Google Ads, TikTok, LinkedIn), their booking calendar (GoHighLevel), and their payment processors (Stripe, CardPointe).
The reader of the report sees Meta Ads spend on the same page as revenue and can answer "did Meta pay off this month?" without switching tabs.
Scopes ProAIE requests
Read-only. The Meta Login for Business configuration pins the scopes to exactly these two:
ads_read— read spend, impressions, clicks, CTR, CPC and campaign metadata for the ad accounts the tenant explicitly picks.business_management— list the ad accounts the tenant is authorized to report on so the picker can render them.
ProAIE does not request
ads_management, pages_manage_*,
instagram_* writes, or any user-data scope.
What ProAIE reads (endpoints)
The integration calls exactly these Meta Graph API endpoints, all read-only:
GET /me/adaccounts— list the ad accounts the tenant granted access to, so the tenant can pick which one feeds the report.GET /{ad_account_id}/campaigns— list campaign IDs + names + status for the picker and the report's campaign ledger.GET /{ad_account_id}/insights— fetch spend, impressions, clicks, CTR, CPC per campaign for the report window (typically last 30 days). This is the only data-reading call.
Present integration scope
The current Meta integration is limited to the two read-only scopes and three endpoints listed above. It does not call any campaign-mutation, audience, creative, budget, organic-content, Messenger, Groups, or user-profile endpoint. 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 Meta data with third parties.
- ProAIE does not use Meta 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. Encrypted at rest. Only used server-side to call the endpoints above.
- Ad account ID and display name. Shown in the report and the tenant's Settings page so they can see which Meta 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 Meta source row, click Disconnect. ProAIE deletes the encrypted credential and stops calling the Meta API for that source.
- On Meta's side. Revoke the app in Facebook → Settings → Business Integrations. ProAIE detects the invalidated 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 Meta integration, or requests to delete specific Meta data: sales@proaie.com.
General policy: Privacy Policy.