Artifact GuideEU

EU Digital Markets Act Frequently asked questions

Answers to the core DMA questions visitors ask about gatekeepers, core platform services, Articles 5, 6 and 7 obligations, Article 11 reporting, interoperability, business-user data access, compliance evidence, and enforcement.

This page helps orient product, legal, policy, engineering, and compliance work before reading the full legal text or a specific Commission designation decision.

Author
Sorena AI
Published
May 9, 2026
Updated
Jul 26, 2026
FAQ modules
5

Structured answer sets in this page tree.

Primary sources
7

Cited legal and guidance references.

Publication metadata
Sorena AI
Published May 9, 2026
Updated Jul 26, 2026
Overview

Regulation (EU) 2022/1925, the EU Digital Markets Act, entered into force on 1 November 2022 and has applied in its main part since 2 May 2023. It applies to undertakings designated by the European Commission as gatekeepers, and its main conduct obligations apply only to the core platform services listed in the designation decision. The Regulation and designation decision control; Commission templates and portal materials explain procedure and expected evidence but do not replace the binding text. This FAQ explains the designation test, covered service categories, Articles 5, 6 and 7 duties, Article 11 reporting, interoperability, business-user data access, evidence, and enforcement.

Browse sub-FAQs

Choose the question set you need

These focused FAQ modules break this artifact into narrower answer sets so teams can move straight to the right source-backed guidance.

Browse all FAQ items19
Focused FAQ modules
5
Showing 5 of 5
Question 1

Who is a DMA gatekeeper?

A DMA is an undertaking designated by the European Commission because it has a significant impact on the internal market, provides a that is an important gateway for business users to reach end users, and has or is expected to have an entrenched and durable position.

The quantitative presumption uses three main tests: at least EUR 7.5 billion annual Union turnover in each of the last three financial years or at least EUR 75 billion average market capitalisation or equivalent fair market value in the last financial year; the same in at least three Member States; and, for that service in the last financial year, at least 45 million monthly active end users established or located in the Union and at least 10,000 yearly active business users established in the Union. The user thresholds must have been met in each of the last three financial years for the entrenched-and-durable-position presumption.

  • An undertaking that meets the thresholds must notify the Commission without delay and in any event within two months after the thresholds are met.
  • The Commission must designate a threshold-meeting undertaking without undue delay and at the latest within 45 working days after receiving complete information.
  • Meeting the thresholds creates a presumption, but the undertaking may submit sufficiently substantiated arguments that the relevant service does not meet the requirements.
  • The Commission can also designate an undertaking that meets the qualitative Article 3 requirements even if it does not satisfy every quantitative threshold.
Question 2

Which services count as core platform services?

Article 2(2) lists ten categories: online intermediation services, online search engines, online social networking services, video-sharing platform services, number-independent interpersonal communications services, operating systems, web browsers, virtual assistants, cloud computing services, and online advertising services provided by an undertaking that also provides another listed core platform service. Software application stores fall within online intermediation services; they are not a separate eleventh category.

The designation decision matters: DMA Articles 5, 6 and 7 apply to the with respect to each listed for that undertaking. Do not assume every product of a gatekeeper is covered in the same way.

  • Build the scope map by undertaking, legal entity, designated , user metrics, geography, and the Article 3(9) designation decision.
  • Treat integrated products carefully because the DMA Annex distinguishes services by category and by user purpose.
  • Use the Commission gatekeepers page to check currently listed gatekeepers and their listed core platform services before applying an obligation to a product.
Question 3

What do Articles 5, 6 and 7 require?

Article 5 contains obligations that apply directly to listed core platform services, including restrictions on combining or cross-using personal data without valid consent, anti-steering limits, app-store and payment-choice protections, complaint-access protections, and advertising transparency for advertisers and publishers.

Article 6 contains obligations that can be further specified under Article 8. It covers restrictions on using non-public business-user data to compete with those business users, uninstall and default-choice requirements, third-party app and app-store access, self-preferencing in ranking, switching, interoperability with operating system or virtual assistant features, advertising measurement access, end-user data portability, business-user data access, search-data access, fair access conditions, and termination conditions.

