[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fh_wpHwEoLWLd2_THt0xWfN_19nsDl-2XlJwqvN7YYTs":3},{"slug":4,"display_name":5,"profile_url":6,"plugin_count":7,"total_installs":8,"avg_security_score":9,"avg_patch_time_days":10,"trust_score":11,"computed_at":12,"plugins":13},"hugoc","Hugo Carvalho","https:\u002F\u002Fprofiles.wordpress.org\u002Fhugoc\u002F",2,10,100,30,94,"2026-04-05T13:19:11.439Z",[14,36],{"slug":15,"name":16,"version":17,"author":5,"author_profile":6,"description":18,"short_description":19,"active_installs":8,"downloaded":20,"rating":21,"num_ratings":21,"last_updated":22,"tested_up_to":23,"requires_at_least":24,"requires_php":25,"tags":26,"homepage":32,"download_link":33,"security_score":9,"vuln_count":21,"unpatched_count":21,"last_vuln_date":34,"fetched_at":35},"click-trail-handler","ClickTrail – UTM, Click ID & Ad Tracking (with Consent)","1.5.2","\u003Cp>ClickTrail stores attribution data from landing pages and keeps it available for later form submissions, WooCommerce orders, and event flows.\u003C\u002Fp>\n\u003Cp>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 \u003Ccode>view_item\u003C\u002Fcode>, \u003Ccode>view_item_list\u003C\u002Fcode>, \u003Ccode>view_cart\u003C\u002Fcode>, \u003Ccode>add_to_cart\u003C\u002Fcode>, \u003Ccode>remove_from_cart\u003C\u002Fcode>, and \u003Ccode>begin_checkout\u003C\u002Fcode>, plus post-purchase milestones, through the same ClickTrail pipeline.\u003C\u002Fp>\n\u003Cp>It is designed for cases where attribution often breaks in practice: cached pages, dynamic forms, multi-page journeys, repeat visits, consent requirements, and optional server-side delivery.\u003C\u002Fp>\n\u003Cp>The plugin keeps first-touch and last-touch context available until the conversion point and makes that context usable inside WordPress.\u003C\u002Fp>\n\u003Cp>It captures first-touch and last-touch source data, keeps it available during the user journey, and makes that data usable where conversions actually happen:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>WooCommerce orders\u003C\u002Fli>\n\u003Cli>supported forms\u003C\u002Fli>\n\u003Cli>browser events\u003C\u002Fli>\n\u003Cli>optional server-side delivery\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Teams can start with order or form attribution first, then add browser events, consent handling, or server-side transport when needed.\u003C\u002Fp>\n\u003Ch4>What problems it solves\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Cstrong>WooCommerce orders losing source data\u003C\u002Fstrong>: 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.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Checkout continuity breaking before purchase\u003C\u002Fstrong>: WooCommerce storefront journeys can now emit opt-in \u003Ccode>view_item\u003C\u002Fcode>, \u003Ccode>view_item_list\u003C\u002Fcode>, \u003Ccode>view_cart\u003C\u002Fcode>, \u003Ccode>add_to_cart\u003C\u002Fcode>, \u003Ccode>remove_from_cart\u003C\u002Fcode>, and \u003Ccode>begin_checkout\u003C\u002Fcode> signals through the same ClickTrail event layer used elsewhere in the plugin.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Cached or dynamic forms\u003C\u002Fstrong>: Hidden fields often break on cached pages or AJAX-rendered forms. ClickTrail includes client-side fallback and dynamic-content support.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Cross-domain breaks\u003C\u002Fstrong>: Approved link decoration and attribution tokens help keep continuity between domains or subdomains.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Consent and transport complexity\u003C\u002Fstrong>: Consent controls, browser events, webhook intake, and server-side transport live in the same plugin.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Core capabilities\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Cstrong>Capture\u003C\u002Fstrong>: first-touch and last-touch UTMs, major ad click IDs, and referrers with automatic organic\u002Fsocial\u002Freferral fallback when UTMs are absent.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>WooCommerce\u003C\u002Fstrong>: checkout attribution persistence, thank-you purchase event push, enriched commerce payloads, optional storefront commerce events, and optional order-status milestones.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Forms\u003C\u002Fstrong>: 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.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Events\u003C\u002Fstrong>: browser event collection with \u003Ccode>dataLayer\u003C\u002Fcode> pushes, canonical REST intake, webhook ingestion, lifecycle updates, one-time WordPress follow-up events such as \u003Ccode>login\u003C\u002Fcode>, \u003Ccode>sign_up\u003C\u002Fcode>, and \u003Ccode>comment_submit\u003C\u002Fcode>, and optional WooCommerce storefront events.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Delivery\u003C\u002Fstrong>: optional server-side transport, retry queue, diagnostics, consent-aware dispatch, and failure telemetry.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>What is new in 1.5.2\u003C\u002Fh4>\n\u003Cp>This maintenance release focuses on code-quality cleanup and standards compliance without changing runtime behavior:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Line-ending cleanup\u003C\u002Fstrong>: normalized mixed line endings in key PHP handlers so packaging and standards checks stay consistent across environments.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Standards cleanup\u003C\u002Fstrong>: resolved PHPCS findings in the consent, attribution-token, and privacy handlers, including targeted documentation for intentional exceptions.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>No runtime change\u003C\u002Fstrong>: behavior remains the same as \u003Ccode>1.5.1\u003C\u002Fcode>; this is a maintenance release focused on code hygiene.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Current admin structure\u003C\u002Fh4>\n\u003Cp>The main settings experience is organized by capability:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Capture\u003C\u002Fli>\n\u003Cli>Forms\u003C\u002Fli>\n\u003Cli>Events\u003C\u002Fli>\n\u003Cli>Delivery\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Operational screens stay separate:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Logs\u003C\u002Fli>\n\u003Cli>Diagnostics\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Supported integrations\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Cstrong>Forms\u003C\u002Fstrong>: Contact Form 7, Elementor Forms (Pro), Fluent Forms, Gravity Forms, Ninja Forms, WPForms\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Commerce\u003C\u002Fstrong>: WooCommerce\u003C\u002Fli>\n\u003Cli>\u003Cstrong>CMP sources\u003C\u002Fstrong>: ClickTrail banner, Cookiebot, OneTrust, Complianz, GTM, custom\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Webhook providers\u003C\u002Fstrong>: Calendly, HubSpot, Typeform\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Server-side adapters\u003C\u002Fstrong>: Generic collector, sGTM, Meta CAPI, Google Ads \u002F GA4, LinkedIn CAPI, Pinterest Conversions API, TikTok Events API\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Forms behavior by plugin\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Cstrong>Contact Form 7 and Fluent Forms\u003C\u002Fstrong>: ClickTrail can add hidden attribution fields automatically.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Gravity Forms and WPForms\u003C\u002Fstrong>: ClickTrail can populate matching hidden fields you add to the form.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Recommended for Gravity Forms and WPForms\u003C\u002Fstrong>: add the hidden fields you want stored or exported, and ClickTrail will fill them.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Elementor Forms (Pro)\u003C\u002Fstrong>: ClickTrail uses the available submission hooks and attribution fallback, not automatic hidden-field injection.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Ninja Forms\u003C\u002Fstrong>: ClickTrail stores attribution with the submission and surfaces it in the submission record, not as automatic hidden-field injection.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Supported click IDs\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Google: \u003Ccode>gclid\u003C\u002Fcode>, \u003Ccode>wbraid\u003C\u002Fcode>, \u003Ccode>gbraid\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>Meta: \u003Ccode>fbclid\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>TikTok: \u003Ccode>ttclid\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>Microsoft: \u003Ccode>msclkid\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>X \u002F Twitter: \u003Ccode>twclid\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>LinkedIn: \u003Ccode>li_fat_id\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>Snapchat: \u003Ccode>sccid\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>Pinterest: \u003Ccode>epik\u003C\u002Fcode>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Additional capture fields\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Extended UTMs: \u003Ccode>utm_id\u003C\u002Fcode>, \u003Ccode>utm_source_platform\u003C\u002Fcode>, \u003Ccode>utm_creative_format\u003C\u002Fcode>, \u003Ccode>utm_marketing_tactic\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>Browser\u002Fplatform identifiers: \u003Ccode>fbc\u003C\u002Fcode>, \u003Ccode>fbp\u003C\u002Fcode>, \u003Ccode>_ttp\u003C\u002Fcode>, \u003Ccode>li_gc\u003C\u002Fcode>, \u003Ccode>ga_client_id\u003C\u002Fcode>, \u003Ccode>ga_session_id\u003C\u002Fcode>\u003C\u002Fli>\n\u003C\u002Ful>\n","Consent-aware attribution for WooCommerce, WordPress forms, and event flows. Capture UTMs and click IDs across conversion paths.",638,0,"2026-03-14T19:20:00.000Z","6.9.4","6.5","8.1",[27,28,29,30,31],"attribution","consent-mode","server-side-tracking","utm","woocommerce","https:\u002F\u002Fgithub.com\u002Fvizuh\u002Fclick-trail-handler","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fclick-trail-handler.1.5.2.zip",null,"2026-03-15T14:54:45.397Z",{"slug":37,"name":38,"version":39,"author":5,"author_profile":6,"description":40,"short_description":41,"active_installs":21,"downloaded":42,"rating":21,"num_ratings":21,"last_updated":43,"tested_up_to":23,"requires_at_least":44,"requires_php":45,"tags":46,"homepage":52,"download_link":53,"security_score":9,"vuln_count":21,"unpatched_count":21,"last_vuln_date":34,"fetched_at":54},"floaty-book-now-chat","Floaty Book Now Chat","1.0.0","\u003Cp>Floaty adds a clean floating call-to-action button to your site so visitors can \u003Cstrong>book faster\u003C\u002Fstrong> or \u003Cstrong>start a WhatsApp chat\u003C\u002Fstrong>—without digging through menus.\u003C\u002Fp>\n\u003Cp>Choose your mode:\u003Cbr \u002F>\n* WhatsApp mode: click-to-chat with optional prefilled message\u003Cbr \u002F>\n* Custom mode: open a link or launch an iframe modal (great for booking widgets)\u003C\u002Fp>\n\u003Ch4>Key Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Floating CTA on every page (bottom-left \u002F bottom-right)\u003C\u002Fli>\n\u003Cli>Modes: WhatsApp or Custom\u003C\u002Fli>\n\u003Cli>Custom mode actions: open link or iframe modal\u003C\u002Fli>\n\u003Cli>dataLayer click event for GTM\u002FGA4 tracking\u003C\u002Fli>\n\u003Cli>Custom CSS field for quick styling overrides\u003C\u002Fli>\n\u003Cli>Lean, WordPress-native settings UI\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Apointoo Booking (Optional)\u003C\u002Fh4>\n\u003Cp>If you use Apointoo, Floaty includes an optional integration tab for booking configuration used in Google Search\u002FMaps booking flows where available via your provider setup.\u003C\u002Fp>\n\u003Cp>Need a Merchant ID? Email support@vizuh.com.\u003C\u002Fp>\n\u003Cp>Note: Booking visibility on Google Search\u002FMaps depends on eligibility and provider setup.\u003C\u002Fp>\n","Lightweight floating “Book Now” button + WhatsApp chat. Open a link, launch a modal, and track clicks via dataLayer.",102,"2026-01-07T02:53:00.000Z","6.4","7.4",[47,48,49,50,51],"appointments","booking","chat","modal","whatsapp","https:\u002F\u002Fgithub.com\u002Fvizuh\u002Ffloaty-book-now","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ffloaty-book-now-chat.1.0.0.zip","2026-03-15T15:16:48.613Z"]