---
sourceDocument: Brazil Sales Customer Relationship Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/order-management

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Sales Customer Relationship Management

ft:clusterId :

    - omgmt

bundleId :

    - omgmt

workflow :

    - Customer and Industry


---

# Common browser issues while using ServiceNow CPQ

# Common browser issues while using ServiceNow CPQ {#ariaid-title1}

Release version: Brazil  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Common browser issues while using ServiceNow CPQ

When using ServiceNow CPQ, proper browser cookie handling is essential for the configurator to function correctly.
Blocking cookies---either by the browser itself or through browser extensions---can prevent configuration tasks, causing errors like the configurator failing to load or 403 errors.
ServiceNow CPQ relies on authentication cookies to manage active sessions across browser tabs, which are deleted upon closing the browser and do not track users.
Show full answer Show less  

## Browser Cookie Blocking

By default, browsers such as Safari and Firefox block all cross-site cookies, interfering with ServiceNow CPQ's authentication cookies, especially when integrated with Salesforce. To use the configurator in these browsers, cookies must be enabled. If end users have no control over their browser choice and your implementation uses easyXDM, you can request a "runtimeAPI" parameter through a ServiceNow support case to improve compatibility with default browser settings.

Administrators should consult browser privacy settings documentation to adjust cookie permissions as needed.

## Cookie-Blocking Extensions

Cookie-blocking can also stem from browser extensions. Common third-party extensions that may block cookies include:

* uBlock Origin
* Privacy Badger
* Ghostery
* Disconnect
* Cookie AutoDelete

Other extensions, such as those related to email templates or crypto wallets (e.g., Briskine, BNB Chain Wallet, MetaMask, WalkMe), can also interfere with cross-site cookies required by ServiceNow CPQ.

To diagnose issues, review and disable browser extensions. If configuration succeeds after disabling extensions, one or more extensions may be causing the problem. If you identify problematic extensions not listed above, it is recommended to report them to ServiceNow support.  
When cookies are blocked by the browser or by browser extensions, it can interfere with the use of ServiceNow CPQ.

If attempting to configure in ServiceNow CPQ results in an error (configurator not loading, a 403 error is returned, or similar) and using another browser resolves the issue, then the issue must be with the settings of the original browser.

ServiceNow CPQ uses [authentication cookies](https://en.wikipedia.org/wiki/HTTP_cookie) to track active sessions across browser tabs. These cookies do not track the user and are deleted when the user closes their web browser. Their only purpose is to validate the user and
their organization for the use of the software.

If cookies are not enabled in the browser, ServiceNow CPQ cannot configure products. The browser itself or the extensions used by the end user in this browser could be inhibiting this active cookie.

Here are some reasons this issue might occur.

## Cookie blocking by the browser {#common_browser_issues_while_using_logik_io__inherent_browser_cookie-blocking}

By default, Safari and Firefox block all cross-site cookies. This behavior interferes with the authentication cookie that jumps across ServiceNow CPQ and Salesforce. If either of these browsers is your (or your end userʼs) default browser, cookies must be allowed to use the configurator.

If you have no control over what browsers end users use to access the ServiceNow CPQ Configurator, and you use easyXDM, submit a support case requesting a "runtimeAPI" parameter. Once the runtime clients are updated to include this parameter, the browsers should work with their default
settings.  
Note:  
Submit a support case by using the [ServiceNow Support portal](https://support.servicenow.com). For step-by-step instructions, see [Create a case on Now Support for CPQ Customers](https://support.servicenow.com/kb?sys_kb_id=d67d3e71475d7a90f64de825126d4326&id=kb_article_view).

Consult your browser's documentation to find the settings that affect whether cookies are blocked. These settings are often found in the privacy options sections of the browser settings.

## Cookie-blocking extensions {#common_browser_issues_while_using_logik_io__common_cookie-blocking_extensions}

Cookies can also be blocked by browser extensions that are installed by the user. Some third-party cookie-blocking browser extensions include:

* uBlock Origin
* Privacy Badger
* Ghostery
* Disconnect
* Cookie AutoDelete
{#common_browser_issues_while_using_logik_io__ul_dd1_js4_ygc}  
Other extensions such as email templates or crypto wallets can also cause issues with cross-site third-party cookies. These extensions include:

* Briskine
* BNB Chain Wallet MetaMask
* WalkMe
{#common_browser_issues_while_using_logik_io__ul_ctz_gs4_ygc}

Review your browser's plugins to check whether any other extensions could be interfering while using ServiceNow CPQ. If the end user can configure after all browser extensions are disabled, one of the extensions must be causing the issue. If you identify an extension that causes the issue and is not in the list above,
please let us know.

