mariastellatech

<p>Stella Cookies is a WordPress cookie consent plugin for managing a cookie banner, consent categories, and third-party content controls for analytics, marketing, and embedded services.</p>
<p>The plugin includes support for Google Consent Mode v2, configurable consent categories, script blocking patterns, iframe blocking, cookie policy content, and a built-in shortcode for displaying your cookie policy and cookie declaration page.</p>
<p>It is built for site owners who need a configurable cookie banner and for developers who need flexible controls for consent-based script loading.</p>
<h4>Free Features 🚀</h4>
<ul>
<li>Enable or disable the cookie banner from one settings screen.</li>
<li>Support for Google Consent Mode v2 workflows.</li>
<li>Block analytics and marketing scripts until consent.</li>
<li>Optional strict prior blocking for uncategorized third-party scripts.</li>
<li>Configure statistics and marketing script patterns.</li>
<li>Configure allowlist patterns for trusted scripts.</li>
<li>Optional iframe blocking for embedded third-party content.</li>
<li>Consent version control for resetting consent after policy changes.</li>
<li>Cookie Policy content editor.</li>
<li>Cookie declaration list for transparency pages.</li>
<li><code>[stella_cookies_policy]</code> shortcode for policy and consent reset display.</li>
<li>Banner design templates and custom styling controls.</li>
<li>Button text, color, and font size customization.</li>
<li>Preference manager with necessary, statistics, and marketing controls.</li>
<li>Floating badge option to reopen consent controls.</li>
<li>Live admin preview for banner design changes.</li>
<li>In-admin help guide and system status summary.</li>
</ul>
<h4>Who It Is For</h4>
<ul>
<li>Website owners who need a configurable consent banner.</li>
<li>Agencies managing privacy compliance across client sites.</li>
<li>Developers who need finer control over script loading behavior.</li>
<li>Businesses that want a clean free plugin and an upgrade path to advanced compliance workflows.</li>
</ul>
<h4>Upgrade to Pro⚡</h4>
<p>Stella Cookies Pro extends the free plugin with advanced compliance tools including cookie scanning, staged scan review, scan history, email alerts, consent logs, analytics reporting, geo targeting, Global Privacy Control support, GTM sync, and additional banner branding controls.</p>
<h3>External services</h3>
<p>This plugin does not make direct HTTP requests to any external service or API on its own.</p>
<p>However, the plugin includes built-in script-blocking pattern lists that reference well-known third-party domain strings. These strings are used <strong>locally</strong> to match and block scripts loaded by your own site before consent is granted. No data is sent to these domains by the plugin itself.</p>
<p>The following third-party domains are referenced in the built-in blocking pattern defaults:</p>
<h4>Google Tag Manager / Google Analytics</h4>
<p>Pattern used: <code>googletagmanager.com/gtag</code>, <code>google-analytics.com</code></p>
<p>These patterns allow the plugin to identify and block Google Analytics and Google Tag Manager scripts until the visitor consents to the Statistics category.</p>
<p>If your site loads Google tags, those tags will connect to Google’s servers. Please refer to Google’s own terms and privacy policy:<br />
* Terms of Service: https://marketingplatform.google.com/about/analytics/terms/us/<br />
* Privacy Policy: https://policies.google.com/privacy</p>
<h4>Meta (Facebook) Pixel</h4>
<p>Pattern used: <code>connect.facebook.net</code></p>
<p>This pattern allows the plugin to identify and block Facebook/Meta Pixel scripts until the visitor consents to the Marketing category.</p>
<p>If your site loads the Meta Pixel, it will connect to Meta’s servers. Please refer to Meta’s own terms and privacy policy:<br />
* Terms of Service: https://www.facebook.com/legal/terms/businesstools<br />
* Privacy Policy: https://www.facebook.com/privacy/policy/</p>
<h4>Other built-in patterns</h4>
<p>The plugin also includes built-in blocking patterns for other common analytics and advertising services including <code>clarity.ms</code> (Microsoft Clarity), <code>hotjar.com</code>, <code>doubleclick.net</code> (Google Ads), <code>googleadservices.com</code>, <code>googlesyndication.com</code>, <code>ads-twitter.com</code>, <code>platform.twitter.com</code>, <code>tiktok.com</code>, <code>snap.licdn.com</code>, <code>ct.pinterest.com</code>, <code>matomo</code>, <code>plausible.io</code>.</p>
<p>All of these patterns are used solely to match and block third-party scripts on your own site. The plugin itself does not transmit any data to these services. Data transmission to these services only occurs after the visitor grants consent, or if the scripts are loaded by other means outside the plugin’s control.</p>
<h3>Developer API (Hardcoded Scripts)</h3>
<p>The safest and most WordPress-native way to load scripts is using <code>wp_enqueue_script()</code>. Stella Cookies will automatically detect and block these enqueued scripts based on your consent settings.</p>
<p><strong>Please do not paste raw <code><script></code> tags directly into your theme templates (<code>header.php</code>, <code>footer.php</code>, etc.).</strong> Hardcoded raw scripts cannot be reliably blocked without causing conflicts with other plugins.</p>
<p>If you are a developer and absolutely must output a script manually, please use the provided helper functions. These functions will automatically enforce the user’s consent choice without rewriting the whole page.</p>
<p><strong>For external scripts:</strong><br />
    stella_cookies_script( ‘https://connect.facebook.net/en_US/fbevents.js’, ‘marketing’ );</p>
<p><strong>For inline scripts:</strong><br />
    <code>php<br />
stella_cookies_inline_script( "<br />
    window.dataLayer = window.dataLayer || [];<br />
    function gtag(){dataLayer.push(arguments);}<br />
    gtag('js', new Date());<br />
    gtag('config', 'G-XXXXXXXXXX');<br />
", 'statistics' );</code></p>


Stella Cookies

Cookie banner plugin for GDPR and CCPA with Consent Mode v2, script blocking, iframe blocking, cookie policy shortcode, and banner design controls.

Hugo Carvalho

<p>Attribution usually breaks somewhere between the ad click and the conversion. ClickTrail makes it survive: cached pages, dynamic forms, multi-page journeys, repeat visits, and consent requirements.</p>
<p>ClickTrail keeps the source of the visit, not a profile of the visitor. Capture is first-party and consent-aware: the plugin does not call external services to identify or enrich visitors, and data only leaves your site through integrations you enable yourself (GTM, webhooks, server-side delivery).</p>
<p>ClickTrail stores first-touch and last-touch attribution from the landing page and keeps it available until the conversion point, where it becomes usable inside WordPress:</p>
<ul>
<li>WooCommerce orders</li>
<li>supported forms</li>
<li>browser events</li>
<li>optional server-side delivery</li>
</ul>
<p>In WooCommerce, ClickTrail stores attribution on the order, pushes enriched purchase events on the thank-you page, and can optionally emit GA4-style storefront events for <code>view_item</code>, <code>view_item_list</code>, <code>view_cart</code>, <code>add_to_cart</code>, <code>remove_from_cart</code>, and <code>begin_checkout</code>, plus post-purchase milestones, through the same ClickTrail pipeline.</p>
<h4>Pick a starting path</h4>
<ul>
<li><strong>WooCommerce store</strong>: enable Capture and WooCommerce. Orders carry campaign context from day one; add storefront events later if you want funnel signals.</li>
<li><strong>Lead-gen forms</strong>: enable Capture and Forms. Contact Form 7 and Fluent Forms get hidden fields automatically; Gravity Forms and WPForms fill the <code>ct_*</code> fields you add.</li>
<li><strong>GTM / sGTM stack</strong>: enable Capture, Events, and Delivery. Browser events push to the <code>dataLayer</code>, and the server-side adapters feed sGTM or platform APIs directly.</li>
</ul>
<h4>What problems it solves</h4>
<ul>
<li><strong>No paid order reports as “direct”</strong>: Paid traffic often ends up looking like direct traffic by the time an order is placed. ClickTrail stores attribution on the order and keeps purchase reporting tied to campaign context.</li>
<li><strong>No checkout journey goes dark</strong>: WooCommerce storefront journeys can emit opt-in <code>view_item</code>, <code>view_item_list</code>, <code>view_cart</code>, <code>add_to_cart</code>, <code>remove_from_cart</code>, and <code>begin_checkout</code> signals through the same ClickTrail event layer used elsewhere in the plugin.</li>
<li><strong>No cached or AJAX-rendered form drops attribution</strong>: Hidden fields often break on cached pages or dynamically rendered forms. ClickTrail includes client-side fallback and dynamic-content support.</li>
<li><strong>No cross-domain hop breaks continuity</strong>: Approved link decoration and attribution tokens keep continuity between domains or subdomains.</li>
<li><strong>No consent signal is ignored</strong>: Consent controls, browser events, webhook intake, and server-side transport live in the same plugin and respect the same consent state.</li>
</ul>
<h4>Core capabilities</h4>
<ul>
<li><strong>Capture</strong>: first-touch and last-touch UTMs, major ad click IDs, and referrers with automatic organic/social/referral fallback when UTMs are absent.</li>
<li><strong>WooCommerce</strong>: checkout attribution persistence, thank-you purchase event push, enriched commerce payloads, optional storefront commerce events, and optional order-status milestones.</li>
<li><strong>Forms</strong>: automatic hidden-field enrichment for Contact Form 7 and Fluent Forms, compatible hidden-field population for Gravity Forms and WPForms, client-side fallback, dynamic form support, and WhatsApp attribution continuity.</li>
<li><strong>Events</strong>: browser event collection with <code>dataLayer</code> pushes, canonical REST intake, webhook ingestion, lifecycle updates, one-time WordPress follow-up events such as <code>login</code>, <code>sign_up</code>, and <code>comment_submit</code>, and optional WooCommerce storefront events.</li>
<li><strong>Delivery</strong>: optional server-side transport, retry queue, diagnostics, consent-aware dispatch, and failure telemetry.</li>
</ul>
<h4>Recent additions</h4>
<p>Recent releases extended the Gravity Forms integration with channel classification, merge tags, and per-form controls:</p>
<ul>
<li><strong>Channel classification</strong>: every GF entry now receives a <code>ct_ft_channel</code> value — a human-readable label such as Google Ads, ChatGPT, or Mailchimp — derived from click IDs, UTM parameters, or referrer context. A server-side fallback covers sessions where JS attribution was unavailable.</li>
<li><strong>Expanded click ID capture</strong>: six additional click IDs (Reddit <code>rdt_cid</code>, Pinterest <code>pin_cid</code>, Snapchat <code>snap_cid</code>, Mailchimp <code>mc_cid</code> / <code>mc_eid</code>, and Display & Video 360 <code>dclid</code>) are now captured and stored.</li>
<li><strong>Merge tags</strong>: nine <code>{clicutcl_*}</code> merge tags are available in GF notifications and confirmations, including <code>{clicutcl_channel}</code>, <code>{clicutcl_click_id}</code>, and seven UTM-based tags.</li>
<li><strong>Per-form toggle</strong>: attribution tracking can be enabled or disabled per form via a dedicated ClickTrail section in Gravity Forms form settings.</li>
<li><strong>Admin QA mode</strong>: attribution data is stored in <code>sessionStorage</code> only when a <code>manage_options</code> user is logged in, preventing admin browsing from appearing in attribution reports.</li>
<li><strong>sessionStorage fallback</strong>: attribution capture now falls back to <code>sessionStorage</code> when the browser blocks cookies.</li>
<li><strong>Minification protection</strong>: ClickTrail script tags carry exclusion attributes recognised by Autoptimize, Cloudflare Rocket Loader, WP Rocket, and LiteSpeed Cache (corrected attribute set in 1.7.0).</li>
</ul>
<h4>Current admin structure</h4>
<p>The main settings experience is organized by capability:</p>
<ul>
<li>Capture</li>
<li>Forms</li>
<li>Events</li>
<li>Delivery</li>
</ul>
<p>Operational screens stay separate:</p>
<ul>
<li>Logs</li>
<li>Diagnostics</li>
</ul>
<h4>Supported integrations</h4>
<ul>
<li><strong>Forms</strong>: Contact Form 7, Elementor Forms (Pro), Fluent Forms, Gravity Forms, Ninja Forms, WPForms</li>
<li><strong>Commerce</strong>: WooCommerce</li>
<li><strong>CMP sources</strong>: ClickTrail banner, Cookiebot, OneTrust, Complianz, GTM, custom</li>
<li><strong>Webhook providers</strong>: Calendly, HubSpot, Typeform</li>
<li><strong>Server-side adapters</strong>: Generic collector, sGTM, Meta CAPI, Google Ads / GA4, LinkedIn CAPI, Pinterest Conversions API, TikTok Events API</li>
</ul>
<h4>Forms behavior by plugin</h4>
<ul>
<li><strong>Contact Form 7 and Fluent Forms</strong>: ClickTrail can add hidden attribution fields automatically.</li>
<li><strong>Gravity Forms and WPForms</strong>: ClickTrail can populate matching hidden fields you add to the form.</li>
<li><strong>Recommended for Gravity Forms and WPForms</strong>: add the hidden fields you want stored or exported, and ClickTrail will fill them.</li>
<li><strong>Elementor Forms (Pro)</strong>: ClickTrail uses the available submission hooks and attribution fallback, not automatic hidden-field injection.</li>
<li><strong>Ninja Forms</strong>: ClickTrail stores attribution with the submission and surfaces it in the submission record, not as automatic hidden-field injection.</li>
</ul>
<h4>Supported click IDs</h4>
<ul>
<li>Google: <code>gclid</code>, <code>wbraid</code>, <code>gbraid</code></li>
<li>Meta: <code>fbclid</code></li>
<li>TikTok: <code>ttclid</code></li>
<li>Microsoft: <code>msclkid</code></li>
<li>X / Twitter: <code>twclid</code></li>
<li>LinkedIn: <code>li_fat_id</code></li>
<li>Snapchat: <code>sccid</code></li>
<li>Pinterest: <code>epik</code></li>
</ul>
<h4>Additional capture fields</h4>
<ul>
<li>Extended UTMs: <code>utm_id</code>, <code>utm_source_platform</code>, <code>utm_creative_format</code>, <code>utm_marketing_tactic</code></li>
<li>Browser/platform identifiers: <code>fbc</code>, <code>fbp</code>, <code>_ttp</code>, <code>li_gc</code>, <code>ga_client_id</code>, <code>ga_session_id</code></li>
</ul>


ClickTrail – UTM, Click ID & Ad Tracking (with Consent)

Consent-aware attribution for WooCommerce, WordPress forms, and event flows. Capture UTMs and click IDs across conversion paths.

Stella Cookies vs ClickTrail – UTM, Click ID & Ad Tracking (with Consent)