Next.js sites and Google Ads conversion tracking: 53.0% count a click, page load or login
TL;DR. 79 of 149 Next.js sites (53.0%, 95% interval 45 to 60.9%) send Google Ads a conversion on a click, a page load or a login. The all-site figure is 50.8%, so Next.js sits inside the noise of the whole sample. One gap does show: 30.9% have a duplicate conversion, against 20.5% of all sites. We saw the container, not the Ads account: a conversion we flag may be secondary and harmless to bidding.
What did the 149 Next.js sites send?
Share of Next.js sites with each pattern, next to all 886 sites in the study. A site can show several patterns, so rows overlap.
| Pattern | Next.js (n=149) | 95% interval | All sites (n=886) |
|---|---|---|---|
| Any noise trigger | 53.0% 79 of 149 | 45 to 60.9% | 50.8% 450 of 886 |
| Button or link click | 35.6% 53 of 149 | 28.3 to 43.5% | 31.6% 280 of 886 |
| Page load (every page or a plain page view) | 22.8% 34 of 149 | 16.8 to 30.2% | 26.1% 231 of 886 |
| Duplicate conversions | 30.9% 46 of 149 | 24 to 38.7% | 20.5% 182 of 886 |
| Login counted | 11.4% 17 of 149 | 7.2 to 17.5% | 7.9% 70 of 886 |
| No conversion value on any action | 66.4% 99 of 149 | 58.5 to 73.5% | 68.8% 610 of 886 |
Intervals are Wilson 95%. Where the Next.js interval holds the all-site share, we can't say Next.js sites differ.
What does each pattern mean?
- Click. The conversion fires when someone presses a button or link, not when a form is accepted. It counts people who clicked and then failed to submit. Fix: button click conversions.
- Page load. The conversion fires on a page view of a page that is not a clear success page, or on every page. Fix: conversions on every page.
- Duplicate. The same label sits on two tags, or one trigger fires two labels. Fix: duplicate conversions in GTM.
- Login. A login or account page is a conversion. Fix: login and trial conversions.
- No value. No conversion sends a value, so value-based bidding has nothing to learn from. Fix: conversion value for lead gen.
What can't we see?
- Primary vs secondary lives in the Ads account. A click conversion set to secondary does not drive bids.
- Which plugin or tag manager created the tag. We read the public container. We make no claim about plugins.
- Server-side tags are not in the public container, so real rates are likely higher.
- Cause. Many sites share a platform and a setup habit. These are shares of what we saw, not proof that Next.js causes them. The sample is not random.
Method
Static HTTP read of the homepage, /pricing, /signup and /demo (robots.txt respected) and the public googletagmanager.com containers of 886 sites with a readable Google Ads conversion. A site counts as Next.js when the page source shows it; a site can carry two platforms, so platform rows overlap. No forms, logins or bot evasion. Full rules: method. All-site results: the study.
Check your own Next.js site.
The free scan runs the same checks in seconds. Public data only.
Scan my siteRelated: the full 1,727-site study · primary vs secondary · all guides