-
Notifications
You must be signed in to change notification settings - Fork 146
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
Analytics shows server location traffic instead of customer location #80
Comments
I am having the same issue however I understand this is the "expected" behavior since the requests are coming from the server and not the client (I use this in a chatbot where everything runs on the server). It would be nice to be able to override this somehow. |
You can, the Measurement Protocol parameter |
Hi @jtillmann, does this module support passing these values to override IP and User Agent? If not, I can work of it and send you a pull request. I'm think, these override parameters can be sent as part of visitor options. Something like this:
|
They can not be provided to the visitor options, they need to be provided as parameters to track calls or as persistent parameters. |
Great! I didn't see that part of the documentation. This module already supports passing override parameters. |
Currently experiencing this issue on my fargate instance on AWS. I am setting the vistor using |
@michaelhidalgo using version 0.4.23 seems not have the issue. In my case I needed to downgrade the package. |
Could you check the debug output? There should be no difference between .4 and .5 in this regard. |
Hi folks, this is just a question.
I deployed an application with universal-analytics and the application was deployed into a cloud server, however when accessing the site from Costa Rica, I can see in Google Analytics that the location of the traffic is the on from server, not my remote location.
I used the same samples from this repository and I was wondering if i need to pass somehow the remote ip so it can use my location instead of the server's one.
Thanks.
The text was updated successfully, but these errors were encountered: