Get set up in under five minutes.

1. 01

   Add the tracking script

   Copy your site's snippet from the dashboard, then pick your platform below. No cookie banner needed: the script is cookieless by default.

   This script also automatically captures campaign and click-ID parameters from the URL when a visitor arrives: Meta's fbclid, Google's gclid, Microsoft's msclkid, TikTok's ttclid, LinkedIn's li_fat_id, X's twclid, and standard UTM parameters. There's nothing separate to configure for this, and no Meta or Google account to connect.

   HTMLNext.jsReactVercelWordPressShopifyWebflowGoogle Tag Manager

   Paste it before the closing </head> tag of your site's HTML.

   <script defer src="https://thexly.com/script.js" data-website-id="YOUR-WEBSITE-ID"></script>

   Copy
2. 02

   Connect your payment processor

   Go to Settings → Integrations, and pick whichever platform your revenue runs through: Stripe, Lemon Squeezy, Polar, Dodo, or Yolfi. Stripe and Polar support scoped, read-only keys. Lemon Squeezy and Dodo only offer account-level keys, since neither has a permission-scoping option today. Either way, Thexly only ever reads payment data; the only write action any connection makes is registering its own webhook. Not using one of these five? See the Manual API instead.

   Stripe's restricted-key permissions:

   Checkout Sessions

   Read

   Webhooks

   Write

   Everything else

   None

3. 03

   Verify it's working

   Visit your site, then check your Thexly dashboard. You should see your own visit appear within a few seconds. Make a test purchase, or wait for your first real one, to confirm revenue attribution is linking correctly.

   Receiving events, last seen 4 seconds ago

The install script tracks pageviews automatically. Anything past that, a signup, a click on a pricing button, a form submission, you define yourself as a custom event. Custom events count toward your plan's event limit the same as pageviews. There are three ways to send one, in order of how much code they need.

1. Zero-code, with an HTML attribute

Add data-thexly-event to any link or button and Thexly tracks a click on it automatically, no JavaScript required. Add extra detail with data-thexly-event-* attributes.

<button data-thexly-event="signup-clicked" data-thexly-event-plan="agency">
  Start free trial
</button>

2. From JavaScript

Call thexly.track() from your own code for anything the attribute can't reach, form submissions, checkout completion, a step inside a multi-page flow.

thexly.track('signup-clicked', { plan: 'agency' });

3. From your server

For events that happen server-side, a webhook firing, a subscription renewing, send them directly to the collector endpoint with your website ID.

curl https://your-thexly-domain/api/send \
  -H "Content-Type: application/json" \
  -d '{
    "type": "event",
    "payload": {
      "website": "YOUR_WEBSITE_ID",
      "name": "subscription-renewed",
      "data": { "plan": "agency" }
    }
  }'

When a visitor arrives from an ad, the script captures whatever click ID or UTM parameters are present in the URL. This happens automatically, with no ad account connection required. That information is attached to the visitor's session.

If that same visitor later completes a payment through Stripe, Thexly matches the payment back to that visitor, using the explicit session at checkout when one's available, or otherwise their most recent tracked session, so the payment is credited to the one channel that actually led to it, not to every platform that happened to serve an ad along the way. There's no expiration window on this: a session from months earlier is still eligible to match, as long as the visitor can still be identified.

Separately, you choose an attribution model per website: credit the channel that first brought the visitor in, or the one that closed the sale. You can change it anytime without losing history.

On the Agency plan, add each client as a separate website under your account. Each one gets its own tracking script and its own payment processor connection. Client data is kept separate, but all visible from the same login.

1. 01From your dashboard, add a new website for the client
2. 02Install that client's script on their site (same snippet, different site ID)
3. 03Connect that client's payment processor with its own restricted API key

On the Agency plan, invite teammates from a website's Settings → Team tab. Add someone by their Thexly username and pick a role. If they don't have a Thexly account yet, they'll show as Pending until they sign up with that username.

• OwnerThe account that created the website. Full access, can't be changed or removed.
• MemberCan view every report and change website settings (payment connections, attribution model, team).
• ViewerCan view every report, can't change any settings.

Roles are per website, not account-wide, so someone can be a Member on one client and a Viewer on another. Remove access anytime from the same table.

Switching from Plausible or Umami? Upload an export file during setup and Thexly will bring that history in rather than starting from zero: daily traffic and page metrics from Plausible, or full sessions, page views, and events from Umami. GA4 import isn't available yet.

Thexly doesn't set cookies and doesn't store your visitors' IP addresses. To tell one visitor's session from another without a cookie, the tracking script combines the visitor's IP, their browser's user agent, and your site, into a one-way hash. That hash rotates on a schedule (monthly by default), so it changes rather than identifying the same visitor indefinitely, and the raw IP that went into it is never written to the database.

No name, email, or other personal identifier is collected on the traffic and analytics side. That's what makes a cookie consent banner unnecessary for the tracking script itself.

Revenue data is different, by necessity: connecting Stripe or another payment processor pulls in whatever that processor already holds on a payment, customer email, name, amount, because reconciling a sale against a visit requires it. That data is exactly as sensitive as what your payment processor stores today, is read through an API key you control (scoped to read-only where your processor supports it) and can be disconnected at any time.

One caveat worth being explicit about: this describes what Thexly itself collects. Using Thexly doesn't automatically make your site, or a client's site, compliant with GDPR, CCPA, or any other regulation on its own, that depends on everything else the site does. Thexly removes the analytics-cookie problem; it isn't a substitute for a privacy policy or a full compliance review.