cgzirim

<p>Markopolo AI is a lightweight tracking plugin that captures key WordPress site events and sends them to the Markopolo AI analytics platform for reporting and attribution.</p>
<h4>Key Features</h4>
<ul>
<li><strong>Page and interaction tracking</strong>: captures <code>page_view</code>, <code>click</code>, <code>form_interaction</code>, and <code>Search</code> events.</li>
<li><strong>Form data capture</strong>: can capture name, email, and phone values when they are present in forms.</li>
<li><strong>Session tracking</strong>: uses a UUID-based session identifier to group user activity.</li>
<li><strong>First-party identifier</strong>: manages a <code>muid</code> cookie for visitor identification.</li>
<li><strong>Marketing attribution data</strong>: can include common attribution cookies such as Facebook Pixel, TikTok, Google Analytics, and Microsoft UET cookies when present.</li>
<li><strong>Simple configuration</strong>: add your Tag ID from a WordPress admin settings page.</li>
<li><strong>Lightweight front-end script</strong>: loads only when a valid Tag ID and endpoint are configured.</li>
</ul>
<h4>How It Works</h4>
<ol>
<li>Install and activate the plugin.</li>
<li>Go to <strong>Settings > Markopolo AIr</strong>.</li>
<li>Enable <strong>Enable Tracking</strong> in plugin settings.</li>
<li>Enter your <strong>Tag ID</strong>.</li>
<li>Save settings.</li>
<li>The plugin loads its front-end script and sends tracked events to the Markopolo endpoint.</li>
</ol>
<p>Tracking is off by default. The plugin does not load front-end tracking until <strong>Enable Tracking</strong> is enabled by an admin and a valid Tag ID is provided.</p>
<h3>External Services</h3>
<p>This plugin relies on Markopolo AI services to provide analytics and attribution functionality.</p>
<h4>Service A: Event ingestion endpoint</h4>
<ul>
<li><strong>What it is used for</strong>: Receiving browser-side analytics events for reporting and attribution.</li>
<li><strong>Endpoint</strong>: <code>https://mtag.markopolo.ai/mark</code></li>
<li><strong>When data is sent</strong>: On tracked front-end events (for example page views, clicks, form interactions, and search events) only after admin opt-in via <strong>Enable Tracking</strong>, with a valid Tag ID and endpoint configured.</li>
<li><strong>Data sent may include</strong>: tag ID, page URL/path/title, referrer, language, timezone, viewport/screen data, session and visitor identifiers, attribution cookies when available, click metadata, and form-related values such as name/email/phone/search terms when detected.</li>
</ul>
<h4>Service B: Settings webhook endpoint</h4>
<ul>
<li><strong>What it is used for</strong>: Notifying Markopolo when plugin settings lifecycle events occur.</li>
<li><strong>Endpoint</strong>: <code>https://api-alpha.markopolo.ai/v1/integrations/wordpress/webhook</code></li>
<li><strong>When data is sent</strong>:
<ul>
<li>Only after an admin has enabled <strong>Enable Tracking</strong>.</li>
<li>When Tag ID is set for the first time.</li>
<li>When Tag ID is updated.</li>
<li>When Tag ID is removed.</li>
<li>During plugin uninstall, only when tracking is enabled and a Tag ID is configured.</li>
</ul>
</li>
<li><strong>Data sent</strong>: event name, tag ID, previous tag ID (when applicable), plugin name, site URL, and event timestamp.</li>
</ul>
<h4>Service terms and privacy</h4>
<ul>
<li>Terms and legal information: https://markopolo.ai/legal</li>
<li>Privacy policy: https://markopolo.ai/legal</li>
</ul>
<h4>Event Types Tracked</h4>
<ul>
<li><strong>page_view</strong>: fired on page load.</li>
<li><strong>click</strong>: fired when users interact with common clickable elements.</li>
<li><strong>form_interaction</strong>: fired on form change and submit events.</li>
<li><strong>Search</strong>: fired when a search term is detected from a search form or search URL.</li>
</ul>
<h4>Data Collected</h4>
<p>Depending on the page and user interaction, the plugin may collect and send:</p>
<ul>
<li>Page URL, path, title, referrer, language, timezone, viewport, and screen size</li>
<li>Session ID and visitor identifier (<code>muid</code>)</li>
<li>Marketing attribution cookies when available</li>
<li>Form values such as name, email, phone, and search terms</li>
<li>Click metadata such as element text, ID, class, and coordinates</li>
</ul>
<h4>Privacy & Consent</h4>
<p>This plugin tracks customer behavior including:<br />
* Page views, clicks, searches, and form interactions<br />
* Email addresses and phone numbers from form interactions<br />
* Marketing cookies (Facebook Pixel, TikTok, Google Analytics)<br />
* Session data and user identifiers</p>
<p>All data is sent to the Markopolo AI platform for analytics purposes. Ensure your privacy policy covers this data collection and complies with applicable privacy regulations (GDPR, CCPA, etc.).</p>
<p>Important: Site owners are responsible for obtaining any user consent required under applicable laws and regulations before enabling or using tracking features.</p>
<p>Plugin-level enablement requires admin opt-in. If <strong>Enable Tracking</strong> is disabled, front-end tracking and settings webhooks are disabled. Front-end tracking also requires a valid Tag ID.</p>
<h4>Developer Notes</h4>
<ul>
<li>The plugin uses a WordPress admin settings page for configuration.</li>
<li>Settings are sanitized before being saved.</li>
<li>Events are sent asynchronously from the front end.</li>
<li>The plugin includes an uninstall routine that removes its saved settings.</li>
</ul>
<h3>Support</h3>
<p>For support, contact the Markopolo team through your account or via email support@markopolo.ai.</p>


Markopolo AI

Track WordPress events and send them to the Markopolo AI analytics platform.

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.

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