Starting July 1, 2026, Meta is passing Digital Services Tax costs directly to advertisers — adding 2% to 5% surcharges on every impression served in Austria, France, Italy, Spain, Turkey, and the United Kingdom. For teams running large-scale user acquisition campaigns across European markets, this is not a rounding error. On a $100K monthly Meta spend targeting France and Italy, you are now looking at an extra $3,000 that buys zero additional reach. The surcharge sits on top of your budget, not inside it, which means your effective CPA just rose by the same percentage — with no improvement in performance.
This article breaks down exactly what Meta’s location fees mean for ad budgets, why Google Ads paired with PWA install campaigns offers a structurally cheaper alternative, and how to launch your first Google Ads PWA campaign to reclaim margin that Meta is quietly taking away.
→ Want to bypass Google Play entirely? See how ROiBest PWA works — no submission, no cut, 1.2x installs.
Meta’s Digital Service Tax: What It Means for Ad Budgets
In March 2026, Meta emailed advertisers a notice that most initially skimmed past: beginning July 1, the company will add “location fees” to ad invoices whenever impressions are delivered in countries that levy a Digital Services Tax (DST). These fees are not optional. There is no toggle in Ads Manager to turn them off. They apply based on where your ads are shown — not where your business is incorporated.
The Country-by-Country Breakdown
Here are the surcharge rates Meta is imposing:
- Austria — 5% location fee
- Turkey — 5% location fee
- France — 3% location fee
- Italy — 3% location fee
- Spain — 3% location fee
- United Kingdom — 2% location fee
These are not taxes that you owe to governments. They are fees Meta charges you to offset the taxes Meta itself owes. On a $50,000 monthly spend targeting UK audiences, that is an additional $1,000 every month. Targeting France, Italy, and Spain simultaneously? Add 3% across all three markets. For a team spending $200K/month on European user acquisition through Meta, the annual impact easily exceeds $70,000 — money that generates no additional impressions, clicks, or installs.
The Expansion Risk
Six countries are on the list today, but Belgium, the Czech Republic, Latvia, Norway, Slovakia, and Slovenia have all announced intentions to implement their own DSTs. When those taxes take effect, Meta has signaled it will extend location fees to those markets as well. This is not a one-time adjustment — it is a structural trend that will make Meta advertising progressively more expensive across Europe.
How Location Fees Actually Hit Your P&L
The critical detail many advertisers miss: location fees are billed separately from your campaign budget. If you set a $10,000 daily budget and your ads serve in Italy, you do not spend $10,000. You spend $10,000 plus $300 in location fees, plus VAT on the combined total. Your financial models, ROAS targets, and CPA benchmarks all need recalculating. A campaign that was marginally profitable at a $12 CPA on Meta may now be underwater once the 3–5% surcharge is factored in.
Why Google Ads + PWA Is the Cost-Efficient Alternative

