Skip to content

LMG Consent 1.2.1 — block marketing pixels (Meta, LinkedIn, TikTok, Bing, Pinterest, X)

Choose a tag to compare

View all tags
@ericisaksen ericisaksen released this 30 Jun 15:22
· 1 commit to main since this release
1.2.1
6dfeb43

Marketing-pixel blocking

Extends v1.2.0's CIPA prior-blocking beyond Google. The plugin now also neutralizes the common advertising-pixel loaders until the visitor grants Marketing consent — same mechanism (rewrite the external loader to type="text/plain", reactivate after opt-in), so no per-site changes are needed.

Pixels now blocked (all → Marketing)

  • Meta / Facebook — connect.facebook.net/…/fbevents.js
  • LinkedIn Insight — snap.licdn.com/li.lms-analytics/insight.min.js
  • TikTok — analytics.tiktok.com/i18n/pixel/events.js
  • Microsoft / Bing UET — bat.bing.com/bat.js
  • Pinterest Tag — s.pinimg.com/ct/core.js
  • X / Twitter — static.ads-twitter.com/uwt.js

Inline init calls (fbq(…), lintrk(…), ttq.track(…), etc.) are left in place but stay inert without their loader — no transmission until consent.

Notes

  • Pixels fired through a GTM container are already covered by the existing gtm.js block (the whole container is held until Marketing consent).
  • A site running a non-standard loader can still add it via LMG_CONSENT_EXTRA_PATTERNS.
  • No back-compat changes.
Assets 2
Loading