Rejection Recovery in Complianz App for Shopify

How Rejection Recovery Works 

When a visitor: 

1. Rejects one or more cookie categories 
2. Tries to view content that depends on those categories 

Complianz: 

• Blocks the iframe or script 
• Displays a placeholder 
• Shows a button that allows the visitor to update their preferences 

This applies automatically to most standard iframes, such as: 

• YouTube embeds 
• Vimeo embeds 
• Google Maps 
• Other external iframe content 

When Rejection Recovery Is Applied Automatically 

Rejection Recovery works automatically when: 

• The content is embedded using standard iframe code 
• The iframe is detected by Complianz’s autoblocking system 
• The purpose category is correctly assigned 

In these cases, you don’t need to do anything. 

When You Need to Apply Rejection Recovery Manually 

Sometimes, the placeholder does not appear automatically. 

This usually happens when Complianz cannot detect the correct container where the placeholder should appear. In these situations, you need to configure Rejection Recovery manually. 

Common Scenarios 

Here are typical examples where manual setup is required: 

1. A Plugin Uses a Custom Video Module

Some Shopify apps or theme modules do not use a standard YouTube iframe. 

Instead of embedding: 

<iframe src="https://www.youtube.com/embed/xyz"></iframe> 

They: 

• Inject the video with JavaScript 
• Wrap it inside multiple custom div elements 
• Load it dynamically after page load 

⚠️ Because of this structure, Complianz may block the iframe but cannot determine which container should display the placeholder. 

Result: The video disappears, but no consent message is shown. 

💡 In this case, you must manually add the required class and attribute to the correct parent container. 

2. The Iframe Is Deeply Nested

Sometimes the iframe is inside several nested elements, for example: 

<div class="video-wrapper"> 
  <div class="custom-module"> 
    <div class="media-container"> 
      <iframe src="..."></iframe> 
    </div> 
  </div> 
</div> 

⚠️ Complianz may block the iframe, but it does not know whether the placeholder should appear in: 

• .video-wrapper 
• .custom-module 
• .media-container 

💡 Since this cannot be determined automatically, you need to define the correct container manually. 

3. The Content Is Injected Dynamically

Some themes load content only after user interaction or via JavaScript. 

For example: 

• A “Click to play” video button 
• A lazy-loaded banner 
• A dynamic product video section 

⚠️ In these cases, autoblocking works, but Rejection Recovery may not attach the placeholder automatically. 

💡 Manual configuration ensures the consent message appears in the correct place. 

4. Non-Standard YouTube or External Embeds

If a plugin: 

• Rewrites the YouTube embed URL 
• Uses a background video system 
• Converts the iframe into a script-based player 

⚠️ Complianz may not detect the structure properly.

💡 In these situations, you must manually apply Rejection Recovery to the appropriate container or use a standard integration code. 

How to Manually Apply Rejection Recovery 

To use Rejection Recovery manually, you must: 

1. Add a specific CSS class 
2. Add a required data attribute 
3. Apply both to the correct container element 

Required Class and Attribute 

Add the following to the container that wraps your video or iframe: 

class="_iub_cs_prompt" 
data-iub-purposes="3,s"

What These Mean 

• _iub_cs_prompt → Tells Complianz to display a consent placeholder in this element 
• data-iub-purposes=”3,s” → Defines which consent categories must be accepted before the content loads 

⚠️ Important:

The purposes must match the purposes assigned to the blocked content. 

For example, YouTube videos often require Marketing and/or Measurement consent, depending on your configuration.