→ Want to bypass Google Play entirely? See how ROiBest PWA works — no submission, no cut, 1.2x installs.
If you’re running paid advertising campaigns in Europe or Turkey, you’ve likely already felt the sting of Meta’s digital services tax (DST) surcharges. Since Meta began passing these costs directly to advertisers, budgets allocated to Facebook and Instagram campaigns in key markets have quietly shrunk — without any change in ad spend or targeting settings. Understanding exactly how these surcharges work, and how to strategically redirect your budget toward lower-cost channels, is now a fundamental part of performance marketing in 2026.
This article breaks down Meta’s DST surcharges by country, explains why Google Ads PWA install campaigns are emerging as a cost-efficient alternative, walks you through a five-step budget migration process, and provides a direct cost comparison so you can make data-driven decisions for your advertising strategy.
What Are Digital Services Taxes and Why Is Meta Passing Them On?
Digital services taxes are government-levied fees imposed on large technology companies generating revenue from digital advertising and data monetization within a country’s borders. Rather than absorbing these taxes as an operating cost, Meta has chosen to pass them directly to advertisers in the form of surcharges applied to their ad invoices.
This approach was confirmed when Meta updated its advertiser terms of service to include DST cost pass-through clauses. The rationale from Meta’s perspective is straightforward: these taxes represent an incremental cost of doing business in specific jurisdictions, and passing them to advertisers keeps Meta’s effective margin stable.
For advertisers, this means that every euro, pound, or lira you spend on Meta advertising in affected markets now costs more than the nominal amount shown in your campaign budget settings. Your actual effective cost per thousand impressions (eCPM), cost per click (CPC), and cost per install (CPI) are all higher than what your dashboard suggests at face value.
Meta DST Surcharges by Country: The Full Breakdown
The surcharges are not uniform across markets. Each country’s DST rate is determined by its domestic legislation, and Meta applies a corresponding surcharge percentage to all applicable ad spend in that market. Here is the current rate schedule for the most significant affected markets:
France — 3% DST Surcharge
France was among the first European nations to implement a standalone digital services tax, and Meta’s corresponding surcharge stands at 3%. For advertisers targeting French users on Facebook and Instagram, every €100 of ad spend effectively costs €103 before any other fees or platform charges. Given that France is a major e-commerce and app market, this surcharge materially affects campaigns targeting French-speaking audiences across Europe.
United Kingdom — 2% DST Surcharge
The UK’s Digital Services Tax, which came into force in April 2020 and was set at 2% of qualifying revenues, results in Meta applying a 2% surcharge to UK-targeted ad spend. While 2% may appear modest compared to other markets, the UK represents one of the highest average CPMs globally for mobile advertising. A 2% surcharge on already-premium inventory translates to meaningful absolute budget losses for advertisers with significant UK audience segments.
Italy — 3% DST Surcharge
Italy’s digital services tax follows France’s model at 3%. Italian mobile app markets have grown substantially over the past three years, making this a market where many app publishers have concentrated their user acquisition budgets. The 3% surcharge applies to all qualifying Meta ad spend targeted at Italian users, adding to an already competitive bidding environment for mobile install campaigns.
Spain — 3% DST Surcharge
Spain’s DST surcharge is also 3%, consistent with the broader Southern European approach to taxing digital advertising revenues. Spain is a priority market for mobile gaming, fintech, and subscription app publishers operating across Latin American and Spanish-speaking audiences, making this surcharge particularly impactful for teams building scaled regional campaigns.
Turkey — 7.5% DST Surcharge
Turkey carries the highest DST surcharge rate in Meta’s current schedule at 7.5%. This reflects Turkey’s aggressive stance on digital economy taxation. For advertisers targeting Turkish users — a younger, mobile-first population with high app engagement rates — this surcharge represents a substantial effective price increase. A campaign with a €10,000 monthly budget targeting Turkish audiences is effectively spending €10,750 in value terms once the surcharge is applied.
The Compounding Effect: How DST Surcharges Erode Campaign ROI
The impact of these surcharges extends beyond the headline percentage. When you account for the full economics of a user acquisition campaign, the DST surcharge compounds with other cost factors to erode return on investment significantly.
Consider a campaign targeting users across France, Italy, and Spain simultaneously. Your blended DST surcharge across those markets averages 3%. But that 3% is applied on top of your existing CPM, which may already include auction competition premiums, creative quality adjustments, and platform optimization fees. The result is that your effective CPI — the real cost to acquire each app install — increases by more than 3% in absolute terms, because you are paying the surcharge on gross spend while only receiving value on net deliverable impressions.
Furthermore, these surcharges are often buried within invoice line items rather than displayed as explicit campaign costs within the Ads Manager interface. Many advertisers running month-over-month comparisons are attributing performance degradation to creative fatigue or audience saturation when the actual cause is an incremental 2-7.5% cost increase on their delivery budget.
Why Google Ads PWA Install Campaigns Avoid These Costs
Google Ads currently does not apply digital services tax surcharges in the same manner as Meta. This creates a meaningful cost differential for advertisers who can shift their install campaign spend from Meta to Google Ads, particularly in the DST-affected markets outlined above.
Beyond the tax question, Progressive Web App (PWA) install campaigns on Google Ads offer a structurally different cost model for mobile app user acquisition. Unlike native app install campaigns that direct users to the Google Play Store, PWA campaigns send users directly to a web-based install flow. This eliminates several cost layers that are typically invisible to advertisers running traditional app campaigns.
For a deeper look at how to set up and optimize these campaigns, see our guide at Google Ads PWA Install Campaign Guide v2 and Google Ads PWA Install Campaign 2026.
The key cost advantages of PWA install campaigns include:
- No Google Play Store revenue cut: Google Play typically takes 15-30% of in-app purchases made through apps distributed via the Play Store. PWAs bypass this entirely, meaning the revenue you generate from converted users stays with your business.
- No app store review delays: Submitting an app update to Google Play introduces review cycles that can range from 24 hours to several weeks. PWAs deploy instantly, meaning your marketing campaigns can align with product changes in real time without waiting for store approval.
- Lower funnel friction: PWA install flows require fewer taps and no app store account authentication. This reduces abandonment between click and install, improving your effective conversion rate on the same ad spend.
- No DST surcharge on Google Ads: Because Google handles its tax obligations differently and has not implemented the same advertiser-facing DST pass-through model as Meta, your Google Ads budget in affected markets reflects more accurately what you intend to spend.
Cost Comparison: Meta Campaigns vs. Google Ads PWA Install Campaigns
The following table illustrates the effective cost differential between Meta campaigns subject to DST surcharges and Google Ads PWA install campaigns in the same markets. Figures are illustrative based on typical benchmarks for mobile app install campaigns.
| Market | Meta DST Surcharge | Meta Effective CPI (Indexed) | Google Ads PWA CPI (Indexed) | Cost Advantage (Google Ads PWA) |
|---|---|---|---|---|
| France | 3% | 103 | 95 | ~8% lower |
| United Kingdom | 2% | 102 | 96 | ~6% lower |
| Italy | 3% | 103 | 94 | ~9% lower |
| Spain | 3% | 103 | 93 | ~10% lower |
| Turkey | 7.5% | 107.5 | 91 | ~18% lower |
The Turkey case is particularly striking: the combination of Meta’s 7.5% DST surcharge and the higher baseline conversion efficiency of PWA install flows (due to reduced funnel friction) results in an estimated 18% cost-per-install advantage for Google Ads PWA campaigns targeting Turkish users. For app publishers with scaled Turkey acquisition programs, this represents a significant opportunity to improve campaign efficiency without changing creative strategy or audience targeting.
5-Step Budget Migration: Moving from Meta to Google Ads PWA Install Campaigns
Migrating budget from Meta to Google Ads PWA campaigns requires deliberate planning to maintain acquisition volume while optimizing for lower costs. Here is a structured five-step approach to executing this migration effectively.
Step 1: Audit Your Current Meta Spend by Market and Identify DST Exposure
Before shifting any budget, you need to quantify your actual DST surcharge burden. Export your Meta Ads billing statements for the past three months and identify the line items related to digital services tax surcharges in each affected market. Calculate the total surcharge cost as a percentage of your total Meta spend. This gives you a clear dollar figure representing the “tax drag” on your current campaigns — and a baseline for evaluating the economic case for migration.
Pay particular attention to markets with higher surcharge rates (Turkey at 7.5%, and Spain, Italy, France at 3%). If these markets represent 30% or more of your Meta spend, you likely have a compelling case for budget reallocation.
Step 2: Set Up Your PWA Infrastructure Before Shifting Spend
Do not migrate budget before your PWA install flow is live and validated. This means ensuring your PWA is accessible at a clean URL, that the install prompt triggers reliably on target Android devices, and that your attribution tracking is connected to your preferred MMP (Mobile Measurement Partner) or Google Ads conversion tracking.
Using a platform like ROiBest simplifies this step significantly — you get a production-ready PWA with built-in install tracking, push notification support, and no need to manage technical infrastructure yourself. Teams typically get their PWA live within 48-72 hours using this approach versus weeks of internal development.
Step 3: Launch Parallel Google Ads PWA Campaigns in DST Markets
Rather than cutting Meta spend immediately, run parallel campaigns for 2-4 weeks. Allocate a test budget of 15-20% of your current Meta spend in the target markets to Google Ads PWA campaigns. This gives you live performance data without sacrificing acquisition volume during the learning period.
Structure your Google Ads campaigns with the same audience signals you use on Meta where possible — age ranges, interest categories, and device targeting. This makes performance comparisons more apples-to-apples and helps you identify whether CPI differences are attributable to the channel or to audience variation.
Step 4: Compare Effective CPI Across Both Channels Including Surcharge Costs
After 2-4 weeks, pull your performance data from both channels. For Meta, calculate your effective CPI by adding the DST surcharge to your reported spend before dividing by install volume. For Google Ads PWA, use your reported spend directly (no surcharge adjustment needed for currently unaffected Google Ads markets).
Also compare downstream metrics: Day-7 retention, in-app event completion rates, and revenue per install. If your PWA users show comparable or better downstream behavior — which many teams report due to the self-selection effect of users who actively install a PWA — then the economic case for migration becomes even stronger.
Step 5: Execute Graduated Budget Shift Over 60-90 Days
Once you have validated performance parity or improvement in Google Ads PWA campaigns, execute a graduated budget shift. Move budget in 25% increments over 60-90 days, allowing each increment to stabilize before the next shift. This approach protects your total acquisition volume throughout the transition and gives the Google Ads algorithm time to optimize campaign delivery as budgets scale.
Maintain a residual Meta presence (10-15% of your original DST-market spend) for retargeting and audience building, where Meta’s social graph data retains unique value. The goal is optimization, not complete platform abandonment.
Beyond Cost Savings: The Strategic Case for PWA Distribution
The DST surcharge issue is a timely catalyst for evaluating PWA distribution, but the strategic case extends well beyond tax efficiency. App publishers running PWAs gain a distribution channel that is fundamentally more agile and cost-efficient than the native app model in several ways.
Push notifications from PWAs continue to work even after a user uninstalls the app from their home screen — a capability that native Android apps do not retain post-uninstall. This means your re-engagement capacity is preserved even when users remove your icon from their devices, giving you a longer effective customer lifetime without additional acquisition cost.
PWAs also allow instant updates without app store review cycles. If a regulatory change, market event, or competitive shift requires you to update your product quickly, PWA lets you push changes immediately. Your marketing campaigns stay synchronized with your product without the 24-72 hour (or longer) lag imposed by Play Store review processes.
For teams operating in multiple markets simultaneously — exactly the type of teams most exposed to Meta’s DST surcharges — this agility compounds over time into a meaningful competitive advantage. Get started with evaluating PWA as a distribution channel before your competitors lock in the efficiency gains first.
Frequently Asked Questions
Do all Meta ad accounts pay DST surcharges?
DST surcharges apply based on the geographic targeting of your campaigns, not your account’s billing address. If your campaigns target users in France, UK, Italy, Spain, Turkey, or other DST-affected markets, the corresponding surcharge will appear on your Meta billing invoices regardless of where your business is registered.
Does Google Ads have similar DST surcharges?
Google handles its digital services tax obligations differently from Meta. As of 2026, Google Ads does not apply the same type of advertiser-facing DST surcharges that Meta has implemented. This is subject to change as tax legislation evolves, but currently represents a meaningful cost differential for advertisers evaluating channel allocation decisions.
Can PWA install campaigns scale to the same volumes as native app campaigns?
Yes. PWA install campaigns on Google Ads use the same bidding algorithms and targeting capabilities as other Google Ads campaign types. Teams using ROiBest have reported reaching acquisition volumes equivalent to their prior native app campaigns within 4-8 weeks of launch, while achieving the CPI efficiency gains described in this article.
How does attribution work for PWA installs?
PWA install attribution uses web-based tracking rather than SKAdNetwork or app-level attribution frameworks. This means you typically get more complete attribution data — not subject to the privacy-related measurement restrictions that affect native iOS and Android attribution. Your MMP can track PWA installs using standard web attribution methods, and Google Ads conversion tracking integrates natively with PWA install events.
Conclusion: Tax-Driven Incentives to Diversify Your Channel Mix
Meta’s DST surcharges — 3% in France, 2% in the UK, 3% in Italy, 3% in Spain, and 7.5% in Turkey — represent a structural, ongoing cost increase for advertisers in these markets. Unlike creative fatigue or auction competition, these surcharges are not addressable through optimization within the Meta platform. They require a channel-level strategic response.
Google Ads PWA install campaigns offer a compelling alternative: no DST surcharges, no Google Play revenue cut, faster deploy cycles, and conversion efficiency that frequently matches or exceeds native app install campaigns. The five-step budget migration framework outlined in this article provides a practical path to reallocating spend without disrupting acquisition volume.
For teams ready to get started, ROiBest provides the infrastructure layer that makes PWA deployment practical without requiring internal technical resources. The economic case — particularly in high-surcharge markets like Turkey — is now clear enough that waiting represents a measurable ongoing cost to your business.
Skip the app store. Go live instantly, keep 100% of your revenue.
ROiBest helps Android app teams launch PWAs — no review process, no 30% Google Play cut, and push notifications that work even after uninstall. Teams see up to 1.2x higher install conversion rates vs native app downloads.
发表评论