DMA Article 6 Self-Preferencing Fines Q2 2026: Apple Ads Carve-Out, Google Specification Proceedings & Advertiser Workflow Implications

Article 6 in the DMA Framework

Article 6 of the Digital Markets Act establishes the core behavioural obligations on designated gatekeepers — twenty-two distinct duties covering self-preferencing in ranking, data combination across services, interoperability for operating system features, business user access to advertising performance data, and portability of end-user data. The article operates alongside Article 5's directly applicable obligations and Articles 7 and 8's procedural rules for ongoing compliance dialogue between gatekeepers and the European Commission.

Two years into DMA application the enforcement architecture has matured into a recognisable shape. Preliminary findings precede formal non-compliance decisions. Fines under Article 30 reach up to 10% of worldwide annual turnover with repeat-infringement uplift to 20%. The Article 8 specification proceedings translate broad behavioural obligations into the technical, organisational, and audit measures that gatekeepers must implement going forward. Q2 2026 brings several active enforcement threads to inflection points.

The most consequential developments are the two Google specification proceedings opened in January 2026 targeting Article 6(7) Android interoperability and Article 6(11) search data sharing, the February 5 Commission decision that Apple Ads and Apple Maps fall outside the gatekeeper designation, and the ongoing Meta pay-or-consent assessment following the €200 million fine from April 2025. Each development reshapes the operational space for advertisers in distinct ways.

"Today's preliminary findings translate the high-level obligation in Article 6(7) into the technical measures that Google must implement. The measures specify the access regime, the timing, the documentation, and the audit framework that will govern Android interoperability with third-party AI services from the date of the final decision."
— European Commission Statement, 27 April 2026 (Google specification proceedings)

For consolidated EU compliance framework, see EU DSA Compliance and ongoing tracking through Policy Tracker.

Q2 2026 Enforcement Timeline

The Q2 2026 enforcement calendar is dense. Several proceedings move through preliminary findings, public consultation, and final decision phases simultaneously, with the most consequential decisions arriving by 27 July 2026.

Active Proceedings Timeline

Q3-Q4 Outlook

Beyond the July deadline several enforcement threads continue. The Commission's ongoing assessment of Meta's modified pay-or-consent model is widely expected to produce a follow-up decision in Q3 or Q4 2026. The first DMA review published on 27 April 2026 found that the framework remains fit for purpose and identified priority areas for 2027 enforcement focus including AI service integration, advertising portfolio data access, and end-user data portability.

For ongoing decision tracking and historical context, see DSA Enforcement Signals.

Google Article 6(7) and 6(11) Specification Proceedings

The two specification proceedings opened against Google on 27 January 2026 represent the most operationally specific DMA enforcement to date. Rather than imposing fines for past conduct the specifications translate broad behavioural obligations into the technical, organisational, and audit measures that Google must implement going forward.

Article 6(7) — Android Interoperability for AI Services

The Article 6(7) obligation requires gatekeepers to provide third-party developers with effective interoperability with hardware and software features controlled by their operating systems on the same terms available to the gatekeeper's own services. The Google specification focuses on interoperability with Android features used by Google's own AI services including Gemini — third-party AI providers must receive equally effective access to the same Android features.

The April 27 preliminary findings define the technical scope of the obligation. The measures specify the Android APIs, the system integration capabilities, the on-device sensor access, and the background execution permissions that Google must make available to third-party AI services on the same terms it provides to Gemini. The consultation period closed 13 May 2026 with the final binding decision due by 27 July 2026.

Article 6(11) — Search Data Sharing with Rival Search Engines

The Article 6(11) obligation requires gatekeepers to grant third-party search engine providers access to anonymised ranking, query, click, and view data on fair, reasonable, and non-discriminatory terms. The Google specification translates the broad obligation into the specific data fields, anonymisation methods, access conditions, pricing structure, and audit regime that will govern data sharing.

The April 16 preliminary findings published a 29-page specification document defining the obligation at the field level. The document covers the granularity of query data, the time horizon of historical data made available, the anonymisation thresholds that protect end-user privacy, the commercial terms governing access fees, and the audit framework that verifies Google's compliance with the access regime. The consultation period closed 1 May 2026 with the final binding decision due by 27 July 2026 alongside the interoperability decision.

Eligibility for AI Chatbot Providers

One distinctive element of the Article 6(11) specification is its treatment of AI chatbot providers. The preliminary findings indicate that AI chatbot operators can qualify for search data access if they meet defined eligibility criteria including operational scale, technical capacity, and compliance posture. The treatment matters because chatbot providers including OpenAI's search-augmented services and Anthropic's web-access services have material data needs that would be served by the framework if eligibility is confirmed.

For automated compliance scanning of search-driven campaigns, run AI Compliance Audit.

Apple Ads and Apple Maps Carve-Out

The 5 February 2026 Commission decision found that Apple Ads and Apple Maps should not be designated as core platform services under the DMA. The decision is significant for advertisers because Apple Ads escapes the obligations that would apply to a designated advertising service — including the advertising data transparency, performance measurement access, and portfolio data obligations under Articles 5 and 6 that apply to designated advertising services.

Decision Rationale

The Commission's assessment turned on whether Apple Ads constitutes an "important gateway" for business users to reach end users under Article 3 of the DMA. The assessment found that Apple Ads has very limited scale in the EU online advertising sector, with Apple's advertising business operating at a fraction of the scale of designated services like Google Search Ads and Meta Ads. The limited scale failed the gateway threshold because business users have alternative routes to reach Apple device users that do not depend on Apple Ads.

