Start troubleshooting from a reset choice and one service at a time. The service ID, Raincheck Privacy ID, accept class, and decline class must describe the same service.
Content loads before consent
Confirm that the third-party embed or script is inside the consent-controlled pattern rather than also being placed elsewhere on the page. Check the service’s unique IDs and the decline control class.
The placeholder remains after acceptance
Check that the Raincheck Privacy ID exactly matches the service ID and that the unblock button uses the service’s accept class. Then verify both ON controls in the privacy panel.
OFF or ON does nothing
Compare the duplicated section with a working example. The OFF control must use the decline name; the ON controls must use the accept name. Similar-looking service names are not interchangeable.
A previous choice keeps returning
Use Reset Cookie Settings, reload the public page, and test again. When debugging, avoid editor preview and use the same public origin throughout the test.
Panel and placeholder accessibility
Use clear service names and descriptions.
Test the panel and every action with the keyboard.
Keep focus indicators visible.
Maintain strong contrast for text, OFF/ON states, and action buttons.
Make protected-content placeholders understandable without the blocked media.
Keep the reset or reopen control easy to find.
Review the adapted wording and behavior against the requirements that apply to the site. CrunchGuard supplies the technical project, but it cannot determine legal compliance for a particular service or jurisdiction.
If the problem remains, email support@stackswork.com with the project version, affected service, the four matching identifiers or classes, public test URL, and steps taken after resetting the choice.
Related: Choosing a CrunchGuard layout and editing the privacy panel and Adding a consent-controlled service to CrunchGuard.