Docs
Merchandising Hub
Pers. content
Product recs
Product badging
Product Insights
IntroWelcomeGlossaryFAQsGet updates & take actionSee how your campaigns are performingTake actionSettings and toolsEnable Google AnalyticsView products in your catalog
Get startedShort guideBasic build flowYour dashboardTutorialsCreate a hotspot on a PLP
Add personalized contentStep 1 - Choose whereStep 2 - Decide who & whatStep 3 - Set visibilityStep 4 - Decide whenStep 5 - Review & launchReferenceMetrics
Experimentation Hub
Target customers
Data in/out
Analyze your data
Work with experiencesFirst stepsManageGet resultsBuild from a templateBuild Visual or CustomBuild Abandonment recoveryBuild Product recommendationsBuild Social proofBuild Visitor pulseGuides & tutorialsReference
Build segmentsFirst stepsCreateAnalyzeGuides, tutorials & reference
Collect visitor sentimentIntroSet it upGet results
Developers
Setup
Placements
Experiences
Setup Merchandising HubEcommerceTravel
Setup Experimentation HubWays to set up with QubitWeb setupMobile setupCMS setupValidate your setupProduct feedSmartserveTracking setup & property settingsManage your Auth keyManage your users & profilesAdvanced topicsAnalyticsThird-party toolsQubit scripts
API
FAQs
QP events
Setup Merchandising Hub
Ecommerce
Travel
Setup Experimentation Hub
Ways to set up with Qubit
Web, mobile & CMS
Web setup
Our three steps
eCommerce
eGaming
Travel
Mobile setup
Our SDKs and mobile APIs
For iOS
For Android
React Native SDK
CMS setup
Intro
Salesforce Commerce Cloud (Demandware)
SAP Commerce Cloud (Hybris)
Magento
Shopify
Contentsquare
Validate your setup
Why validate?
Data validation at Coveo Qubit
With Coveo Qubit Explorer
With Validation Dashboard
Product feed
Import and manage a Google product feed
Smartserve
Get your Smartserve Script
Edit your Smartserve prescript
Tracking setup & property settings
Review your tracking setup
Edit your property settings
Manage your Auth key
What is it and what's it for?
Generate new key
Configure existing key
Manage your users & profiles
Roles & permissions
Manage users
Manage profiles
Advanced topics
Hosting & self-hosting
Qubit events 101
Schema extensions
Product Id vs SKU
Correct use of product.categories
Round number fields
Qubit & ad blocking
Event enrichment
Analytics
Bounce rates - Qubit v GA
Session v entrance
Cross-domain tracking
Landing page tagging guide
Third-party tools
Set up GTM
Qubit scripts
Intro to Qubit scripts
UV API
Smartserve.js
Jolt
Qubit cookies
Intro to Qubit cookies
qubitTracker
qb_permanent
qb_session
qb_generic
Call-centre tracking
Track call as events
How it works
Set it up

Qubit's cookies

In this article...

We'll discuss our first-party cookies and how we use them to deliver personalization at scale.

First-party cookies

Qubit sets first-party cookies as a reliable way to:

  • Identify individual visitors, and tie them into the data that we collect
  • Target the correct visitor and provide them with a consistent personalized journey
  • Undertake deep analysis of experiences and journeys across a visitor's lifetime
  • Write and get experience data
  • Ensure cookies are working and supported in the browser

Refer to the following table for more details about each cookie. These are set for all customers that have added the smartserve.js script to their site pages.

Cookie

Expiry

Description

Rolling 1 year

Stores user's Qubit Id

Rolling 1 year

Stores all persistent Qubit data

30 min inactivity

Stores all session based Qubit data

Rolling 1 year

Stores and retrieves experience data

qb_persist_test

1 day

Checks if cookies are working and supported in the browser

No data stored

INFO: Qubit also sets qubit_explorer when Qubit Explorer is open.

Last updated: January 2023
Previous: Jolt
Qubit scripts
Next: qubitTracker
Qubit cookies
Did you find this article useful?