Embeds Blocked After Consent (YouTube, Maps, Vimeo)

SureCookie’s script and content blocking hold third-party embeds like YouTube, Google Maps, and Vimeo until a visitor consents, showing a placeholder in their place. When an embed stays blocked even after someone has given consent, it’s almost always because the embed belongs to a consent category the visitor didn’t accept, or a cache is serving the pre-consent version of the page.

The good news: once the visitor accepts the category the embed needs, it loads right where it was, with no page reload required.

How Embeds Are Blocked and Unblocked

When blocking is on, SureCookie replaces each third-party embed with a placeholder and holds it until consent. Every embed is assigned a consent category:

• YouTube and Vimeo are usually Marketing.
• Google Maps is usually Functional.

The embed loads only when the visitor accepts the category it belongs to. If they accept some categories but not that one, the embed stays blocked, and that is the intended behavior.

Check Which Category the Embed Needs

Most “still blocked after consent” reports are a category mismatch: the visitor (or you, while testing) accepted some categories but not the one the embed uses.

1. Go to SureCookie → Settings → Compliance → Resource Blocking.
2. Make sure Enable Script and Content Blocking is on.
3. In Detected Resources, find the embed by its service name or domain (Type: Iframe) and read its Category.
4. Confirm that the visitor accepted that category. If they didn’t, the embed will stay blocked.

Note: The category shown here is set by SureCookie’s detection and is read-only. The control you can change is each resource’s Block toggle: leave it on to keep gating the embed behind consent, or turn it off only if you consider that embed essential and want it to load without consent. Turning off blocking for a resource is a compliance decision, so use it deliberately.

Test With a Fresh Consent Choice

Your browser remembers your earlier choice, so you may be looking at an old “declined” state.

• Open your site in a private or incognito window and accept the category the embed needs.
• Or reopen your cookie preferences and accept that category.

The embed should appear immediately after you accept. A reload isn’t required, but it doesn’t hurt.

Clear Your Caches

A page cache or CDN can keep serving the pre-consent version of the page, placeholder and all, even after consent is given.

1. Clear your WordPress page cache and purge your CDN.
2. Reload and accept again in a private window.

The Embed Isn’t in the Detected List

If the embed’s service isn’t listed under Detected Resources, SureCookie may not be gating it the way you expect.

1. Run a scan under SureCookie → Cookie Manager → Manual that includes the page with the embed, so the resource is detected and categorized.
2. Return to Resource Blocking and confirm the embed now appears with a category.

The Embed Loads via a Separate Script

Some embeds are injected by a loader script rather than a plain iframe. If accepting the iframe’s category doesn’t help, check whether a related entry with Type Script (for example a tag manager) sits in a different category that the visitor also needs to accept.

Still Blocked?

If the embed still won’t load, contact support with the details so we can investigate.

• The embed’s service and URL.
• The category it’s listed under in Detected Resources.
• Whether you tested in a private window after accepting that category.
• Your caching and CDN setup.