About this plugin
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. Visitor 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, the visitor’s IP address and browser headers (used to tell people from bots and to check a crawler against its operator’s published addresses), 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
OneLence bot choices
Used to download which bots and crawlers your OneLence workspace keeps, and OneLence’s current list of bots when it changed, so server-side tracking doesn’t send visits from the bots your workspace doesn’t keep.
- What is sent: your site’s address, its OneLence site identifier and secret key, the version of the plugin’s list of bots, and how many visits from bots your workspace doesn’t keep were skipped, per day and bot. No visitor data is sent.
- When: every 15 minutes, and when the plugin’s settings change, while server-side or hybrid tracking has a secret key.
- 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