Lesson Objective
To introduce a basic understanding of user-level analysis and initial segmentation, within a responsible privacy framework.

From aggregated data to the user

When a newsroom works only with aggregated data, it usually sees the overall performance of content but does not always understand who is behind that behavior. It knows how many visits an article received, but it cannot clearly distinguish whether that traffic came from regular users, new readers, people arriving from search engines, or an already loyal audience.

Thinking in terms of individual users does not mean monitoring specific people. It means recognizing that behind aggregated volume there are different behavioral profiles, and that these profiles may have different needs, journeys, and value for the media organization.

This perspective is useful because it allows more precise questions to be asked:
Which type of reader returns more frequently?
Which segment consumes more pieces within a single session?
Which users are more likely to register?
What type of experience works better on mobile?

Basic segmentation

At this first level of maturity, it is not necessary to work with complex segmentations. It is enough to understand some basic and useful categories.

A first segmentation can be done by geographic location. Not to identify specific individuals, but to detect differences in consumption between territories or areas of interest.

Another basic segmentation is device type: mobile, desktop, tablet. This variable is very relevant because reader behavior changes significantly depending on the context of use.

Segmentation can also be done by language, when the media outlet publishes in more than one language or receives traffic from different linguistic areas.

Finally, a segmentation by basic behavior is very useful: new users vs. returning users, readers with low consumption vs. heavy readers, visitors who only read one page vs. those who circulate through several pieces.

These segmentations do not exhaust the analysis, but they already allow a move from a generic view to a somewhat more detailed understanding of the audience.

Why segmentation is useful

Segmentation helps avoid decisions based on misleading averages.

A global average may hide the fact that a piece performs very well on mobile but poorly on desktop, that a newsletter performs well with loyal users but not with new readers, or that an article attracts a lot of search traffic but generates little recurrence.

Segmentation helps detect these differences. And above all, it helps understand that the audience is not homogeneous.

In editorial work, this idea has many applications: prioritizing formats, making distribution decisions, improving headlines, adapting pieces to different reading contexts, or identifying opportunities for loyalty.

Privacy, consent, and responsible use

Working with user data requires a minimum understanding of privacy and consent. It is not necessary to turn the newsroom into a legal expert, but some basic principles should be incorporated.

The first is minimization: no more information should be collected than necessary.

The second is purpose limitation: data must be used for clear and legitimate objectives.

The third is consent, when processing requires it. In European environments, this point is especially relevant and cannot be treated as a purely technical formality unrelated to editorial work.

The fourth is proportionality: not everything that is technically possible is editorially or ethically desirable.

In a course like this, the important thing is for the student to understand that useful analytics and responsible privacy are not incompatible ideas. On the contrary, a mature data culture requires clear rules in order to be sustainable.

Try it yourself

Your analytics dashboard shows the following for a recent long-form investigation:

Overall
22,000 users · Avg. reading time: 3:20 · Scroll depth: 52% · 18 subscriptions started

You then apply a basic segment by device:

Desktop users (8,400 users)
Avg. reading time: 6:45 · Scroll depth: 81% · 16 subscriptions started

Mobile users (13,600 users)
Avg. reading time: 1:10 · Scroll depth: 29% · 2 subscriptions started

Consider:

  1. The overall numbers looked acceptable. What does segmentation reveal that the aggregate hid?
  2. Where is the piece working — and where isn’t it? What might explain the difference?
  3. What is one editorial or technical decision you might propose based on this data?
  4. Which segment would you want to explore next? (Hint: think about where users came from, not just what device they used.)

Averages describe the middle. Segments tell you what the middle is actually made of.

Lesson Conslusion
Understanding the audience does not consist simply of adding up visits. It means recognizing that different types of users behave differently and that these differences can and should be interpreted within a framework that respects privacy.