Loading Glimmio…
Loading Glimmio…
Glimmio uses Google's OAuth 2.0 to access your Google Ads account. Here is what is requested and why.
Sign in with Google asks only for your name and email address, so that Glimmio can create or match your account. It grants no access to your advertising data. Connecting Google Ads is a separate step, and its permissions are requested then — not at sign-in.
https://www.googleapis.com/auth/adwords
The Google Ads API scope. It covers reading campaign data, performance reports, keyword data, and search term reports. It also allows making changes to campaigns (budgets, pausing, keyword management) when you approve an action.
https://www.googleapis.com/auth/datamanager
Uploads your own store's conversion events back to your Google Ads account, so campaign reporting reflects what actually sold. Google retired the older conversion upload method for new integrations, so this is the only available path.
https://www.googleapis.com/auth/content
Merchant Center, through the Content API for Shopping. Glimmio reads your account status and per-product approval results so it can show which products Google disapproved and what the fix is. This is read-only — Glimmio does not edit your Merchant Center settings or submit changes to your product feed.
https://www.googleapis.com/auth/gmail.send
Requested only if you pick Gmail as the sender for lifecycle email, and never as part of the Google Ads connection. It permits sending the messages you compose in Glimmio and nothing else — we cannot read, search, or download anything in your mailbox.
Campaign data is stored in Glimmio's PostgreSQL database and restricted to the connected business account.
You can revoke Glimmio's access from Google Account → Security → Third-party apps with account access → Glimmio. Access can also be removed from Settings → Integrations → Google Ads → Disconnect in Glimmio.