High "Click-to-Land" discrepancy (60% loss).

[WasabiWarrior]

The network reports 1,000 clicks, but my landing page only shows 400 sessions. LP speed is 95+ on Mobile. Is this just bot traffic or are the redirects being blocked by Chrome’s built-in ad blocker?

 

[Sawyerbroach]

Usually tracking or bot traffic messing with the numbers.

 

[HavenX]

The network reports 1,000 clicks, but my landing page only shows 400 sessions. LP speed is 95+ on Mobile. Is this just bot traffic or are the redirects being blocked by Chrome’s built-in ad blocker?

Probably both, bot traffic inflates clicks and some browsers or ad blockers can block redirects, causing the loss.

 

[ThalosVire]

could be bots or safari itp stripping your tracking, but usually 60% loss means your lander is taking too long to trigger the pixel. try moving your tracking script to the top of the head or switch to server-side tracking to bypass adblockers.

 

[megemedia]

A 60% difference is a bit much, but it's usually not due to a single reason.

Things that come to mind:

Bot/low-quality traffic, especially in display or broad campaigns
Exiting before the page fully loads, Analytics not recording a session

Analytics code might be triggered late on some devices

Session recording might be lost due to cookies or permission banners

Chrome's ad blocker usually blocks ad formats, not landing pages.

 

[ChillBuddy]

your tracking is likely getting killed by aggressive browser redirects or data center bot traffic that never intends to load your page.

 

[Rankify008]

A 60% click-to-land discrepancy is usually related to traffic quality or a tracking mismatch rather than browser blocking. Before assuming it’s Chrome, compare the network’s reported clicks with your raw server logs to confirm how many real requests are actually reaching your landing page.

You can also test with a clean direct 302 redirect (without extra scripts or trackers) to rule out any redirect or tracking conflicts. That should help you determine whether the issue is bot/pre-LP activity or something technical within your funnel setup.

 

[Cat Boss]

Pretty normal, losses can come from bots, prefetch, blocked redirects or tracking mismatch
check logs & tracker not just speed...

 

[ShawoRanker0]

Ad networks count every click attempt, while your landing page only counts sessions that actually load and fire analytics.

 

[SerenAstra]

The network reports 1,000 clicks, but my landing page only shows 400 sessions. LP speed is 95+ on Mobile. Is this just bot traffic or are the redirects being blocked by Chrome’s built-in ad blocker?

Could be bots, ad blockers, or tracking issues, check your tracker setup, test redirects, and compare with another analytics source to pinpoint the leak.

 

[geo_hall]

A 60% click-to-landing gap is too large to dismiss as normal, but it’s also rarely just one cause. It’s usually a mix of tracking gaps, platform behavior, and some low-quality traffic.

 

[Rankwave]

A 60% drop usually points to multiple layers of loss rather than one specific problem. I’ve seen cases where browser privacy filters, delayed page loads, aggressive redirects, and traffic quality all contributed at the same time. Since your LP speed is already good, it might be worth checking whether the sessions are being lost before analytics fires or during the redirect process itself.

 

[EbonFrost]

60% loss between clicks and landings is very high. Usually it happens because of slow page load, redirect issues, bot traffic or tracking scripts not firing correctly.

 

[AdNomad]

60% click to land loss is way too high. From what I've seen , it's usually caused by redirects, slow loading pages, bot traffic or tracking scripts not firing properly.

 

[TrafficLoop]

60% loss is usually a mix of bot clicks + junk traffic, not Chrome blocking redirects.
A lot of ad networks inflate clicks hard, especially on push/pop traffic.
Check your tracker for VPN/datacenter IPs and super low time-on-page visits.
Also test your redirect chain, some networks add messy hops that drop users before LP loads.

 

[WPGads]

60% loss is way too high

I'd check the basics first - what traffic source are you using, are there multiple redirects, is the tracker firing correctly, and are you comparing clicks to real page views or to GA4 sessions?

I've seen cases where the network counted every click, but a huge chunk never actually loaded the page because of accidental clicks, bot traffic or poor mobile connections

If you're buying push or pop traffic, 20-30% loss can happen. 60% usually means something is broken or the traffic quality is terrible

 

[anes2010]

A 60 percent loss looks high. It could be bot traffic tracking issues filtered clicks or redirect problems I would check logs and tracking first before blaming Chrome ad blocking

 

[DarkSpend]

60% loss is way too high, sounds more like junk traffic or bad redirects than LP speed tbh. Seen this happen a lot with push/pop traffic. Some clicks never fully load the page. Also check if tracking scripts are blocked or firing late on mobile.

 

[Orangereview]

Even with a fast LP, not every click turns into a recorded session. Some traffic sources inflate click numbers pretty heavily.

 

[DarkMatterLab]

60% loss is way too high for just normal dropoff. Usually it’s junk traffic, accidental pops, bad placements or bot clicks from the network side.
Chrome blocking can happen sometimes with aggressive redirects, but not at that level unless your flow is sketchy. I’d test direct linking + tracker check first and cut bad zones fast.