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.

Buildio

<p>Ad blockers, iOS privacy changes and cookie restrictions mean your browser-based tracking pixel is only reporting a fraction of your actual conversions. Your ads cannot optimise on data they never receive.</p>
<p>UniPixel fixes this by sending conversion events directly from your WordPress server to Meta, Pinterest, TikTok, Google and Microsoft — bypassing the browser entirely. No external cloud hosting, no GTM server container. Install, paste your credentials, and server-side tracking is live.</p>
<h3>What It Does</h3>
<ul>
<li><strong>Meta Conversion API (CAPI)</strong> — server-side and client-side event sending with full deduplication.</li>
<li><strong>Pinterest Conversions API</strong> — server-side and client-side tracking with full deduplication.</li>
<li><strong>TikTok Events API</strong> — server-side and client-side tracking with automatic deduplication.</li>
<li><strong>GA4 Measurement Protocol</strong> — server-side event delivery to Google Analytics and Google Ads.</li>
<li><strong>Microsoft UET & Conversions API</strong> — client-side tracking via UET with early support for Microsoft’s Conversions API (CAPI) pilot program. WooCommerce events and custom events supported.</li>
<li><strong>WooCommerce events</strong> — ViewContent, AddToCart, InitiateCheckout and Purchase tracked automatically with full product data (names, categories, variants, values).</li>
<li><strong>Custom events</strong> — create your own click, view and interaction events for any WordPress page. Not limited to WooCommerce.</li>
<li><strong>Automatic deduplication</strong> — each event gets a unique ID shared between client and server, so platforms count it once.</li>
<li><strong>Built-in consent management</strong> — fully featured popup with built-in translations for 18 languages, editable wording per language, 5 layout styles (centred card / top or bottom bar / corner card), optional non-blocking mode, and a Reject all button toggle. Or skip the popup entirely and let UniPixel read consent from your existing CMP — supports OneTrust, Cookiebot, Osano, Silktide, Orest Bida, Complianz, CookieYes, Moove GDPR, and CookieAdmin (Softaculous).</li>
<li><strong>Live event testing</strong> — real-time console shows events as they fire, with full payload data.</li>
<li><strong>Event logging</strong> — optional database storage of every event sent, for debugging and audit.</li>
</ul>
<h3>Why Server-Side Tracking Matters</h3>
<p>Around 43% of internet users run ad blockers. Safari limits cookies to 7 days. iOS App Tracking Transparency reduced reported conversions by 30-40% for many advertisers. When your tracking relies only on a browser pixel, these restrictions silently discard your conversion data.</p>
<p>Server-side tracking sends conversion data directly from your server to the ad platform API. Ad blockers cannot touch it. Cookie limits do not apply. The result: your ad platforms see your real conversions, optimise better, and your ad spend works harder.</p>
<h3>Why UniPixel</h3>
<p>UniPixel sends API calls directly from your own WordPress server. No GTM server container, no external cloud, no routing your data through third-party services.</p>
<ul>
<li><strong>Meta, Pinterest, TikTok, Google and Microsoft</strong> — server-side and client-side tracking for all five platforms.</li>
<li><strong>No GTM required</strong> — no server container setup, no custom subdomain, no separate hosting.</li>
<li><strong>No external cloud</strong> — your data goes from your server to the ad platform. Nothing in between.</li>
<li><strong>Works on any WordPress site</strong> — WooCommerce stores get automatic ecommerce event tracking. Non-WooCommerce sites use custom events for lead gen, SaaS, content or anything else.</li>
<li><strong>Five-minute setup</strong> — install, enter your Pixel ID and access token, enable the platform. Done.</li>
</ul>
<p>Optional <a href="https://unipixelhq.com/unipixel-docs/advanced-matching-setting-with-unipixel/" rel="nofollow ugc">Advanced Matching</a> sends hashed user data (email, phone, address) alongside events to help platforms improve Event Match Quality.</p>
<h3>Tips</h3>
<h4>Deduplication</h4>
<p>UniPixel automatically prevents duplicate counting when both client-side and server-side events are enabled.</p>
<p>Each event is assigned a unique <strong>event_id</strong> when triggered. This same ID is sent to both the browser pixel and the server API, allowing platforms to merge identical events.</p>
<ul>
<li><strong>Meta (Facebook / Instagram)</strong> — uses <code>event_id</code> to match Pixel and Conversion API events so they count once.</li>
<li><strong>Pinterest</strong> — uses <code>event_id</code> to match Tag and Conversions API events for full deduplication.</li>
<li><strong>TikTok</strong> — uses shared event IDs across Pixel and Events API for seamless deduplication.</li>
<li><strong>Google (GA4 / Ads)</strong> — uses shared <code>client_id</code> and <code>session_id</code> values for client/server matching. Works automatically for both client-first and server-first setups.</li>
<li><strong>Microsoft (Bing / UET)</strong> — uses <code>eventId</code> to match UET tag and Conversions API events for deduplication.</li>
</ul>
<p>No extra setup is required — UniPixel handles ID creation and matching automatically.</p>
<h3>Privacy and 3rd Party Services</h3>
<p>This plugin sends event data to external services for analytics and advertising purposes. Data is only sent to platforms you have enabled in UniPixel settings.</p>
<ul>
<li><strong>Meta (Facebook) Pixel and Conversion API</strong>: Sends user event data (e.g., PageView, Purchase) to Meta for tracking and ad optimisation.</li>
<li><strong>Pinterest Tag and Conversions API</strong>: Sends event data to Pinterest for ad tracking and campaign optimisation.</li>
<li><strong>TikTok Pixel and Events API</strong>: Sends event data to TikTok for ad tracking and campaign optimisation.</li>
<li><strong>Google Analytics and Measurement Protocol</strong>: Sends event data to Google for analytics and conversion tracking via GA4 and Google Tag Manager.</li>
<li><strong>Microsoft UET and Conversions API</strong>: Sends event data to Microsoft for ad tracking and conversion optimisation via Bing Ads.</li>
</ul>
<h3>Domains</h3>
<p>This plugin communicates with the following domains:<br />
– <strong>Meta (Facebook)</strong>:<br />
  – https://www.facebook.com<br />
  – https://graph.facebook.com<br />
