One professional league, many platforms.
One measurement standard.
We work as the external analytics team for a major European professional sports league: website, new app, fantasy game and a whole network of further domains. Matomo and Amplitude run in parallel, cookie-based and cookieless, under a consent banner and a subscription model. A weekly check-in, and in between tickets, tracking concepts, tests and analyses.
Millions of fans, many workstreams at once.
A league is not a single shop. There is the big website with live ticker, tables and articles, an app that is currently being rebuilt, a fantasy game, B2B and media portals, campaign and foundation sites. Each platform has its own development team, often external agencies.
On top of that come strict requirements: a consent banner with its own opt-in rates, a subscription model for reading without ads and tracking, and the question of which data may be collected at all without consent. Our job: making sure everyone ends up working with the same reliable figures.
What is measured depends on the visitor.
Choose how a visitor decides. We made sure that in every case only what is permitted runs, while clean reach figures still remain.
The full picture, cleanly controlled.
The tag manager loads, Amplitude measures web and app with a user ID, Matomo counts the reach. Marketing tags only run according to the consent category.
No cookies, but still reach.
No tag manager, no marketing tags. Matomo keeps running, built in and cookieless, and provides anonymous reach figures. The legal department is checking whether Amplitude may measure in anonymised form.
Those who pay are not tracked.
With the subscription, fans read without ad tracking. The tag manager stays off. To keep the reach figures accurate, we decoupled Matomo from the tag manager and built it directly into the pages.
Simplified view. Which variant runs on which domain was agreed for each platform with the league's data protection team.
From the tracking concept to the management KPI.
A selection of tickets from recent months. Click through the workstreams.
Tracking for the new app
Tracking structure for the new React Native app, events in the tracking plan, tests on dev, acceptance and go-live.
Onboarding & registration
First analysis after the launch: where new users drop off, including noticeable errors during registration.
New users & retention
How many new users stay, comparing the old and new app version, also in the fantasy game.
Connecting the app and web views
Tracking concept so that user journeys between the app and embedded web pages do not break.
Web-to-app click rate
A management KPI: all entry points from the website into the app captured and made measurable, including an A/B test for live ticker votes.
Promo banners
Impressions and clicks of the app banners, new placements in the tracking concept and analysis of their impact.
New features
Tracking concepts for line-ups, match bar, tables, partner shops and article summaries.
Video advertising
Viewability metrics for ad videos, also prepared for programmatic video ads.
Opt-in rates
Analysis of consent rates in the consent banner and clarification of discrepancies together with the provider's support.
Cookieless tracking
Requirements for cookieless Matomo, test of the cookieless mode in Amplitude and experience from other projects.
Contentpass
Technical documentation for the developers, tests of several implementations, approval and data quality check after the release.
Cookie check
Inventory of all cookies set, including those of monitoring tools, as a basis for data protection.
Matomo migration
From Matomo via the tag manager to built-in, cookieless Matomo, domain by domain with each development team.
Separate properties
Separate Matomo properties for subdomains and campaign pages, so that every site has clean figures.
Tag manager clean-up
Plan and implementation of a leaner container structure, agreed with the development team.
Avo Inspector
Guide and rollout: events and values are automatically checked against the tracking plan.
Matomo vs. Amplitude
The key KPIs of both tools compared, discrepancies explained and checked again at the start of the season.
Campaigns & votes
Analysis of voting campaigns and marketing attribution.
Licensing partner report
Analysis of licensed partners' products, as the basis for a management presentation.
Session replay
Tested on dev, approved and set up for the website and apps.
AI agents in Amplitude
Research into what the new AI agents can do and how the league can use them sensibly.
A/B tests
Preparing for experiments with Amplitude Experiment.
From the design to clean data.
A deployment breaks the tracking.
After a website release, data was suddenly missing. We narrowed down the cause with the developers, tested the fix and prepared the reports so that the gap is clearly marked instead of distorting the figures.
New group domains in a few days.
When the league moved its corporate sites to new domains, we set up the consent banner and Matomo for both domains and checked all events and parameters after the migration.
Services and tools used in this project.
For reasons of confidentiality, we do not name the league and do not show any user or reach figures.
