Try or ByeTry or Bye

PostHog Events Not Showing Up

Workaround available Web, iOS, Android, server SDKs Updated October 21, 2026

Quick answer

Missing PostHog events are usually caused by a misconfigured SDK (wrong project key or region host), ad blockers, an app filtering events, or ingestion delay. Check the Network tab for requests to /e, then the Ingestion warnings page.

Most likely fix: Verify the SDK sends requests.

Symptoms

Activity / live events stay empty, new event names don't appear in insight dropdowns, or counts are much lower than expected.

Why it happens

  • Wrong project token or api_host (e.g. US host for an EU project, which should use eu.i.posthog.com)
  • Requests blocked by an ad or tracking blocker
  • A Filter Out app or transformation dropping events
  • Automated browsers (Playwright, Puppeteer, Selenium) filtered as bots
  • Ingestion delay or an ongoing incident
  • Billing limit or free-tier limit reached for product analytics

How to fix it

Try these in order — the most common fix is first.

  1. 1. Verify the SDK sends requests

    1. Open your site, then DevTools > Network
    2. Filter for '/e' or your PostHog host and reload
    3. If no requests appear, check posthog.init() runs and the project token is correct
    4. If requests fail, enable debug mode and read the [PostHog.js] console lines

  2. 2. Check the region host

    1. Open Project settings and note whether the project is US or EU Cloud
    2. Set api_host to the matching host (EU projects use https://eu.i.posthog.com)
    3. Optionally point api_host at webhook.site temporarily to confirm the library sends events at all

  3. 3. Rule out ad blockers

    1. Disable your ad blocker or test in a clean browser profile
    2. If events appear, set up a reverse proxy (managed proxy or your own) for production

  4. 4. Disable apps that filter events

    1. Open Data pipelines and check any Filter Out app or transformation
    2. Temporarily disable it, then all other enabled apps, to find the one dropping events

  5. 5. Check ingestion warnings, status and limits

    1. Open the Ingestion warnings page in the app
    2. Check status.posthog.com for ingestion incidents
    3. Open Organization > Billing to see whether a billing limit stopped ingestion
    4. Send a test event with cURL and allow up to an hour before contacting support

This guide also covers

  • posthog events not showing
  • posthog not capturing events
  • posthog events missing
  • posthog not working
  • posthog no data

Still not working?

If PostHog keeps failing, you're not alone. See every PostHog problem users report or the alternatives people switch to.

Other PostHog errors