Skip to main content

Runbook: Google Analytics Permission Issue

ServiceWebku x Tripla Page
Owner Team slack handle@bnl-dev-bali
Team's Slack Channel#bnl-teams-b

Table of Contents​

  • [[#Important Links]]
  • [[#1. Triage]]
  • [[#2. Decision Point]]
  • [[#3. False Alarm]]
  • [[#4. True Incident]]
    • [[#4.1. Recover the System]]
    • [[#4.2. Clean up]]
Alert[Sentry Issue Link – AxiosError Network Error]
Logs[Browser DevTools Network Tab]
DashboardConfiguration → Integration → Google Analytics Report
Google Analytics Adminhttps://analytics.google.com

1. Triage​

Goal: Confirm whether the issue is caused by Google Analytics permission misconfiguration.

  1. Open the Sentry issue.
  2. Confirm error message:
AxiosError: Network Error
  1. Open browser DevTools → Network tab.
  2. Locate request to Google Analytics API.
  3. Check response status.
  • Is response 403 Forbidden?
  • Was Property ID recently changed in:
Configuration → Integration → Google Analytics Report
  1. Confirm whether service account email has access:
analytic-report@bnl-webku.iam.gserviceaccount.com

2. Decision Point​

  • IF API response is 403 and service account lacks permission...

    • ➡️ Go to: [[#4. True Incident]]

  • IF API response is 200 and report loads normally...

    • ➡️ Go to: [[#3. False Alarm]]

3. False Alarm​

  1. Confirm analytics report loads.
  2. Confirm API returns 200 OK.
  3. Monitor Sentry for recurrence (15 minutes).

Post in Slack:

Sentry alert reviewed. No active permission issue detected.
Monitoring for recurrence.

4. True Incident​

Impact:

  • Google Analytics report does not load.
  • Users cannot view analytics inside Webku dashboard.

4.1. Recover the System​

Diagnostic Steps

  1. Confirm 403 response.
  2. Confirm incorrect or changed Property ID.
  3. Check Google Analytics → Property Access Management.

Remediation Plan

  1. Grant Viewer access to:
analytic-report@bnl-webku.iam.gserviceaccount.com
  1. Role must be:
Viewer
  1. Save changes.
  2. Refresh Webku dashboard.

Verification

  • API response returns 200.
  • Analytics report loads successfully.
  • No new AxiosError logs in Sentry.

Reference: How to Connect Google Analytics to Webku Dashboard

4.2. Clean up​

  1. Confirm no analytics configuration corruption.
  2. Notify client if misconfiguration was client-triggered.
  3. Monitor Sentry for 30 minutes.
  4. Document incident if repeated.