“How do I put ads on my Lovable app” has two meanings, and Lovable supports neither natively. If you mean running paid campaigns to get users, Lovable has no Meta or Google Ads integration; you build the campaign in the ad platforms or through an agent. If you mean showing ads inside your app to earn revenue, that is an ad network SDK (Google AdSense for web) that you add to the generated code. This guide covers the first meaning, which is what almost everyone asking wants.
Lovable is a prompt-to-app builder that generates a React front end with a Supabase-backed cloud (the Base44 vs Lovable comparison covers the backend in depth). It publishes to a lovable.app subdomain or a custom domain, and it will edit the generated code when you ask, which is all you need for a pixel. Everything after the pixel is the ads stack, and this is the setup.
What Lovable supports natively
Lovable’s documentation, checked on September 4, 2026, gives you these building blocks and stops there:
Lovable does
- Publishing on a custom domain. Connect your own domain from project settings; Meta and Google both verify and track against it.
- Editing the generated code by prompt. Ask Lovable to add a script to
index.htmlor the app shell and it will, which is how the Meta pixel and Google tag get in. - Supabase backend. Signups, trials and purchases are rows you control, so the campaign that acquired each user can be stored next to the user.
- Edge functions with secrets. Where a server-side conversion event (Meta Conversions API, Google enhanced conversions) can live.
- GitHub sync. The pixel and event code are ordinary code in your repository, so they survive rebuilds and can be reviewed.
Lovable does not
- Create or manage ad campaigns on Meta, Google, TikTok or LinkedIn.
- Install tracking pixels automatically or manage consent for them.
- Sync a product catalogue to Meta or Google Merchant Center.
- Report on ad spend or performance.
So Lovable hands you a published app with a database you control, and stops. The ads side is Meta Ads Manager and Google Ads by hand, or an agent such as Sprites that runs both through the official APIs against the app you just shipped.
How to run Meta and Google ads for a Lovable app
One setup covers both platforms; where Meta and Google differ, the step says so. Do it in order: a campaign launched before the conversion event fires wastes its first week.
1. Publish the app on a custom domain
Connect your domain in Lovable’s project settings and publish. A lovable.app subdomain works for testing, but Meta domain verification, Google Ads conversion linking and your own brand all want a domain you own. Check the published site over HTTPS on mobile, because that is where most paid traffic arrives.
2. Set up the ad accounts
For Meta: a business portfolio, an ad account with billing, a Facebook Page and, for Instagram placements, a connected Instagram account; verify the domain under Brand Safety and Suitability. For Google: a Google Ads account, billing, and a linked Google Analytics 4 property or a Google tag for conversions. Both take minutes; the approval and payment-method checks are what add a day, so do this first.
3. Add the pixel and the Google tag to the app
Create a Meta dataset in Events Manager and a Google tag (or GA4 property) in Google Ads. Prompt Lovable to add both snippets to index.html so they load on every route, then confirm with the Meta Pixel Helper and Google Tag Assistant on the published domain. Because Lovable apps are single-page, ask for the page-view events to re-fire on client-side navigation.
4. Fire a conversion event on signup
On the success state of your signup, trial or checkout, fire CompleteRegistration (or StartTrial, Purchase) for Meta and a conversion event for Google. For match quality that survives browser limits, mirror the event from a Supabase edge function to the Meta Conversions API and Google enhanced conversions with the user’s hashed email and a shared event ID. Mark the events as conversions in each platform. If you hand the setup to Sprites, this is the step it does during onboarding, browser and server side, and verifies before launch.
5. Store the acquiring campaign on the user
Have the landing page read UTM parameters and the Meta and Google click IDs (fbclid, gclid) and write them to the user row in Supabase at signup. Ads Manager and Google Ads will tell you cost per signup; this tells you which signups became active or paying users, which is the number that decides what to scale.
6. Build the campaigns
Meta: a Leads or Sales objective on the conversion event, Advantage+ placements, broad targeting in launch markets, three to five creatives that show the app in use (a screen recording beats a stock image every time). Google: a Search campaign on the problem your app solves, with a handful of exact and phrase keywords, responsive search ads with your app’s specific claims, and the conversion from step 4 as the bidding goal; add Performance Max only after Search has data. See what the category already runs in the Lovable ads library and the Base44 ads library before writing, or let Sprites do the research and draft both campaigns to this structure for your approval.
7. Run the weekly loop
Each week: pause the creative with the worst cost per activated user, move budget to the ad set or keyword with the best, add negative keywords from the Google search-terms report, and refresh one creative. That loop, not the launch, is what makes ads work for an app, and it is the part that is worth automating.
Where automation takes over
The first five steps are a one-time setup. The last two are a standing job, and for a solo founder or a two-person team it is the job that gets skipped, which is why so many Lovable apps run one campaign for a month and conclude that ads do not work.
Sprites connects to your Meta and Google ad accounts through the official partner APIs, sets up the pixel and conversion event on the published domain, researches the category (including the ads your competitors are running, from the ads library), drafts copy and creative to spec, builds the campaign, and then runs the weekly optimisation loop: budgets, audiences, creative rotation, negative placements. Every change is proposed with its reasoning and waits for your approval, so the app builder stays your build tool and the agent becomes your media buyer.
Frequently asked questions
Can Lovable run ads for my app?
No. Lovable builds and hosts the app and will edit its code, but it has no integration with Meta, Google or any ad platform. Campaigns are created in the ad platforms or through an ad automation agent such as Sprites.
How do I add the Meta pixel to a Lovable app?
Create a dataset in Meta Events Manager, copy the base code, and prompt Lovable to add it to index.html so it loads on every route. Verify with the Meta Pixel Helper on the published domain, then fire a standard event such as CompleteRegistration on your signup success state.
Can I show ads inside my Lovable app to make money?
Yes, with an ad network rather than Lovable itself. For a web app that means applying to Google AdSense (or a network like Ezoic or Mediavine once traffic is high enough) and prompting Lovable to add the network’s script and ad slots to the pages you choose. Most networks require an approved domain and content that meets their policies.
Should I use Meta or Google Ads for a Lovable app?
Google Search if people already search for the problem your app solves, because intent is highest and the conversion event makes bidding efficient quickly. Meta if the app is new-category or visual, because you can show it in use to people who did not know to search. Most apps end up running both, with Search catching demand and Meta creating it.
How much should I spend on ads for a Lovable app?
Enough to get 30 to 50 conversion events a week per campaign, which is what the platforms need to optimise. At a $10 cost per signup that is roughly $50 a day per campaign. Below that, results are noise; better to run one campaign properly than three thinly.
Does Sprites work with Lovable apps?
Yes. Sprites uses the Lovable app as the destination, sets up the pixel and conversion events on the published domain, builds the Meta and Google campaigns and runs the weekly optimisation loop, with every change approved by you.