Open gmilon opened 1 week ago
let response = await caches.default.match(request)
just a fly-by comment that we keep a short TTL on the main static assets so they update when we release new versions (which happens frequently) so it's worth making sure you're not extending their lifetime too much with his statement 🤞
there are two kinds of heatmaps in posthog
$heatmap_data
property which is extracted during ingestionif you set posthog.debug(true)
in the console, or use the toolbar's event debugger you'll be able to see if events are being sent and if they include heatmap data.
is the site public for us to take a look?
Bug Description
Bug description
Not sure if this is something related to our account settings or if it affects other users. We are not getting any heatmap or autocapture events from our web frontend app with a custom proxy.
How to reproduce
Observations:
We can see the clicks are tracking in the posthog admin, we even see session replay with clicked event attached to it.
It seems like the proxy is working as expected the first /decide API call returns a 200 response with the config.
When we open the heatmap we don't see any data coming from the API: the https://eu.posthog.com/api/heatmap/ endpoint returns a 200 with an empty result:
Debug info