Markopolo AI vs OneLence Connect for WordPress

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

OneLence is a marketing decision layer that helps teams understand which channels, campaigns, creators, affiliates, and customer journeys actually contribute to growth—so decisions are based on evidence, not guesswork. OneLence Connect is the official WordPress integration for the OneLence platform. It sends reliable server-side attribution and conversion data from your WordPress site into your OneLence workspace, including WooCommerce activity, with less data loss from ad blockers and browser restrictions. Once connected, your WordPress data becomes part of the broader OneLence decision workflow: attribution, channel evaluation, conversion analysis, reinvestment decisions, and growth prioritization. This plugin is focused on reliable data collection and delivery for OneLence. Reporting, decision workflows, and strategic insights happen inside your OneLence workspace. What you get More reliable attribution with server-side tracking and reduced data loss WooCommerce conversion tracking with automatic retry handling when delivery fails Consent-aware tracking compatible with popular CMPs and OneLence Consent Hybrid tracking mode that combines server reliability with browser SDK capabilities without duplicate page views No-code event setup using the Events tab with visual selectors and rule builders Diagnostics and validation tools in wp-admin, including Test Connection before launch Reliable inputs for OneLence decisions about channels, campaigns, creators, affiliates, and growth priorities What you need A OneLence account (free trial available) Use Connect to OneLence in the plugin dashboard—your site is linked and credentials are configured automatically Works on any WordPress site, including WooCommerce stores, SaaS sites, landing pages, content-driven brands, and lead-generation websites. WooCommerce support is optional but fully supported for order and conversion tracking. Learn more OneLence — marketing decision layer WordPress setup guide Integrations overview External services This plugin connects to external services. Data is only sent when tracking is enabled and your consent settings allow it. OneLence ingestion API Used to deliver server-side attribution events and WooCommerce conversions to your OneLence workspace. What is sent: page URLs, visitor identifiers (olm_vid), UTM and attribution parameters, event names and configured properties, WooCommerce order metadata when store tracking is enabled, and optional user email on login for identify events. When: on page views, configured events, conversions, and related server-side actions according to your tracking mode and consent mode. Where: https://ingest.onelence.com Provider: Crelora / OneLence — Terms of Service, Privacy Policy Mark browser SDK (Hybrid / JS-only modes) Used for client-side tracking when Hybrid or JS-only tracking modes are enabled. What is sent: analytics and attribution data configured in the plugin, including page views and custom events, subject to your CMP and consent settings. When: after consent is granted (or immediately when no CMP is detected and your consent mode allows it). Where: the Mark SDK bundled inside this plugin (assets/js/mark.browser.umd.js). No third-party script host is used on WordPress.org builds. Provider: Crelora / OneLence — Terms of Service, Privacy Policy Connect to OneLence (setup) Used when an administrator clicks Connect to OneLence in wp-admin to link the WordPress site to a OneLence workspace. What is sent: OAuth/session tokens and site metadata required to obtain API credentials. When: during the administrator-initiated connect flow. Where: OneLence web properties under onelence.com Provider: Crelora / OneLence — Terms of Service, Privacy Policy OneLence Consent (optional separate plugin) Not required. If installed, OneLence Connect reads consent signals from that plugin and may forward optional coverage metrics when forwarding is enabled in settings. What is sent: consent state required for tracking decisions and optional lightweight coverage metrics when forwarding is enabled. When: while visitors interact with the consent banner and when forwarding is enabled. Where: local WordPress installation (OneLence Consent plugin). Download: onelence.com/consent/download Provider: Crelora / OneLence — Terms of Service, Privacy Policy Privacy Cookies: olm_vid (visitor identity) and olm_utm (attribution parameters). These are set according to your consent mode and detected CMP. Consent: OneLence Connect reads consent signals from your CMP; it does not replace your cookie banner. Optional OneLence Consent is available as a separate plugin. WordPress tools: Personal data export is registered with WordPress privacy tools. Use Keep Data on Uninstall in Tracking settings if you want plugin options retained after uninstall. Policy: OneLence privacy policy For developers OneLence Connect exposes WordPress hooks for custom integrations, including: onelco_should_track onelco_event_payload onelco_conversion_payload onelco_visitor_id onelco_event_sent onelco_conversion_sent onelco_load_mark_sdk Custom conversions can use: ONELCO_Tracker::track_custom_conversion() onelco_track_custom_conversion action Full integration reference: WordPress setup docs