Use the existing service pattern when CrunchGuard must control another script or embedded service. Complete the whole connection before changing its visual design.

Duplicate and identify the service

  1. Duplicate a Cookie Script from the CrunchGuard partial.

  2. Change the first part of its IDs to a unique service name such as logo or pixel.

  3. Do not change the Clear field.

Use the same unique name consistently. A mismatch between the script, placeholder, and panel controls prevents the service from responding to the choice.

Add an optional placeholder

If protected content should show a message before consent, duplicate a Raincheck placeholder. Set its Privacy ID to the unique ID created for the service.

On the placeholder’s unblock button, set the class to the service’s accept name. This lets the visitor permit that service directly from the placeholder.

Add the panel controls

  1. Open the Cookie Panel in the CrunchGuard partial.

  2. Duplicate an existing service section.

  3. Set the OFF control class to the new service’s decline name.

  4. Set the corresponding Raincheck Privacy ID to the same unique ID.

  5. Set both ON control classes to the service’s accept name.

  6. Replace the service name and description.

Test the complete path

Reset the cookie settings, decline the new service, and confirm that its content or code remains blocked. Then enable only that service, save the selection, and confirm that it loads. Finally test the placeholder’s unblock button and the global Accept all and Decline services actions.

Related: Getting started with CrunchGuard and Troubleshooting CrunchGuard consent and placeholders.