What is the sbjs_current cookie?
sbjs_current is an HTTP cookie set by Sourcebuster.js, an open-source library bundled with the WooCommerce plugin for WordPress. It appears on any online store running WooCommerce with traffic-source tracking enabled, regardless of whether the site owner uses additional marketing extensions.
The cookie is created automatically on a visitor's first page load and is updated whenever the current session changes, for example when a new visit arrives from a different traffic source.
What data it stores
sbjs_current stores information about the current traffic session: the source type (organic, direct, referral, social, paid), the source name (e.g. a specific search engine or social network), and any UTM campaign parameters present in the URL. The value is a structured string used internally by the Sourcebuster script, not a direct personal identifier.
The data stays stored locally in the visitor's browser and is read by WooCommerce's own scripts on the site to later associate it with a completed order; it is not sent by default to external WooCommerce or Automattic servers.
What it is used for
The cookie's purpose is order attribution: WooCommerce uses the data in sbjs_current (together with related sbjs_ cookies) to determine which marketing channel a customer came from before placing an order — organic search, paid ads, social media, email, or direct traffic.
For the site owner, this information typically surfaces in order reports or sales-analytics extensions, helping evaluate which marketing channels actually drive purchases.
Does it require consent?
CookieFix classifies sbjs_current under the statistics (analytics) category, since its purpose is traffic measurement and attribution rather than strictly necessary technical functioning of the site. Under Romania's Law 506/2004 (implementing the ePrivacy Directive) and the GDPR, this type of cookie requires the visitor's prior consent before being set.
- The site owner must list the cookie in the cookie policy, including its purpose, duration, and provider.
- The script that sets sbjs_current must be blocked until consent for the statistics category is given.
- Refusing consent does not affect basic store functionality, only traffic-source attribution.
How to block or delete sbjs_current
A visitor can manually delete or block sbjs_current from the privacy/cookie settings of their browser (Chrome, Firefox, Edge, Safari), either by clearing cookies for that domain or by enabling blocking of tracking/third-party cookies.
For site owners, the practical approach is using a CMP like CookieFix, which automatically blocks the Sourcebuster.js script (and therefore the setting of sbjs_current) until the visitor consents to the statistics category, ensuring alignment with ePrivacy rules without manually editing theme or plugin code.
Frequently asked questions
It's a session cookie set by the Sourcebuster.js script used by WooCommerce to identify a visitor's current traffic source, for the purpose of order attribution.
It's a session cookie, meaning it is automatically deleted when the visitor closes their browser, unlike some other sbjs_ cookies that persist longer.
It doesn't contain direct identifiers like a name or email, only information about the marketing channel that brought the visitor to the site; however, it can qualify as personal data when combined with other identifiers under GDPR.
Yes, since it is classified as a statistics/analytics cookie, it requires the visitor's prior consent under Law 506/2004 and the GDPR, as it is not strictly necessary for the site to function.