Question before collection
Define the business decision, markets, population, observation unit, and refresh period before selecting sources.
Research provenance
Collect market-specific public evidence with a declared source list, route policy, timestamp, and review trail—without confusing network location with research validity.
Verification record · VR-2048
Evidence before conclusion
Observation accepted
Required route, response, and evidence fields are present.
Requested market
US · New York
Observed route
rotating · session 8F2A
Response artifact
HTML + headers + timestamp
Decision reason
page accepted by validation policy
Decision guide
Define the business decision, markets, population, observation unit, and refresh period before selecting sources.
List public sources, expected fields, access constraints, ownership, and known bias instead of discovering targets during extraction.
Align route, language, currency, timezone, and page state so records from different regions are comparable.
Store URL, timestamp, route context, parser version, and a compact artifact for every accepted record.
Avoid treating duplicated listings, syndicated content, or repeated seller pages as independent evidence.
Escalate contradictory, high-impact, or low-confidence findings rather than forcing every page into an automated conclusion.
Make each stage explicit so a later analyst can understand how the dataset was produced.
Write the question, target markets, source types, sample rules, required fields, and exclusion criteria.
Test a small source set directly and through the intended routes; document localization, consent, and rendering behavior.
Schedule permitted requests, isolate state, validate responses, and stop on denial or repeated challenge conditions.
Standardize units, currencies, entities, and timestamps while preserving the original value and source.
Quantify coverage and missingness, review outliers, and link conclusions back to the supporting observations.
No. It changes the network location of the observation. Representativeness depends on source selection, sampling, timing, account state, and the market question.
Use it when a multi-step public workflow must keep locale, consent, or pagination state. Independent observations should usually rotate or use separate sessions.
Keep source URL, timestamp, requested and observed market, response status, extracted fields, parser version, and a compact redacted artifact.
Preserve both observations, attach source and time context, and apply a documented reconciliation or human-review rule rather than silently choosing one.