Browse Source

Mixpanel cross_site_cookie changed to secure instead of false

James Peret 2 years ago
parent
commit
a9eca40509
1 changed files with 3 additions and 3 deletions
  1. 3 3
      themes/kairoscope-theme/layout/_partial/analytics.ejs

+ 3 - 3
themes/kairoscope-theme/layout/_partial/analytics.ejs

@@ -34,7 +34,7 @@
             // if true, cookie will be set with SameSite=None; Secure
             // this is only useful in special situations, like embedded
             // 3rd-party iframes that set up a Mixpanel instance
-            cross_site_cookie: false,
+            cross_site_cookie: secure,
             // super properties span subdomains
             cross_subdomain_cookie: true,
             // debug mode
@@ -67,7 +67,7 @@
             property_blacklist: [],
             // if this is true, mixpanel cookies will be marked as
             // secure, meaning they will only be transmitted over https
-            secure_cookie: false,
+            secure_cookie: true,
             // the amount of time track_links will
             // wait for Mixpanel's servers to respond
             track_links_timeout: 300,
@@ -76,7 +76,7 @@
             // properties from it, then the old cookie is deleted
             // The upgrade config option only works in the initialization,
             // so make sure you set it when you create the library.
-            upgrade: true,
+            upgrade: false,
             // extra HTTP request headers to set for each API request, in
             // the format {'Header-Name': value}
             xhr_headers: {},