Artifact GuideEU

EU Digital Markets Act (DMA) Applicability Test

Scope core platform services (CPS), assess gatekeeper designation likelihood, and identify your first DMA workstreams.

Grounded in Regulation (EU) 2022/1925: CPS definitions, gatekeeper thresholds, notification/designation timing, and the 6-month compliance clock.

Author
Sorena AI
Published
Feb 21, 2026
Updated
Feb 23, 2026
Sections
5

Structured answer sets in this page tree.

Primary sources
5

Cited legal and guidance references.

Publication metadata
Sorena AI
Published Feb 21, 2026
Updated Feb 23, 2026
Overview

This DMA applicability test helps product, legal, compliance, and policy teams answer one question fast: are we (or a partner platform) likely to be a DMA gatekeeper for one or more core platform services in the EU, and if yes, what deadlines and obligations start to matter immediately? As of 6 March 2026, the Commission's public gatekeeper page lists 7 gatekeepers and 23 designated core platform services, which makes CPS-level scoping more important than company-level labels alone.

Section 1

Step 1: Are you providing a core platform service (CPS)?

The DMA applies to core platform services (CPS) provided or offered by gatekeepers to business users established in the EU or end users established or located in the EU.

Start by mapping your products to the CPS categories in the DMA definition. If you provide any CPS category at scale, you should treat DMA scoping as a product requirement and a compliance program.

  • CPS categories include: 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 linked to those CPS categories.
  • Define CPS boundaries the way engineering ships them: user journeys, authentication, data flows, ranking and recommendation systems, ads stack, and developer interfaces.
  • Document "CPS vs non-CPS" calls with rationale; these decisions become evidence in Commission questions, stakeholder submissions, and compliance reports.
Section 2

Step 2: Gatekeeper presumption thresholds (Article 3(2))

An undertaking is presumed to meet the gatekeeper conditions when it hits quantitative thresholds on market impact, gateway role, and durability.

Use this as a screening test for each CPS separately (for example: an app store CPS may qualify even if another CPS does not).

  • Market impact presumption: >= EUR 7.5B annual EU turnover in each of the last 3 financial years OR >= EUR 75B average market capitalisation/fair market value in the last financial year, and the same CPS in at least 3 Member States.
  • Gateway presumption: in the last financial year, the CPS has >= 45M monthly active end users established or located in the EU AND >= 10,000 yearly active business users established in the EU (calculated using the Annex methodology).
  • Durability presumption: the gateway thresholds are met in each of the last 3 financial years.
Section 3

Step 3: Notification, designation, and the compliance clock

If you meet all presumption thresholds, the DMA expects a notification to the Commission quickly, with a strict back-and-forth timeline.

This timing matters because the DMA's core obligations (Articles 5-7) must be complied with within 6 months after a CPS is listed in the designation decision.

  • Notify the Commission without delay and in any event within 2 months after the thresholds are met (including information per CPS).
  • Commission designation deadline: at the latest within 45 working days after receiving complete information.
  • Compliance deadline: obligations in Articles 5, 6, and 7 apply within 6 months after the CPS is listed in the designation decision.
  • Practical filing readiness: keep your case file, signatory workflow, and secure submission channel ready before thresholds are hit, because DMA submissions are handled digitally and delays usually come from incomplete information, not from the form itself.
Section 4

Step 4: What if you don't meet the thresholds (but still look like a gatekeeper)?

The DMA also allows designation based on qualitative assessment when thresholds are not met but the three conditions (market impact, gateway role, durable position) appear satisfied.

Treat "near-threshold" or "structural advantage" signals as early warning indicators and start designing DMA-ready controls before designation.

  • Qualitative factors include: size/market position, user and business user numbers, network effects and data advantages, scale and scope effects, lock-in and switching costs, and vertical integration/conglomerate structure.
  • Plan for evidence and defensibility: why a CPS should or should not be listed; what features are "essential" vs "optional"; what integrity/security measures are necessary and proportionate.
  • Use current Commission outcomes as calibration: the public gatekeeper list now shows 7 gatekeepers and 23 designated CPS, while Facebook Marketplace was undesignated on 23 April 2025 and Apple Ads and Apple Maps were not designated on 5 February 2026 after notification and review.
  • If you are a business user, competitor, or end user, you can submit information about potential non-compliance to national competent authorities or the Commission.
Section 5

DMA scoping deliverables (what to produce in week one)

