EuropeDigital Markets Act

Digital Markets Act (DMA): gatekeeper rules and consent

The Digital Markets Act sets obligations for the largest digital platforms, which the European Commission designates as gatekeepers. It is not a cookie law, and its consent rules bind gatekeepers rather than website owners. Most websites are not directly regulated by the DMA. They may still encounter DMA-driven changes in gatekeeper services they use, including consent and data-sharing controls in products such as Google advertising tools.

Regulation (EU) 2022/1925DMAEuropean UnionDigital Markets Act
Applies to
Designated gatekeepers
Enforced by
European Commission
Consent standard
As defined in the GDPR
Standard maximum fine
10% of worldwide turnover
Applies since
2 May 2023
Last updated
November 5, 2026
Overview

The DMA at a glance.

Who the regulation covers, what it regulates and where consent comes into it.

  • Who it applies to

    Only gatekeepers designated by the European Commission

    A company is designated when a core platform service it provides is an important gateway for businesses to reach end users in the EU. The DMA applies to those services wherever the gatekeeper is established. Most website operators, online shops and apps are not gatekeepers. The DMA’s gatekeeper obligations apply only to undertakings designated by the European Commission for specific core platform services.

  • Core platform services

    Ten categories of service

    Online intermediation services such as app stores and marketplaces, online search engines, online social networks, video-sharing platforms, number-independent messaging services, operating systems, web browsers, virtual assistants, cloud computing services and online advertising services.

  • Presumed gatekeepers

    €7.5bn turnover or €75bn market value, plus user thresholds

    The presumption applies where a company has EU turnover of at least €7.5 billion in each of the last three financial years, or an average market capitalisation of at least €75 billion in the last one, provides the same service in at least three Member States, and that service had at least 45 million monthly active end users and 10,000 yearly active business users in the EU in each of the last three years. Meeting the thresholds creates a presumption, not an automatic designation: the company must notify the Commission, which decides whether to designate it. The Commission can also designate a company that does not meet these thresholds.

  • Designated gatekeepers

    Seven gatekeepers, 23 core platform services

    Alphabet, Amazon, Apple, Booking, ByteDance, Meta and Microsoft, according to the Commission’s list in October 2026. The Commission reviews each designation at least every three years.

  • Where consent comes in

    GDPR consent before a gatekeeper combines personal data

    Article 5(2) bars gatekeepers from combining or cross-using personal data across their services, signing users in to combine data, or processing for advertising the personal data of people using third-party sites and apps that rely on the gatekeeper’s services, unless the user was given the specific choice and consented as defined in the GDPR.

  • Who enforces it

    The European Commission

    The Commission designates gatekeepers, monitors their compliance and decides on fines. This differs from the GDPR, which national data protection authorities enforce.

Timeline

How the DMA took effect.

The regulation applies in stages: first the rules, then a designation decision for each gatekeeper, then six months for that gatekeeper to comply.

  1. 1

    In force

    Regulation (EU) 2022/1925, published on 12 October 2022, entered into force on 1 November 2022.

    1 Nov 2022
  2. 2

    Applicable

    The rules applied from 2 May 2023. Companies meeting the thresholds had two months to notify the Commission.

    2 May 2023
  3. 3

    First gatekeepers

    Alphabet, Amazon, Apple, ByteDance, Meta and Microsoft were designated for 22 core platform services.

    6 Sep 2023
  4. 4

    Obligations bind

    Six months after designation, the obligations became legally binding on the first gatekeepers.

    Mar 2024
  5. 5

    First fines

    The Commission fined Apple €500 million and Meta €200 million in its first non-compliance decisions.

    23 Apr 2025
  6. 6

    Google fined

    Google was fined €890 million in total for self-preferencing in Google Search and steering restrictions on Google Play.

    23 Jul 2026
Obligations

What gatekeepers must do.

