Works with your stack
Cookie consent for Embed Plus for YouTube
the script calls youtube too
Embed Plus for YouTube adds YouTube videos and galleries. Holding the video frame is not enough: the plugin’s own script loads YouTube’s player code before the choice. Cookie Rocks holds that script with YouTube until the visitor agrees.
By EmbedPlus Labs, LLC · embedplus.com · WordPress.org
Is this your product? Tell us if anything here is out of date. Write to us
Embed Plus for YouTube
WordPress plugin
- Tested version
- 14.2.6.1
- How
- Tested automatically around each Cookie Rocks version
- Last test
- 7 November 2026
- Latest version
- 14.2.6.1 tested
- Active installs
- 100,000+
What Embed Plus for YouTube adds to your visitors’ browser
Trackers it loads
- YouTube →Marketing
What matters for consent with Embed Plus for YouTube
Two things to hold
The plugin writes a normal YouTube frame, and its own script adds YouTube’s player code even when the frame waits. Cookie Rocks holds that script with YouTube.
Thumbnails come from YouTube
In facade mode and in galleries, preview images load from YouTube’s image server before any choice. In facade mode, a click builds the YouTube frame with JavaScript.
Its own consent message
“Show Consent Message” is off by default. It is decided on the server from a cookie, and reloads the page. On a cached page, visitors can get the message or the video whatever they chose.
No Cookies is not consent
The “No Cookies” option only switches the player to youtube-nocookie.com. YouTube’s player still loads.
Cookie Rocks with Embed Plus for YouTube
- In its default iframe mode, each YouTube video keeps its place with a “Load the video” button, then loads from youtube-nocookie.com.
What our tests found on Embed Plus for YouTube
Good to know · Cookie RocksEmbed Plus setup stops when released after load
When Cookie Rocks 2.11.0 releases Embed Plus for YouTube after the page has loaded, the video plays, but its setup does not finish: ytprefs.js waits for the window load event, which has already passed, so apiInit never runs and its player events do not start. Sending the load event again finishes the setup.
Seen in our tests, 6 November 2026, Cookie Rocks.
Set before the choice · Embed Plus for YouTubeEmbed Plus for YouTube loads YouTube before the choice, even with the video held
Embed Plus for YouTube loads its own script, which injects YouTube's iframe API before the choice even when the video frame is held; YouTube then sets its cookies. Cookie Rocks 2.5.1 holds that script with YouTube.
Seen in our tests, 17 October 2026, Embed Plus for YouTube.
Set before the choice · Embed Plus for YouTubeEmbed Plus for YouTube loads YouTube thumbnails before the choice
setting “Facade mode” · by default: off
- Default mode: a normal YouTube iframe that lazy-load plugins leave in place.
- Facade mode: an i.ytimg.com thumbnail loads first; a click builds the YouTube player.
- A playlist facade fetches youtube.com/oembed from the browser.
- Gallery thumbnails load from i.ytimg.com before any choice.
Read in its code, 16 October 2026, Embed Plus for YouTube 14.2.6.1.
Full detail
By default Embed Plus for YouTube writes a normal youtube.com/embed iframe carrying no-lazyload and data-no-lazy=1, so lazy-load plugins leave its src in place. In facade mode there is no iframe in the HTML: a div with data-facadesrc and an i.ytimg.com thumbnail load before any choice, a playlist facade fetches youtube.com/oembed from the browser, and a click builds the YouTube iframe in JavaScript. Gallery thumbnails load from i.ytimg.com as CSS backgrounds, before any choice.
Depends on a setting · Embed Plus for YouTubeEmbed Plus for YouTube consent message reloads the page and can be cached
setting “Privacy/GDPR - Show Consent Message” · by default: off
Its own message (off by default) sets ytprefs_gdpr_consent for 30 days and reloads. A cached page can keep the wrong state. No Cookies only switches to youtube-nocookie.com.
Read in its code, 16 October 2026, Embed Plus for YouTube 14.2.6.1.
Full detail
Embed Plus for YouTube's own Show Consent Message (off by default) is decided on the server from the cookie ytprefs_gdpr_consent: without the value 1, a message replaces each video and gallery thumbnails. The button sets that cookie for 30 days (path /) and reloads the page, so a cached page keeps showing the message (or the video) whatever the choice unless the cache varies on it. It does not use WP Consent API. The No Cookies option only switches the player host to youtube-nocookie.com.
How we test it
Around each version, with its latest release
Around each Cookie Rocks version, a fresh WordPress installs its latest version from WordPress.org next to Cookie Rocks and runs the same checks. A new version joins the next run on its own.
- Embed Plus for YouTube 14.2.6.1, tested on 7 November 2026.
- The banner shows, the trackers of the test page wait for consent and load after it, and Cookie Rocks raises no PHP error.
- Settings of the test: Default settings after activation.
- Last run: Embed Plus for YouTube 14.2.6.1 on 7 November 2026, with WordPress 7.1.3.
Galleries, feeds and maps
Other plugins of the same kind.
Questions
Do I need the plugin’s own consent message?
It works on the server and does not use WP Consent API, so it does not follow the choice made in another consent plugin. Its reload and page caching do not mix well.
What happens after the 30-day trial?
The banner, your visitors’ choices and your proofs of consent keep working. Without a key, most settings lock, updates and support stop. Take a key at any time and everything opens again.
For sites with Embed Plus for YouTube
Videos after consent, script included.
the script waits too
Every feature of the complete plugin for 30 days, no card.
- During the trial: everything, including the full settings and the scans
- After 30 days without a key: the banner, your visitors’ choices and your proofs of consent keep working
- What waits for a key: most settings, updates and support
Get your trial key
Your e-mail and your site. Your key arrives as soon as you confirm your e-mail.