How to Test Consent Auto-Blocking on a Spartacus Storefront
Consent auto-blocking is an important part of a compliant SAP Commerce Cloud storefront. However, it can silently break features that load only after a customer interacts with the site. A common example is SAP Customer Data Cloud (Gigya). The identity script may not load when the page first renders. Instead, it may load only after the customer clicks the Sign In link. If that script is incorrectly matched by a consent auto-blocking rule, the page will look healthy, but the sign-in dialog will never open. In this tutorial, we will cover how to identify, test, and safely deploy consent auto-blocking …
