You know what the site does
Events defined by meaning — attempts against completed actions — show which pages produce enquiries and which only produce visits.
Measure school website actions without collecting student details.
We define events for programme interest, open-day requests and practical website use. Clicks, submitted enquiries and confirmed applications remain distinct, and event properties exclude private form contents and unnecessary personal information.
A few clients we’ve worked with
What we do
Analytics setup for schools: Event definitions, Tracking configuration, Payload verification.
Decisions that shape the work.
Which events can the website actually observe?
Which fields must stay out of measurement payloads?
What you cannot decide without measurement.
Page views alone do not explain which actions the website supports. Without that, every decision about the site is an argument about taste.
Spend has a feedback loop
When a conversion can be verified, campaign and content decisions can be made against outcomes instead of impressions.
The numbers agree
Documenting which system can verify each conversion stops two dashboards reporting two different truths.
Analytics setup: scope of work.
The brief records the website scope, approved source material and responsibilities for review.
Event definitions
Specify actions and the evidence required for completion signals.
Tracking configuration
Implement approved tools and consent behavior with limited event fields.
Payload verification
Inspect emitted data, duplicates and provider limitations.
What clients say.
Reviews from the companies we have built and maintained websites for.
Read every review on Clutch“We didn’t choose them to be impressed — we chose them because we knew they’d deliver high-level results with no risk. As a CTO myself, that’s exactly what I look for in a long-term partnership.”
“And, you know, the great part about the fact that you hit the goal, it's not that you had to compromise anything that you were doing, because, honestly, the end result far exceeded what we could have imagined.”
“I would just say that you deliver on quality … I just thought we clicked, and you delivered what we were looking for.”
“Norml Studio's professionalism and responsiveness were impressive.”
What you receive.
The agreed engagement produces the following artifacts.
- 01
An event and permitted-property plan.
- 02
Configured agreed tracking.
- 03
Verification examples and reporting limits.
Our process
How the work runs.
Define the questions
Agree useful measurements with admissions and website owners.
[ 01 ]
Configure bounded events
Implement approved fields without student or enquiry text.
[ 02 ]
Inspect actual output
Test events and document what external systems do not expose.
[ 03 ]The people who do this work.
No account layer between you and them. These are the Norml specialists this work runs through.
Max Tymoshyn
Founder & Architect
Iryna Melnyk
Full-Cycle SEO Specialist
Artur Tsitou
DevOps & Backend Developer
Let's chat
“I've spent 10 years working across development and marketing. I started as a developer, but design, SEO and advertising were already part of the job. That taught me to treat a website as one system: the business, the content, the design and the code have to work together. At Norml, I lead the architecture behind our work and stay involved wherever strategy, design, development and search meet.”
Max TymoshynFounder & Architect
Get startedAnalytics setup for schools: questions.
Does an application-link click count as an application?
No. A click only records that action; a confirmed application needs an authorized completion source.
Will analytics include student names?
No. The proposed event plan excludes student identities and private submission content.
Website 2.0 combines strategy, design, development and launch in one engagement.