Support

In Google Analytics, open Admin → Property details. The property ID is the numeric value shown there, usually nine digits, like 123456789. It is not the measurement ID that starts with G-, and not the tracking ID that starts with UA-. SiteGlance asks for it on first run.

One that has at least Viewer access on the property you want to watch. If you can open the property in the Analytics web interface with that account, SiteGlance can read it. If you manage several properties, sign in with the account that can see the one you care about — SiteGlance shows one property at a time.

No. It is free, has no in-app purchases, no subscription, and no ads.

An iPhone on iOS 17 or later. The Watch app and its complications need watchOS 10 or later on a paired Apple Watch. There is no iPad or Mac version.

SiteGlance’s Google OAuth consent screen is in Google’s Testing status. Google expires sign-ins for unpublished apps after about seven days, for every app in that state — nothing has gone wrong with your account or with the app.

When it happens, background updates stop and the app shows the sign-in screen with a short note explaining why. Tap Sign in with Google and everything resumes, including the widgets, on the next refresh. Your property ID is remembered, so it is one tap.

On Google’s consent screen there is a checkbox for the Analytics permission, separate from choosing your account. If it is left unticked, sign-in completes but SiteGlance has nothing it can read, and it says so rather than showing an empty dashboard. Sign in again and make sure the Analytics permission is ticked before continuing.

That warning appears for any app whose consent screen has not been through Google’s verification review. It is about the app’s status with Google, not about what the app does with your data. SiteGlance requests one read-only Analytics permission and stores everything on your device — the privacy policy sets out exactly what is accessed.

Usually one of four reasons, all of them expected:

• Today is partial. Today’s figure changes all day and Google revises recent data as it finishes processing.
• Time zone. Days are counted in your GA4 property’s configured time zone, not your phone’s.
• The metric. SiteGlance shows page views (screenPageViews). A report showing sessions, users, or active users counts something different.
• Freshness. A widget shows the last successful refresh, which may be some minutes or hours old. Open the app and pull down to fetch now.

The channel breakdown covers today or the last 7 days. The trend chart covers the last 7, 14, or 30 days. The switches work directly on the Home Screen widget without opening the app: the app has already fetched 30 days plus both channel breakdowns, so switching re-slices data that is already on your device rather than fetching anything.

Those names come straight from GA4’s default channel grouping and vary per property. SiteGlance renders whatever Google returns rather than mapping it to a fixed list. "Unassigned" means Google could not attribute those sessions to a channel — typically missing or stripped campaign parameters. The top four channels get a bar each; the rest are listed by name underneath.

Not today. SiteGlance shows page views for one property, which is what fits a glanceable widget. If multiple properties or another metric would be useful to you, say so by email — it is a short list and real requests move it.

iOS decides when a widget may refresh, and it budgets that tightly to save battery — a handful of updates a day is normal, and iOS gives fewer when battery is low, Low Power Mode is on, or you rarely look at that widget. SiteGlance cannot override this; no app can.

To force fresh data now, open the app and pull down to refresh. The widgets update from the same fetch. If widgets are stale for more than a day, see the troubleshooting steps below.

The widgets never touch the network at all — they only read a cache the main app wrote. The app fetches in the background at most about every 30 minutes, and only when iOS grants the request; each fetch is three small API calls. Tapping a range switch on a widget makes no network request whatsoever.

The Watch never signs in and never fetches anything itself: it receives a copy from the iPhone after each successful refresh. So if the Watch is empty, start on the phone.

• Open SiteGlance on the iPhone and pull down to refresh. That pushes a fresh copy across.
• Check the Watch is paired, in range or on the same Wi-Fi, and unlocked.
• Open the SiteGlance app on the Watch once, so watchOS has run it at least once.

Open SiteGlance, tap the gear icon at the top right, then Sign Out & Delete Data. That removes the Google sign-in tokens, every cached figure on the iPhone and the paired Watch, and your saved property ID. Deleting the app removes what is left.

To revoke the app’s access to your Google account entirely, go to Google Account Permissions, find SiteGlance, and choose Remove Access. Full instructions are in the privacy policy.

No. It holds one read-only permission and there is no code in it that writes anything to Google. It cannot alter, delete, or create data in your Analytics property, and it cannot see any property other than the one whose ID you entered.

No. It talks to Google’s sign-in and Analytics endpoints and to nothing else. There is no SiteGlance server, no account, no analytics SDK, and no crash reporter. Your figures are cached on your own device and nowhere else.