---
sourceDocument: Australia Sales and Order Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/order-management

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia Sales and Order Management

ft:clusterId :

    - omgmt

bundleId :

    - omgmt

workflow :

    - Customer and Industry


---

# Common browser issues while using CPQ

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

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 Minute Lesedauer

When cookies are blocked by the browser or by browser extensions, it can interfere with the use of CPQ.

If attempting to configure in 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.

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 our software.

If cookies are not enabled in the browser, 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 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 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.

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 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.