A strong DMA applicability test ends with artifacts that product and compliance teams can execute against - not just an "in scope / out of scope" label.

These deliverables also shorten the path to a defensible compliance report if the CPS is designated.

  • CPS inventory: services, user journeys, APIs, and dependencies (per CPS).
  • Gatekeeper threshold workbook: EU turnover/market cap, Member State coverage, MAU/BAU methodology assumptions, and confidence ranges.
  • Owner map: product owners + policy owners for each obligation cluster (data use, ranking, interoperability, choice screens, app distribution, ads transparency).
  • Evidence plan: what logs, policies, screenshots, demos, and metrics you can produce on demand.
Recommended next step

Turn EU Digital Markets Act (DMA) Applicability Test into an operational assessment

Assessment Autopilot can take EU Digital Markets Act (DMA) Applicability Test from deciding whether these obligations apply in practice to a reusable workflow inside Sorena. Teams working on EU Digital Markets Act (DMA) can keep owners, evidence, and next steps aligned without copying this guide into separate documents.

Primary sources

References and citations

Related guides

Explore more topics

DMA Compliance Checklist (Execution-Ready) | EU Digital Markets Act
An execution-ready EU DMA checklist: CPS scoping, gatekeeper thresholds, designation readiness, Article 5-7 obligation mapping, product/engineering controls.
DMA Compliance Program & Monitoring (Compliance Function + Evidence)
How to build an EU DMA compliance program that survives scrutiny: Article 28 compliance function design, monitoring readiness.
DMA Deadlines & Compliance Calendar (Key Dates) | EU Digital Markets Act
A calendar-ready DMA deadlines guide: application date, gatekeeper notification (2 months), designation (45 working days), 6-month compliance deadline.
DMA Do's and Don'ts for Product Teams | EU Digital Markets Act
Practical DMA do's and don'ts for product and engineering teams: how to avoid self-preferencing, implement choice screens and default changes.
DMA Enforcement: Penalties, Remedies, and Process | EU Digital Markets Act
How EU DMA enforcement works: information requests, monitoring, preliminary findings, non-compliance decisions, commitments, interim measures, remedies.
DMA Fines & Penalties (10% / 20% / 1% + 5% per day) | EU Digital Markets Act
A practitioner guide to DMA penalties: non-compliance fines up to 10% worldwide turnover, repeat infringement fines up to 20%, procedural fines up to 1%.
DMA Obligations List (Articles 5, 6, 7) - By Obligation | EU Digital Markets Act
A detailed, obligation-by-obligation breakdown of the EU Digital Markets Act (DMA): Article 5 restrictions, Article 6 obligations (choice screens, app stores.
DMA Self-Preferencing Compliance Examples (Article 6(5)) | EU Digital Markets Act
Practical self-preferencing compliance guidance for DMA Article 6(5): what counts as self-preferencing in ranking/indexing/crawling, what "transparent, fair.
DMA vs DSA: What's the Difference? (EU Platform Laws)
A practical comparison of the EU Digital Markets Act (DMA) vs the Digital Services Act (DSA): what each law regulates, who is in scope, core obligations.
EU Digital Markets Act (DMA) Requirements (Articles 5-7)
A deep, execution-ready overview of EU DMA requirements for gatekeepers: Article 5 restrictions, Article 6 obligations (choice screens, app distribution.
EU DMA Compliance Guide (How to Comply) | Digital Markets Act (DMA)
A practical guide to EU Digital Markets Act (DMA) compliance: how to scope CPS, start the 6-month clock after designation, implement Articles 5-7 obligations.
EU DMA FAQ (Gatekeepers, Obligations, Deadlines) | Digital Markets Act
EU Digital Markets Act (DMA) FAQ: what is a gatekeeper, what counts as a core platform service (CPS), what are the key obligations (Articles 5-7).
EU DMA Timeline & Key Milestones | Digital Markets Act (2022/1925)
A grounded EU Digital Markets Act (DMA) timeline: application date, gatekeeper designations, compliance clocks, Article 7 staged interoperability milestones.
Gatekeeper Compliance Checklist (DMA Articles 5-7 + Article 11)
A gatekeeper-focused DMA compliance checklist: what to implement within 6 months per listed CPS, how to structure the Article 11 compliance report.
Gatekeeper Designation Guide (DMA Article 3) | EU Digital Markets Act
A practical guide to DMA gatekeeper designation: core platform service mapping, Article 3 thresholds (45M / 10,000 / EUR 7.5B / EUR 75B).