Base44’s Instagram integration is a content connector, not an ads integration. Through its OAuth connector system a Base44 app can connect an Instagram Business account to read media, insights and comments and to publish posts, and individual users of your app can connect their own accounts. Creating a Meta ad campaign, installing the pixel on the published domain and optimising spend all happen outside Base44, in Meta Ads Manager or in an ad automation agent that drives it.
That is not a gap so much as a boundary. Base44 is a vertically integrated app builder: database, auth, backend functions, realtime, connectors and hosting in one place (the Base44 vs Lovable comparison goes into the architecture). Paid acquisition for the app you built is a different job with different tools. This guide covers exactly what Base44 does natively, then the full setup for Instagram and Meta ads, then the point where automation makes sense.
What Base44 supports natively
Base44’s public documentation and connector catalogue, checked on September 4, 2026, put the line here:
Base44 does
- Instagram Business connector. An OAuth connection to an Instagram Business or Creator account for reading profile data, media, insights and comments, and for publishing posts from inside your app.
- Per-user connections. Base44 distinguishes shared connectors (one account for the whole app) from app-user connectors, so each user of a social tool you build can connect their own Instagram.
- Custom domains and hosting. The published app runs on a Base44 domain or your own, which is the domain Meta will verify and the pixel will fire on.
- Backend functions and automations. Server-side code with secrets, which is where a server-side conversion event (Meta Conversions API) can live if you need one.
- Zapier and webhooks. For pushing signups or purchases from the Base44 database to a CRM, a sheet or an ads tool.
Base44 does not
- Create, edit or launch ad campaigns, ad sets or ads in Meta Ads Manager.
- Install or manage the Meta pixel for you; it goes into the app like any other script.
- Sync a product catalogue to Meta Commerce Manager for catalogue ads.
- Report ad performance; spend, CPA and ROAS live in Ads Manager.
In short: Base44 gets you the app, the domain, the signup event and, if you want it, organic Instagram publishing. Everything from the pixel onward is the ads stack, whether that is Ads Manager by hand or an agent such as Sprites driving it through the official API.
How to run Instagram and Meta ads for a Base44 app
The setup below takes an afternoon the first time. It assumes the app is built and you have a Meta account; every step is the same whether you do it by hand or hand it to an agent.
1. Publish the app on a custom domain
Publish from Base44 and connect a domain you control (for example app.yourbrand.com or the marketing site’s domain). Meta ties pixels, domain verification and link ownership to a registered domain, and a shared builder subdomain makes verification and Aggregated Event Measurement awkward. Confirm the site loads over HTTPS before moving on.
2. Set up the Meta business assets
In Meta Business Suite create or open your business portfolio, add an ad account with a payment method, and connect the Instagram Business account you want ads to run from (Instagram placements require a connected Instagram account or a Facebook Page to represent you). Under Brand Safety and Suitability, verify the domain from step 1 with the meta-tag or DNS method.
3. Install the Meta pixel in the Base44 app
Create a dataset (pixel) in Events Manager and copy the base code. Base44 generates a React app, so ask the builder to add the pixel snippet to the app shell so it loads on every route, then open the published app with the Meta Pixel Helper extension and confirm a PageView fires. If your app is a single-page app, make sure the PageView is re-sent on route changes. This is the check most first campaigns skip; Sprites runs it on the published domain before it spends anything.
4. Define the conversion event
Decide what a paid click should produce: a signup, a trial start, a purchase. Fire a standard event (CompleteRegistration, StartTrial, Purchase) from the Base44 page where that happens, for example on the success state of your signup form. For stronger matching, send the same event from a Base44 backend function through the Conversions API with a shared event ID, so browser and server copies deduplicate. Mark the event as your conversion in Events Manager.
5. Build the landing path inside the app
Paid traffic should land on a page that explains the app in one screen and has a single action, not the logged-out home of a workspace. Build a dedicated landing route in Base44 with the pitch, a screenshot or short recording, and the signup form. Capture UTM parameters into the signup record so every user in your Base44 database carries the campaign that acquired them; that is the report Ads Manager cannot give you.
6. Create the campaign in Ads Manager
Choose the Leads or Sales objective with website conversions, select the pixel and the event from step 4, and let Advantage+ placements include Instagram Feed, Stories and Reels. Start with a broad audience in your launch markets and a modest daily budget; let the pixel data narrow it. Write three to five headline and primary-text variants and upload creative in 1:1 and 9:16. Before you write from scratch, look at what the category is already running in the Base44 ads library and the Lovable ads library; the hooks that have run longest are the ones that work. This is also the step an agent builds for you: give Sprites the event from step 4 and the landing route from step 5 and it drafts the campaign, copy and creative to this structure for approval.
7. Launch, then read results in two places
Ads Manager tells you cost per result on the pixel event. Your Base44 database, with the UTM fields from step 5, tells you which of those signups activated and paid. Compare the two weekly. The first week is about whether the event fires and the creative gets clicks; from week two the question is cost per activated user by ad, which is what to scale.
Where automation takes over
Steps 1 to 5 are done once. Steps 6 and 7 repeat every week for as long as the campaign runs, and they are where most founders on an app builder stall: the campaign launches, the first creative fatigues, budget sits on the wrong ad set, and nobody has the hours to keep optimising.
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
Does Base44 integrate with Instagram?
Yes, for content. Base44 has an Instagram Business connector that lets your app read media, insights and comments and publish posts, either from one shared account or from each user’s own account. It does not create or manage Instagram ads.
Can I run Meta ads from inside Base44?
No. Base44 has no Meta Ads integration. Campaigns are built in Meta Ads Manager or by an ad automation agent such as Sprites that drives Ads Manager through the official API. Base44’s role is the app, the domain, the pixel placement and the conversion event.
How do I add the Meta pixel to a Base44 app?
Create a dataset in Meta Events Manager, then ask the Base44 builder to add the pixel base code to the app shell so it loads on every route. Verify with the Meta Pixel Helper on the published domain, and fire a standard event such as CompleteRegistration on your signup success state.
Can Base44 send conversions server-side?
Yes. Base44 backend functions can call external APIs with encrypted secrets, so a signup handler can post the event to the Meta Conversions API with the same event ID as the browser pixel, which improves match quality and survives browser tracking limits.
What should a Base44 app’s first Meta campaign look like?
A Leads or Sales objective on the pixel conversion, Advantage+ placements including Instagram Feed, Stories and Reels, broad targeting in your launch markets, a modest daily budget and three to five creative variants that show the app itself. Scale on cost per activated user, not cost per click.
Does Sprites work with Base44 apps?
Yes. Sprites treats the Base44 app as the destination: it sets up the pixel and event on the published domain, researches the category, builds the Meta and Google campaigns and runs the optimisation loop, with every change approved by you.