Skip to content

GDPR & cookies

Embedding YouTube, Vimeo, Facebook, TikTok, Dailymotion or Gcore videos loads code (and often cookies) from those third parties. Under GDPR, that requires explicit customer consent. Mediaverse ships with a cookie-consent overlay that gates third-party iframes until the customer agrees.

By default (Settings → System → System Config → Product videos → General settings → Do not require cookies accept = off):

  1. The customer opens a product page with an embedded video.
  2. Mediaverse renders the thumbnail and a play-icon overlay — but no iframe yet.
  3. When the customer clicks the play overlay, a cookie-consent overlay appears asking them to accept third-party cookies.
  4. On accept, the iframe loads and the video plays.
  5. The consent is remembered through Shopware’s standard cookie storage so next clicks load videos immediately.

For YouTube specifically, you can dodge the consent step by enabling YouTube nocookie in Settings → System → System Config → Product videos → YouTube settings → YouTube nocookie. The plugin then uses youtube-nocookie.com URLs, which do not set marketing cookies until the customer interacts with the player. In most legal interpretations this means you do not need separate consent for YouTube embeds, but always confirm with your DPO.

If your store is outside the EU or you handle consent differently, bypass the gate entirely:

Settings → System → System Config → Product videos → General settings → Do not require cookies accept → on.

The plugin then loads iframes immediately (or on lazy-load trigger).

Mediaverse integrates with Shopware’s standard cookie configuration. The plugin registers its own cookie group containing entries for Facebook, Vimeo, Dailymotion and TikTok so the consent overlay matches the rest of the site’s cookie banner.

YouTube is handled separately — instead of a cookie-group entry, YouTube consent is controlled by the YouTube nocookie toggle described above. With nocookie enabled, YouTube embeds bypass the cookie gate entirely; with it disabled, YouTube falls back to the same play-overlay → cookie-consent flow as the other providers.