LynBro Plugins
/ Tags
LynBro Plugins
/ Tags
Paste an ID, pick nothing else, and the tag is on your site — switched off until the visitor agrees to it. Nothing a vendor ships runs, or is even fetched, before the visitor has said yes to that category. When they do, the tag starts on the spot, without a reload.
Free, with nothing held back. It sets no cookies of its own, records no visitor data and sends no telemetry.
vendor tags from an ID alone — each one behind a consent category.
Every tag is printed as an inert placeholder, so the browser neither runs it nor fetches anything from it. The only scripts that run straight away are the plugin’s own: the Consent Mode default and the small script that switches tags on after consent.
Lynbro Cookie Consent is used natively — its stored choice, its event, and only the categories its banner actually asks about. Any other consent plugin that supports the WP Consent API works too. Without a consent plugin, statistics and marketing tags do not load at all unless you tick Load without a consent plugin, which is off by default.
A lower-case g-ab12… is fixed, a pasted vendor snippet is reduced to its ID, and something that is not an ID is refused with the reason — the previous value stays.
No "Pro" tier, no nag screens. The features other plugins paywall are here from day one.
Measurement ID (G-…). Statistics by default.
Container ID (GTM-…). Marketing by default, because a container can hold anything.
Conversion ID (AW-…), with an optional conversion label and a one-line JavaScript call to count a conversion — which does nothing until the visitor has given marketing consent.
Meta Pixel, Microsoft Advertising (UET), LinkedIn Insight Tag, TikTok Pixel and Pinterest Tag as marketing; Microsoft Clarity and Hotjar as statistics. The category can be changed per tag.
When a Google tag is configured, the default — all four signals denied — is printed before it, and each choice is sent as an update. If Lynbro Cookie Consent already prints a default, it is not printed twice.
Every configured tag against three visitors — no consent, statistics only, statistics and marketing — worked out by the same function the front end uses.
Consent Mode is updated to denied straight away. Tags that already started on the current page keep running until the next page load, where they no longer start.
On templates that do not call wp_head(), wp_body_open() or wp_footer(), lynbro_tags_output() prints each place once per request — never twice.
No. Every tag is printed as an inert placeholder (type=“text/plain”), so the browser neither runs it nor fetches anything from it. The only scripts that run straight away are this plugin’s own: the Consent Mode default and the small script that switches tags on after consent.
Lynbro Cookie Consent, or any consent plugin that supports the WP Consent API.
They cannot answer a consent banner, so they get no tags. The Tag Manager <noscript> fallback is only printed when you load tags without a consent plugin.
Consent Mode is updated to denied straight away. Tags that already started on the current page keep running until the next page load, where they no longer start.
Not yet. The fields are there but reserved: they are stored, and no request is made to Meta from your server.
No. Everything described here is in the plugin, free.