– <strong>Google</strong>:<br />
  – https://www.google-analytics.com<br />
  – https://www.googletagmanager.com<br />
– <strong>Pinterest</strong>:<br />
  – https://api.pinterest.com<br />
  – https://s.pinimg.com<br />
– <strong>TikTok</strong>:<br />
  – https://business-api.tiktok.com<br />
– <strong>Microsoft</strong>:<br />
  – https://bat.bing.com<br />
  – https://capi.uet.microsoft.com<br />
– <strong>Buildio</strong>:<br />
  – https://buildio.dev</p>
<h3>Data Sent</h3>
<p>Data sent to these domains may include:<br />
– User interactions (e.g., clicks, page views, purchases)<br />
– IP address and user agent (collected by tracking mechanisms)<br />
– Custom event data such as purchase amount, currency, and transaction ID (depending on configuration)<br />
– Diagnostic information may be sent to Buildio to assist with plugin performance and bug fixes, including site URL, IP address and basic interactions. No sensitive information or keys are sent.</p>
<h3>Privacy and Terms</h3>
<p>For more details on privacy policies and terms of use, please visit the following links:</p>
<ul>
<li><a href="https://www.facebook.com/about/privacy" rel="nofollow ugc">Meta (Facebook) Privacy Policy</a></li>
<li><a href="https://www.facebook.com/terms.php" rel="nofollow ugc">Meta (Facebook) Terms of Service</a></li>
<li><a href="https://policies.google.com/privacy" rel="nofollow ugc">Google Privacy Policy</a></li>
<li><a href="https://policies.google.com/terms" rel="nofollow ugc">Google Terms of Service</a></li>
<li><a href="https://policy.pinterest.com/privacy-policy" rel="nofollow ugc">Pinterest Privacy Policy</a></li>
<li><a href="https://policy.pinterest.com/terms-of-service" rel="nofollow ugc">Pinterest Terms of Service</a></li>
<li><a href="https://www.tiktok.com/legal/privacy-policy" rel="nofollow ugc">TikTok Privacy Policy</a></li>
<li><a href="https://www.tiktok.com/legal/terms-of-service" rel="nofollow ugc">TikTok Terms of Service</a></li>
<li><a href="https://privacy.microsoft.com/privacystatement" rel="nofollow ugc">Microsoft Privacy Statement</a></li>
<li><a href="https://about.ads.microsoft.com/en-us/resources/policies/microsoft-advertising-agreement" rel="nofollow ugc">Microsoft Advertising Agreement</a></li>
<li><a href="https://unipixelhq.com/privacy" rel="nofollow ugc">UniPixel Privacy Policy</a></li>
</ul>
<h3>License</h3>
<p>This plugin is licensed under the GPLv2 or later.</p>


UniPixel: Meta, Pinterest, TikTok, Google & Microsoft Server-Side Tracking for WooCommerce

Send conversion events from your WordPress server to Meta, Pinterest, TikTok, Google and Microsoft. No cloud, no GTM. WooCommerce and custom events.

ClickTrail – UTM, Click ID & Ad Tracking (with Consent) vs UniPixel: Meta, Pinterest, TikTok, Google & Microsoft Server-Side Tracking for WooCommerce