Standard embed

The raw tracking snippet for any site — it follows the embed type chosen in Settings. Most platforms are easier to set up from Platforms.
Third-party embed active — the tracker loads from {{TRACKDOMAIN}}. Fastest setup, but Safari may cap the cookie. You can switch to first-party in Settings.
1Add to every page's <head>
Paste before </head> on every page of the site.
Embed snippet
<script async
  src="{{EMBED}}/tracker.js"
  data-write-key="{{KEY}}"></script>

Platforms

Pick a platform to set it up — each opens step-by-step with copy-paste code.
Stores
Kanalio
Kanalio
Store & checkout
Shopify
Shopify
Store & checkout
WooCommerce
WooCommerce
Orders & refunds
Websites & builders
WordPress
WordPress
Blog & website
Lovable
Lovable
Landing page
Wix
Wix
Website
Squarespace
Squarespace
Website
Webflow
Webflow
Website
Framer
Framer
Website
Forms
Typeform
Typeform
Lead forms
WPForms
WPForms
Lead forms
Everything else
Custom HTML
Custom HTML
Any website

Privacy & cookie policy

Paste this into your privacy or cookie policy page. It's a template — have your counsel review it.
English
Analytics & conversion measurement (Tracking)

This website uses Tracking, an analytics and conversion-measurement service operated for us at {{TRACKDOMAIN}}, to understand which marketing campaigns bring visitors to our site and to measure purchases and enquiries.

Cookies. We set _rvx_vid, a random visitor identifier used to attribute your visit and any later purchase or enquiry to the campaign that brought you here (duration: up to 13 months). Where present, we also read the _fbp and _fbc cookies (set by Meta) and the _ga cookie (set by Google) to improve conversion-measurement accuracy.

Data we collect. Pages you visit on this site (URL, referrer, page title), browser language, device and browser type, IP address, advertising click identifiers when you arrive from an ad (e.g. gclid — Google; fbclid — Meta; msclkid — Microsoft; ttclid — TikTok) and campaign (UTM) parameters. When you make a purchase or submit a form, we additionally process the order value and currency, your email address, phone number, name and billing city/postcode/country.

How it is shared. Directly identifying data (email address, phone number, name and billing address details) is pseudonymised by hashing (SHA-256) before it is shared. Technical identifiers — your IP address, browser information and the Meta cookie identifiers (_fbp/_fbc) — are shared in their original form, as the advertising platforms' interfaces require. Recipients: Meta Platforms Ireland Ltd (Conversions API) and Google Ireland Ltd (Google Analytics 4 / Google Ads enhanced conversions), for the purpose of measuring advertising performance.

Legal basis. Your consent. Your consent choices are honored end-to-end (Consent Mode v2): if you decline advertising or analytics storage, the corresponding data is not sent to the advertising platforms.

Retention. The visitor cookie lasts up to 13 months; ad-click data is kept for approximately 90 days. After that period we retain only aggregated, non-identifying statistics (for example, clicks per campaign per day). Event data is retained according to our data-retention policy.

Your rights. You can withdraw consent at any time via the cookie settings on this site, and exercise your access or erasure rights by contacting us at [your contact email].

Data API

Query your tracking data from your own dashboards, scripts or AI tools. Everything is read-only, JSON, and isolated to your data server-side — your API key can only ever see your own events.
1Get your API key
Kanalio provisions it for you — ask us and we hand you a rk_live_… key once (we store only a hash). Send it on every request as Authorization: Bearer rk_live_…. Two scopes exist: read:metrics (curated metrics + schema) and read:sql (custom SQL). Keep the key server-side; never ship it in a browser.
2Discover the schema
Returns every table you can query, column meanings, correctness rules (purchases appear twice — dedupe by order id!) and example queries. If an AI writes your queries, give it this response first — it is what makes generated SQL come out right.
GET /v1/schema
curl -H "Authorization: Bearer rk_live_…" \
  {{ORIGIN}}/v1/schema
3Curated metrics
Pre-built, correction-aware metrics — same numbers everywhere. List them with GET /v1/metrics, then query with dimensions, filters, a date range and a granularity:
POST /v1/query — revenue by channel per day
curl -H "Authorization: Bearer rk_live_…" \
  -H "content-type: application/json" \
  -d '{
    "metric": "revenue",
    "dimensions": ["channel"],
    "date_range": { "from": "2026-06-01", "to": "2026-06-30" },
    "granularity": "day"
  }' \
  {{ORIGIN}}/v1/query
Response: { "rows": [{ "period": "2026-06-01", "channel": "paid_search", "revenue": 439.25, "orders": 4, "aov": 109.81 }, …], "totals": { … } }. Available metrics: conversions, revenue, attribution_last_touch, funnel, top_products, event_volume.
4Custom SQL
Full flexibility for custom panels: send one read-only SELECT (ClickHouse dialect) and get ClickHouse JSON back. Ideal for AI-generated dashboards — on an error, the database's message is returned so the AI can fix its query and retry.
POST /v1/sql
curl -H "Authorization: Bearer rk_live_…" \
  -H "content-type: application/json" \
  -d '{"sql": "SELECT event, count() AS n FROM tracking.events GROUP BY event ORDER BY n DESC"}' \
  {{ORIGIN}}/v1/sql
Limits: SELECT only, one statement per request, isolated to your data at the database server (not filterable away). 30s execution timeout, 100k rows / 100MB per query, 20MB per response. Rate limits: 120 requests/min for metrics and schema, 30/min for SQL — a 429 includes a Retry-After header.

Settings

These two values personalize every code snippet on this page — the standard embed, the platform guides and the privacy policy text. They're pre-filled from the setup link we sent you; only change them if we tell you to.
Embed type
This switch previews the snippets on this browser. The live embed type is stored with your project — tell us once your DNS record is in and we'll switch it on our side.
Fastest to set up — nothing to change on your DNS. The tracking cookie lives on {{TRACKDOMAIN}}, so Safari may drop it sooner and browsers treat it as third-party. Great for direct-response funnels (ad → landing → buy in one session); weaker for returning visitors and long consideration cycles.

Kanalio — store & checkout

Kanalio stores install tracking with the built-in Storefront Head Scripts plugin — about a minute, no theme changes.
1Install Storefront Head Scripts
Admin → Settings → Plugins → Marketplace → install Storefront Head Scripts.
2Paste the snippet
Installed tab → Configure → paste the snippet (full <script> tags — the field expects raw HTML) into Custom head script (HTML) → toggle Enable → Save. Saving triggers a storefront sync; allow a minute or two.
Embed snippet
<script async
  src="{{EMBED}}/tracker.js"
  data-write-key="{{KEY}}"
  data-source="kanalio"></script>
3Done
Page views arrive tagged kanalio, click-ids/UTMs captured. Page views only for now — server-side order tracking is a planned integration, not yet available to switch on.

Shopify — your store

1Theme code
Online Store → Themes → Edit code → open theme.liquid → paste just before </body>.
Cart-attribute bridge
<script>
(function(){function gc(n){return(document.cookie.match('(^|;)\\s*'+n+'\\s*=\\s*([^;]+)')||[])[2]||null;}
function qp(n){return new URLSearchParams(location.search).get(n);}
var v=gc('_rvx_vid')||qp('_rvx_vid'),a={'__rvx_vid':v,'__rvx_gclid':qp('gclid'),'__rvx_gbraid':qp('gbraid'),'__rvx_wbraid':qp('wbraid'),'__rvx_fbclid':qp('fbclid'),'__rvx_utm_source':qp('utm_source'),'__rvx_utm_medium':qp('utm_medium'),'__rvx_utm_campaign':qp('utm_campaign')},p={};
Object.keys(a).forEach(function(k){if(a[k])p[k]=a[k];});
if(Object.keys(p).length)fetch('/cart/update.js',{method:'POST',headers:{'Content-Type':'application/json'},body:JSON.stringify({attributes:p})}).catch(function(){});})();
</script>
2Custom Pixel
Settings → Customer events → Add custom pixel → name it "Tracking" → paste → Save.
Custom Pixel
const COLLECTOR_URL = "{{ORIGIN}}/v1/batch";
const WRITE_KEY = "{{KEY}}";

async function cookie(name) {
  try { return (await browser.cookie.get(name)) || undefined; } catch (e) { return undefined; }
}
async function cookieJar() {
  // _ga_<container> has an unknown suffix, so it needs the full cookie string.
  try { const all = await browser.cookie.get(); return typeof all === "string" ? all : ""; }
  catch (e) { return ""; }
}
function gaClientId(ga) {
  if (!ga) return undefined;
  const p = ga.split(".");
  return p.length >= 4 ? p[2] + "." + p[3] : undefined;
}
function gaSessionId(jar) {
  // GS1: "GS1.1.<sid>.<n>…" → numeric 3rd dot-segment. GS2: "GS2.1.s<sid>$o<n>$…" → "s" field.
  const m = jar.match(/(?:^|;\s*)_ga_[^=;]+=([^;]+)/);
  if (!m) return undefined;
  const seg = m[1].split(".")[2] || "";
  const id = seg.match(/^s?(\d{7,})/);
  return id ? id[1] : undefined;
}

async function sendEvent(eventName, event) {
  const rvxVid = await cookie("_rvx_vid");
  const ids = {
    ga_client_id: gaClientId(await cookie("_ga")),
    ga_session_id: gaSessionId(await cookieJar()),
    fbp: await cookie("_fbp"),
    fbc: await cookie("_fbc"),
    shopify_client_id: event.clientId
  };
  const ctx = event.context || {};
  const orderId = event.data && event.data.checkout && event.data.checkout.order
    ? event.data.checkout.order.id : undefined;
  const payload = {
    writeKey: WRITE_KEY, event: eventName, messageId: event.id,
    eventId: orderId || event.id, timestamp: event.timestamp,
    anonymousId: rvxVid,
    source: "shopify_pixel",
    context: {
      userAgent: ctx.navigator && ctx.navigator.userAgent,
      locale: ctx.navigator && ctx.navigator.language,
      page: ctx.document ? { url: ctx.document.location && ctx.document.location.href,
        referrer: ctx.document.referrer, title: ctx.document.title } : undefined,
      ids: ids
    },
    properties: Object.assign({}, event.data, { shopifyClientId: event.clientId, rvxVid: rvxVid || null })
  };
  try {
    fetch(COLLECTOR_URL, { method: "POST", keepalive: true,
      headers: { "Content-Type": "application/json" }, body: JSON.stringify(payload) }).catch(() => {});
  } catch (e) {}
}

analytics.subscribe("page_viewed", (e) => sendEvent("page_view", e));
analytics.subscribe("product_viewed", (e) => sendEvent("view_content", e));
analytics.subscribe("product_added_to_cart", (e) => sendEvent("add_to_cart", e));
analytics.subscribe("checkout_started", (e) => sendEvent("begin_checkout", e));
analytics.subscribe("payment_info_submitted", (e) => sendEvent("add_payment_info", e));
analytics.subscribe("checkout_completed", (e) => sendEvent("purchase", e));
analytics.subscribe("alert_displayed", (e) => sendEvent("checkout_error", e));
3Order webhook
Settings → Notifications → Webhooks → "Order payment" (orders/paid), format JSON → URL:
{{ORIGIN}}/shopify/{{KEY}}/webhook
Then send the signing secret shown there so the orders can be verified.

WooCommerce — orders & refunds

Same plugin as WordPress — orders are forwarded server-side, so COD, bank-transfer and "mark as paid" count too. No pixel-only gaps.
1Install the plugin
Plugins → Add New → Upload Plugin → choose rivex-tracking.zip (the signed zip we send) → Install → Activate. Ask us if you don't have the file yet.
2Enter your keys
Settings → Tracking → paste these and Save:
Plugin settings
Write key:        {{KEY}}
Tracking domain:  {{TRACKDOMAIN}}
HMAC secret:      (the secret we provisioned for you)
For reference — the webhook the plugin posts to (no action needed):
{{ORIGIN}}/wp/{{KEY}}/webhook
3Nothing else to add
Paid orders (processing/completed), refunds and cancellations flow automatically tagged woocommerce; the visitor id is captured at checkout so orders join back to the ad click; HPOS-compatible. Don't add Google/Meta purchase pixels — Tracking sends conversions server-side.

WordPress — blog & website

The Tracking plugin gives you first-party tracking automatically — visitor cookie on your own domain, no DNS/CNAME needed.
1Install the plugin
Plugins → Add New → Upload Plugin → choose rivex-tracking.zip (the signed zip we send) → Install → Activate. Ask us if you don't have the file yet.
2Enter your keys
Settings → Tracking → paste these and Save:
Plugin settings
Write key:        {{KEY}}
Tracking domain:  {{TRACKDOMAIN}}
HMAC secret:      (the secret we provisioned for you)
3Done
Page views tagged wordpress. Running WooCommerce or WPForms? The same plugin picks them up automatically — see those tiles.

Lovable — your landing page

1Open your Lovable project, paste this prompt, and send it.
Lovable is an AI builder — it adds the tracker for you from this prompt.
Prompt for Lovable
Add our first-party conversion tracker to this site. Make exactly these changes and nothing else:

1) In index.html, add this inside <head> so it loads on every page:
<script async
  src="{{EMBED}}/tracker.js"
  data-write-key="{{KEY}}"
  data-shop-domain="{{SHOP}}"
  data-source="lovable"></script>

2) CRITICAL: every "Buy" / checkout button that goes to the store MUST be a real
   link to {{SHOP}}, e.g. <a href="https://{{SHOP}}/...">. Never a JS-only redirect.

3) On every lead / email / signup form: add data-rvx-lead to the <form> tag, with
   the email field as <input type="email"> and any phone field as <input type="tel">.

4) Preserve ALL URL query parameters on load and navigation — never strip
   gclid, gbraid, wbraid, fbclid, utm_source, utm_medium, utm_campaign.

5) If the site uses client-side routing, call
   window.rvx && window.rvx.track('page_view') after each route change.

6) Do NOT add Google Analytics, Meta Pixel, or Google Tag Manager.

Keep all existing design and content unchanged.

Wix — website

Requires a Wix premium plan with a connected domain — Wix only allows custom code on upgraded sites.
1Add the code
Dashboard: Settings → Custom Code (under Advanced) → + Add Custom Code → paste → name it "Tracking".
Embed snippet
<script async
  src="{{EMBED}}/tracker.js"
  data-write-key="{{KEY}}"
  data-source="wix"></script>
2Apply to all pages
Add Code to Pages: All pages (Load code once) · Place Code in: Head → Apply.
3Done
Page views tagged wix. Wix's native form blocks can't be tagged for leads — track a thank-you page view or ask us.

Squarespace — website

Code injection needs a Squarespace Business plan or higher.
1Open Code Injection
Settings → Advanced → Code Injection (newer dashboards: Settings → Developer Tools → Code Injection).
2Paste into Header
Paste into Header → Save.
Embed snippet
<script async
  src="{{EMBED}}/tracker.js"
  data-write-key="{{KEY}}"
  data-source="squarespace"></script>
3Done
Page views tagged squarespace.

Webflow — website

Site-wide custom code needs a paid Webflow site plan.
1Paste into Head code
Site settings → Custom Code → paste into Head code → Save.
Embed snippet
<script async
  src="{{EMBED}}/tracker.js"
  data-write-key="{{KEY}}"
  data-source="webflow"></script>
2Publish
Publish the site.
3Done
Page views tagged webflow. Bonus: Webflow forms can send leads — in the Designer, add custom attribute data-rvx-lead to the Form element (email/phone read by input type). Optional: cookie banner → window.RVX_CONSENT.

Framer — website

Custom code needs a paid Framer site plan.
1Paste the snippet
Site Settings → General → Custom Code → paste into End of <head> tag → Save.
Embed snippet
<script async
  src="{{EMBED}}/tracker.js"
  data-write-key="{{KEY}}"
  data-source="framer"></script>
2Republish
Republish the site.
3Done
Page views tagged framer. Honest limit: Framer navigates client-side, so only the landing page view is automatic — internal navigation isn't re-tracked (yet; SPA route hook is future work).

Typeform — lead forms

Typeform is hosted on typeform.com, so the tracker can't run inside the form itself. Embed the form on a page of your site and we record the submit from the embed.
1Embed your form
Typeform: Share → Embed in a web page → add to your landing/contact page (any embed type).
2Install the snippet on that page
Add to that page's <head>:
Embed snippet
<script async
  src="{{EMBED}}/tracker.js"
  data-write-key="{{KEY}}"
  data-source="typeform"></script>
3Done
Completing the embedded form records a lead tied to the visitor's ad click. Honest limits: answers stay inside Typeform (the lead is counted, not enriched); standalone form.typeform.com links can't be tracked — use an embed (webhook path is future work). Optional: using a cookie banner? Feed it to window.RVX_CONSENT.

WPForms — lead forms

Same plugin as WordPress — WPForms submissions become lead events server-side, email/phone picked up by field type.
1Install the plugin
Plugins → Add New → Upload Plugin → choose rivex-tracking.zip (the signed zip we send) → Install → Activate. Ask us if you don't have the file yet.
2Enter your keys
Settings → Tracking → paste these and Save:
Plugin settings
Write key:        {{KEY}}
Tracking domain:  {{TRACKDOMAIN}}
HMAC secret:      (the secret we provisioned for you)
Optional: WPForms allowlist (comma-separated form IDs; empty = all forms).
3Done
Every submission arrives as a lead tagged wpforms, joined to the visitor's ad click. Optional: using a cookie banner? Feed it to window.RVX_CONSENT — explicit opt-outs are honored end-to-end.

Custom HTML — any website

1Paste the snippet
In your <head> on every page (no data-source → recorded as web).
Embed snippet
<script async
  src="{{EMBED}}/tracker.js"
  data-write-key="{{KEY}}"></script>
2Optional lead forms
Add data-rvx-lead to any <form>; email/phone read from type=email / type=tel inputs.
3Single-page apps
Call window.rvx.track('page_view') after each route change; window.rvx.lead({email}) works anywhere. Optional: cookie banner → window.RVX_CONSENT.