Skip to content

Services › Impact and evolution › Measurement and web analytics

Measurement and web analytics

We set up measurement for catalog and documentation sites around real questions: product page views, site searches, downloads, forms, paths, and events that help decide what to do next.

Installing a tool is one part of analytics. The work also defines what each event means, how it's compared, and which parts of user behavior can be observed with the available data.

How many times was the surgical technique guide downloaded this month?

Measurement starts with what each team needs to know.

Measurement plan

We define questions, events, and criteria before setting up tools so measurement focuses on what matters rather than visits alone.

Events

We set up actions with names and parameters that distinguish product pages, documents, courses, forms, and other content.

Tools

We work with Google Analytics 4, Search Console, and Tag Manager, reviewing what already exists first.

GA4GSCGTM

Conversions

The company defines which actions count as progress and we measure them, without attributing sales to the site unless there's data to back it up.

Dashboards

We organize views so each team can follow the questions that matter to it without wading through dozens of irrelevant metrics.

Reports

A periodic review that shows what changed, what deserves attention, and what's worth testing next.

How it works

Before setting up an event, write down the question.

See the method
  1. Questions

    We identify what Management, Marketing, Product, Education, and other teams need to know.

  2. Measurement model

    We link each question to the events, dimensions, sources, and comparison windows available.

  3. Setup

    We implement and test the measurement on the real site.

    We check that events have the agreed meaning, rather than simply checking that they “fire.”

  4. Interpretation

    The first review helps catch setup errors and start building a baseline for future decisions.

Work · SAI

1,396 people downloaded technical documentation in 39 days.

After SAI's new site launched, 8,153 documentation download events by 1,396 people were recorded during the first 39 days analyzed.

FAQ

How can the company measure whether its new site is working properly?

With two equal time windows, before and after launch, and usage data: product page visits, downloads, searches with no results, and catalog response time.

What should count as a conversion on a medical device website?

Whatever the company defines as real progress. It usually includes a contact request, downloading a surgical technique guide or an IFU, and signing up for a course. It's decided before measurement is set up.

Can the website's return be measured in terms of sales?

What happens on the site can be measured and, if the company records it, where each inquiry came from. What happens afterward depends on many people and long cycles, and we don't attribute it to the site without data to back it up.

What happens to the data of someone who fills out a form?

Forms include a privacy notice and a consent checkbox. What each country requires and how that data is stored is defined by the company's legal team; we implement it on the site.

Do we need to switch analytics tools?

First, we review what's already installed. Properly configured Google Analytics 4 and Search Console are usually enough for a catalog site; another tool is added when there's a question those two can't answer.

Start with a question the current report doesn't answer.