Portfolio stats
Plus reports aggregate activity from published pages, including visits, gallery views, and photo opens. It does not identify individual visitors.
Updated August 24, 2026
On this page
Open stats
- 01Open DashboardSign in to Studio and open Dashboard. Portfolio stats appear after the setup guide is complete.
- 02Choose a rangeSelect 7D, 30D, or 90D. The headline metrics, daily chart, table, and top-content lists use the same range.
- 03Inspect a dayPoint to or focus a chart bar to see visits, portfolio page views, gallery views, and photo opens. Use View daily data for an exact table.
What each number means
Anonymous portfolio entries counted once per browser-tab session. This is not a count of identified people or guaranteed unique visitors.
Loads of the public portfolio overview.
Loads of a public gallery page.
Opens in the photo viewer or on an individual photo page, not raw image-file requests.
Photo opens divided by visits for the selected range. It is an engagement ratio, not the percentage of visitors who opened a photo.
Use Top photos and Top galleries
Top photos ranks meaningful photo opens; Top galleries ranks gallery views. Use them to learn which published work receives attention, but do not treat a small difference as a verdict on artistic quality.
- Compare galleries over a meaningful period rather than reacting to one day.
- Account for placement: the first gallery and opening images naturally receive more exposure.
- Use a direct gallery link when sharing a specific series, then look for activity in that gallery.
- Removed items can remain in historical reporting with a Removed label. Analytics history is not rewritten when content is deleted.
Privacy and owner-view filtering
ISO100 uses aggregate, no-cookie public analytics. It does not create a cross-site visitor identity graph, and normal Studio reporting does not expose raw IP addresses.
Opening a live portfolio from Studio sets a browser-local owner-view exclusion for that browser so routine checks do not inflate the account's stats. Automated user agents are filtered on a best-effort basis.
Why counts can differ
- Visits are tab sessions, while page views and photo opens are engagement events. One visit can contain many of the other events.
- Privacy tools, content blockers, failed requests, offline browsing, or a closed tab can prevent an event from being recorded.
- Bot filtering is best effort. Very small residual automated activity or missed human events can occur.
- The dashboard groups activity by UTC date for stable reporting, so a local late-night view can appear on the adjacent reporting day.
- Stats begin with recorded public activity; they do not reconstruct traffic from before analytics collection existed.
If stats show zero
- 01Confirm the portfolio is publishedStats are generated by the public pages. A Studio draft or preview does not create normal public traffic.
- 02Check the selected rangeSwitch from 7D to 30D or 90D if the portfolio has not been shared recently.
- 03Use an independent browserA portfolio opened from Studio is intentionally excluded in that browser. Test from a different browser or device, then allow time for the aggregate to update.
- 04Contact support with specificsIf known external visits never appear, include the portfolio URL, approximate date and time, browser, and the selected range.
Open Studio to make the change.
Related docs