← Back
ConsentMagic Pro / Tracking & Blocking / Pre-Defined Scripts

Pre-Defined Scripts

Last updated: February 12, 2026

Go to ConsentMagic Pro → Scripts & Cookies → Pre-defined Scripts.

This tab controls ConsentMagic’s built-in library of known scripts and embeds (Google, Meta, TikTok, YouTube, Vimeo, etc.). Instead of manually writing rules for each one, you simply enable/disable blocking and assign each script to a consent category.

Block pre-defined scripts (master switch)

At the top you’ll see Block pre-defined scripts.

  • ON → ConsentMagic will actively control (block/allow) these known scripts based on the visitor’s consent and the rule that applies to them.
  • OFF → ConsentMagic won’t block these pre-defined items (they may still appear in scans, but they won’t be controlled from here).

This setting matters only when you actually use ConsentMagic for consent enforcement (and Script Blocking is enabled in the plugin).

How each row works

Every pre-defined item has the same 3 controls:

1) Per-script toggle (left)

Turns control ON/OFF for that specific script.

  • ON → ConsentMagic will manage it (block until allowed).
  • OFF → ConsentMagic ignores it (it can load normally, even if other scripts are blocked).

2) Script category (dropdown)

Assign the script to a consent category (examples shown in your screen: Marketing, Analytics, Embedded Videos, Google Fonts, Necessary).

This is the key link between:

  • what the visitor chooses in the banner (Accept / Reject / Customize), and
  • what actually runs on the page.

Example logic:

  • If a user rejects Marketing, then anything categorized as Marketing stays blocked.
  • If a user allows Embedded Videos, then YouTube/Vimeo embeds can load.

3) Details (right)

Opens the script’s definition (what it is, how it’s detected/blocked, and any technical identifiers). This is useful when you’re unsure what category a script should belong to.

Special case: Google Consent Mode signals

Items like:

  • Google ad_storage
  • Google analytics_storage
  • Google ad_user_data
  • Google ad_personalization
  • Google url_passthrough

…are related to Google Consent Mode behavior (consent signals that influence how Google tags behave).

In your screenshot they’re categorized like this (common setup):

  • ad_storage / ad_user_data / ad_personalization → Marketing
  • analytics_storage → Analytics
  • url_passthrough → Necessary (often treated as essential for maintaining attribution flow)

What you typically control here

From your list, the main groups are:

  • Analytics / measurement
    • Google Analytics, Hotjar, Matomo, etc.
  • Advertising / marketing
    • Google Ads Tag, Facebook Pixel, TikTok Pixel, Pinterest, LinkedIn, Microsoft UET, Reddit, Twitter, etc.
  • Embeds
    • YouTube Embedded, Vimeo Embedded, Instagram embed, Soundcloud, Slideshare, Google Maps
  • Functional / necessary
    • Google Captcha (often essential for spam protection)
    • PixelYourSite cookies (commonly necessary for site functionality/tracking logic—depends on your policy)
    • Conversion Exporter cookies (your chosen category will depend on how you use them)

Best practice

  • Start by keeping the default categories, then adjust only what’s legally/policy-accurate for your site.
  • If something is loading unexpectedly, check:
    1. Block pre-defined scripts is ON
    2. the script’s own toggle is ON
    3. the script category matches what the visitor accepted
    4. the active Rule for that visitor is set to actually enforce consent (and Script Blocking is enabled)