Hot answers tagged

2

It means that you should remove/destroy all traces of the person when they log out or the browser (or tab) is closed (if possible). You don't want the next person to sit down at the computer to have hint of what the last person was doing or see anything that belongs to them.


2

From what I understand your main objective is to re-target your website visitors. It doesn't really matter from which source they first came to your website as long as they came and if you had google analytics installed you can re-target them. There is no need to do anything with the cookies. In your Google Ads account you have to go to: Tools&...


1

RewriteCond %{HTTP_COOKIE} sbjs_migrations|sbjs_current_add|sbjs_first_add|sbjs_first|sbjs_current|sbjs_udata RequestHeader unset Cookie Note that RewriteCond (mod_rewrite) and RequestHeader (mod_headers) are unrelated. You need to modify/edit the Cookie HTTP request header to remove just those specific cookies, which you can do using the RequestHeader ...


1

At first glance the problem does not appear related to SameSite restrictions in the new Chrome v80. Apparently, that is exactly what causes the problem. When the user is in the bank payment portal and has successfully paid, he is redirected back to the ecommerce site by a POST request to the "ok" URL. This POST request is seen as a crosssite request, thus ...


1

MyDomain1.example is my current domain and OtherDomain1.example is one of an external domain so Our Server that belongs to MyDomain1.example check if there is any request to OtherDomain1.example and do remaining... I still think I'm missing something here? It sounds like you are wanting to intercept and modify the request coming from your site MyDomain1....


1

The ID is contained in the cookie. When the cookie expires, the browser automatically deletes it and the web site doesn't get it back on the next visit. Therefore, once the cookie expires, there is no way for Google Analytics to know what the old ID was. The new cookie will get a brand new ID in it. When cookie_update is set to true, the cookie will get ...


1

I don't think that is possible via real time reports. Real time reporting offers a limited set of data and standard ga segments do not work with real time reporting. To see what is offered by the real time reporting, more specific information can be found on the following page https://support.google.com/analytics/answer/1638637?hl=en&ref_topic=1638563 ...


1

To remember your logged in state a site needs to send some data to the browser that the browser then sends back on the next request to show they are logged in. This data is usually stored in a cookie. If you select "remember me" the cookie will be set to expire some time in the future, so if you return within that time you'll be remembered, otherwise it's ...


1

Using cookie free domains has very little to do with the web server that you are using. It is a technique for not sending cookie data when fetching static assets such as images, JavaScript, and CSS. Those assets don't typically need that data and it can make the requests slower to send lots of data to them in the cookies. The technique only makes sense if: ...


1

I do not know Azure or Sitecore, however, I did do some poking around and this is what I found. While it appears that some sitecore cookies can be disabled such as analytics, I see no reference to disabling the cookies for login and other management aspects of the CMS. As far as Azure is concerned, the only reference to what you are asking is for static ...


Only top voted, non community-wiki answers of a minimum length are eligible