Google Play’s New Link-Out Fees Change the Math for Web-First Apps
For web-first companies, sending an Android user to the web has often looked like the cleanest route around app-store complexity. The product can live at one URL, checkout can use the company’s own stack, and an installable web app can keep the customer relationship close to the open web.
Google Play has now put a price and a reporting obligation on part of that journey. In an update published on July 22, Google said participants in its US external content links program must begin reporting qualifying transactions and successful downloads—and paying the applicable Play service fees—on October 1, 2026.
This is not a new browser restriction, and it is not a fee on ordinary PWA installation. It is a distribution rule for Play-listed Android apps that send users to websites or external app downloads. That distinction is precisely why founders using native shells, Android wrappers, or Trusted Web Activities around web products should pay attention.
What Google changed
Google’s external content links program lets a Google Play-distributed app serving US users link outside the app for two purposes: purchasing in-app digital items or downloading an app whose installation and updates are not managed by Google Play.
The program is optional. A developer that does not offer those links does not need to join it. But participating apps must enroll, integrate Google’s external links APIs, present Google’s information screen before the user leaves, and comply with registration, reporting, support, refund, and destination requirements.
From October 1, qualifying activity completed within 24 hours after a user follows an external content link can generate fees:
- Recurring subscriptions: Google’s published table lists a 10% service fee.
- Other digital offers: the standard published rate is 20%, with lower rates applying in specified earnings tiers or experience programs.
- External app installations: Google lists a fixed fee of $2.85 for an app and $3.65 for a game.
Google says those fixed install charges are subject to periodic adjustment. It also draws a useful boundary around app-download links: when a user follows a link to install an external app, Google assesses the fixed download fee rather than adding a transaction fee for purchases arising from that same initial link-out. A later transaction link initiated from the downloaded app is assessed separately.
This is not a tax on browser-installed PWAs
The narrow scope matters. Google’s policy applies when the journey begins inside an eligible Play-distributed mobile or tablet app or game. It does not say that opening a website, installing a PWA from a browser, or buying directly on a website independently triggers these Play fees.
A pure web acquisition path therefore remains different. If someone discovers a service through search, a direct link, a campaign, or a browser and then installs its PWA, the Google Play external content links program is not the source of that journey.
The calculation changes when a company uses Google Play as the front door. A web-first product might publish an Android wrapper or Trusted Web Activity to gain store discovery, reviews, familiar installation, and a launcher presence. If that Play-distributed package then sends the user to web checkout or an external APK, the link-out can fall inside Google’s program.
In other words, the underlying product can still be built with web technology while its acquisition route is governed by store economics. The web destination does not automatically make the journey store-independent.
Why the 24-hour window matters
The most consequential detail is not simply the percentage. It is attribution. Google says fees apply when a qualifying transaction or external installation is completed within 24 hours of following the link.
That creates a new measurement boundary for product and finance teams. A checkout may happen in the company’s browser experience, use the company’s payment provider, and be supported by the company, yet still produce a Play service fee because the user arrived through the enrolled Android app.
The fixed download fees can be especially important for products with low customer value. A $2.85 charge may be manageable for a high-retention business app but difficult for a free utility, a low-margin companion app, or a portfolio that relies on large numbers of experimental installs. Teams need to model the fee against activation and lifetime value rather than treating every off-Play download as free distribution.
There is operational cost too. Participants must track and report covered activity, including specified zero-value events such as free trials. External apps and their updated APK versions must be registered and approved before links can point users to them. This is not merely a new button in the Play version of an app; it is a policy, backend, and support workflow.
The trust layer comes with conversion friction
Google requires an information screen before a user is directed outside the Play app. External download destinations must disclose details including the app name, icon, description, version, download size, and developer information. They must provide accessible support, user-data policies, explicit user-controlled installation, and evidence that they have the right to distribute the listed software.
Those controls address a real trust problem. A link that moves someone from a vetted store app to an unfamiliar download page can expose the user to impersonation, misleading redirects, or unsafe packages. Google also prohibits deceptive destinations and requires protection for personally identifiable information included in external URLs.
But every trust screen and transition can affect conversion. Web-first teams should test the entire experience: the in-app call to action, Google’s disclosure, the browser destination, authentication continuity, payment, installation, and the return path. A technically compliant funnel can still feel fragmented compared with a direct browser journey or an in-app purchase.
What PWA and web-first teams should do now
- Map the actual entry points. Separate users acquired directly on the web from users entering through a Play-distributed package.
- Model the 24-hour attribution window. Estimate fees using real conversion timing, subscription mix, install volume, and customer lifetime value.
- Audit every external destination. Confirm that landing pages, linked packages, disclosures, privacy handling, support, and refund processes meet the program’s requirements.
- Revisit wrapper strategy. Compare the incremental discovery and trust supplied by Play with the fees and operational work attached to link-outs.
- Preserve a direct web channel. Search, sharing, account recovery, browser installation, and owned marketing remain strategically different from a store-originated journey.
The strategic payoff
The lesson is not that web-first companies should abandon Google Play. Store presence can still be valuable, and a Play package can complement an installable web app. The lesson is that distribution architecture is now part of unit economics.
A founder deciding between a direct PWA, a Trusted Web Activity, a fuller native shell, or a combination of all three is not choosing presentation alone. The choice determines who controls discovery, which trust layer the customer sees, what reporting must exist, and which fees can follow the user onto the web.
Qué vigila IndApp a continuación
The October 1 start will show how Google applies the reporting and fee system in practice. The program exists in connection with a US court order, and Google explicitly says its availability and terms may change if the legal position changes.
IndApp will also watch whether Google adjusts the fixed install charges, how consistently external packages are reviewed, how the disclosure screen affects conversion, and whether Play-listed web wrappers receive clearer implementation guidance.
The open web is still an independent distribution channel. But when a Play app sends the customer there, the path now carries its own meter. Web-first teams should design for that boundary before October—not discover it in their first fee report.
Lectura adicional
Noticias recientes