Google Ads does not currently impose location-based DST surcharges on advertisers in the same way Meta does. While Google has its own regulatory cost structures, the absence of a blanket 2–5% fee on European impressions creates an immediate cost advantage for teams willing to diversify their channel mix.
But the cost advantage goes deeper when you pair Google Ads with PWA (Progressive Web App) distribution instead of traditional Google Play app installs.
Cost Advantage 1: No DST Surcharge on Impressions
When you run a Google Ads PWA install campaign, your impressions in France, Italy, Spain, Austria, Turkey, and the UK are not subject to Meta’s 2–5% location fee. That alone saves $20,000–$50,000 annually on a mid-six-figure European ad budget. The savings compound as more countries adopt DSTs and Meta extends its fee schedule.
Cost Advantage 2: No 30% App Store Commission
Traditional Google Play installs mean Google takes a 30% cut (or 15% for the first $1M under the reduced rate program) on every in-app purchase and subscription. PWAs bypass the app store entirely. Users install directly from the web — no Play Store listing, no review process, no revenue share. For an app generating $500K in annual revenue, that is $150K retained instead of sent to Google. Combined with DST savings from avoiding Meta, the total margin recovery is substantial.
Cost Advantage 3: Better Attribution and Lower CPA
Meta’s attribution has been degrading since iOS 14.5, and the situation has not improved in 2026. Modeled conversions, limited event matching, and shrinking attribution windows make it harder to optimize campaigns toward true install value. Google Ads, particularly through Performance Max campaigns and Universal App Campaigns (UAC), offers more deterministic conversion tracking for PWA installs because the entire journey — from ad click to PWA install to first open — happens within the Google ecosystem.
Teams using Google Ads instead of Meta for PWA tracking report tighter feedback loops between spend and measurable outcomes. When you can see which keywords, placements, and audiences actually drive installs — not modeled estimates — you can cut waste faster and push budget toward what works.
Cost Advantage 4: First-Party Data Integration
Google’s Customer Match lets you upload hashed email lists and phone numbers to target existing users or build lookalike audiences directly within Google Ads. For PWA campaigns, this means you can retarget users who visited your PWA but did not complete a key action — without depending on third-party cookies or Meta’s increasingly restricted pixel data. First-party data campaigns on Google consistently deliver 20–40% lower CPAs compared to broad targeting because you are reaching people who have already demonstrated intent.
The CPI Comparison
Current 2026 benchmarks show Android app install CPIs averaging $1.92 on Google Ads, up 8% year over year. iOS CPIs are significantly higher at $5.84. PWA installs, however, bypass the app store friction entirely — no Play Store listing page, no competing apps shown alongside yours, no “similar apps” carousel pulling users away. Teams running PWA install campaigns through Google Ads report install conversion rates up to 1.2x higher than native app downloads, which directly translates to a lower effective CPI.
How to Launch Google Ads PWA Campaigns
Shifting budget from Meta to Google Ads for PWA distribution is not a weekend project, but it is not a six-month migration either. Here is the step-by-step process to get your first campaigns live.
Step 1: Set Up Your PWA for Install Tracking
Before you can run install campaigns, your PWA needs to fire conversion events that Google Ads can track. Work with your PWA provider (ROiBest handles this end-to-end) to implement:
- A service worker that enables the “Add to Home Screen” prompt
- Web push notification permissions requested post-install
- Google Tag Manager (GTM) or gtag.js firing a conversion event when the PWA is added to the home screen
- Enhanced conversions enabled in your Google Ads account for better match rates
The conversion event is the foundation of everything. Without it, Google Ads cannot optimize toward installs, and your campaigns will underperform.
Step 2: Build Your Campaign Structure in Google Ads
For PWA installs, you have three primary campaign types to evaluate:
- Performance Max (PMax) — Google’s fully automated campaign type that serves across Search, Display, YouTube, Discover, and Gmail. PMax works well for PWA installs because it optimizes across all Google surfaces simultaneously, finding the cheapest install wherever it exists. Start here if you want maximum reach with minimal manual management.
- Universal App Campaigns (UAC) — Traditionally used for Play Store installs, UAC can be adapted for web app installs by using web conversion actions. This requires some configuration but gives you access to Google’s app install optimization algorithms.
- Search + Display campaigns — For more granular control, run separate Search campaigns targeting high-intent keywords (e.g., “[your app category] app,” “[competitor] alternative”) and Display campaigns for broader awareness. This approach requires more hands-on management but lets you allocate budget precisely.
Set your target CPA based on the benchmarks above — $1.50–$2.50 is a reasonable starting range for Android PWA installs in most verticals. Begin with a daily budget of at least $50–$100 to give Google’s algorithms enough data to optimize.
Step 3: Upload First-Party Audiences
Do not rely solely on Google’s broad targeting out of the gate. Upload your existing customer lists through Customer Match to create:
- Retargeting audiences — Users who visited your landing page or PWA but did not install
- Lookalike (Similar) audiences — Based on your highest-value existing users
- Exclusion lists — Current subscribers or users who already installed, so you do not waste budget on existing customers
First-party data seeding is especially powerful in the first two weeks of a new campaign, when Google’s algorithms have limited conversion data to work with.
Step 4: Allocate Budget Strategically Across Markets
Here is where the Meta DST savings become actionable. Calculate your current Meta spend in DST-affected countries and model the surcharge impact:
- If you spend $30K/month on Meta ads in France + Italy + Spain → $900/month in location fees ($10,800/year)
- If you spend $20K/month targeting Austria + Turkey → $1,000/month in location fees ($12,000/year)
- If you spend $50K/month on UK audiences → $1,000/month ($12,000/year)
Take even 30–50% of that DST-affected Meta budget and redirect it to Google Ads PWA campaigns targeting the same markets. You immediately save the 2–5% surcharge, and you gain the attribution and app store commission benefits described above.
Step 5: Optimize Creative for PWA Install Intent
PWA install ads require different creative messaging than traditional app download ads. Your creative should emphasize:
- Instant access — “No download required, open instantly from your home screen”
- Speed — PWAs load in under 2 seconds on most connections vs. multi-minute app store downloads
- No storage concerns — PWAs typically use less than 5MB vs. 100MB+ for native apps
- Full functionality — Push notifications, offline access, same experience as a native app
Test at least 3–5 creative variations in each campaign, including both static images and short video (15-second format works well for YouTube placements in PMax campaigns).
Ready to shift budget from Meta to Google Ads PWA? ROiBest handles the full technical setup — PWA build, install tracking, push notifications — so your team can focus on campaign optimization. Talk to the team.
Summary + Action Checklist
Meta’s Digital Services Tax location fees are a structural cost increase that will only expand as more countries adopt DSTs. For Google Ads buying teams running European user acquisition, the combination of Google Ads and PWA distribution offers a triple cost advantage: no DST surcharges, no 30% app store commission, and better attribution for lower CPAs.
Here is your action checklist:
- Audit your Meta spend — Calculate how much you are spending on impressions in Austria, France, Italy, Spain, Turkey, and the UK. Multiply by the applicable surcharge rate (2–5%) to quantify your annual DST exposure.
- Model the Google Ads alternative — Use current Android CPI benchmarks ($1.50–$2.50 for most verticals) to estimate what the same install volume would cost on Google Ads without the DST surcharge.
- Set up PWA install tracking — Implement conversion events for “Add to Home Screen” actions so Google Ads can optimize toward real installs.
- Launch a test campaign — Start with PMax or UAC targeting one DST-affected market (UK is a good starting point given the lower 2% rate and large English-speaking audience). Run for 14 days with a $1,500–$3,000 budget.
- Upload first-party audiences — Use Customer Match to seed your campaigns with high-value user profiles from day one.
- Compare CPA and ROAS — After 14 days, compare Google Ads PWA CPA (including all costs) vs. Meta CPA (including DST surcharges). Adjust budget allocation based on results.
- Scale winning campaigns — Once you have a CPA-positive campaign on Google Ads, increase daily budgets by 20% weekly and expand to additional DST-affected markets.
The teams that move fastest on this shift will lock in cheaper CPIs on Google Ads before competition from other Meta refugees drives costs up. The DST surcharges are not going away — but your dependence on Meta does not have to stay.
For a complete walkthrough of PWA install campaign setup, read the Google Ads PWA Install Campaign Guide.
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.



发表回复