Replit + Meta ads
If your audience lives on Facebook and Instagram, Meta Audience Network can be an alternative to AdMob. WebViewGold integrates the native Audience Network SDK: timed or page-triggered interstitials on iOS, banners and interstitials on Android, configured in Config.swift and Config.java and steered from your Replit app. Here is the setup, the privacy paperwork and where ad apps get rejected.
From $109 one-time per platform, or let our team do it all from $698.
Set useFacebookAds to true and enter your Placement ID in facebookAdsID (Config.swift). Show ads on a timer (useTimedAds with showFBAdsEveryNSeconds, 120 seconds or more recommended) or when a URL contains a trigger word from fbadstriggerurls, such as /thank-you/.
Set USE_FACEBOOK_ADS (it replaces AdMob), switch banner and full-screen ads on in Config.java, choose after how many clicks an interstitial appears (SHOW_AD_AFTER_X) and enter your Meta ad IDs in strings.xml.
On Android, disableads:// switches ads off for the current user and enableads:// back on, for example after a purchase recorded in Express/Flask/FastAPI backends with Replit Postgres or external databases. On iOS, use trigger-word ads and keep paying users away from those pages.
Personalized Meta ads need the App Tracking Transparency prompt. Your web app reads the answer as trackingDisabled after user-disable-tracking://, and ATTDeniedShowAds in Config.swift decides whether ads still appear after a "no".
Paste this into Replit to implement the web-app side. Review the result, publish, then test inside the WebViewGold app.
Prepare this Replit app for Meta Audience Network ads in the WebViewGold native wrapper. In the backend, expose GET /api/me with an is_premium flag from the Stripe subscription, and serve an app-ads.txt file from the site root with the lines I will paste from Meta Monetization Manager. In the React front end, add syncAds(isPremium) that, inside the Android app (navigator.userAgent contains my WebViewGold token and Android), navigates to disableads:// for premium users and enableads:// for free users, only when the state stored in localStorage changes. Add a route /summary that free users see after finishing a task (I will use /summary as the iOS trigger word) and let premium users skip it. Inside the iOS app, navigate once per session to user-disable-tracking:// and read window.trackingDisabled after 500 ms; skip analytics pixels if it is true. Update the privacy page to name Meta Audience Network as an advertising partner.
Great way of converting your web app to a native app! Fast turn-around, and a great way to get your apps into the app stores without the need to develop a full native app!
| Question | Meta Audience Network | AdMob |
|---|---|---|
| Formats in WebViewGold | iOS: interstitial. Android: banner and interstitial | Banner, interstitial and rewarded on both platforms |
| Before you can earn | Meta's current quick start requires a live App Store or Google Play listing to register the app in Monetization Manager | Ad units can be created before launch; AdMob reviews the app once it is listed in a store |
| How ads are sold | Bidding only; fill depends on Meta's demand for your audience and region | Google's ad demand |
| Rewarded ads | Not part of the documented Meta integration | displayrewardedad:// |
| Ad-free for premium users | Android: disableads://; iOS: trigger-word pages only | disableads:// and enableads:// (documented for Android) |
| Privacy work | ATT prompt, App Privacy, Data safety, ads declaration | The same, plus Google's consent form (askForAdConsent) |
A few hours, plus waiting for the store listing.
Meta's current Audience Network quick start says Monetization Manager registers properties only for apps with a live store listing, while the WebViewGold iOS docs note you can connect an unpublished app for testing. Plan for a two-step launch: ship version 1, then turn Meta ads on in an update.
In Monetization Manager, create a property, connect the iOS and Android apps and create the placements. Copy the Placement ID into facebookAdsID (iOS) and the ad IDs into strings.xml (Android).
Pick natural breaks in your Replit app (after a finished task, a completed quiz, a confirmation page) and give them their own URL, so trigger words match only there. Never on login, checkout, account deletion or while the user is typing.
Write a clear Privacy - Tracking Usage Description in Info.plist ("We use this to show you relevant ads, which keep the app free"), read trackingDisabled in your web app and never block features after a "no".
Per the iOS docs: a real iPhone (not the simulator), registered as a test device, with the Facebook app installed and logged in and Limit Ad Tracking disabled. Switch test mode off before the release, or real users see test ads.
App Store Connect: App Privacy with the data the Meta SDK collects (device ID, advertising data, product interaction, under "Data Used to Track You" when tracking). Google Play: "Contains ads", the Data safety form and the advertising ID declaration. Publish an app-ads.txt on your developer website if Monetization Manager shows you lines for it.
Call syncAds() whenever the plan changes and withTrackingDecision() before loading any pixel or attribution script. YourAppToken is your custom user agent.
var ua = navigator.userAgent;
var inApp = ua.indexOf("YourAppToken") !== -1;
var isAndroidApp = inApp && /Android/.test(ua);
var isIOSApp = inApp && /iPhone|iPad/.test(ua);
// Android: ads off for premium users, back on after a downgrade (only on change)
function syncAds(isPremium) {
if (!isAndroidApp) return;
var wanted = isPremium ? "off" : "on";
if (localStorage.getItem("adsState") === wanted) return;
localStorage.setItem("adsState", wanted);
window.location.href = isPremium ? "disableads://" : "enableads://";
}
// iOS: read the App Tracking Transparency decision once per session
function withTrackingDecision(callback) {
if (!isIOSApp) { callback(false); return; }
window.location.href = "user-disable-tracking://";
setTimeout(function () { callback(window.trackingDisabled === true); }, 500);
}
withTrackingDecision(function (denied) {
if (!denied) { loadMarketingPixels(); } // your own function; skip it entirely after a "no"
});Personalized Meta ads are tracking. Show the system prompt with a clear purpose string, respect a "no", never reward or require "Allow", and keep App Privacy consistent with the SDK.
Ads must suit the age rating, must not target sensitive data, and interstitials need an easy, visible close button. No display ads in widgets, extensions or notifications.
Name Meta Audience Network as an advertising partner, explain personalized ads and how to opt out, and link Meta's privacy policy.
Declare that the app contains ads, list the data types the Meta SDK collects (device or other IDs among them) and avoid interstitials that interrupt normal use, which Google treats as disruptive ads.
If children are part of your target audience, only ad SDKs certified for Google Play Families are allowed; check Meta's current status there before you enable it.
Meta's current Audience Network quick start says Monetization Manager registers properties only for apps with a live store listing, so most apps launch first and switch Meta ads on in an update. Test ads on registered test devices can run earlier; check the current flow in Monetization Manager.
On Android, USE_FACEBOOK_ADS replaces AdMob with Meta, so the documented setup is one network or the other. Test which one fills better for your audience and region; there is no built-in mediation between the two in the documented configuration.
For personalized ads on iOS, yes. Without permission, ads are less targeted and earnings usually drop, so write a clear purpose string and explain the trade-off before the system prompt. Android has no such prompt, but the Data safety form and the advertising ID declaration apply.
Use a real iPhone, register it as a test device in Monetization Manager, have the Facebook app installed and logged in, and disable Limit Ad Tracking, as the iOS docs describe. In production, fill depends on Meta's bidding, and new apps with little traffic often see low fill at first.
On Android, call disableads:// after the purchase reaches Express/Flask/FastAPI backends with Replit Postgres or external databases and enableads:// after a downgrade. On iOS, the documented Meta options are timed or URL-triggered interstitials, so switch timed ads off and show ads only on trigger pages that premium users never reach.
Same result, different amount of work on your side. All three come with the approval guarantee and 24/7 human support.
$109 per platform, one-time
The WebViewGold license: a finished Xcode or Android Studio project. Paste your URL, set name and icon, switch on features, build and submit. Free updates forever.
See plans on the main page$349 per license, one-time add-on
No Mac, no Xcode, no Android Studio: configure in the browser, we build both apps in the cloud and hand them to App Store Connect and the Play Console.
How the Cloud Builder works Try the free demo$698 per platform $798
Send us your URL and icon. Our team configures, builds and delivers your app within 72 hours, white-label, with source projects. Both platforms for $1,158.
Full Service details Powered by
Winter Sale prices valid until December 31, 2026.
App Store & Google Play approval guarantee – or your money back within 14 days
Rather hand it over? Full Service: we configure, build and deliver within 72 hours, from $698 per platform. Questions? Chat with us 24/7.
Refunds are granted under the conditions listed in our FAQ: a non-content rejection by Apple and/or Google, claimed within 14 days after purchase.