You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After I upgraded my to posthog-js version from 1.117 to 1.128.1, I noticed that insights broke down by referring domain suddenly started being dominated by my domain.
I grabbed a screenshot as an example:
You can see here that pageviews from colorbliss.art started spiking on the day that I upgraded to posthog-js@1.128.1. To test this, I downgraded to posthog-js@1.119.2 yesterday to see if that would change anything. You can see in the screenshot that www.google.com spiked and colorbliss.art dropped.
Not sure if others have experienced the same.
This is especially visible on events I capture around purchases, since 95% of those events now have no meaningful referral data.
I haven't yet narrowed down which version of posthog-js introduced the error. I've looked through the release log and didn't see anything obvious to me that looked like a fix for it either.
I can keep experimenting with versions, but just wanted to flag in case others are seeing the same.
The text was updated successfully, but these errors were encountered:
After I upgraded my to posthog-js version from 1.117 to 1.128.1, I noticed that insights broke down by referring domain suddenly started being dominated by my domain.
I grabbed a screenshot as an example:
You can see here that pageviews from
colorbliss.art
started spiking on the day that I upgraded toposthog-js@1.128.1
. To test this, I downgraded toposthog-js@1.119.2
yesterday to see if that would change anything. You can see in the screenshot thatwww.google.com
spiked andcolorbliss.art
dropped.Not sure if others have experienced the same.
This is especially visible on events I capture around purchases, since 95% of those events now have no meaningful referral data.
I haven't yet narrowed down which version of
posthog-js
introduced the error. I've looked through the release log and didn't see anything obvious to me that looked like a fix for it either.I can keep experimenting with versions, but just wanted to flag in case others are seeing the same.
The text was updated successfully, but these errors were encountered: