Clicks, sessions, and conversions are different events

The measurement boundary

An ad platform may count the ad click; the redirect service sees a request for the short link; the destination analytics tool may create a session; the destination application may record a signup, lead, or sale. These counts need not match. A visitor can click twice, abandon before the destination loads, decline analytics consent, switch devices, or arrive through a bot or automated fetch.

Ad click → managed-link request → redirect response → destination page load → analytics session → key event / lead / purchase
Ad platform         JustLNK side           Destination analytics and application

Define the unit before comparing numbers

Raw requests are not people. A unique-user estimate depends on identifiers, time windows, privacy settings, and filtering. A session groups activity under rules set by the destination analytics system; it is not the same event as a redirect request. Google Analytics, for example, starts a session when a user opens the app or views a page without an active session.

A conversion is an explicitly defined downstream action. One person can have multiple clicks, sessions, or conversion events. If you divide conversions by clicks, document the date range, attribution model, bot filters, and whether both counts cover the same audience. Otherwise the ratio may be useful only as a rough signal.

Attribution is a model, not a redirect property

UTM parameters supply campaign labels to the destination when they survive the redirect and are accepted by its analytics. Referrer may be missing because of browser policy, privacy tools, or transitions between environments. Last-click, first-click, and multi-touch attribution assign credit differently; no redirect count determines that allocation by itself.

Compare the two systems to diagnose gaps. If managed-link requests rise but destination sessions do not, investigate the target's load, redirect errors, consent, tag installation, and the time periods. If sessions rise but key events do not, inspect the landing experience and conversion event setup. Do not present the gap as proof of fraudulent traffic without further evidence.

• Check that the final URL retains intended UTM values.
• Use matching date ranges and time zones.
• Inspect repeated requests and known automated traffic separately.
• Confirm a destination event fires before reporting conversion rate.

What the current JustLNK surface shows

The free UTM Builder constructs a URL in your browser. It does not record clicks or conversions. To measure outcomes, check the actual link service, destination analytics and application events used by your campaign.

A diagnostic example

Imagine a campaign with 1,000 ad-platform clicks, 920 link requests, 780 destination sessions and 24 recorded leads. Those are illustrative counts, not a funnel automatically measured by one tool. First inspect whether the ad platform uses its own filters and click window. Then test redirect failures, landing-page load, analytics consent and session definitions. Finally verify that a lead event is fired once per submission and that attribution windows are aligned.

1,000 ad clicks | 920 link requests | 780 sessions | 24 lead events
Each stage has a different observer and counting rule.

Avoid a false precision trap

The 24 leads divided by 920 link requests is about 2.6 percent, but calling it the campaign conversion rate requires compatible populations and attribution. A person can return directly later and convert without another managed-link request. Conversely a bot can request a link without creating a real visit. Label the calculation and its assumptions rather than presenting it as a definitive business outcome.