christian baumgertel

Transparency

How I measure
this website

No cookies, no banner, no third parties. I still see which content leads to enquiries. Since this is exactly what I advise clients on, I show openly how it works.

The path of an event

Three stops, all under my control.

  1. In the browser

    What is sent?

    A few lines in main.js, no library. They send an event via sendBeacon to /api/collect, on the same domain.

  2. On my server

    What is checked?

    A cloud function in Frankfurt only accepts known events and fields, drops everything else and stores neither IP address nor user agent.

  3. In BigQuery

    What do I analyse?

    A log sink writes the events to BigQuery, where I analyse them with SQL. They are deleted after 14 months.

An event as it arrives

This is what a page view looks like when it reaches the server.

{
  "event": "page_view",
  "path": "/en/",
  "lang": "en",
  "ref": "www.linkedin.com",
  "utm_source": "linkedin"
}

That is all. No ID, nothing that links two page views.

What is measured

A few events, each with a clear purpose.

  • Page views with path, language and the domain you came from
  • Campaign parameters (utm_…) from the link, e.g. from LinkedIn or an ad
  • Clicks on contact options: booking, email, phone, form
  • Form started and, confirmed on the server, message delivered
  • Opened FAQ questions

What is not measured

  • No cookies and nothing in local storage
  • No identifiers, no fingerprinting, no recognition across visits
  • No IP address and no user agent in the stored data
  • No third parties: no Google Analytics, no pixel, nothing shared with ad platforms
  • No measurement if you object: Global Privacy Control or Do Not Track stops everything

What I can see, and what not

For a website of this size, that is enough.

Which pages and sources lead to enquiries. An enquiry only counts once the function has actually delivered the email. That is a server-side conversion, not a button click.

What visitors are interested in: which contact options get used and which FAQ questions get opened.

Not: how many different people visit. Without an identifier there are only page views, no users, and no customer journey across visits.

And for your website?

For shops using ad platforms this alone is not enough. They need consent and usually server-side tracking. The principle stays the same: as little data as necessary, controlled in one place.

The legal details are in the privacy notice.