Articles 5, 6 and 7 list the obligations, and Article 13 stops gatekeepers from getting around them. These are the ones that concern personal data, consent and the businesses and people using gatekeeper services. They bind designated gatekeepers, not the websites that use their services.

  • Ask before combining personal data

    No processing of third-party data for advertising, no combining or cross-using of personal data across services and no signing users in to combine data, unless the user was presented with the specific choice and gave consent as defined in the GDPR.

    Art. 5(2)
  • Ask again no more than once a year

    If a user refuses or withdraws that consent, the gatekeeper may not repeat the request for the same purpose more than once within a year.

    Art. 5(2)
  • Offer a less personalised alternative

    Users who do not consent should get a less personalised but equivalent service, and use of the service should not depend on consent. Not giving consent should be no harder than giving it.

    Recitals 36–37
  • Keep the choice neutral

    Gatekeepers must not degrade their service for users who exercise their DMA rights or choices, or make those choices difficult through non-neutral options or interface design.

    Art. 13(6)
  • Let business users collect consent

    Where consent is needed to comply with the DMA, the gatekeeper must let business users obtain the consent required under the GDPR or the ePrivacy Directive directly, or meet data protection rules another way, such as anonymised data. It may not make obtaining that consent harder than for its own services.

    Art. 13(5)
  • Give business users their data

    Free, continuous and real-time access to the data generated through their products on the platform. Personal data is shared only where it is directly connected to that use and the end user opts in by consenting.

    Art. 6(10)
  • Give advertisers and publishers transparency

    On request and free of charge, daily information on prices, fees and publisher remuneration, plus access to the gatekeeper’s performance measuring tools and the data needed to verify ad inventory independently.

    Art. 5(9)–(10), 6(8)
  • Let users choose and switch

    Users must be able to uninstall apps, change defaults, pick a search engine, browser or virtual assistant from a choice screen, install third-party apps and app stores, and switch between services.

    Art. 6(3)–(4), 6(6)
  • Make data portable

    End users, and third parties they authorise, can port the data they provide or generate on the service, free of charge, including continuous and real-time access.

    Art. 6(9)
  • Treat business users fairly

    No ranking the gatekeeper’s own products above similar third-party ones, and business users stay free to promote offers to customers and conclude contracts with them outside the platform, free of charge.

    Art. 5(4), 6(5)
  • Audit consumer profiling

    Within six months of designation, an independently audited description of the gatekeeper’s consumer profiling techniques goes to the Commission, which passes it to the European Data Protection Board. A public overview is updated at least once a year.

    Art. 15
Enforcement and penalties

The Commission enforces the DMA directly.

The European Commission is the DMA’s enforcer. It designates gatekeepers, opens non-compliance proceedings and decides on fines. National authorities may not take decisions that run counter to the Commission’s, and anyone, including business users, competitors and end users, can report a gatekeeper’s practices to the Commission or to a national competition authority.

Non-compliance
10%
Up to 10% of total worldwide turnover in the preceding financial year (Article 30(1)).
Repeat infringement
20%
Up to 20% for the same or a similar infringement on the same core platform service within eight years (Article 30(2)).
Periodic penalty payments
5% a day
Up to 5% of average daily worldwide turnover per day, to compel compliance with a decision (Article 31).
Systematic non-compliance
Remedies
After at least three non-compliance decisions in eight years, a market investigation can lead to behavioural or structural remedies, including a temporary ban on acquisitions (Article 18).

Procedural breaches, such as supplying incorrect information or failing to notify, can be fined up to 1% of total worldwide turnover (Article 30(3)). The Court of Justice can cancel, reduce or increase any fine (Article 45).

Decisions so far

In April 2025 the Commission fined Apple €500 million over App Store anti-steering rules, and Meta €200 million because its “consent or pay” model gave Facebook and Instagram users no equivalent option that uses less of their personal data; that decision covers March to November 2024. In December 2025 the Commission acknowledged Meta’s undertaking to offer EU users a less personalised ads option from January 2026. In July 2026 it fined Google €460 million for self-preferencing in Google Search and €430 million for steering restrictions on Google Play.

