Website analytics without analytics cookies
MOJAQ records pageviews and custom events with a cookieless approach, then connects traffic to deploy, error and uptime context inside one EU-hosted developer suite.
EU-hosted in Helsinki · GDPR-native · DPA included · free during the private beta
What a cookieless setup changes
| Design question | MOJAQ approach | Implementation note |
|---|---|---|
| Analytics cookies | No analytics cookies | Audit other scripts separately |
| Core measurement | Pageviews and custom events | Choose a minimal event set |
| Persistent profiles | Not the product goal | Do not add identifiers as event data |
| Hosting | Helsinki, Finland | DPA included |
| Operational context | Errors, uptime and deploys in one suite | Grant access by job need |
| Browser performance | RUM with Core Web Vitals in beta | Validate beta fit before relying on it |
| Current access | Free during the private beta | Paid plans announced in advance |
Cookieless describes a mechanism, not a magic label
Traditional analytics often relies on a browser cookie to recognise a returning device across requests. Cookieless analytics removes that analytics-cookie dependency. For many teams, that is a sensible reduction in browser state and tracking surface, especially when the real goal is to understand page demand and a handful of product actions rather than build advertising profiles.
The boundary matters. A cookieless analytics script does not remove cookies set by authentication, embedded media, chat, experiments or advertising tags. It also does not turn careless custom events into anonymous data. Audit the full page and decide what each technology does instead of using the word cookieless as a description of the entire site.
Measure decisions, not everything available
Start with pageviews and add a custom event only when someone can name the decision it supports. A documentation team might need a completed-example event; a product team might need a registration milestone. Neither automatically needs the visitor's email address, free-text input or a complete copy of the URL query string.
MOJAQ provides cookieless pageviews and custom events. Keep event names stable, property lists short and dynamic paths under review. This makes dashboards easier to interpret and reduces the chance of collecting personal values accidentally. It also gives engineering and privacy reviewers a small, readable measurement contract instead of an undocumented stream.
Traffic makes more sense beside product health
A sudden fall in pageviews can come from seasonality, a broken release or an unavailable route. An analytics-only view cannot distinguish those causes. MOJAQ places web measurement beside error tracking, uptime monitoring, logs and deploy tracking, with a shared timeline for the signals around a change.
That integration is particularly useful for a small team because it does not require a separate data project. One account, one API key and one dashboard cover the suite. RUM is also available in beta with Core Web Vitals, adding browser experience where appropriate. Teams that require mature RUM workflows should validate the beta rather than assuming it is production-equivalent to a specialised performance product.
EU hosting is part of privacy-first design
MOJAQ hosts service data in Helsinki and includes a GDPR DPA. Pageview data may be deliberately sparse, but residency and processor terms are still legitimate procurement questions. Applying the same Helsinki model to analytics, errors, uptime and logs also avoids scattering operational data across several regional arrangements.
Privacy-first is an ongoing practice. Describe analytics accurately in your notice, limit dashboard access, review new custom events and examine other vendors on the page. Whether a particular implementation requires consent or another lawful basis is a legal and factual assessment for your organisation; cookieless design is useful input to that assessment, not a universal answer.
How to adopt cookieless analytics
List the metrics people actually use, then translate them into pageviews and the smallest practical set of custom events. Check page paths and event properties for direct identifiers, free text and sensitive query values. Install MOJAQ in a test environment, verify that expected navigation is visible, and document the event contract. During a parallel run, expect counts to differ from a cookie-based tool because the measurement models are different; mark the cutover date rather than splicing unlike visitor metrics into one trend.
Questions
Does MOJAQ set analytics cookies?
No. MOJAQ web analytics is cookieless and measures pageviews and custom events without analytics cookies.
Will cookieless analytics match my old visitor counts?
Not necessarily. Cookie-based and cookieless systems can define visitors, repeat activity and bot handling differently. Compare whether the measurements support your decisions and record the cutover date.
Can I send custom events without identifying users?
Yes. Keep properties limited to the decision the event supports, and do not include email addresses, form contents, secrets or other direct identifiers.
Is cookieless analytics automatically exempt from consent?
MOJAQ does not make that legal claim. Requirements depend on your implementation, purpose and jurisdiction. Cookieless design reduces tracking surface, while your organisation remains responsible for its assessment and transparency.
Measure the site without analytics cookies
Start with focused pageviews and events, hosted in Helsinki and connected to the developer signals that explain change.
Request beta access →