# Manual Cookie Blocking Setup | Secure Privacy Tag Blocking

> [CMP v1] Learn how to identify unblocked cookies in your Secure Privacy Scan Report and manually configure tag blocking for scripts, pixels, and iframes using the Classification settings.

- Canonical: https://support.secureprivacy.ai/article/cmp-v1-block-cookies-manually-in-secure-privacy-scan-report
- Product: Consent Management
- Category: Secure Privacy Legacy
- Published: 2026-03-06T12:44:00+00:00
- Updated: 2026-03-22T16:58:39.6+00:00
- Reading time: 3 minutes

---

Most cookies and trackers are automatically detected and blocked by Secure Privacy's blocking engine. However, certain cookies may not be blocked automatically due to specific website setups or non-standard script configurations. This guide explains how to identify unblocked cookies in your scan report and configure **manual cookie blocking** using Secure Privacy's Tag Blocking feature.

## Who Is This For?

-   Website administrators and developers identifying and resolving cookies not blocked automatically by Secure Privacy
    
-   Compliance teams verifying that all non-essential cookies require prior consent before loading
    
-   Implementation teams configuring tag blocking for scripts, pixels, and iframes not covered by auto-blocking
    

## Step 1: Locate Cookies Not Blocked Automatically

Go to the **Report** page in your Secure Privacy dashboard. Scroll down to the detected cookies section and look for cookies marked with a **red X** in the **Blocking** column. These indicate cookies or services that are not currently being blocked automatically and require manual configuration.

![Secure Privacy Report page showing detected cookies with red X indicators in the Blocking column for unblocked services](https://pub-7bd19505838640d0a08ef1bd6ec3fb9b.r2.dev/articles/c83774ffe344b3b6ece3-d7704e4ec8f5.webp)

## Step 2: Identify the Script, Pixel, or iframe Source

Consult your implementation or development team to determine the source script, pixel, or iframe responsible for the unblocked cookie or service. You will need the source URL or domain associated with the service to configure blocking in the next step.

## Step 3: Apply Manual Blocking Configuration

In the Secure Privacy dashboard, navigate to **Classification > Tag Blocking**. Add the service you want to block by specifying:

-   The **type** — Script, Iframe, or Pixel
    
-   The **source URL or domain** associated with the service
    

![Secure Privacy Classification Tag Blocking tab showing interface for adding a script, iframe, or pixel source URL to manual blocking configuration](https://pub-7bd19505838640d0a08ef1bd6ec3fb9b.r2.dev/articles/d1bc8c8ee6ec5aad33fc-b012ced93d7d.webp)

## Step 4: Rescan Your Website to Verify Blocking

Once the Tag Blocking configuration is saved, run a website rescan from the **Scan Report** page. After the scan completes, check whether the previously unblocked service now shows as successfully blocked in the Blocking column.

![Secure Privacy Scan Report page showing rescan in progress to verify manual blocking configuration is working correctly](https://pub-7bd19505838640d0a08ef1bd6ec3fb9b.r2.dev/articles/acddf22c55fd34f49434-36756ba4526e.webp)

## Summary

-   Identify unblocked cookies by looking for red X indicators in the Blocking column of your Scan Report.
    
-   Find the related script, pixel, or iframe source responsible for the unblocked service.
    
-   Manually configure blocking for that source in **Classification > Tag Blocking**.
    
-   Rescan your website to confirm the service is now successfully blocked.
    

## Frequently Asked Questions

### Why are some cookies not blocked automatically by Secure Privacy?

Secure Privacy's auto-blocking engine covers the majority of commonly detected scripts and services. However, some cookies may not be automatically blocked due to non-standard script implementations, custom-built tracking solutions, or services that Secure Privacy has not yet detected and classified for your specific website setup. Manual Tag Blocking allows you to close these gaps.

### What information do I need to add a service to Tag Blocking?

You need to know the type of tag — Script, Iframe, or Pixel — and the source URL or domain associated with the service. Your development or implementation team can usually identify this from the page source or network requests visible in the browser's developer tools.

### How long does a rescan take, and when should I run it?

Rescan times vary depending on website size and complexity. Run the rescan after saving your Tag Blocking configuration to verify the service is now blocked. If the red X is still showing after the rescan, double-check that the source URL or domain entered in Tag Blocking exactly matches the one identified in the scan report.

## See Also

-   [Do I Need to Block All Cookies?](https://support.secureprivacy.ai/article/should-you-block-all-cookies-gdpr-cookie-categories-explained)
    
-   [How to Classify and Edit Your Cookies and Services](https://support.secureprivacy.ai/article/cmp-v1-how-to-classify-and-edit-your-cookies-and-services)
    
-   [Ongoing Checkups: Best Practices](https://support.secureprivacy.ai/article/cmp-v1-ongoing-checkups--best-practices--secure-privacy)
    
-   [How Do I Add a Custom Service or Cookie?](https://support.secureprivacy.ai/article/cmp-v1-how-do-i-add-a-custom-servicecookie)