How CookieHub helps

Consent signals for gatekeeper tools.

CookieHub does not make a website “DMA compliant”: the DMA’s obligations fall on gatekeepers. Where it meets your site is consent. The choices your visitors make need to reach the gatekeeper tools you use, such as Google’s advertising and measurement products. Consent Mode v2 is Google’s mechanism for receiving these consent signals; the DMA itself does not require ordinary websites to implement Consent Mode v2.

  • Regional settings can apply explicit opt-in behaviour for visitors in the EU and EEA.
  • Supported or configured consent-dependent scripts and advertising tags can be held back until the visitor decides.
  • Visitor choices can be sent to Google tags through Consent Mode v2, including ad_user_data and ad_personalization.
  • When consent records are enabled, consent decisions can be recorded with the visitor token, timestamp and category choices.
See how consent management works
Google consent signalscookiehub.com · example
  1. Visitor / regionEEA visitor detectedregion: euEuropean Union / EEAGeo-detected
  2. Consent defaultsDefaults applied before a choiceconsent defaultad_storageDeniedad_user_dataDeniedad_personalizationDenied
  3. Consent updateVisitor choice sent to Googleconsent updateanalytics_storageGrantedad_user_dataDeniedad_personalizationDenied
For websites

What the DMA means for your website.

Most website owners are not gatekeepers, so the DMA gives them no gatekeeper obligations. What matters is meeting GDPR and ePrivacy rules, and passing consent to the gatekeeper tools they use as those tools’ own policies require.

  1. 01

    Check your role

    Work out whether the DMA applies to you directly.

    1. 01Check the Commission’s list: the DMA applies directly only to designated gatekeepers, for the core platform services listed in their designation.
    2. 02If you advertise, publish ads, sell or distribute apps through a gatekeeper, you are a business user. As a business user, the DMA primarily gives you rights in relation to the gatekeeper, such as data access and advertising transparency; it does not make you a gatekeeper.
  2. 02

    Collect consent

    Your own consent obligations come from the GDPR and national ePrivacy rules.

    1. 03Obtain consent before using cookies or trackers that require it under applicable ePrivacy rules, and keep consent-dependent tags blocked until the visitor decides.
    2. 04Give visitors a clear way to refuse, and let them withdraw consent as easily as they gave it.
  3. 03

    Pass consent on

    Make sure gatekeeper tools receive the choices your visitors made, as their own policies require.

    1. 05Google’s EU user consent policy requires consent from users in the EEA, the UK and Switzerland for ads personalisation, and records of that consent.
    2. 06Send visitor choices to Google through Consent Mode v2. For consent-based ad personalisation, ensure that ad_user_data and ad_personalization reflect the visitor’s choices, alongside other applicable Google consent requirements.
    3. 07Check that the signals arrive, and check again when you add or change advertising tools.
    ongoingReview when your tools change
FAQ

Digital Markets Act questions.

The DMA applies to core platform services that designated gatekeepers provide to business users established in the EU or to end users established or located in the EU, wherever the gatekeeper itself is based. Its purpose is to keep digital markets where gatekeepers are present contestable and fair. Markets for electronic communications networks and services, other than number-independent messaging services, are excluded.

A company the European Commission has designated because it has a significant impact on the internal market, provides a core platform service that is an important gateway for business users to reach end users, and enjoys an entrenched and durable position, or foreseeably will. Meeting the turnover and user thresholds in Article 3(2) creates a presumption that these conditions are met. The Commission can also designate a company that does not meet the thresholds after a market investigation.

