Portfolio analytics
Folio hosts your portfolio and counts its traffic in the same account, so there is no tag to paste, no plugin to add, and no cookie banner to show. A visit is identified by a one-way daily hash of the IP, the browser, your site and the date, never by a cookie, and the dashboard reports views, visits, entry pages, referring sites, contact leads and downloads. Counting starts on the first public page load and is included on the free plan, because no paid tier gates the report.
Publish the site. The traffic report is already running.
Free to publish, no card, no tracking code. Every table in the window downloads as a CSV, so the counts stay yours even if you leave.
The honest version
The first thing almost everybody asks about their own site is who visited it. No analytics product can answer that, and any product implying otherwise is either guessing from a corporate IP block or selling you data it had no business collecting. A web server sees requests, not people. What you can honestly know is counts and shapes: how many pages were opened, how many separate people opened them, where each visit landed first, which site sent it, and what it did before leaving.
Folio reports exactly that and then stops. A visit is recorded as a one-way hash built from the visitor IP, the browser string, your site, and the UTC date, salted with a server secret. It cannot be reversed into an IP. Because the date is part of the material, it changes at midnight: two page loads by the same person on the same day collapse into one visit, and the same person tomorrow is counted as a new one.
That is the whole trade, stated plainly. You give up cross-day identity and you never learn a name. In exchange you set no cookie, you ask nobody for consent, and you hold nothing about a visitor that could later be subpoenaed, sold, or leaked.
The dashboard
Built for one professional site and the decisions you actually make about it, not for a sales funnel you do not have.
Traffic
Page views and unique daily visits over a 7, 30, or 90 day window. Each headline number carries its change against the previous equal window, and that change is left blank rather than faked when the prior window had nothing in it to compare against.
Sources
Referrers are stored as a bare hostname, never the full URL and never the query string. Visits that arrived with no referrer at all are reported as direct, which on a portfolio usually means somebody typed you in or clicked the link in your signature.
Pages
The page each visit started on, ranked, next to the pages that pulled the most views. On a portfolio those two lists are rarely the same, and the gap between them tells you which project is doing the recruiting for you.
Conversions
Booking opened, resume downloaded, portfolio downloaded, press kit downloaded. Contact-form leads are counted from the leads themselves on the server rather than from a browser event, so an ad blocker cannot quietly hide one from you.
Rhythm
Views by hour and by weekday, plus views per visit and the share of visits that only ever saw one page. The hours are marked UTC on the page, so a number is never quietly wrong for the timezone you read it in.
Export
Every table in the selected window downloads as a CSV. Rows are kept for 400 days by default, so a job search that ran long is still there in full when you go back to look at what worked.
Setup
On most platforms this is a four-step chore that ends in a cookie banner. Here it is not a task at all.
01
Counting begins with the first public page load at portfolio.wrxstack.com/yourname. Nothing to generate, nothing to paste into a header, no ownership to verify, no plugin directory to go shopping in.
02
The dashboard sits in your admin, one click from the editor. Same login as the site itself, so there is no second product to learn and no second password to lose.
03
Choose 7, 30, or 90 days. The busiest day, the busiest hour, the top referrer and the entry pages are all on the first screen, which makes a weekly check about a minute of work.
04
If a client or an employer needs the numbers inside Google Analytics, paste the measurement ID into settings. GTM and PostHog take an ID too. All three set cookies, so Folio holds them behind a consent gate and your visitors start seeing a banner. That is the real price of adding them, and it is precisely why the built-in report exists.
Against the builders
The site builders all get you a number. The question is what it costs you, in money and in consent, to see it.
| Capability | Folio | Wix | Squarespace | Adobe Portfolio |
|---|---|---|---|---|
| Analytics with nothing installed | Built in. The counter runs from the first published page load. | A traffic dashboard is included. The deeper reporting moves with the plan you are on. | An analytics panel is included, and how much of it you get follows your plan. | No visitor dashboard of its own. You connect a Google Analytics property. |
| What it costs to see your traffic | Nothing. There is no analytics entitlement anywhere in the plan, so no part of the report is held back on Free. | A free tier exists, and the fuller reporting is a reason to leave it. | There is no free plan to be on. Publishing at all needs a paid subscription once the trial ends. | It rides on a paid Creative Cloud plan, and the numbers still come from Google rather than Adobe. |
| Cookie banner for the default setup | None. The built-in count writes nothing to the browser, so there is no consent to collect. | In practice yes. The stack sets cookies and the platform ships a consent tool to declare them. | In practice yes. The built-in measurement uses cookies and a banner is provided for them. | Yes, the moment Google Analytics is connected, because that is the thing setting the cookies. |
| Where the numbers live | In the same account as the site. One login, one dashboard, one CSV button. | In the platform dashboard, alongside a field for pasting a Google Analytics ID. | In the platform panel, alongside a field for pasting a Google Analytics ID. | In your Google Analytics property. A second product, a second login, a second thing to learn. |
| What the report is shaped for | One portfolio or profile site. Resume downloads, booking clicks and contact leads are first-class rows. | Any site, stores included, so the report leans on a commerce funnel you do not have. | Any site, with commerce reporting sitting at the center of the richer plans. | Page views for a gallery. Nothing at all about hiring intent. |
Competitors are described at the shape of the published offer, never at a price, because tiers change and a number here would rot. Verify each before you decide. Every Folio row is checkable inside the product on a free account.
The limits
It cannot be installed on a site you already own. The counter is a part of the hosting, not a tag you can drop into WordPress, Webflow, or something you deployed to Netlify yourself. If that is the problem you have, buy Plausible, Fathom, or Matomo. That is their job, they are good at it, and this page is not going to pretend otherwise.
There is no returning-visitor number, and there never will be a fabricated one. The daily rotating hash is the thing that makes the cookieless claim true, and the same design makes it genuinely impossible to say that Tuesday is the same human as Monday. Any tool offering you both is holding something on your visitors that Folio chose not to hold.
There is no e-commerce reporting. No revenue, no carts, no checkout funnel, because Folio does not sell anything on your behalf and will not fake a measurement of a sale it never took part in.
And free is really free here, but it is not everything, so here is the rest of it. The free plan carries zero custom domains, so the site lives at portfolio.wrxstack.com/yourname and not at a name you bought. A Made with Folio credit stays on the page. AI drafting stops after 10 generations in a month, and you get the core designs rather than the full 60-theme gallery. The traffic report is the one thing that does not move: it is identical on Free and on Pro.
First-party facts
0
Cookies set by the built-in counter
$0
Cost of the traffic report on Free
400
Days of history kept by default
4
Conversion events tracked out of the box
FAQ
You cannot, and nobody selling you a tool can either, not honestly. A web server receives requests, not names. Folio tells you how many visits and page views arrived, which page each visit opened first, which site referred it, and which downloads or booking clicks followed. It will not show you a person, a company, an email, or an IP address, and it cannot, because the IP is never stored in the first place. Visitor identity here is a salted one-way hash that is discarded and rebuilt fresh the next day.
There is nothing to add. From the moment your first page is public, views and visits are being recorded, and the Insights dashboard is already waiting in your admin. No tracking code, no property to create, no site ownership to verify. If you also want the numbers to land in Google Analytics, settings has a field for a GA4 measurement ID, one for a GTM container, and one for a PostHog project key.
GA4 has a free tier that is more than enough for a portfolio, so money is not the reason to skip it. The reasons are that it writes cookies, which means you now owe your visitors a consent banner, and that it is a whole second product whose reports were designed around ad campaigns you are not running. Connect it anyway if you want it. Folio keeps its own count regardless, so the two never depend on each other.
Cookieless means nothing at all gets written to the browser and nothing trails the visitor from one site to the next. Folio hashes the IP, the browser string, your site, and the current UTC date together with a server secret, and keeps only the resulting 32-character string. It cannot be turned back into an IP. Nothing is placed on the visitor device, which is why there is nothing for them to clear and nothing for them to opt out of.
For the built-in count, no banner is required, because no cookie is written and nothing personal sits at rest. A short privacy note is still a good habit and costs you one page. That answer flips the second you paste in a GA4, GTM, or PostHog ID: those write cookies, so Folio keeps them behind a consent gate and your visitors will meet a banner before those scripts ever load.
No, and it would be dishonest to blur that. This is measurement for a site Folio hosts, not a snippet you can install somewhere else. There is nothing to paste into WordPress, into Webflow, or into a site you deployed yourself. If that is the requirement, a standalone privacy-first analytics product is the right buy, and it is simply a different purchase from this one.
The dashboard reads 7, 30, or 90 days at a time and lines each window up against the equal window immediately before it. Rows are retained for 400 days by default, which comfortably outlasts a long job search. Every table in the window you are looking at downloads as a CSV, so the underlying counts remain yours after you have moved on.
Keep going