Article 7 addresses interoperability for number-independent interpersonal communications services. Where such a service is listed in the designation decision, the must make specified basic functionalities interoperable with services of another provider offering or intending to offer such services in the Union, upon request and free of charge. One-to-one text and attached-file functions apply following listing, subject to the general six-month compliance period; group functions apply within two years after designation; and listed voice and video call functions apply within four years.

  • For each obligation, identify the relevant first; the same undertaking can have different duties for different listed services.
  • For Article 5 data-combination controls, check consent flows and whether refusal or withdrawal is respected without repeated requests for the same purpose more than once within one year.
  • For Article 6 ranking, access, switching, portability, and interoperability duties, keep technical implementation records because Article 8 requires the to ensure and demonstrate effective compliance.
  • For Article 7 messaging interoperability, preserve security, including end-to-end encryption where applicable, and keep request, reference-offer, timing, and data-minimisation evidence.
Question 4

What does Article 11 require in a DMA compliance report?

Within six months after designation, a must provide the Commission with an describing, in a detailed and transparent manner, the measures implemented to ensure compliance with Articles 5, 6 and 7. It must also publish and provide the Commission with a non-confidential summary, then update the report and summary at least annually.

The Commission's Article 11 template asks gatekeepers to report for each designated and each applicable obligation. It expects a compliance statement, an exhaustive explanation, supporting data, internal documents, implementation dates, product and geographic scope, technical and engineering changes, terms and condition changes, user or business-user consultation, testing, metrics, and reasons where an obligation cannot by nature apply to a service.

  • Organize evidence by , Article 5/6/7 obligation, measure, implementation date, market scope, and owner.
  • Keep non-confidential summaries specific enough for third parties to provide meaningful input to the Commission.
  • Track omitted obligations explicitly; the template allows omission only where the undertaking explains why a specific obligation cannot by nature apply to the relevant .
  • The template says the report, annexes, non-confidential summary, and underlying data should be machine-readable.
Question 5

How do interoperability and business-user data access work?

Interoperability appears in two important places. Article 6(7) requires free and effective interoperability with, and access for interoperability to, the same hardware and software features controlled through listed operating systems or virtual assistants as are available to the 's own services or hardware, subject to strictly necessary and proportionate integrity protections that the gatekeeper justifies. Article 7 separately covers interoperability of listed number-independent interpersonal communications services.

Article 6(10) requires a , on request and free of charge, to provide business users and authorised third parties with effective, high-quality, continuous and real-time access to aggregated and non-aggregated data generated in the context of the relevant or supporting services by those business users and the end users engaging with their products or services. Personal data access is limited to data directly connected with the end user's use of the relevant business user's products or services and requires end-user opt-in consent.

  • For interoperability requests, keep the request, feature requested, service or hardware provider, API or interface offered, security assessment, refusal or limitation rationale, and delivery timing.
  • For business-user data access, keep request records, authorisations, data categories, personal-data consent status, latency or continuity evidence, access logs, and any refused categories with reasons.
  • The Commission's resources for businesses page links to materials for Article 6(7) OS interoperability, Article 6(9) data portability, and Article 6(10) data access.
Question 6

What compliance evidence should a gatekeeper maintain?

DMA evidence should prove effective compliance, not only policy intent. The Article 11 template points to concrete evidence categories: implemented measures, supporting data, internal documents, implementation timing, technical and engineering changes, user-interface flows, APIs, terms and condition changes, consultation records, market analysis, A/B testing, user or business-user surveys, consent rates, metrics, and impact evaluation.

Article 13 also matters for evidence because a may not undermine effective compliance through contractual, commercial, technical, interface-design, or other behaviour. Evidence should therefore show that DMA rights are not made unduly difficult to exercise and that choices are not presented in a non-neutral way.

  • Keep a service-by-service obligation matrix for Articles 5, 6 and 7.
  • Attach engineering release evidence, API documentation, access logs, ranking-change records, data-access records, consent-flow records, and interoperability request records to the relevant obligation.
  • Record rejected alternatives and reasons, especially for interoperability and access choices where the Commission template asks for alternatives considered.
  • Keep user and business-user communications consistent with the internal compliance evidence.
