Every problem ValiqAI finds shows how many real people reached its page in the last 7 days, from your PostHog pageviews: "142 people in the last 7 days". A blocker on a page nobody visits can wait; one on your sign-up page can’t.
Pages are matched by path, so visits on production count for a problem ValiqAI found on staging. ValiqAI only reads: one small count per scan, cached for an hour, with a key that can query and nothing else.
How it works
- A scan finds problems. Each on a page: /signup, /checkout, /forgot-password.
- ValiqAI asks PostHog. How many distinct people viewed those paths in the last 7 days, in one query.
- Each problem shows it. Real users, right next to the page, so the team fixes what hurts most first.
Set up
In ValiqAI, open Integrations › PostHog in your workspace.
- In PostHog, create a personal API key with the Query Read and Project Read permissions.
- Paste it here and pick your region (or your self-hosted address).
- Pick the project your site sends events to.
Plan
PostHog is on the Teams plan (Teams and Enterprise). A connection made before a plan change keeps working.
With AI tools
With the ValiqAI MCP server added to your AI coding tool, you can ask:
- “Which blocker from the last ValiqAI scan of staging affects the most real users?”
- “Scan the checkout flow with ValiqAI and rank the problems by how many people reach each page.”