Screeb system hidden fields: full list and usage

On every response collected, Screeb automatically records a set of hidden fields about the context of the person answering: the page they were on, their browser, their device, their location, etc. You don't need to send anything yourself: these fields are captured natively by the SDK.

They serve one purpose:

• Filtering responses already collected, in a survey's Analytics view (Filter button), on these same fields.

In the Analytics view, the exact path is: Filter → Select group: "Response" → Select type: "Hidden Field" → pick the field (e.g. active_page.url) → operator ("Is"...) → value.

Page / URL

• active_page.url — full URL of the page at the time of the response
• active_page.title — page title
• active_page.domain — domain of the URL
• active_page.path — path of the URL (no domain or query string)
• active_page.search — the URL's query string
• active_page.hash — the fragment after the # in the URL
• active_screen.name — name of the screen displayed (mobile apps)

Campaign / UTM

• campaign.name — campaign name (utm_campaign)
• campaign.source — utm_source
• campaign.medium — utm_medium
• campaign.term — utm_term
• campaign.content — utm_content

Operating system

• os.name — e.g. Windows, iOS, Android
• os.version — OS version

Device

• device.model — model (e.g. iPhone 12, Pixel 6)
• device.manufacturer — manufacturer (Apple, Samsung, Google...)
• device.name, device.brand, device.type — additional device info
• platform — desktop, mobile, tablet or other

Browser and SDK

• browser.name — e.g. Chrome, Firefox, Safari
• browser.version — browser version
• user_agent — the raw user-agent string
• library.name — SDK used (sdk-js, sdk-react...)
• library.version — SDK version
• bot — bot/crawler detection (true/false)
• app.version — mobile app version

Screen

• screen.width, screen.height — screen dimensions in pixels
• screen.scale — zoom factor / devicePixelRatio
• screen.density — pixel density (mobile)

Network (mobile)

• network.wifi, network.cellular, network.bluetooth, network.offline, network.carrier

Locale

• locale — e.g. fr, en-US
• timezone — e.g. Europe/Paris

Geolocation (automatically inferred from IP)

• geoip.city — city
• geoip.country.code, geoip.country.name, geoip.country.emoji, geoip.country.currency, geoip.country.tld, geoip.country.capital, geoip.country.call_code, geoip.country.is_in_european_union — country info
• geoip.continent.code, geoip.continent.name — continent
• geoip.location.latitude, geoip.location.longitude, geoip.location.accuracy_radius — coordinates
• geoip.timezone.name, geoip.timezone.abbreviation, geoip.timezone.offset
• geoip.subdivision_1.code/name, geoip.subdivision_2.code/name, geoip.subdivision_3.code/name — region/subdivision

How to use them

In a survey's Analytics view filter (Analyze tab → Survey analytics → Filter button → "Response" group → "Hidden Field" type), these fields show up as conditions available alongside your custom properties and events. Pick the field (e.g. active_page.url), an operator, and a value.

Common example: to keep only responses given on a specific page, filter on active_page.url in the Analytics view.

Updated on: 17/07/2026