reCAPTCHA v3 Enterprise on every page
Google reCAPTCHA v3 Enterprise scores each page load without any visible challenge.
In one line
Can score every page visit for bot behavior without showing a challenge
Google reCAPTCHA v3 Enterprise scores each page load without any visible challenge.
Sends page behavior and device signals to Google to get a bot risk score. Invisible to the person; Google sets its own cookies and receives IP and browser data.
What it can and can't do
What the user does: Nothing. It happens each time a LinkedIn page loads
It can
- Watch how the page is used to judge if you are a bot
- Send a score about the visit to LinkedIn
- Share device and browser signals with Google for the score
It cannot
- Show a puzzle or ask you to click anything in v3
- Name you on its own
- See other tabs, files or apps
- Work if blocked, though blocking may stop the page from loading
Browser support
| Browser | Status | First version | Note |
|---|---|---|---|
| Chrome | Supported | Not available | None |
| Edge | Supported | Not available | None |
| Firefox | Supported | Not available | None |
| Safari | Supported | Not available | None |
| Safari on iPhone | Supported | Not available | None |
| Chrome on Android | Supported | Not available | None |
| Samsung Internet | Supported | Not available | None |
How a site asks for it
| API | grecaptcha.enterprise.execute(siteKey, {action: 'onPageLoad'}) |
| How access is granted | none |
| What the user sees | None (no browser prompt) |
| Needs a secure context (HTTPS) | No |
| Needs a user gesture | No |
| How long it lasts | Per page load |
| How to take it back | Not listed |
| Inside an iframe | Not listed |
Typical flow
- LIX flag pemberly.tracking.recaptcha.v3 enables it
- Token requested with action onPageLoad
- Token sent with tracking payload for server verification
Data you get
What comes back: Risk token
Shape: object
How often: per page load
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
token | string | None | opaque | one use |
Technical limits
- Google decides what signals it reads
- Frequency (every page) is reported by BrowserGate, 35 reCAPTCHA references in the snapshot
The story
What it is
An invisible Google check that scores every page load for bot risk.
For you
You never see a puzzle or a box. The page quietly sends signals about your browser and clicks to Google, which sends back a score. If the score is bad, the site may then ask you to prove you are real.
For makers
Fake logins, scraping and spam are constant. A score without a puzzle keeps real people moving fast while bots get stopped. The price is that Google gets a signal of your visit to the site, plus your IP and browser data.
Where you see it
| Type | Example | Apps |
|---|---|---|
| security | A login page on LinkedIn gets a score for each visit, and asks for extra proof only when the score looks bot like. | |
| shopping | A ticket site uses the score to push likely bots to the back of the queue. | Ticketmaster, Eventbrite |
| payments | A checkout page asks reCAPTCHA about a card test, and blocks it when it looks like a bot testing stolen cards. | Stripe Checkout, Shopify |
| games | A game sign up page scores each new account to stop bot farms that sell gold or cheat. | Roblox, Steam |
| social | A comment form scores each post to stop spam bots before they add links. | |
| analytics | A team removes bot traffic from its reports using the same score. | Google Analytics |
Risks
- Google sees the visit
- Real people may be wrongly flagged
What the platform says
- Google Cloud: reCAPTCHA Enterprise. Google pitches it as a way to detect bots and fraud with a risk score and no puzzle for real people.
Good uses and abuse
Legitimate uses
- Cheap bot filtering with no friction
Known abuse
- Third party sees every page view
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 2 of 5 | How revealing the data is |
| Utility | 3 of 5 | How useful it is to honest apps |
| Friction | 0 of 5 | How much the user has to do |
| Fingerprint bits | Not rated | Rough identifying entropy, when known |
A real example: LinkedIn
Action onPageLoad and the LIX flag are in the snapshot; BrowserGate says it runs on every page.
Related capabilities
Related
- HUMAN Security (PerimeterX) hidden iframe. Can run a hidden bot check on LinkedIn pages and tie it to its browser ID
Sources
- mdp/linkedin-extension-fingerprinting (LinkedIn script snapshot and ID list)
- BrowserGate: how it works (48 feature table)
- Google reCAPTCHA Enterprise docs
How well checked: Based on official documentation.