We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I have tracking code in php and js.
res
screen resolution
Unknown
If I remove step 2, so first tracking request goes from frontend it works fine, screen resolution is presented in visitor's profile.
Is it intended behaviour? Can I fix it? Should backend tracking request be executed after frontend tracking request for correct metrics?
The text was updated successfully, but these errors were encountered:
Why are you making a "backend tracking" request at all? Is it to not miss any tracking requests that might be blocked by ad blockers or similar?
Sorry, something went wrong.
Yes. This request is generated on initial page load. Is this not fixable by design and first request must be done on frontend? @sgiehl
It's by design that only the first tracked request is able to set the resolution. It requires some code changes to change that behaviour
Btw. Mixing both tracking methods might result in duplicate page views.
No branches or pull requests
I have tracking code in php and js.
res
parameterscreen resolution
asUnknown
If I remove step 2, so first tracking request goes from frontend it works fine, screen resolution is presented in visitor's profile.
Is it intended behaviour? Can I fix it? Should backend tracking request be executed after frontend tracking request for correct metrics?
The text was updated successfully, but these errors were encountered: