Overview
If your website is built with a CMS, website builder, ecommerce platform, or static HTML setup, you can activate OneLence by adding a small script snippet to your site.
This is the fastest way to enable base tracking without installing a package or modifying your application build process.
Use this method for setups such as:
- WordPress
- Webflow
- Shopify theme code
- static HTML sites
- simple front-end websites without npm or yarn
If your site runs on WordPress, you can follow the dedicated WordPress Setup guide for platform-specific placement examples and conversion tracking patterns.
Use the snippet from your own OneLence onboarding page
In your OneLence onboarding page, you will see a tracking snippet that is already prepared for your workspace.
Use the snippet shown in your own workspace.
Do Not copy the example values from this documentation, because the tracking key and site details shown here are for explanation only.
In case you're logged in as an OneLence user, you can fetch real values and use the code directly for your integration.
<script src="https://unpkg.com/@crelora/mark@latest/dist/browser.umd.js"></script>
<script>
Mark.init({
key: 'pk_your_publishable_key',
require_consent: false,
autocapture: { pageview: true },
site_id: 'your_site_id',
site_host: 'your-site-host'
});
</script>
Where to place the snippet
Add the snippet to a site-wide code area so it loads on every page. Depending on your platform, this may be called:
- Layout
<head>section - Head code injection
- Global custom code
- Site-wide
<script>area - Theme header code
For traditional HTML sites, place it inside the <head> section of your main template.
On builders such as WordPress or Webflow, this is typically added through a global site settings or custom code panel.
What happens after installation
Once the snippet is added and your site is published, OneLence automatically begins capturing:
- page view activity
- visitor session signals
- marketing attribution parameters such as UTM values and click IDs
This is called base tracking.
Base tracking does not automatically include custom interactions such as:
- button clicks
- form submissions
- sign-up actions
- purchase events
- custom conversions
These require additional event configuration later in the setup process.
If your product uses a JavaScript application framework and you want more control over event tracking, continue to the developer setup path.