Question 7

How is the DMA enforced and what penalties can apply?

The European Commission enforces the DMA. It can open proceedings, specify measures for effective compliance, adopt non-compliance decisions, order the to cease and desist, and require explanations of how the gatekeeper plans to comply.

For non-compliance with Articles 5, 6 or 7 and specified measures, remedies, interim measures, or binding commitments, the Commission may impose fines up to 10% of the 's total worldwide turnover in the preceding financial year. For the same or similar infringement of an Article 5, 6 or 7 obligation for the same after a non-compliance decision in the preceding eight years, the fine can be up to 20%. The Commission may also impose periodic penalty payments up to 5% of average daily worldwide turnover in the preceding financial year per day to compel compliance with listed DMA decisions or information duties.

  • Do not treat the 10% and 20% figures as automatic penalties; the Commission fixes fine amounts by considering gravity, duration, recurrence, and, for some procedural fines, delay caused to proceedings.
  • Separate substantive non-compliance evidence from procedural evidence such as notifications, information responses, inspection cooperation, compliance-function records, and access-to-file conditions.
  • Commission enforcement can also rely on interim measures, commitments, market investigations, and specification decisions where the DMA conditions are met.
Primary sources

References and citations

digital-markets-act.ec.europa.eu
Referenced sections
  • Current Commission portal listing designated gatekeepers, their designated core platform services, and the related case records.
"Core platform services"
digital-markets-act.ec.europa.eu
Referenced sections
  • Current Commission portal for Article 6(7) specification proceedings and gatekeeper-specific interoperability resources.
"same OS hardware and software features"
digital-markets-act.ec.europa.eu
Referenced sections
  • Commission page explaining that the DMA contains designation rules and gatekeeper obligations, with procedural rules for implementation and enforcement.
"implementation and enforcement of the DMA"
Related guides

Explore more topics

