Skip to content

REX Browsing History Data

Schema overview and sample records, prepared by BRIC. Updated November 2026.

This page describes the browsing history data collected by a REX browser extension’s history module (rex-history).

A record is one visit to one web page, read from the browser’s own history. The record type is rex-history-visit. If a participant opens the same page three times, that produces three records, each with its own visit_id and visit_time.

Volume: one record per page visit, so volume follows how much the participant browses.

Granularity: a single visit. Visits can be chained into browsing paths with referring_visit_id, and grouped into tabs and sessions when rex-page-events is also installed.

Coverage: on first run, the module reads back lookback_days days of existing history, then keeps collecting new visits. It reads Chrome’s history, so it sees visits from any window except private (Incognito) windows.

Provenance: every record carries the participant ID, the extension name and version, and a hash of the configuration that produced it in passive-data-metadata.

Level of detail: set per study by lists of sites, described below. Lists change what a record contains; they never remove the visit. Every visit leaves a record, so researchers always know how much browsing took place.

Each visit is recorded at one of three levels of detail. The researcher controls which sites fall at each level through named lists of sites (see rex-lists).

LevelSet byurl and titledomain
FullDefault, or a site on an allow listKeptKept
Domain onlyA site on a domain_only_lists listReplaced with DOMAIN ONLYKept
CategoryA site on a filter_lists listurl replaced with CATEGORY:<category>, such as CATEGORY:other; title blankedBlanked
CategoryAny site missing from every allow list, when allow_lists is seturl replaced with CATEGORY:NOT_ON_ALLOWLIST; title blankedBlanked

When a site matches more than one kind of list, domain-only lists apply first, then allow lists, then filter lists. At every level the record keeps the visit’s timing and navigation fields.

Separately, category_lists tag visits with category labels in categories without changing the URL, title or domain.


Below are three records, one at each level of detail. They show the properties object of each data point; see the Data Reference Overview for the fields stored around it.

{
"name": "rex-history-visit",
"date": 1785420060000,
"url": "https://www.example.org/articles/garden-guide",
"recorded_url": "https://www.example.org/articles/garden-guide",
"domain": "example.org",
"title": "A Guide to Pollinator Gardens",
"visit_time": 1785420060000,
"transition_type": "link",
"is_local": true,
"categories": ["news"],
"visit_id": "48213",
"referring_visit_id": "48212",
"history_item_id": "9921",
"last_visit_time": 1785420060000,
"visit_count": 3,
"typed_count": 0,
"allowed_by_list": "news-sites",
"allowed_by_list_entry": {
"list_name": "news-sites",
"matched_pattern": "example.org",
"matched_pattern_type": "domain",
"matched_source": "server",
"matched_metadata": {}
},
"filtered": false,
"tab_id": 1204,
"window_id": 1,
"session_id": "session-5f2c",
"page_events_url_shown_at": 1785420060120,
"passive-data-metadata": {
"source": "participant-0001",
"generator": "rex-history-visit: Research Extension/1.0.0 Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/141.0.0.0 Safari/537.36",
"generator-id": "rex-history-visit",
"timestamp": 1785420060,
"timezone": "America/Chicago",
"configuration-hash": "1f3c0e9a7b2d4c5e6f708192a3b4c5d6e7f8091a2b3c4d5e6f708192a3b4c5d6",
"enqueued-at": 1785420061
}
}
{
"name": "rex-history-visit",
"date": 1785420120000,
"url": "DOMAIN ONLY",
"recorded_url": "DOMAIN ONLY",
"domain": "example.com",
"title": "DOMAIN ONLY",
"visit_time": 1785420120000,
"transition_type": "typed",
"is_local": true,
"categories": [],
"visit_id": "48214",
"referring_visit_id": "0",
"history_item_id": "9930",
"last_visit_time": 1785420120000,
"visit_count": 1,
"typed_count": 1,
"filtered": true,
"filtered_by_list": "social-media-sites",
"filtered_by_list_entry": {
"list_name": "social-media-sites",
"matched_pattern": "example.com",
"matched_pattern_type": "domain",
"matched_source": "server",
"matched_metadata": {}
},
"passive-data-metadata": { "...": "as above" }
}
{
"name": "rex-history-visit",
"date": 1785420180000,
"url": "CATEGORY:other",
"recorded_url": "CATEGORY:other",
"domain": "",
"title": "",
"visit_time": 1785420180000,
"transition_type": "link",
"is_local": true,
"categories": [],
"visit_id": "48215",
"referring_visit_id": "48214",
"history_item_id": "9931",
"last_visit_time": 1785420180000,
"visit_count": 2,
"typed_count": 0,
"filtered": true,
"filtered_by_list": "history-filter",
"filtered_by_list_entry": {
"list_name": "history-filter",
"matched_pattern": "example.net",
"matched_pattern_type": "domain",
"matched_source": "server",
"matched_metadata": { "category": "other" }
},
"passive-data-metadata": { "...": "as above" }
}

The table below flattens five sample visits into an analysis-ready rectangle. Times are shown in the participant’s local time zone (from passive-data-metadata.timezone).

visit_timeurldomaintitletransition_typecategoriessource
2026-07-30 09:01:00 CThttps://www.example.org/articles/garden-guideexample.orgA Guide to Pollinator Gardenslinknewsparticipant-0001
2026-07-30 09:02:00 CTDOMAIN ONLYexample.comDOMAIN ONLYtypedparticipant-0001
2026-07-30 09:03:00 CTCATEGORY:otherlinkparticipant-0001
2026-07-30 09:05:41 CTCATEGORY:NOT_ON_ALLOWLISTlinkparticipant-0001
2026-07-30 09:07:12 CThttps://www.example.org/example.orgExample News Hometypednewsparticipant-0001

FieldTypeDescription
namestringAlways rex-history-visit.
datenumberSame as visit_time.
urlstringThe URL as recorded: the full URL, DOMAIN ONLY, or a CATEGORY: label, depending on the level of detail.
recorded_urlstringSame as url.
domainstringRegistered domain of the page, such as example.org for news.example.org. Blank at the category level.
titlestringPage title, DOMAIN ONLY, or blank, depending on the level of detail.
visit_timenumberWhen the visit happened, in epoch milliseconds.
transition_typestringHow the participant reached the page, as reported by Chrome: for example link, typed, auto_bookmark, form_submit, reload or generated.
is_localbooleantrue if the visit happened in this browser, false if it was synced from another device signed in to the same browser account.
categoriesstring[]Category labels from category_lists that match this page. Empty if none match.
visit_idstringChrome’s ID for this visit. Unique per visit within one browser profile.
referring_visit_idstringvisit_id of the visit that led here, or "0" if none. Use it to rebuild browsing paths.
history_item_idstringChrome’s ID for the URL. Shared by every visit to the same URL.
last_visit_timenumberMost recent visit to this URL, in epoch milliseconds, at the time of collection.
visit_countnumberTotal visits to this URL in the browser’s history, at the time of collection.
typed_countnumberHow many of those visits came from typing the address.
allowed_by_liststringName of the allow list that matched, when allow lists are in use.
allowed_by_list_entryobjectThe allow-list entry that matched: list name, pattern, pattern type, source and metadata.
filteredbooleantrue if a domain-only or filter list reduced this record.
filtered_by_liststringName of the list that reduced this record.
filtered_by_list_entryobjectThe entry that reduced this record: list name, pattern, pattern type, source and metadata.
tab_id, window_id, session_idnumber, number, stringBrowser tab, window and session identity. Present only when rex-page-events is installed and the visit was matched to a tab.
page_events_url_shown_atnumberWhen rex-page-events saw the URL become active in the tab, in epoch milliseconds. Present only with tab_id.
passive-data-metadataobjectParticipant, record type, timestamp, time zone and configuration hash. See Exploring the Data.

Fields with no value, such as allowed_by_list when no allow lists are configured, are left out of the record.