Artifact GuideEU

EU Digital Markets Act (DMA) Gatekeeper Designation Guide

How gatekeeper designation works under DMA Article 3 (and how to prepare).

CPS boundaries, threshold screening, notification timeline, Commission designation decision, and the 6-month compliance clock.

Back to main artifact Review sources

Author

Sorena AI

Published

Feb 21, 2026

Updated

Feb 23, 2026

Sections

Structured answer sets in this page tree.

Primary sources

Cited legal and guidance references.

Publication metadata

Sorena AI

Published Feb 21, 2026

Updated Feb 23, 2026

Overview

Gatekeeper designation is the pivot point for DMA implementation. Once a core platform service (CPS) is listed in a designation decision, the 6-month compliance clock starts for Articles 5-7. This guide helps you scope CPS boundaries, run the quantitative threshold test, prepare defensible submissions, and build an implementation timeline you can execute.

Section 1

1) Define your core platform service (CPS) boundaries first

DMA designation is not just about company size; it is about specific core platform services (CPS). The designation decision lists which CPS are covered, and obligations attach to each listed CPS.

Start with a CPS inventory that matches how your systems ship: user journeys, authentication surfaces, ranking, ads stack components, developer APIs, and cross-service data sharing points.

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.
Write an explicit boundary statement per CPS (what's included, what's excluded, and why).
Capture "where the CPS ends": off-platform payment flows, external identity, external ad measurement, third-party app stores, and partner integrations.

Section 2

2) Run the presumption test (Article 3(2)) per CPS

Article 3 sets three conditions for designation (market impact, gateway role, durable position) and provides quantitative thresholds that create a presumption the conditions are satisfied.

Treat this as a repeatable screening model you can rerun quarterly. It helps you anticipate the notification requirement and the likely timing of a designation decision.

Market impact: >= 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 role: 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 (Annex methodology).
Durability: the gateway thresholds are met in each of the last 3 financial years.

Section 3

3) Notification + Commission designation timeline (2 months -> 45 working days)

If you meet all thresholds, the DMA requires notification to the Commission without delay and in any event within 2 months after the thresholds are met.

After the Commission receives complete information, it must designate the undertaking as a gatekeeper without undue delay and at the latest within 45 working days.

Notification content matters: provide information for each CPS that meets the user/business-user thresholds.
Expect completeness questions: incomplete information can delay the "45 working day" clock.
Prepare a single source of truth: metrics definitions, EU location methodology, active user counting, and confidence ranges.

Section 4

4) Rebuttal arguments and qualitative designation

An undertaking can present sufficiently substantiated arguments that, exceptionally, although thresholds are met, it does not satisfy the designation requirements due to circumstances in which the CPS operates.

Separately, the Commission can designate gatekeepers that do not meet thresholds based on qualitative assessment (size, network effects, data advantages, lock-in, vertical integration, and other structural characteristics).

If you plan to argue "exceptional circumstances", build a fact file that links the argument to CPS boundaries and market realities.
For near-threshold CPS, treat designation as "foreseeable" and begin building DMA-ready controls early (ranking fairness, data separation, portability tooling).
Track designation precedent: the Commission's published gatekeepers list is a living calibration dataset and, as of 6 March 2026, it shows 7 gatekeepers and 23 designated CPS after both designations and status changes.

Section 5

5) The post-designation compliance clock (6 months) and what to do immediately

After a CPS is listed in the designation decision, the gatekeeper must comply with Articles 5, 6, and 7 within 6 months.

This is where teams tend to lose time: mapping obligations to product features, designing choice screens, changing default settings, updating ad transparency tooling, and building evidence.

Create an obligation-to-feature map per CPS (Articles 5-7), with owners and acceptance criteria.
Start the evidence library now: screenshots, recorded demos, API documentation, ranking parameter explanations, consent flows, and change logs.
Stand up the DMA compliance function (independent from operational functions) so reporting and monitoring are not bolted on later.
Prepare the Article 11 report workflow from day one, because the detailed report, non-confidential summary, and machine-readable supporting material are due within 6 months after designation.

Section 6

Quick checklist: what a strong designation readiness pack contains

A designation readiness pack should reduce ambiguity for internal stakeholders and make it easy to respond quickly to Commission questions.

If you are a business user (not a gatekeeper), the same pack helps you identify which obligations you can rely on and what "good compliance" should look like from your platform partner.

CPS inventory + boundary statements (per CPS).
Threshold workbook (EU turnover/market cap, Member State coverage, MAU/BAU methodology and assumptions).
Risk register: obligations most likely to change product behavior (self-preferencing, app distribution, consent/data combination, interoperability).
Implementation timeline: 0-6 months plan aligned to Articles 5-7 obligations, with evidence milestones.

Recommended next step

Use EU Digital Markets Act (DMA) Gatekeeper Designation Guide as a cited research workflow

Research Copilot can take EU Digital Markets Act (DMA) Gatekeeper Designation Guide from clarifying scope and applicability with cited answers 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.

Research workflow

Open Research Copilot for EU Digital Markets Act (DMA) Gatekeeper Designation Guide

Start from EU Digital Markets Act (DMA) Gatekeeper Designation Guide and answer scope, timing, and interpretation questions with cited outputs.

Explore next step

Talk to Sorena

Talk through EU Digital Markets Act (DMA)

Review your current process, evidence gaps, and next steps for EU Digital Markets Act (DMA) Gatekeeper Designation Guide.

Explore next step

Primary sources