Web Tracking Pixel

Why this matters

Your LinkForty links are great at getting people to your site. But once a visitor lands, what happens next — do they read, bounce, sign up, buy? Generic web analytics can tell you that something happened, but not which link or campaign drove it. The connection between the click and the conversion gets lost.

The Web Tracking Pixel closes that loop. It's the web counterpart to our mobile SDKs: a tiny script that records on-site activity and attributes it straight back to the link that brought the visitor in — so you can finally answer "what did people do after they clicked this link?"

One line to install

Add a single script tag to your site — anywhere, ideally before </head>:

<script src="https://cdn.linkforty.com/pixel.js" data-workspace="ws_your_site_key" async></script>

Your workspace's site key lives in your dashboard Settings (the Web Pixel section), and in the onboarding checklist. That's the entire install — no build step, no package to add, no tag manager required (though it works fine inside one).

What it captures

Out of the box, with zero extra code:

Page views — every page load, including client-side route changes in single-page apps.
Engagement — time on page, scroll depth, and whether the visit bounced.
Conversions — the moments that matter, marked two ways:
- Declarative: add data-lf-event="signup" (and an optional data-lf-value="49") to any button or link.
- In code: call window.LinkForty.track('purchase', { value: 49 }).
Autocapture (opt-in) — flip on data-autocapture="true" to automatically record outbound link clicks, file downloads, and form submissions without tagging anything.

What you see in the dashboard

Everything flows into the Web tab of your Analytics page:

Headline metrics — page views, sessions, unique visitors, conversions, conversion value, conversion rate, bounce rate, average time on page, and pages per session — each with period-over-period comparison.
Top attributed links and recent conversions — which links are actually driving on-site results.
Breakdowns by link, campaign, source, medium, content, referrer, channel, page, country, device, or browser.
Journeys — the most common page paths, plus top entry and exit pages.
Goals & revenue — per-conversion metrics: conversions, conversion rate, total and average value.

Because every web event is tied to the link that drove the visit, a conversion on a later page — even one with no UTM in the URL — still attributes to the link that started the session. Last-click, the way you'd expect.

Privacy-first by design

The pixel is built to be a good citizen on your site:

Tiny. A single ~3 KB (gzipped) script with zero dependencies, loaded async — it never blocks your page.
Cookie-free by default. Sessions use sessionStorage (per tab); a persistent visitor id is strictly opt-in via data-visitors="true".
Respects consent. Honors Do Not Track and Global Privacy Control — those visitors aren't tracked at all.
No raw IPs. Geo (country / region / city) is derived at ingestion and the IP is immediately dropped — it's never stored.

Getting started

Open your workspace Settings and copy the one-line Web Pixel snippet.
Paste it into your site's <head>.
(Optional) Add data-autocapture="true" for automatic outbound / form / download tracking, or tag specific conversions with data-lf-event.
Open Analytics → Web to watch traffic and conversions roll in.

That's everything most sites need. For advanced options — routing events through a custom domain with data-endpoint, the full list of data attributes, the track() API, and the privacy model — see the Web Pixel docs.