Portfolio Development
GA4 for Design Portfolios Measure What Helps
Analytics should help you make a portfolio decision. Install the smallest useful setup, verify it, and read behavior without turning every visit into a score.
The short read
Begin with a decision
Write the question you want the data to help answer before adding tags or events.
Verify the evidence
Use Realtime and DebugView to confirm that the action and its context arrive as intended.
Read paths, not scores
Connect source, landing page, project exploration, and meaningful action before changing the portfolio.
Start with five questions, not fifty metrics
A portfolio rarely needs an enterprise measurement plan. It needs enough evidence to distinguish discovery from exploration and exploration from intent. Write down the decision first, then collect only what could change it.
Where do relevant visitors arrive?
Compare source and landing page. A homepage visit from a recruiter and a project-page visit from a shared link are different journeys.
Do they move beyond the landing page?
Look for navigation into projects, About, résumé, or contact—not a single site-wide engagement score.
Which projects earn attention?
Compare project views and the next action. Popularity can reveal interest, but it does not automatically prove quality.
Which actions show intent?
Contact clicks, form completion, résumé downloads, and deliberate outbound links usually tell you more than raw page views.
What would you change because of this?
If the answer is “nothing,” you probably do not need another event or dashboard yet.
Install GA4, then prove that it works
Create the property and web data stream
Use the portfolio's primary domain, choose the reporting time zone intentionally, and keep the Measurement ID that begins with
G-.Install the Google tag through the site's real publishing system
Many site builders accept the Measurement ID. A coded site can add the Google tag directly. Use Tag Manager only when it genuinely improves how the setup is maintained.
Review enhanced measurement
It can collect page views and events such as scroll, outbound click, site search, video engagement, and file download. Enable only the events that fit the site and your consent approach.
Verify before trusting the reports
Open the live site, perform the journey yourself, and confirm it in Realtime. Use Tag Assistant or DebugView when you need to inspect individual events and parameters.
Let the URL structure do some of the work
If every project has a stable page path, ordinary page views can already answer which work someone opened and what page came next. Do not duplicate that evidence with a custom event unless the page path is ambiguous or the interaction happens without navigation.
Use acquisition and landing-page information to understand how a visit began. Use the page path and subsequent events to understand what happened next. That sequence is more useful than treating all visitors as one audience.
Add custom tracking only where the meaning would otherwise disappear
| Event | Question | Use it carefully |
|---|---|---|
| page_view | Which pages begin and continue a visit? | Built in once collection is installed. |
| scroll | Did someone reach roughly 90% of a page? | Available through enhanced measurement; useful as a rough signal, not proof of reading. |
| click | Did someone follow an outbound link? | Enhanced measurement can collect outbound clicks and relevant link details. |
| file_download | Was a résumé or other file opened? | Enhanced measurement can collect supported file-link clicks. |
| contact_action | Did someone intentionally open email, submit a form, or choose another contact path? | Add one clearly named custom event with a small set of useful parameters. |
| project_view | Which portfolio project did someone choose? | Use only if project selection is not already clear from page paths. |
Keep parameters legible: project slug, page location, action type, and source context are often enough. A parameter collects detail; an event-scoped custom dimension makes custom detail available for analysis in reports and explorations.
The numbers point to a page. What does the page actually communicate?
Share the portfolio and what you are trying to learn. Your free First Read inspects one visible priority in context.
Separate observation, interpretation, and decision
Observation
What happened?
Most search visitors landed on one project. Few continued to another page. Contact clicks came primarily from About.
Interpretation
What might explain it?
The project may satisfy a narrow search, the next path may be unclear, or the About page may provide trust that the project does not.
Decision
What will you test?
Add one relevant next-project path, clarify the project's role and contribution, or move the strongest trust cue closer to the work.
Do not overclaim
A visit is not approval. A scroll is not comprehension. A contact click is not a job offer. Each is one piece of evidence in a larger decision.
Collect less, explain it clearly, and respect consent
Do not send personally identifiable information in event names, parameters, or page URLs. Review what enhanced measurement collects, how your forms and embedded tools behave, and whether analytics should run before or after consent in the places where your portfolio is available.
Privacy requirements vary by location and how data is used. Treat your privacy notice, consent implementation, data retention, and vendor configuration as current operational work—not a paragraph copied from a generic guide.
Use a 20-minute monthly review
Check collection health
Did traffic and events arrive, and did a site change break any paths?
Compare relevant sources and landing pages
Notice changes, but avoid conclusions from a tiny sample or a single unusual referral.
Follow one journey
Connect arrival, project selection, supporting pages, and the strongest meaningful action available.
Write one decision
Keep, investigate, or test one change. If the evidence is too thin, record that instead of inventing certainty.
Sources and current setup references
QuestionsAnswers
Questions, answered.
A few practical details before you keep going
Share this resource
Written by
Nikki KippleProduct Designer & Design Instructor
Designer, educator, founder of The Crit. I've spent years teaching interaction design and reviewing hundreds of student portfolios. Good feedback shouldn't require being enrolled in my class — so I built a tool that gives it to everyone. Connect on LinkedIn →
Analytics can show the path. A critique can inspect the experience.
Share the portfolio and what the data made you wonder about. We will examine the visible evidence and identify one useful next move.