Why ad clicks and landings can differ

Clicked and Landed describe two different observations. A difference can come from normal counting rules, privacy choices, or a tracking problem. The size of the gap alone does not tell us which one. A sustained gap, especially paid clicks with no recorded landings, deserves investigation.

What each number measures

Clicked is the number of ad clicks reported by the connected ad platform for the selected campaign or ad. Landed counts human visits recorded by Serge on your website. For a selected campaign, a visit also needs usable attribution to that campaign. “Paid traffic only” can include other tagged paid visits, while its click total covers campaigns connected to Serge. Neither number is a count of unique people.

Clicks do not map one-to-one to visits

In Serge’s current visit model, activity is grouped within a browser tab, ending after 30 minutes of inactivity or a maximum of 24 hours. Repeated clicks during a visit can produce several platform clicks and one landing. A new tab or a later visit can produce another landing. Serge does not stitch people together across tabs or devices. Returning with a tagged URL can also produce a recorded campaign visit without a new platform click. Older integrations retain their existing session rules.

The website did not finish loading

The platform can record a click before your page finishes loading. Closing the tab quickly, a slow or failed page, or a network problem can prevent the website measurement from reaching Serge. A click therefore does not prove that the visitor saw a usable page.

Measurement was unavailable or blocked

Consent choices, browser privacy controls, ad blockers and JavaScript restrictions can prevent collection. An absent tracking tag, a restrictive content security policy, or a collection outage can have the same effect. Serge respects consent and does not invent visits to make the totals match.

The visit arrived, but its campaign context was lost

Redirects or link handling can remove a click identifier or campaign tag. A wrong campaign identifier or ambiguous account binding can also prevent a match. A recorded visit may then appear in all traffic without appearing under the selected campaign. Compare all traffic with campaign traffic and verify the complete published destination, including every redirect. Never add a real click identifier to a synthetic test.

The reports cover different hours or update times

Serge stores timestamps as UTC instants. Website date filters and displayed times use your browser’s timezone. Ad platforms supply daily totals in the ad account’s timezone; Serge retains that timezone and displays a note when the two differ. A daily total cannot be accurately redistributed into another timezone without more detailed source data. For example, a September day in Los Angeles begins at 07:00 UTC, while a September day in London begins at 23:00 UTC on the previous date. Reports also refresh separately; check the last report time before comparing them.

Corrections and incomplete coverage matter too

Platforms can revise their reports or apply their own invalid-click filtering. Serge applies its own traffic classification and visit rules. Model changes, collection interruptions, pending processing and sessions excluded by safety limits are shown separately when known. Earlier server arrival records are not added to browser visits: they do not establish a page-by-page journey.

What the difference cannot prove

Serge cannot assign an exact cause to an unobserved visit. There is no universal “acceptable” discrepancy percentage, and a large gap should not be dismissed as normal. We do not turn the difference into a bounce rate or a click-to-landing conversion rate: the two counters are not a verified, matched population.

How to investigate a persistent gap

Compare the same campaign or ad and dates. Read the timezone note and the platform’s last report time.
Open the published destination on mobile and desktop. Check the whole redirect chain and that the page loads successfully.
In the project’s tracking settings, confirm that collection is receiving activity and human visits are enabled. Check tag installation, consent and browser/network errors.
Compare all traffic with the selected campaign. If visits appear only in all traffic, check the campaign tags and account binding.
If the gap persists, contact Serge with the campaign, date range, timezone, destination and a recent test time. Do not send API keys or private visitor data.