Skip to content

Briefing · 21 October 2026

Tracking pixels after IMY’s fines: what went wrong and what to check

In 2024 the Swedish Authority for Privacy Protection (IMY) fined Avanza, Apoteket and Apohem a combined SEK 60 million after the Meta pixel sent customer data to Meta. The decisions show what is expected of anyone running marketing tools on their website.

By Europe Cyber-Safe · Published · Reviewed

A tracking pixel is a small piece of code from an advertising platform that sends information about visitors’ behaviour – and sometimes much more – back to that platform. IMY’s three decisions from 2024 all concern the Meta pixel, but the lessons apply to any similar tool.

Three decisions, one pattern

  • Avanza Bank (decision of 24 June 2024, SEK 15 million). Between November 2019 and June 2021, data on an estimated 500,000–1,000,000 people was transferred, including personal identity numbers, account numbers with credit limits, securities holdings and loan amounts – some of it in clear text. IMY found breaches of Article 5(1)(f) and Article 32(1) of the GDPR.
  • Apoteket (decision of 29 August 2024, SEK 37 million). Between January 2020 and April 2022, data on purchases in 17 sensitive product categories – such as pregnancy tests, contraceptives and products for sexually transmitted infections – was sent, along with hashed contact details. According to the company, up to around 930,000 people were affected. Breach of Article 32(1).
  • Apohem (decision of 29 August 2024, SEK 8 million). Between April 2021 and April 2022, purchase data and hashed contact details on around 15,000 people were transferred, including from pages on sexual health, contraception and diabetes. Breach of Article 32(1).

What went wrong

The decisions point to the same shortcomings in all three cases:

  • Features switched on without a risk assessment. The pixel’s Automatic Advanced Matching feature – and at Avanza also Automatic Events – was activated without the companies’ own procedures being followed. In two of the cases the company could not establish afterwards who had activated the feature or when.
  • No check on what was actually sent. There were no technical limits on the data transferred, and nobody regularly checked what the pixel was collecting.
  • Reliance on the recipient’s filter. The companies relied on Meta’s filtering mechanism, but IMY found that it only operates after the data has already been transferred.
  • Discovered from outside. In every case the problem was flagged by an external source, and the transfers stopped only after that.

Hashing the data did not prevent a fine, although IMY took it into account when assessing the seriousness of the infringement. Note too that Apoteket only sent purchase data for visitors who had accepted marketing cookies. Cookie consent, in other words, did not answer the question of security of processing.

The cookie rule in the Swedish Electronic Communications Act

Alongside the GDPR sits the cookie rule in Chapter 9, Section 28 of the Swedish Electronic Communications Act (lagen (2022:482) om elektronisk kommunikation, LEK), which implements the ePrivacy Directive. It requires consent to store or access information on a user’s terminal equipment, with exceptions including storage that is strictly necessary to provide a service the user has explicitly requested. The Swedish Post and Telecom Authority (PTS) supervises that rule.

In the Avanza and Apoteket decisions IMY considered whether the cookie rule applied, but concluded that it did not in those particular cases, because the data came from information that users had entered themselves rather than from storing or reading data on their devices. The GDPR therefore applied and IMY was the competent authority. The takeaway: these are two separate regimes. You need both valid consent for non-essential cookies and secure processing of the personal data your tools handle.

What to check on your own website

  1. Inventory. List every pixel, tag and script – including those added through a tag manager – and who has permission to change them.
  2. Review the settings. Are features such as Automatic Advanced Matching or Automatic Events switched on? Are they needed for your purpose?
  3. Limit where tools run. Consider removing pixels from logged-in pages, checkout flows and pages about sensitive products or services.
  4. Consent before firing. Check that no non-essential cookies or scripts load before the visitor has consented, and that a refusal is respected.
  5. Review server-side tracking. Sending data from your server rather than the browser moves the data flow, not the responsibility. Check which fields are actually sent.
  6. Minimise. Send only the data needed for the purpose, and avoid identifiers such as personal identity numbers, email addresses and account numbers.
  7. Clarify roles and contracts. Document the allocation of roles and the contract terms that apply with each tool provider, including any transfers to third countries.
  8. Control changes and test. Require a risk assessment before new tags or changed settings, log the changes, and regularly test what actually leaves your website.

Get the EU Rules Radar

One short email, about once a month, on what changed in EU cyber, AI and data protection rules.

    See what your website actually sends

    Tell us which website you want checked. We reply within two working days.