Integrations#
Vector connects to your existing analytics platforms to analyze your data and generate recommendations.
Supported Platforms#
PostHog#
Best for: Product analytics, feature flags, session replays
PostHog provides rich product analytics data that Vector uses to identify:
- Feature adoption patterns
- Funnel drop-offs
- User behavior anomalies
- Engagement trends
Setup
- Log into PostHog
- Go to Settings → Personal API Keys
- Create a new key with read access
- Copy the key (starts with
phx_) - Find your Project ID in the URL:
app.posthog.com/project/[ID]
Required Permissions
Your API key needs access to:
project:read- Read project datainsight:read- Access dashboards and insightsevent:read- Query event data
Umami#
Best for: Privacy-focused web analytics, self-hosted setups
Umami provides clean, privacy-respecting analytics that Vector uses for:
- Traffic patterns
- Page performance
- Referrer analysis
- Geographic insights
Setup
- Log into your Umami dashboard
- Go to Settings → API Keys
- Create a new API key
- Find your Website ID in Websites → [Your Site] → Settings
Self-Hosted Notes
If you're running Umami self-hosted:
- Ensure your instance is accessible from the internet (or use a tunnel)
- Use HTTPS for secure credential transmission
- Vector connects directly to your Umami API
Google Analytics 4#
Best for: Web traffic, marketing attribution, e-commerce
GA4 provides comprehensive web analytics that Vector analyzes for:
- Acquisition channel performance
- User journey mapping
- Conversion optimization opportunities
- Audience segmentation insights
Setup
GA4 requires a service account for API access:
- Go to Google Cloud Console
- Create a new project (or select existing)
- Enable the Google Analytics Data API
- Create a Service Account:
- Go to IAM & Admin → Service Accounts
- Create account with a descriptive name
- Download the JSON key file
- Grant access in GA4:
- Go to GA4 Admin → Property Access Management
- Add the service account email as a Viewer
- Find your Property ID in GA4 Admin → Property Settings
Service Account JSON Format
The JSON key file should contain:
{
"type": "service_account",
"client_email": "[email protected]",
"private_key": "-----BEGIN PRIVATE KEY-----\n...\n-----END PRIVATE KEY-----\n",
...
}
Coming Soon#
- Mixpanel - Event analytics
- Amplitude - Product analytics
- Heap - Auto-capture analytics
- Plausible - Privacy-focused analytics
Integration Status#
| Status | Meaning | |--------|---------| | Connected | Active and syncing data | | Pending | Credentials saved, awaiting verification | | Error | Connection failed (check credentials) | | Not Connected | Not yet configured |
Troubleshooting#
"Connection failed" error#
- Verify your API key is correct and not expired
- Check that the key has required permissions
- Ensure the host URL is correct (including
https://) - For self-hosted: verify the instance is reachable
"Unauthorized" error#
- Your API key may have been revoked
- Permissions may have changed
- Try generating a new API key
Data not appearing#
- Allow 5-10 minutes for initial sync
- Click Sync to manually refresh
- Check that your analytics platform has recent data