Metrivo
Docs

Troubleshooting

Start with the setup checklist at /app/setup. It turns steps green only after Metrivo sees the real signal.

Common blockers

  • No pageviews: confirm data-site uses the current public key and check /api/tracking/verify.
  • Rejected events: confirm allowed origins include the website domain and custom properties use scalar values only.
  • No attribution: pass window.Metrivo.getAttributionMetadata(), provider customer IDs, customer email, or UTM metadata into payment events.
  • Manual Payment API fails: use an active backend key with payments:write and a website in the same workspace.
  • Experiment events fail: use a running experiment UUID and variant control or variant.
  • AI-search looks low: hidden or direct visits stay unknown unless Metrivo has reliable referrer or payment evidence.

Relevant environment variables

  • TRACKING_SALT hashes client IP data for tracking ingestion.
  • TRUST_PROXY_HEADERS controls whether forwarded IP/country headers are trusted.
  • API_KEY_SALT hashes stored API keys for Manual Payment API authentication.
  • SENTRY_DSN and NEXT_PUBLIC_SENTRY_DSN enable optional Sentry-compatible monitoring forwarding.