Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

scope utm parameters and referrer to a session #477

Closed
pjhul opened this issue Nov 30, 2022 · 0 comments · Fixed by #496
Closed

scope utm parameters and referrer to a session #477

pjhul opened this issue Nov 30, 2022 · 0 comments · Fixed by #496
Labels
bug Something isn't working

Comments

@pjhul
Copy link

pjhul commented Nov 30, 2022

Context

Recently, I made some changes to how we track events on posthog.com, and afterwards we noticed a fairly significant drop when looking at insights filtering based on UTM source and Referrer. After some digging, we found that this had to do with the fact that we persist UTM and Referrer information using a super property.

Before, we were seeing an inflated number of users with a specific UTM source, which was caused by users returning back to the website during a later session, but still having a UTM source sent on their events.

Solution

Ideally, we do still want these properties to be persisted, but only within a session rather than indefinitely. It looks like we do have the sessionStore object already. Perhaps creating a register_session function that registers a super property using the sessionStore?

Overall, I think this should be given quite high priority, as it affects some pretty critical properties, especially for marketing teams.

Further context

@pjhul pjhul added the bug Something isn't working label Nov 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant