Measurement · Tracking
Tracking your browser can't lose.
The capture layer runs first-party, on a domain you own: a JavaScript SDK, server-set cookies that outlive Safari and iOS tracking prevention, redirect links, and drop-in pixels. Every event lands once, even when the network retries.
First-party by design · runs on your own domain · built on AWS.
First-party by design
A JavaScript SDK on your own domain
One line of script loads the tracker from your white-label domain. Because it runs first-party, it isn't the third-party host that ad blockers and browser privacy controls are built to catch, and the cookies it sets are your cookies. Full endpoint reference and SDK snippets live in the developer docs.
- Server-set first-party cookies (
ll_cid,ll_vid) that outlive the seven-day JavaScript-cookie cap ITP imposes on third-party tools - Sitewide include or single-placement tag, both one line, both auto-updating
- Records a click only when the URL actually carries tracking parameters, so it's safe across a whole site
- The tracker keeps its own copy of the click ID, so conversions attribute even if a pixel forgets to pass it
Links your way
Redirect or direct, with sub-IDs end to end
Give affiliates a redirect link on your tracking domain, or, for ad platforms that dislike redirect hops, track directly on your own landing page with the SDK beacon. Either way, five sub-ID slots ride along for attribution and reporting. Plan your slots with the free sub-ID builder, then confirm the redirect end to end with the tracking link tester.
- Redirect tracking links (
/c): record the click, then send the visitor on, nothing to install - Direct tracking with no redirect hop: the SDK beacons the click to
/dcpwith an/i.giffallback - Sub-IDs s1 through s5 captured on every click, reportable and controllable per campaign
- Block a bad sub-ID or set a per-sub-ID payout override for surgical traffic control
Conversions in, once
A drop-in pixel that never double-counts
Paste one line on your thank-you page and conversions flow. Prefer server to server? Post the same fields and read back the conversion ID for your CRM. Retries and re-fires collapse into a single event, so a flaky network or an SQS redelivery never inflates your numbers.
- Image pixel on
/convreturns a 1×1 GIF and can't break your page - Server-to-server postback returns JSON with the minted conversion ID to store in your CRM
- Idempotent ingestion keyed on the transaction ID: a re-fire returns the same ID, never a second row
- Every attempt captured in the pixel log, even the malformed ones, so debugging takes minutes
Your name on the wire
White-label tracking domains, self-serve
Add a domain you own, drop in the records we generate, and it verifies, gets its HTTPS certificate, and goes live on its own, usually within minutes. One visit to your DNS provider; you never come back for a second set of records.
- Add or swap domains yourself, with zero downtime
- One set of DNS records, added once, then auto-provisioned end to end
- HTTPS certificate issued automatically once the records resolve
- Your traffic runs on your domain only, never pooled with another customer's
Keep exploring the platform
Tracking is the first waypoint. Follow the journey from a captured click all the way to attributed revenue.
Attribution
First and last touch, windows, dedup, and the visitor Journey view.
Explore attribution MeasurementReporting
Five reports, one metrics language, CSV export, and saved views.
Explore reporting ProgramPartners
Offers, campaigns, caps, creatives, and a clean affiliate portal.
Explore partners IntelligenceAI operator
LimeliChat recommends changes and applies them with your approval.
Explore the AISee first-party tracking on your own numbers.
Book a demo. We'll stand up your workspace, wire your tracking domain, and show you a click captured first-party, all the way through to an attributed conversion.