Skip to content

Client Onboarding Tracking Setup

Origin: Extracted from memory/client-mcp-ids.md (reference doc) and the /setup-client-tracking skill during knowledge restructure (2026-05-20). The procedure body is preserved verbatim below.

What this covers

When a client onboards, their identifiers must be added to memory/client-mcp-ids.md before the automated monthly report (/monthly-report) can pull their data. This SOP documents the lookup procedure for each identifier.

Step 1: Add the client block to memory/client-mcp-ids.md

Open /Users/jim/Code/Evolve-Agency/memory/client-mcp-ids.md and add a new block at the bottom of the active clients section:

## [Client Name]
- **website:** [domain]
- **gsc_property:** [value — see Step 2]
- **ga4_property_id:** [value — see Step 3]
- **gbp_location:** [value — TBD until manual lookup]

Step 2: Find the GSC property

  1. Open Google Search Console
  2. Use the property selector dropdown to find the client's property
  3. The exact URL shown there is the gsc_property value
  4. Domain properties look like: sc-domain:example.com
  5. URL-prefix properties look like: https://www.example.com/
  6. If the property isn't in GSC yet: mark as TBD (not yet verified in GSC)

Step 3: Find the GA4 property ID

  1. Open Google Analytics
  2. Click Admin (bottom-left gear icon)
  3. Under the "Property" column, click "Property Settings"
  4. The 9-digit number at the top is the ga4_property_id
  5. If not in GA4 or access pending: mark as TBD

Step 4: GBP location (manual)

GBP review data is not available via API — must be pulled manually from the GBP dashboard. Mark as TBD until you have dashboard access. The value is typically the CID (Google Business Profile internal ID) or the place_id format.

Step 5: GHL sub-account (if applicable)

If the client has a GoHighLevel sub-account under Evolve's agency:

- **ghl_location_id:** [sub-account location ID]
- **ghl_dashboard_url:** https://app.gohighlevel.com/v2/location/[id]/dashboard
- **ghl_mcp_access:** ⚠️ NOT accessible via mcp__ghl-evolve__ — that server is locked to Evolve's main location

Step 6: gcloud ADC auth check

Before the first /monthly-report run for a new client, verify GA4 auth is current:

gcloud auth application-default login \
  --scopes="https://www.googleapis.com/auth/analytics.readonly,https://www.googleapis.com/auth/analytics,https://www.googleapis.com/auth/cloud-platform"
gcloud auth application-default set-quota-project evolve-mcp

If GA4 returns auth errors during /monthly-report, this is the fix. The evolve-mcp GCP project is the shared analytics project for all clients.

Reference

Full format and example entries: memory/client-mcp-ids.md

GA4 auth full sequence documented in CLAUDE.md memory feedback_gcloud_adc_auth.md:

gcloud auth application-default login alone is incomplete for GA4. Default scope is cloud-platform only (no analytics.readonly), and the API also requires a quota project. Three-command sequence: (1) re-auth with --scopes=cloud-platform,analytics.readonly, (2) set-quota-project evolve-mcp, (3) verify.