In October 2026 the Commission’s list names seven gatekeepers: Alphabet, Amazon, Apple, Booking, ByteDance, Meta and Microsoft, for 23 core platform services in total. Amazon and Microsoft are already gatekeepers for other services, but their cloud services are not designated: on 25 June 2026 the Commission issued a preliminary view that AWS and Azure should be designated under the DMA. That is not a final designation, and neither service is on the Commission’s current list of designated services.

Not as a regulated party, unless your company has been designated as a gatekeeper. If you use gatekeeper services as an advertiser, publisher, seller or app developer, the DMA gives you rights against the gatekeeper, such as access to data and advertising information. Your own obligations around cookies and consent come from the GDPR and the ePrivacy rules.

No. The DMA does not regulate cookies on ordinary websites. Cookie consent on your site comes from the ePrivacy Directive, as implemented in national law, with the GDPR setting the standard that consent has to meet. The DMA’s consent rule in Article 5(2) applies to gatekeepers combining or cross-using personal data.

It uses the GDPR definition of consent. A gatekeeper may only combine or cross-use personal data across services, sign users in to combine data, or process third-party data for advertising if the user was presented with the specific choice and consented. If the user refuses or withdraws consent, the gatekeeper may not ask again for the same purpose more than once a year. The recitals add that users who refuse should get a less personalised but equivalent alternative.

Google’s EU user consent policy requires sites using its products to obtain consent from users in the EEA, the UK and Switzerland for ads personalisation and, where the law requires it, for cookies. Google states that, as a result of the DMA, it introduced new consent choices for EEA users from March 2024, and that advertisers can choose which Google services may receive the data their visitors consent to share. Consent Mode v2 carries visitor choices to Google through signals such as ad_user_data and ad_personalization. Consent Mode v2 is Google’s mechanism for receiving these consent signals; the DMA itself does not require ordinary websites to implement Consent Mode v2.

The DMA uses the GDPR definition: any information relating to an identified or identifiable natural person, for example through a name, an identification number, location data or an online identifier.

No. The DMA has no separate category of sensitive data. Special categories of personal data are defined in Article 9 of the GDPR: data revealing racial or ethnic origin, political opinions, religious or philosophical beliefs or trade union membership, genetic data, biometric data used to identify a person, health data, and data about a person’s sex life or sexual orientation.

The European Commission. It designates gatekeepers, monitors compliance, runs market investigations and can impose fines and periodic penalty payments. National competition authorities can receive information about gatekeeper practices and pass it to the Commission, but national authorities may not take decisions that run counter to the Commission’s.

The obligations in Articles 5, 6 and 7 apply to companies designated as gatekeepers, and only in relation to the core platform services listed in their designation decisions. Companies and services that have not been designated are not subject to those gatekeeper obligations.

Depending on the designated core platform service, the DMA gives end users greater choice and control: consent before certain cross-service data combination, a less personalised alternative where Article 5(2) applies and they refuse, uninstalling apps and changing defaults, choice screens, free data portability including real-time access, and the freedom to raise non-compliance with public authorities. End users can report gatekeeper practices to the Commission, and consumers’ collective interests can be defended through representative actions.

The DMA applies without prejudice to the GDPR and the ePrivacy Directive, so gatekeepers must meet those rules as well. It uses the GDPR’s definitions of personal data, profiling and consent. The Commission describes the Digital Services Act as complemented by the DMA, which adds rules specifically for gatekeeper platforms.

The regulation is published on EUR-Lex as Regulation (EU) 2022/1925. The European Commission’s DMA website lists the designated gatekeepers, decisions and news. Both are linked in the sources section above.

Legal note

Disclaimer

The information on this page is provided for general reference and does not constitute legal or regulatory advice. Privacy requirements may change, and how they apply depends on individual circumstances. CookieHub helps you implement a consent workflow; it does not determine your legal obligations.

Consent signals

Send your visitors’ consent to the tools that need it.

Scan your site, block supported or configured consent-dependent scripts and tags before permission, collect visitor choices and pass them to Google Consent Mode v2.

  • 14-day trial
  • No card required