For Apple Maps the decision turned on similarly limited overall usage rates in the EU. The Commission found that Apple Maps does not function as the dominant mapping service for EU end users or as an important business-user gateway for location-based advertising or local business presence.

What Continues to Apply

• iOS and iPadOS: Designated as core platform services in September 2023. Continue to face Article 5 and 6 obligations including the App Tracking Transparency framework interactions.
• App Store: Designated. Subject to the anti-steering rules that produced the €500M fine in April 2025 and ongoing compliance monitoring.
• Safari browser: Designated. Subject to default-setting and choice-screen obligations under Article 6(3).
• Apple Ads and Apple Maps: Not designated. Operate outside DMA obligations under Apple's own commercial terms.

Advertiser Implication — Apple Search Ads Workflow

For advertisers using Apple Search Ads the carve-out means that the platform's advertising operations continue under Apple's own commercial terms rather than under DMA-mandated transparency, measurement access, and data portability requirements. The continued commercial freedom preserves Apple's discretion over campaign data exposure, audience definitions, and attribution methodology. The carve-out also limits the data-portability tools that advertisers might have expected to use to consolidate Apple Ads data with Google Ads and Meta Ads data under DMA-mandated formats.

For Apple-specific compliance context across designated services, see Policy Tracker.

Meta Pay-or-Consent Status

The April 2025 Meta non-compliance decision found that Meta's pay-or-consent model violated Article 5(2) — the obligation against combining personal data across designated services without user consent that meets the DMA's specific consent standard. The €200 million fine accompanied an order to bring the model into compliance within 60 days.

The Compliance Path

Meta's response involved several adjustments to the pay-or-consent model. The advertising-supported tier was modified to use less personalised advertising for users who declined personalised data combination, with the modified tier offered alongside the original subscription tier. The modifications were intended to provide users with a meaningful free choice that does not condition platform access on consent to data combination.

Q2 2026 Status

The Commission's assessment of the modified model continues into Q2 2026. The assessment turns on whether the less personalised free tier provides sufficient functionality and quality to constitute a meaningful alternative to the consented or paid tiers. Industry observers and DSC stakeholders have raised concerns that the modified tier may still fall short of the DMA's free-choice standard if the reduced personalisation produces materially worse user experience or if interface design steers users toward consent.

Advertiser Implication — Audience Reach Effects

The pay-or-consent landscape produces measurable effects on advertiser audience reach. Users who decline personalised data combination receive less personalised advertising and have weaker behavioural targeting signals available for campaign delivery. Users who select the paid tier are entirely outside the addressable advertising audience. The combined effect reduces the addressable audience for behavioural targeting on Meta platforms in EU markets.

Industry estimates as of Q1 2026 suggest that approximately 5-8% of EU Meta users select paid or limited-personalisation tiers, with higher rates in Germany, Netherlands, and Nordic markets. The variation by market means advertiser audience planning should incorporate market-specific reach modelling rather than assuming uniform pay-or-consent uptake across EU markets.

For Meta-specific ad policy framework, see Meta Ad Policies.

Advertiser Workflow Implications

The Q2 2026 DMA enforcement architecture has operational consequences across audience strategy, measurement, creative compliance, and platform diversification. The implications are highest for advertisers operating across multiple gatekeeper platforms with significant EU spend.

Audience Strategy Adjustments

• Behavioural targeting capacity: Reduced on Meta due to pay-or-consent uptake. Plan for 5-10% reach reduction on personalised audiences in EU markets.
• Search audience signals: Watch for Article 6(11) data sharing effects on rival search engines and AI chatbot providers gaining query data access.
• Self-preferencing changes: Google Shopping, Hotels, Flights vertical placements may face restrictions; plan for organic visibility shifts in EU search results.
• Apple Search Ads workflow: Operates under Apple's own commercial terms; no DMA-mandated data portability or measurement access.

Measurement and Attribution

• Cross-platform attribution: Apple Ads data remains in Apple's measurement ecosystem; no DMA-mandated portability to consolidated measurement platforms.
• Google measurement specifications: Watch for Article 6(8) effects on Google Ads measurement transparency.
• Conversion data combination: Meta cross-product attribution restrictions for non-consented users.

Creative and Compliance Review

• Cross-platform creative consistency: Reduced as each gatekeeper develops platform-specific compliance signals.
• Documentation requirements: Maintain compliance documentation for advertising data flows, consent capture, and audience derivation.
• Brand safety controls: Continue to operate independently of DMA; no DMA-driven brand safety changes.

For automated compliance scanning, run AI Compliance Audit and Keyword Risk Checker.

Q2 2026 Compliance Checklist

• [ ] Map active EU campaigns against gatekeeper designation status (Apple Ads carve-out vs. Google/Meta in scope)
• [ ] Document consent flows for behavioural targeting on Meta platforms in EU markets
• [ ] Model audience reach scenarios for 5-10% reduction in personalised audience under pay-or-consent uptake
• [ ] Track 27 July 2026 binding decisions on Google Article 6(7) and 6(11) and plan operational response
• [ ] Review Apple Search Ads campaigns for continued reliance on Apple-proprietary measurement
• [ ] Establish monitoring for Q3 2026 enforcement signals including potential repeat-infringement uplift
• [ ] Verify cross-platform attribution documentation accommodates DMA data flow restrictions
• [ ] Update compliance training to reflect Q2 2026 Article 6 specification proceedings outcomes