SETTINGS

API Connections

Manage credentials and test connectivity for all platform integrations.

Integrations

5 configured

Meta Ads

System User token for Meta Marketing API. Used for campaign management, lead form delivery, and pixel data.

Disconnected

META_ACCESS_TOKEN

META_AD_ACCOUNT_ID

META_APP_SECRET

META_WEBHOOK_VERIFY_TOKEN

Pixel ID and Page ID are stored per-client in their profile.

Google Ads

MCC Manager Account via Google Ads API v20 REST. Uses OAuth2 refresh token for all client sub-accounts. 35 accounts accessible.

Disconnected

GOOGLE_ADS_DEVELOPER_TOKEN

GOOGLE_ADS_CLIENT_ID

GOOGLE_ADS_CLIENT_SECRET

GOOGLE_ADS_REFRESH_TOKEN

GOOGLE_ADS_LOGIN_CUSTOMER_ID

Developer token is Basic Access. Login customer ID is the MCC account — individual client IDs are stored per-client.

GRO Lead Terminal

Agency-level API key for sub-account management, contact sync, lead routing, and funnel deployment.

Disconnected

GHL_API_KEY

GHL_LOCATION_ID

Location ID is optional — sub-account location IDs are stored per-client.

Supabase

PostgreSQL database for client profiles, campaign configs, and platform state.

Disconnected

NEXT_PUBLIC_SUPABASE_URL

NEXT_PUBLIC_SUPABASE_ANON_KEY

SUPABASE_SERVICE_ROLE_KEY

Claude (Anthropic)

Powers the AI Command Center, funnel copy generation, and ad copy optimization.

Disconnected

GRO_ANTHROPIC_API_KEY

Updating Credentials

All API keys are stored in .env.local at the project root. Edit that file directly to add or rotate credentials, then restart the dev server for changes to take effect. Never commit .env.local to version control. Use the Test button on each card to verify live connectivity after updating keys.