Click Pixel

A click pixel records a click without a redirect. In the usual flow, an affiliate link points at your tracking domain, the platform logs the click, then bounces the visitor to your landing page. Direct tracking removes that hop: the affiliate links straight to your landing page with tracking parameters on the URL, and a small script already installed on the page reads them, reports the click, and stores the click ID for the conversion pixel to use later.

When to use direct tracking

The redirect flow needs nothing installed on your page, so it is the default. But some ad platforms and partners penalize or reject redirect links. A click pixel lets the affiliate link to your real page directly — no redirect for the ad platform to object to — while still capturing the click. The trade is that the script must be present on the page, or the click goes unrecorded.

A worked example

You install the sitewide script once:

<script src="https://track.yourbrand.com/sdk.js" async></script>
        

Then you hand an affiliate a parameterized link to your own page:

https://yourbrand.com/landing?o=12&aff=34&s1=newsletter
        

Every visit to that URL records a click for offer 12, credited to affiliate 34, tagged with the sub-ID newsletter. The script stores ll_cid as a first-party cookie on your domain, so a later conversion attributes even if the pixel forgets to pass the click ID. The sitewide script stays silent for visitors whose URL carries no tracking parameters, so it is safe across your whole site.

Sitewide vs placement tag

The sitewide include carries no baked IDs and attributes each affiliate from the parameters in their link — install it once, everywhere. The single-affiliate placement tag bakes specific IDs in and credits every visitor who arrives without parameters, so use it only on a page dedicated to one placement. Install exactly one integration per page.

How this works in LimeliJourney

LimeliJourney's tracking generates both variants on the Click Pixel tab: enter your destination URL, pick the offer, and copy the one-line sitewide include or the placement tag (a Download .js button lets you self-host if your site cannot load third-party scripts). Because the click ID is stored as a first-party cookie on your own domain, direct tracking sidesteps much of the cookie fragility that hurts third-party setups. Two install notes: reading the click ID back at conversion needs the same domain, and a strict Content-Security-Policy must allow your tracking domain under script-src and connect-src. Verify a test visit in the Clicks Report.