![]() If you do not want to keep track of the user’s site history in the browser, you can set the maximum storage size to “1” the cookie or session storage key will still be created, but it will stay empty as the user navigates through the site. If they are set, project-level settings override brand-level settings. Once you choose a storage method, you can then set the maximum storage size (in bytes) on either a project-level or on the brand-level (if you are a Brand Admin). ![]() This is a setting that applies to an entire Website / App Insights project. Site History and Page Countįor Site History or Page Count, you can choose between storing information as cookies or as session storage instead. This is a brand-wide setting and cannot be limited to singular accounts or projects. The total size of the cookies listed on this page can be controlled by the Maximum Cookie Size, found under the Organization Settings tab of the Admin page. Cookie LimitĮxcept for when action set logic is based off of Site History or Page Count, all cookies are within 100 bytes. This includes the Site History cookie, Prevent Repeated Display cookie, a cookie that tells us that we have a Pop Under, a cookie that stores history data if localStorage is disabled, and a cookie that tracks user events. Website / App Insights stores certain data inside cookies. ![]() About Website / App Insights Browser Cookies For more information about the differences between Digital Feedback and CustomerXM for Digital, see Digital Feedback vs. Qtip: If you don’t have access to any of the features described on this page, reach out to your Account Executive.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |