Public resources available
Resources listed right now
LaneHelp public stats
LaneHelp,
by the numbers.
LaneHelp publishes these numbers so the community can see how the platform is being used, what people are looking for, what information LaneHelp currently has, and where information may still be missing. These numbers describe activity on LaneHelp. They do not tell us whether someone ultimately received a service.
Why we count: every number here exists to show what Lane County needs — what works, and what is missing. Nothing identifies a person. Using LaneHelp regularly makes that picture clearer for everyone working on it. It takes a village.
Housing leads shown publicly
Housing leads shown publicly now
Communities represented
Lane County communities listed
Page opens
Page opens in this time period
Choose dates or search details
Dates use Lane County time. Search choices change only the search numbers. Resource and page-open totals keep the time shown on their labels.
Discovery
How people found LaneHelp
Counted visits grouped by where the visitor came from. The browser reports this, and browsers can hide it, so this is a helpful picture rather than a complete one.
Arrival paths
Where counted visits came from
Came directly
2,438
73.1%
Search engines
772
23.2%
Social media
91
2.7%
Other websites
32
1%
Shared work links
0
0%
Arrival paths come from browser-reported referrers on counted visits. Browsers and apps can hide the referrer, so "Came directly" includes some visits whose real starting point is unknown.
Search engines
Search engines that sent visits
404
52.3%
Bing
180
23.3%
Duckduckgo
133
17.2%
Yahoo
46
6%
Ecosia.Org
8
1%
Search.Brave.Com
1
0.1%
This is LaneHelp’s own measurement of visits that arrived from a search engine. Search-engine-reported click and impression totals from Google Search Console and Bing Webmaster Tools are shown — see Data sources.
How this is counted
A visit is one first-party session that looked like a real person and opened at least one page. Each visit is placed in exactly one arrival group using the referrer the browser reported when the visit began. Internal navigation, LaneHelp staff, development machines, and bot-classified visits are excluded.
“Came directly” means the browser reported no referrer. Some of those visitors typed the address or used a bookmark; others came from apps or browsers that hide referrers.
Source: LaneHelp activityPeriod: Last 30 daysUpdated: Aug 6, 2026, 4:25 PM PDT
Service directory
What LaneHelp lists
These numbers count active resource listings. A resource can appear in more than one service category. Online and statewide services are kept separate from local places.
Services by type
Active resources by service
Health care
190
28.9%
Community support
175
26.6%
Mental health & recovery
159
24.2%
Youth & family
124
18.9%
Food
91
13.9%
Money & benefits
43
6.5%
Housing help
35
5.3%
Clothing & hygiene
33
5%
Shelter
29
4.4%
Jobs & training
21
3.2%
Legal help
21
3.2%
Transportation
19
2.9%
Older adults
18
2.7%
Disability support
17
2.6%
Veterans
17
2.6%
Domestic & sexual violence support
12
1.8%
Categories with fewer listings. Tan bars show the three categories with the fewest resources. This does not mean fewer people need those services.
Where services are offered
Local, countywide, and online
Eugene / Springfield
462
70.3% of active listings
Outside the metro
141
21.5% of active listings
Countywide
24
3.7% of active listings
Remote / online
26
4% of active listings
Statewide / outside county
3
0.5% of active listings
All active listings are included. 1 listings have more than one address.
Beyond the directory
Events, jobs, and alerts LaneHelp tracks
Upcoming events
Active event listings whose start time is still ahead.
Events added
Event listings first added during this time. One recurring event can appear as several dated listings.
Alerts updated by feeds
Alerts updated by a source during this time. This does not count page opens.
Active job listings
Job listings currently shown as active.
Lane County communities
Listings by community
379
Eugene
80
Springfield
39
Florence
26
Cottage Grove
15
Oakridge
10
Junction City
9
Veneta
6
Creswell
5
Mapleton
4
Lowell
3
Blue River
3
Elmira
3
Eugene/Springfield
3
Pleasant Hill
Housing & shelter
Housing leads and shelter information
Housing numbers count leads, not open units or guaranteed vacancies. LaneHelp does not show a shelter-bed total because the available data is not consistent enough yet.
Housing leads updated by sources
Last 30 days
Housing leads added
Last 30 days
Waitlist / program records
Listed now
Housing sources
Listed now
Last source update
When housing leads were last seen
Seen this week
147
68.4%
Seen in 8–30 days
1
0.5%
Older than 30 days
67
31.2%
Housing status
What sources report
Marked not current by source
75
78.1%
Listed as available
21
21.9%
96 of 215 current leads include a source-reported status. The rest come from sources that list availability only on their own site — LaneHelp links to them rather than guessing.
Website use
Pages opened on LaneHelp
These counts include page opens from visits that look like real people. They do not identify anyone and do not show whether someone received help.
Visits counted (estimated)
Visits from normal phone, computer, and tablet browsers in the United States that showed a sign of real use. One visit can open several pages; 3,517 of these visits also cleared LaneHelp’s strictest people-not-robots check.
Counted visits are estimates. A visit counts when it uses a normal phone, computer, or tablet browser, arrives from the United States, and shows a sign of real use — more than one page, an action, or ten seconds or longer. Known bots and LaneHelp staff are removed first. Automated tools imitate browsers convincingly, so these tests do most of the filtering; some automation may still remain. Repeat page opens are included, and none of these numbers count people, services received, or successful outcomes.
Page opens set aside
- Not a counted visit
- 4,449
- Known automation
- 8
- LaneHelp staff
- 472
Most-opened sections
Where people went
Jobs
1,987
31.6% of page opens
Resources
1,306
20.7% of page opens
Home
704
11.2% of page opens
Housing
400
6.4% of page opens
Aic
334
5.3% of page opens
Map
218
3.5% of page opens
Events
203
3.2% of page opens
Shelter
203
3.2% of page opens
Over time
Page opens by day
Jul 7Aug 6
Most-opened listings
Resources people opened most
Oxford Houses – Lane County
25
6.9%
Oxford Houses – Women's (Lane County)
11
3%
Community Health Centers - South Lane Clinic
8
2.2%
1st Way
7
1.9%
CAHOOTS
6
1.6%
River Avenue Navigation Center
6
1.6%
211info
5
1.4%
Community Supported Shelters Access Center
5
1.4%
Eugene Faith Center Food Pantry
5
1.4%
Lane Senior Guide
5
1.4%
Opens show interest and need, not service quality. A busy listing usually means many people need that kind of help — it is not a rating or an endorsement.
Devices used
Desktop
2,575
77.3%
Mobile
751
22.5%
Tablet
7
0.2%
Searches on LaneHelp
What people searched for help with
- Searches recorded
- 3,879
- Found matches
- 93.5%
- Found nothing
- 247
- Typical matches per search
- 40
77.6% of searches happened outside 9am–5pm — people look for help when most offices are closed.
Recorded searches come from the site search log with LaneHelp staff excluded. Repeat searches are included and automated traffic may remain, so this is an activity count, not a people count. Search text is stored only as an anonymous fingerprint; no one can read what was typed.
A newer, stricter search tracker with need categories started Jul 14 and has counted 6 searches so far (6 in this time period); grouped need patterns will appear once it reaches 20.
Next steps
Actions people took
These are next steps someone started through LaneHelp — calling, getting directions, opening a website, sharing, or printing. Starting an action does not confirm that help was received.
Connection actions
Calls, directions, websites, shares, and prints started through LaneHelp during this time.
These actions show that someone started a next step through LaneHelp. LaneHelp cannot confirm whether a call connected, a website helped, or a service was received.
By type of action
What people did next
Phone calls started
Taps on a phone number. LaneHelp cannot confirm the call connected.
11
Directions started
Taps that opened directions to a listed location.
186
Websites opened
Taps that opened an outside website from a listing.
Listings shared or saved
Share and save actions on listings.
Print and PDF actions
Print buttons and PDF opens for listings, handouts, and Quick Sheets.
3
Paddle & guided help
Help LaneHelp walked people through
Paddle chats answered
Plain-language requests Paddle answered on the web.
Chats that surfaced resources
Chats where Paddle handed back one or more resource cards.
Routes created
Trip plans Paddle built to a real service location.
Resource listings opened
Listing opens recorded by the site log, staff excluded.
Paddle is LaneHelp’s plain-language helper on the web and by text. A chat is one request Paddle answered; a route is a trip plan Paddle built to a real destination. Chat text is not shown here and is not used in this report.
How this is counted
Each count is one accepted action event from a visit that looked like a real person. Repeat taps are included. Page renders, hovers, scrolling, and ordinary navigation are never counted as actions. LaneHelp staff and bot-classified traffic are excluded.
“Collecting data” means LaneHelp has never recorded that action type yet, so no number is shown instead of a possibly false zero.
Source: LaneHelp activityPeriod: Last 30 daysUpdated: Aug 6, 2026, 4:25 PM PDT
Keeping information current
How LaneHelp checks its listings
LaneHelp re-checks listings against their sources on a rolling basis. This section shows how much of the directory was confirmed current at its last check, and how much checking work happened during this time.
Confirmed current
579 of 657 active listings
88.1% confirmed current at the last check
The rest are active listings waiting on their next scheduled re-check. Waiting on a re-check does not mean the information is wrong. A current listing is not a promise that a program has space, funding, appointments, or same-day help.
Open information differences
Open now
Urgent information conflicts
Open now
Source checks
Last 30 days
Listing update actions
Last 30 days
Sources watched
Listed now
Provider links
Listed now
Health care provider data
Resources connected to provider information
These provider, location, and specialty records come from public sources. Always confirm coverage and appointments with the provider.
Provider records
Latest source data
Resources linked
Listed now
Provider locations
Latest source data
Specialties represented
Latest source data
Organizations represented
Latest source data
Example
See how one resource connects
Example resource
Lane County Behavioral Health Clinic
- Provider records
- 46
- Locations
- 2
- Organizations
- 2
Allergy & ImmunologyAllergy & Immunology: AllergyChild & Adolescent PsychiatryClinic/Center: Federally Qualified Health Center (FQHC)Community Health WorkerCounselor
OHP information comes from public provider data. It is not a LaneHelp endorsement or a promise that appointments are available. Confirm with the provider before scheduling.
Data sources
Where these numbers come from
Every number on this page comes from a named source. Sources that are not connected yet are listed here honestly instead of shown as empty charts.
LaneHelp resource data
ConnectedListings, housing leads, jobs, alerts, and verification records from the LaneHelp database.
LaneHelp activity
ConnectedFirst-party page opens, searches, and action events with bot and staff filtering.
SMS Paddle
ConnectedInbound text-message counts. Message contents are never used in this report.
Cloudflare traffic
ConnectedConnected. Edge request and unique-IP estimates come from the Cloudflare analytics API.
Google Search Console
ConnectedConnected. Totals come from the Search Console Search Analytics API.
Bing Webmaster Tools
ConnectedConnected. Totals come from the Bing Webmaster rank-and-traffic API.
Cloudflare edge traffic
Raw infrastructure volume
Estimated internet connections
Estimated distinct client IPs across the filtered range; not verified people or visits.
Website file requests
HTTP requests served at the edge; not a funnel into search submissions.
Edge-measured page loads
Page loads as measured at the edge, including bots and automation Cloudflare could not filter.
Requests served from cache
Requests answered from Cloudflare cache instead of the LaneHelp server.
Edge traffic includes bots, previews, monitoring, and repeat requests. It is infrastructure volume, not people, and it must not be added to the visit counts above.
Search-engine reporting
What search engines report about LaneHelp
Google Search
- Clicks
- 302
- Impressions
- 8,570
- Click-through
- 3.5%
- Avg. position
- 11.8
Bing Search
- Clicks
- 239
- Impressions
- 18,422
- Click-through
- 1.3%
- Avg. position
- —
Impressions mean LaneHelp appeared in search results; they do not mean someone visited. Clicks mean someone selected a LaneHelp result. Average position is an estimate of where LaneHelp appeared. These totals are reported by the search engines themselves and use their own counting rules, so they will not match LaneHelp-side visit counts exactly.
How this is counted
“Connected” means the source answered when this report was made. When a source fails or is not configured, its numbers are hidden rather than displayed as zero, and the failure is noted in the methodology section below.
Impressions mean LaneHelp appeared in search results; they do not mean someone visited. Clicks mean someone selected a LaneHelp result. Average position is an estimate of where LaneHelp appeared. These totals are reported by the search engines themselves and use their own counting rules, so they will not match LaneHelp-side visit counts exactly.
Source: LaneHelp status checks, Cloudflare, Google Search Console, Bing Webmaster ToolsPeriod: Last 30 daysUpdated: Aug 6, 2026, 4:25 PM PDT
What is not measured
What these numbers do not show
Some useful information is still missing or not reliable enough to publish. These four limits matter when reading this page.
Search patterns are still limited
There are not enough grouped LaneHelp searches yet to show a reliable pattern.
We do not know who received help
Opening a page, searching, or following a link does not prove that someone received help, found housing, or finished an application.
Shared and temporary housing are not counted yet
The current data does not label shared and temporary housing consistently, so LaneHelp does not publish a total.
Shelter openings are not counted yet
LaneHelp lists shelters, but the available updates are not current or consistent enough for one public total.
How numbers are counted
The same numbers in every format
The page, copied summary, print view, and spreadsheet use the same saved report. The page does not change the totals.
LaneHelp counts this activity for one reason: to understand what Lane County needs — what people look for, what they find, what is missing, and what is working. Nothing here identifies a person. Using LaneHelp regularly genuinely helps: every counted search and page open makes the picture of the county’s needs clearer, for LaneHelp and for the organizations working to meet them. It takes a village.
Date rule
Custom dates use Lane County time. Both the start date and the end date are included.
Privacy
This page shows totals only. It does not include names, search text, exact personal locations, private assistant conversations, or a person’s activity history.
Freshness
LaneHelp saves this report for 5 minutes before making a new one. “Updated” shows when the report was made, not when every source changed.
What each number means
Searches counted
Source: public.analytics_events · Counted as: search event
Non-internal search_performed events classified human or likely_human.
Not counted: Internal, unknown, likely_bot, and bot classifications; legacy activity_log search rows.
Searches grouped by need
Source: public.needs_signals · Counted as: need-signal row
Rows whose source is lanehelp_search.
Not counted: Resource-view, handout, QuickSheet, provider, and zero-result follow-on signals.
Page opens
Source: public.analytics_events joined to public.analytics_sessions · Counted as: page-view event
Non-internal page_view events whose session reports a normal mobile, desktop, or tablet browser, is not bot-classified, arrives from the United States, and shows engagement — more than one page, a meaningful action, or ten seconds or longer. This is still an estimate.
Not counted: Bot and likely-bot sessions, bot user agents, sessionless events, internal traffic, visits from outside the United States, and single-page visits that took no action and lasted under ten seconds. Browser user agents are trivially spoofed, so the country and engagement tests carry most of the weight here. A stricter behaviorally-verified subset is published alongside as a floor.
Verified page opens (strict floor)
Source: public.analytics_events joined to public.analytics_sessions · Counted as: page-view event
Page opens from sessions the strict behavioral classifier marked human or likely_human (multiple pages, meaningful actions, or long engagement).
Not counted: Ordinary one-page visits that gave the classifier too little signal — which is why this number is a floor, not the estimate. Sessions recorded before 2026-07-23 were classified without the browser user agent and skew low.
Upcoming events
Source: public.events_canonical · Counted as: event listing
Active event listings with a start time in the future.
Not counted: Past, inactive, and source-retired occurrences.
Events added
Source: public.events_canonical · Counted as: event listing
Event listings first recorded during the selected range.
Not counted: Updates to existing listings.
Active event listings
Source: public.events_canonical · Counted as: event listing
Rows with status=active, including recent past occurrences not yet archived.
Not counted: Inactive and superseded rows.
Public resources available
Source: public.resources · Counted as: unique resource row
Rows with status=active.
Not counted: Inactive resource rows and provider-network records not represented as resource rows.
Communities represented
Source: public.resources · Counted as: community label
Active resource rows assigned to local Lane County community labels.
Not counted: Countywide, online-only, statewide or outside-county, and missing-city buckets.
Housing leads shown publicly
Source: public.housing_listings · Counted as: housing lead record
Rows that pass the same source-aware visibility rules as the public housing page.
Not counted: Rows marked no_longer_seen, stale or not-current rental rows, and suspect parsed rentals.
Housing leads updated by sources
Source: public.housing_listings · Counted as: housing lead record
Rows whose last_seen_at falls inside the selected half-open range.
Not counted: Rows last seen outside the selected range.
Alerts updated by feeds
Source: public.alerts_items · Counted as: alert record
Rows whose last_seen_at falls inside the selected half-open range.
Not counted: Rows last seen outside the selected range.
Listings with recent source updates
Source: public.resources · Counted as: unique resource row
Active resources with last_verified_at in the preceding 90 days.
Not counted: Older or missing timestamps. This does not claim a human reviewed the record.
Active job listings
Source: public.job_listings · Counted as: job-listing row
Rows with is_active=true.
Not counted: Inactive job rows.
Text messages received
Source: public.sms_inbound_messages · Counted as: inbound-message record
Inbound-message records created inside the selected range.
Not counted: Message contents and records outside the selected range.
New AIC records
Source: public.jail_roster_items · Counted as: AIC roster record
Records whose first_seen_at falls inside the selected range.
Not counted: Records first seen outside the selected range.
Housing leads added
Source: public.housing_listings · Counted as: housing lead record
Housing lead records created inside the selected range.
Not counted: Records created outside the selected range.
Housing sources
Source: public.housing_sources · Counted as: housing-source row
Rows not marked disabled.
Not counted: Disabled source rows.
Waitlist / program records
Source: public.housing_listings · Counted as: housing lead record
Current rows classified as waitlist, provider_lead, or provider_directory.
Not counted: Rows marked no_longer_seen and ordinary rental or affordable-property inventory rows.
Shared / temporary housing
Source: public.housing_listings · Counted as: housing lead record
No public count is currently published.
Not counted: All rows while the classification is unavailable; null is used instead of a false zero.
Alert sources
Source: public.alerts_sources · Counted as: alert-source row
Rows with enabled=true.
Not counted: Disabled source rows.
Current listings
Source: public.resources · Counted as: resource row
Active rows whose information was confirmed current at the last check.
Not counted: Active rows waiting on their next source check, inactive rows, and any real-time availability claim. A listing waiting on a re-check is not a listing known to be wrong, so the remainder is not broken out here.
Open information differences
Source: public.data_verification_conflicts · Counted as: conflict row
Open, in-review, needs-outreach, and awaiting-provider conflicts.
Not counted: Resolved, ignored, and false-positive rows.
Urgent information conflicts
Source: public.data_verification_conflicts · Counted as: conflict row
Active conflict rows with risk=high.
Not counted: Medium, low, and closed conflicts. No separate critical tier exists.
Source checks
Source: public.data_verification_observations · Counted as: observation row
Observations whose observed_at is inside the selected range.
Not counted: Evidence detail and raw payloads; observations outside the range.
Listing update actions
Source: public.data_verification_events · Counted as: workflow event
Workflow events created inside the selected range.
Not counted: Internal notes, evidence detail, and actor identities.
Sources watched
Source: public.data_verification_source_health · Counted as: source row
Rows with imports_enabled=true.
Not counted: Disabled or unregistered sources.
Provider links
Source: public.resource_provider_links · Counted as: link row
Exact or high-confidence links to active public resources and eligible source-reported OHP profiles.
Not counted: Low or medium confidence, inactive resources, and ineligible provider rows.
Provider records
Source: public.provider_profiles joined to public.provider_network_participation · Counted as: provider profile row
Profiles with source-reported OHP participation.
Not counted: Superseded, review-needed, non-OHP, and unavailable source rows.
Resources linked
Source: public.resource_provider_links joined to public.resources · Counted as: resource row
Active resources with at least one exact or high-confidence eligible provider link.
Not counted: Inactive resources and lower-confidence links.
Provider locations
Source: public.provider_locations · Counted as: provider location row
Locations attached to eligible source-reported OHP profiles.
Not counted: Locations without an eligible profile.
Specialties represented
Source: public.provider_profiles · Counted as: specialty label
Specialties on eligible source-reported OHP profiles.
Not counted: Empty labels and ineligible profiles.
Organizations represented
Source: public.provider_locations · Counted as: organization label
Organization labels on locations attached to eligible profiles.
Not counted: Empty organization labels and ineligible locations.
Searches recorded
Source: public.activity_log · Counted as: search event
Site search submissions with LaneHelp staff and internal traffic excluded. Search text is stored only as an anonymous hash.
Not counted: Reliable bot classification — automated searches may remain, so this is an activity count, not a people count.
Searches that found matches
Source: public.activity_log metadata.result_count · Counted as: search event
Recorded searches whose engine reported at least one matching resource.
Not counted: Searches without a stored result count (older rows) are excluded from the share calculation, not counted as zero.
Searches that found nothing
Source: public.activity_log metadata.result_count · Counted as: search event
Recorded searches whose engine reported zero matching resources — a direct signal of information LaneHelp may be missing.
Not counted: What was searched for: raw text is never stored or shown.
Paddle chats answered
Source: public.activity_log · Counted as: assist request
Paddle plain-language helper requests answered on the web; SMS requests are counted separately.
Not counted: Chat text, identities, and whether the person ultimately got help.
Routes created
Source: public.activity_log metadata.route_destination · Counted as: route plan
Trip plans Paddle built to a real destination (service location, shelter, office).
Not counted: Whether the trip was taken; destinations are counted, never shown.
Resource listings opened (recorded)
Source: public.activity_log · Counted as: listing open
Resource listing opens recorded by the site log with staff excluded.
Not counted: Reliable bot classification — automated opens may remain.
Visits with a known arrival path
Source: public.analytics_sessions · Counted as: session
Counted visits grouped by entry referrer into search engines, direct, social, shared links, and other websites. A visit whose stored entry referrer is a LaneHelp page is counted as direct, because a LaneHelp page cannot be an arrival path.
Not counted: Development hosts, and every visit excluded from the counted-visit basis. Arrival path is browser-reported and can be missing or stripped, so "Came directly" also holds visits whose real starting point was never reported.
Connection actions started
Source: public.analytics_events · Counted as: action event
Non-internal phone, website, directions, share, print, and PDF action events classified human or likely_human.
Not counted: Page renders, hovers, scrolling, internal traffic, bot-classified events. Starting an action does not confirm the service was reached or received.
Phone calls started
Source: public.analytics_events · Counted as: action event
Non-internal phone_clicked events classified human or likely_human.
Not counted: Whether the call connected or help was received; internal and bot-classified events.
Directions started
Source: public.analytics_events · Counted as: action event
Non-internal directions_clicked events classified human or likely_human.
Not counted: Whether the trip was taken; internal and bot-classified events.
Websites opened
Source: public.analytics_events · Counted as: action event
Non-internal website_clicked events classified human or likely_human.
Not counted: What happened on the outside website; internal and bot-classified events.
Print and PDF actions
Source: public.analytics_events · Counted as: action event
Non-internal print and PDF action events classified human or likely_human.
Not counted: Whether a document was physically printed or shared; internal and bot-classified events.
Google search clicks
Source: Google Search Console Search Analytics API · Counted as: search click
Clicks on LaneHelp results in Google Search as reported by Search Console for the selected dates.
Not counted: A click is not a person and not a service received. Search Console data lags by a couple of days, so recent ranges read low, and short ranges may be partial. When the integration does not answer, no Google totals are published at all rather than shown as zero.
Bing search clicks
Source: Bing Webmaster Tools rank-and-traffic API · Counted as: search click
Clicks on LaneHelp results in Bing Search as reported by Bing Webmaster Tools, for the days it reports inside the selected range.
Not counted: A click is not a person and not a service received. Bing reports whole days only, so a range with no completed Bing day publishes nothing rather than a zero.
Estimated internet connections
Source: Cloudflare GraphQL httpRequests1dGroups.uniq.uniques · Counted as: estimated distinct client IP
Client IPs observed by Cloudflare for the zone, summed across the selected UTC date groups.
Not counted: No LaneHelp-side human verification and no cross-day deduplication. Shared IPs can collapse people; changing or proxy IPs can split them. Bots, crawlers, previews, monitoring, and other automation may remain.
Website file requests
Source: Cloudflare GraphQL httpRequests1dGroups.sum.requests · Counted as: HTTP request
Requests observed by Cloudflare for the zone and selected UTC date groups.
Not counted: Nothing is inferred about people, sessions, searches, or service outcomes.
Edge-measured page loads
Source: Cloudflare GraphQL httpRequests1dGroups.sum.pageViews · Counted as: page load
HTML page loads Cloudflare observed for the zone.
Not counted: Nothing — bots and automation Cloudflare could not filter remain. Do not compare directly with LaneHelp-side counted page opens, which exclude bots and staff.
Requests served from cache
Source: Cloudflare GraphQL httpRequests1dGroups.sum.cachedRequests · Counted as: HTTP request
Requests answered from Cloudflare edge cache.
Not counted: Origin-served requests. This is a delivery-efficiency measure, not a people measure.
What these numbers cannot tell us
- Website use does not show total Lane County need or how many people received help.
- Older search records are not used to describe current search patterns because they were counted differently.
- Traffic totals can include repeat visits, automated tools, previews, and monitoring.
- Listings shown now and website use during a time period are different numbers and should not be added together.
- Shelter openings and shared or temporary housing are not shown until the information is consistent and current enough.
- Provider information comes from public sources. It does not show appointment availability or health care quality, and it is not a LaneHelp endorsement.