DMA Anti-Circumvention Design Review for Gatekeeper Product Changes
Review DMA Article 13 anti-circumvention risks in gatekeeper product, interface, contractual, commercial, and technical changes with obligation mapping and evidence records.
DMA Article 6 Business User Data Access Guide
Official source guide to EU Digital Markets Act Article 6 data access for business users, end users, authorised third parties, consent boundaries, and evidence handoffs.
DMA Article 6(7) and Article 7 interoperability obligations
Official source guide to DMA interoperability duties: Article 6(7) operating-system feature access, Article 7 messaging interoperability, request handling, security conditions, and compliance evidence.
DMA Articles 5, 6 and 7 obligations mapped to CPS evidence
Map EU Digital Markets Act Articles 5, 6 and 7 obligations to affected core platform services, product evidence, legal owners, and Article 11 compliance-report artifacts.
DMA compliance program and monitoring for gatekeepers
Build a DMA compliance program around Article 8 effective compliance, Article 11 reporting evidence, Article 13 anti-circumvention controls, and Article 28 compliance-function governance.
DMA Core Platform Service Scoping
Scope EU Digital Markets Act core platform services by service category, designation evidence, user thresholds, and Form GD service-boundary records.
DMA CPS Obligation Matrix Workflow: Articles 5, 6, 7 and Article 11 Evidence
Build a DMA core platform service obligation matrix that links each designated CPS to Articles 5, 6 and 7 duties, product owners, designation evidence, Article 11 report artifacts and review gates.
DMA designation intake workflow for gatekeeper notifications
Build an official source DMA designation intake record covering core platform service classification, Article 3 thresholds, Form GD evidence, Commission handoff, and Article 11 readiness.
DMA enforcement, penalties, and remedies: Commission powers and evidence
Follow DMA enforcement from investigation and preliminary findings to non-compliance decisions, fines, daily payments, interim measures, commitments, and remedies.
DMA Gatekeeper Compliance Checklist for Articles 5, 6, 7 and 11
A cited EU Digital Markets Act checklist for designated gatekeepers: core platform service scope, Article 5/6/7 controls, Article 11 report evidence, anti-circumvention checks, and review gates.
DMA Gatekeeper Designation Guide: Article 3 thresholds, Form GD, and Article 11 readiness
A cited EU Digital Markets Act guide for assessing Article 3 gatekeeper thresholds, scoping core platform services, preparing Form GD evidence, handling rebuttal annexes, and planning Article 11 compliance reporting.
DMA penalties and fines: caps, triggers, and enforcement evidence
Compare DMA Article 30 fine ceilings, the narrow 20% repeat test, 1% procedural fines, and Article 31 daily payments, with decision-specific examples.
DMA Product Change Review Workflow for Articles 5, 6, 7, 11 and 13
Review DMA-relevant product releases for Article 5, Article 6, Article 7, anti-circumvention, Article 11 evidence, and product-owner/legal signoff.
DMA Self-Preferencing Compliance Examples for Ranking and Display
Examples and release-review controls for DMA Article 6(5) self-preferencing checks across ranking, indexing, crawling, search results, marketplaces, app stores, feeds, and virtual assistants.
DMA vs Data Act: gatekeeper duties compared with EU data-sharing rules
Compare the EU Digital Markets Act and EU Data Act by scope, actors, data access, interoperability, reporting, evidence, and enforcement without merging distinct obligations.
DMA vs DSA: Digital Markets vs Services Act
Compare the EU Digital Markets Act and Digital Services Act by covered services, regulated actors, core duties, reporting, dates, evidence, and enforcement.
DMA vs EU competition law: gatekeeper obligations, Article 11 evidence, and enforcement
Compare the EU Digital Markets Act with EU competition law: ex ante gatekeeper and core platform service duties, Articles 5 to 7, Article 11 reports, penalties, and evidence records.
DMA vs GDPR: gatekeeper data obligations compared
Compare DMA gatekeeper duties with GDPR rules for personal-data processing, consent, lawful basis, portability, accountability evidence, and enforcement.
EU Digital Markets Act Article 11 Evidence Calendar
Build a DMA Article 11 compliance-report calendar with the correct designation trigger, service annexes, evidence owners, annual updates, and publication gates.
EU Digital Markets Act checklist for gatekeeper compliance
A source-grounded Sorena DMA checklist for designated gatekeepers and core platform services, covering scope, Articles 5, 6 and 7 obligations, Article 11 reporting, evidence, anti-circumvention, and governance.
EU Digital Markets Act compliance: gatekeeper obligations and evidence
DMA compliance guide for designated gatekeepers: core platform service scoping, Articles 5, 6 and 7 controls, Article 11 reports, anti-circumvention checks, interoperability evidence, and enforcement risk.
EU Digital Markets Act deadlines and compliance calendar
Calculate DMA notification, designation, service-compliance, Article 11 reporting, concentration-notice, and profiling-audit deadlines from the correct legal trigger.
EU Digital Markets Act requirements for gatekeepers
DMA requirements for designated gatekeepers: core platform service scope, Articles 5, 6 and 7 obligations, Article 11 reporting, anti-circumvention, evidence, remedies, and fines.
EU Digital Markets Act timeline: application, designation, reporting, and review
DMA timeline separating fixed legal dates, threshold and designation clocks, recurring reports, service-specific decisions, final enforcement, and the first Article 53 review.
EU DMA Applicability Test: gatekeeper thresholds, core platform services, and evidence
Test whether the EU Digital Markets Act may apply to a platform service using the DMA gatekeeper criteria, core platform service categories, EU user thresholds, notification steps, and evidence records.
EU DMA Article 11 Compliance Reporting Guide
Official source guide to EU Digital Markets Act Article 11 compliance reports: report purpose, template evidence, non-confidential summaries, annual updates, and submission steps.
EU DMA do's and don'ts for product teams
Product release checks for designated DMA gatekeepers: Article 5, 6 and 7 obligations, anti-circumvention review, data access, interoperability, self-preferencing and Article 11 evidence.