GA4 Data Verification

Lumara /products/viso Page

Claim-by-Claim GA4 Verification Report — Oct 6 to Nov 2, 2026

⚠
GA4 Data Unavailable. Both access methods (GA4 Data API and Windsor.ai) are currently blocked. None of the 7 claims below can be verified until access is restored.
GA4 Property
Connected Property Details
Property ID
300388401
Account Name
Illuminate
Name mismatch with "Lumara"
Linked
Today
Nov 3, 2026
Verification Matrix
7 Claims Assessed
# Claim Stated Value Our Finding Verdict
1
VISO page engagement rate
Compared to site average during Oct 6 to Nov 2
30.44% No GA4 page-level data accessible Unverifiable
2
Site-wide average engagement rate
Baseline comparison metric for the full site
53.92% No GA4 site-level data accessible Unverifiable
3
VISO page bounce rate
Higher than site average of 46.08%
69.56% No GA4 page-level data accessible Unverifiable
4
VISO page active users
Total users landing on /products/viso during the period
7,778 No GA4 page-level data accessible Unverifiable
5
Engagement peak on Oct 30
Claimed upward trajectory throughout October
76.79% No GA4 daily trend data accessible Unverifiable
6
Engagement dip on Nov 2
Drop from peak, flagged as below expected range
48.28% No GA4 daily trend data accessible Unverifiable
7
Traffic shift (active users decline)
First half vs. most recent 14-day period
838 → 625 No GA4 period comparison accessible Unverifiable
Access Blockers
Why GA4 Data Is Unavailable

Two independent systems can pull GA4 data. Both are currently blocked for Lumara's property.

Blocker 1
GA4 Data API (ga4_query)
The native Google Analytics 4 Data API can query page-level metrics (pagePath, engagementRate, bounceRate, activeUsers by page). However, it requires a Google Service Account JSON key to be configured in our team_secrets table. This is not currently set up.
Fix: Add GOOGLE_SERVICE_ACCOUNT_JSON to team_secrets, grant Viewer access on GA4 property
Blocker 2
Windsor.ai GA4 Connector
Windsor.ai sees the GA4 property (300388401 / "Illuminate") in its account list, but returns 0 rows for every query. The account name "Illuminate" triggers a name mismatch warning against "Lumara." Additionally, the GA4 property may not be fully connected on Windsor's backend.
Fix: Verify GA4 property is connected in Windsor.ai dashboard, or resolve account name mismatch
Verification Requirements
GA4 Queries Needed to Verify All 7 Claims

Once GA4 access is restored, these are the exact queries that will confirm or refute each claim:

Resolution Path
How to Unlock GA4 Verification
  1. Configure Google Service Account
    Create a Google Cloud service account (or use an existing one), download the JSON key file, and add it to the team_secrets table as GOOGLE_SERVICE_ACCOUNT_JSON. This unlocks the GA4 Data API for ALL clients.
    One-time setup (unlocks all GA4 clients)
  2. Grant Viewer Access on GA4 Property
    In Google Analytics admin for the Illuminate property (300388401), add the service account email as a Viewer. The email will look like name@project.iam.gserviceaccount.com.
    Quick (2 minutes per property)
  3. Run All 5 Verification Queries
    Once access is live, all 7 claims can be verified in under 60 seconds. The queries listed above will be executed automatically, and each claim will be stamped as Confirmed, Partially Confirmed, or Refuted with the actual numbers.
    Automated (under 1 minute)

Bottom Line

The GA4 property for Lumara (300388401 / Illuminate) was linked today, but neither of our two GA4 data pipelines can currently pull page-level metrics. All 7 claims about the /products/viso page (engagement rate, bounce rate, active users, daily trends, traffic shifts) remain unverifiable until the Google Service Account JSON is configured. This is a one-time setup that unlocks GA4 access for every client, not just Lumara. Once done, full verification takes under a minute.