-
Notifications
You must be signed in to change notification settings - Fork 222
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
Add functionality to set the Network User Id #1236
Comments
I like the flexibility of this approach but I'm a little wary of overriding a tracker protocol parameter when the
Have you considered using a global context for this? This should only require defining once and then will get attached to all subsequent requests. |
HI @miike, yes the global context is also what I was referring to. We'd prefer to use network user ID as that is it's intended purpose. A custom context added to every hit would also increase the size of the payload much more than the network user ID would. The parameter would only be overridden if you use this function otherwise the tracker would take the default behaviour. |
Thanks - I think if the end user is aware of any downstream impacts of overriding the @igneel64 We could probably just wrap |
This comment was marked as spam.
This comment was marked as spam.
We would be happy to add a At the moment we can't support persisting the NUID as this is a major change in the behaviour of the collector. Can you let us know if the proposed change works for you? |
Just following up on this, is this something that you would find useful or does this not fix your problem? |
Hi @Jack-Keene, Sorry for the delayed response. Yes the value is stored in a cookie set from in the HTTP header server response. This should always be present and should persist. I do get that this would need to exist on every hit if we wanted to join these hits together. Thanks, |
Is your feature request related to a problem? Please describe.
I need to set my own Network User ID. The advantages of setting a seperate value is that it is one defined by the platform to give a common anonymous user ID. This way different tools can have a same user definition.
Another major advantage is guarding against Apple ITP resetting the user ID on every return visit.
The collector cookie (Network user ID) is designed to solve this but another difficulty is that we use an API gateway that is on a seperate domain to our customer facing sites. If we did get the header cookie to be forwarded it would not resolve our issue.
Describe the solution you'd like
A new function
setNetworkUserId
and/orsetNetworkUserIdFromCookie
that sets thetnuid
value in the tracker protocol.Describe alternatives you've considered
Setting a new custom context including the value. The main disadvantages with this are:
Additional context
The tracker protocol offers a network user override here. It would make sense give the option to use this.
The text was updated successfully, but these errors were encountered: