Connect acquisition to customer revenue.

Revliu creates a first-party anonymous visitor identifier on the customer's website. Campaign and tracked-link context stays attached to that identifier across visits. When the product confirms who the visitor is, an identify event links the existing anonymous history to the customer record instead of creating a disconnected journey.

Copy the site-specific snippet from Settings → Website trackingand add it once to the global layout, ideally before the closing body tag.

<script
  src="https://r.revliu.com/tracker.js"
  data-site-id="YOUR_SITE_ID"
  defer
></script>

React and Next.js applications can use the package for explicit initialization and automatic History API navigation tracking.

pnpm add @revliu/tracker

"use client";

import { init } from "@revliu/tracker";
import { useEffect } from "react";

export function RevliuAnalytics() {
  useEffect(() => {
    init({
      siteId: "YOUR_SITE_ID",
      endpoint: "https://r.revliu.com",
      autoPageview: true,
      autoTrackNavigation: true,
      respectDoNotTrack: true,
    });
  }, []);

  return null;
}

The configured website hostname is used to validate incoming event origins. Publish the tracker on the production domain, open at least one page, then use Check connection in Revliu. Webflow, Framer, WordPress, custom HTML, Next.js and Shopify are supported; the installation surface differs by platform.

1. 1Save the exact public website URL in Workspace settings.
2. 2Choose the matching platform and copy its generated installation code.
3. 3Publish the change globally, not only on the landing page.
4. 4Visit the production site and verify the connection in Revliu.

Call identify after authentication or a confirmed signup. Use a stable internal customer ID whenever possible and include the email and Stripe customer ID as traits. Revliu sends the same anonymous visitor ID with the identify event, links both records, and preserves the earlier acquisition journey.

// Run after authentication or a confirmed signup.
window.Revliu.identify(user.id || user.email, {
  email: user.email,
  name: user.name,
  stripeCustomerId: user.stripeCustomerId,
});

Events advance the acquisition funnel without replacing the customer identity. Send them after the corresponding business action succeeds, not when a user merely opens a form or pricing page.

window.Revliu.track("signup", { plan: "starter" });
window.Revliu.track("trial_started", { plan: "pro" });
window.Revliu.track("subscription_started", {
  plan: "pro",
  billingCycle: "monthly",
});
window.Revliu.track("purchase", {
  orderId: "order_123",
  value: 4900,
  currency: "EUR",
});

Visitor, customer and revenue records remain separate and are joined explicitly. This preserves anonymous analytics while preventing a payment from being attributed without a verified relationship.

Revliu uses Stripe Connect OAuth. The platform never asks customers to paste their secret key. Stripe returns an authorization code to the exact registered callback URL, and Revliu stores the connected account identifier for server-side synchronization.

Revliu supports explicit consent mode and honors Do Not Track by default. In required mode, no page view or identity event is sent until consent is granted. Opt-out clears visitor, session, tracked-link and campaign state from browser storage.

init({
  siteId: "YOUR_SITE_ID",
  endpoint: "https://r.revliu.com",
  consentMode: "required",
});

setConsent(true);  // Start permitted tracking
setConsent(false); // Stop and clear tracking identifiers

• Document Revliu in the website privacy notice.
• Collect only the identity traits required for attribution.
• Never send passwords, authentication tokens, payment details or sensitive data.
• Configure consent before tracking where local law requires it.