LinkTrace
Dashboard
LinkTrace docs

Ship LinkTrace integrations without hunting through dashboard screens

Use this public docs surface for installation, API auth, conversion tracking, and provider setup. The dashboard still contains private setup state, but the implementation model lives here.

Implementation model

LinkTrace works best when you split attribution persistence from business-event tracking.

1. Click
Tracked short links create an attribution id

Every tracked redirect can generate an lt_click_id. That id becomes the join key for later lead and sale events.

2. Persist
Install the script once across your site

Load client.js in your shared layout or head. It stores attribution context and can inject hidden form fields.

3. Track
Send lead and sale events from your backend

Your application decides what counts as success. Once success is confirmed, call the SDK or API from the server side.

Start here

These guides cover the smallest path to production.

Getting started
Docs home
Start with the product model, installation path, and implementation order.
API quickstart
Use secret keys, scopes, machine users, and server-side tracking safely.
Conversion tracking
Install the tracking script once, then send lead and sale events from your backend.
Auth events
Track signup and login events from Supabase, Clerk, NextAuth, or your own backend.
Core product
Links
Create, edit, pause, expire, protect, and route short links across domains and slugs.
Domains
Verify subdomains, activate routing, and assign domains to workspace links.
UTM templates
Standardize campaign parameters and reuse them when creating links.
Analytics
Understand overview, advanced reporting, retention windows, and export boundaries.
Auth providers
Supabase
Track signup and login after your server confirms the Supabase auth action succeeded.
Clerk
Track Clerk signup and login events from your backend callback or application server.
NextAuth
Track NextAuth signups and logins after your application resolves the authenticated user.
Custom backend
Track lead events directly when your own application decides the auth event succeeded.
Payment providers
Stripe
Attach click attribution to Checkout and ingest paid events through webhooks.
Polar
Forward Polar paid events into LinkTrace and preserve attribution metadata.
Lemon Squeezy
Configure webhook ingestion and pass attribution into Lemon Squeezy orders.

What this public docs surface is for

This site is intentionally public and indexable. The dashboard remains the place for private state like API key values, webhook tokens, and workspace-specific plan status.

  • Use these pages to understand the integration model before login.
  • Use the dashboard to generate keys, manage provider connections, and inspect private reporting data.
  • Use the API and provider guides here as canonical implementation references for engineering teams and SEO indexing.
Related guides
API quickstart
Use secret keys, scopes, machine users, and server-side tracking safely.
Conversion tracking
Install the tracking script once, then send lead and sale events from your backend.
Auth events
Track signup and login events from Supabase, Clerk, NextAuth, or your own backend.