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
1st and 3rd party cookie issues #7100
Comments
I haven't used 3rd party cookies so far therefore I can't say so much. I'd assume they are already both the same. Can you maybe to something like When talking about tracking goals on the backend you mean in your backend right? Not the Piwik backend? Do you access the 1st party cookie there to get the visitorId? |
@tsteur yes i'm talking about a "custom/own" backend. I can only access the 1st party cookie, since by security (and thats good) you never receive 3rd party cookies. But yes AFAIK the cookie differ. Backend goals were always tracked as a new visitor. Multiple goals from the same user of course as the same visitor. |
sure, you can't access 3rd party cookies on your own backend. I was wondering if you could get the 3rd party visitor id via the above mentioned JS method, then use this value to set a 1st party cookie. Might be a solution/hack until it is fixed. I'm not sure if the current behaviour is like this by design maybe ping @mattab |
Hi @ThaDafinser if you think there is a bug or something we could improve in Piwik, could you please describe the steps to reproduce / describe the feature or so? |
@ThaDafinser please reopen if you can clarify the issue, or create a new one with steps to reproduce etc. thanks |
What i want to do?
I'm using piwik on many intranet sites, so i would like to use 3rd party cookie, that the visit is always the same accross the websites. This is currently easy to achieve and works.
But as soon as you would like to track e.g. goals on the backend it will be a problem, since the backend wont get the visitorId from the 3rd party cookie.
Only solution: use for 1st and 3rd party cookie the same visitorId.
If my thoughts gone right so far, the new userId feature would also benefit from it, since its only one visit the userId will be available accross all websites if it was set on at least one website.
(there are intranet wesites with a userId and some without)
The text was updated successfully, but these errors were encountered: