Facebook ads for SaaS: optimize for customers, not signups
Run Facebook ads for a SaaS or B2B product: pick the event Meta optimizes on, send trials and payments back, and judge campaigns by paying customers.
By DATALYR · · 4 min read
Contents
What makes Facebook ads work for SaaS
Facebook ads work for SaaS when Meta optimizes toward an event that predicts a paying customer and that event reaches Meta reliably. A campaign told to find signups will find people who sign up; whether they ever pay is a separate question the campaign cannot answer unless you send it the answer.
So the practical work is choosing the deepest event that still happens often enough for delivery to learn from, then making sure the event comes from the system that actually knows it happened. For a self-serve product that is usually a trial start or the first payment. For a B2B product sold through a sales call, it is a booked demo or a qualified lead.
The same logic covers 'Meta ads for SaaS' and 'Facebook ads for B2B'. Instagram placements run through the same Meta campaign and receive the same conversion signal.
Choose the event Meta optimizes on
Meta's standard events already describe a subscription funnel. CompleteRegistration marks a finished signup, StartTrial marks the start of a free trial, Subscribe marks the start of a paid subscription, and Purchase marks a completed payment. Lead and Schedule cover form submissions and booked meetings. StartTrial and Subscribe accept a value, a currency and a predicted lifetime value.
Deeper events carry better information but arrive less often. If a campaign produces only a handful of first payments a week, optimizing on payment may leave delivery with too little to learn from. DATALYR's lead-generation guide uses a simple rule of thumb: optimize on the earlier stage while the later stage has fewer than about 50 a week, and move deeper as volume proves out.
Whatever you choose, keep the event definition stable. Switching the optimization event every week resets what the campaign is learning and makes week-over-week comparisons meaningless.
Three events, three questions
1. Signup
CompleteRegistration
Which ads produce accounts. Highest volume.
2. Trial start
StartTrial
Which ads produce intent to evaluate.
3. First payment
Subscribe or Purchase
Which ads produce customers. Lowest volume.
Example: cheaper signups, fewer customers
This is a hypothetical example. Two campaigns each spend $4,500 in a month on a product priced at $49 a month.
Campaign A produces 600 signups, so it costs $4,500 ÷ 600 = $7.50 per signup. Thirty of those accounts start paying, so its media cost per paying customer is $4,500 ÷ 30 = $150. Campaign B produces 300 signups at $15 each, but 45 accounts start paying, so its cost per paying customer is $4,500 ÷ 45 = $100.
First-month revenue tells the same story. Campaign A's 30 customers pay 30 × $49 = $1,470, a first-payment ROAS of $1,470 ÷ $4,500 ≈ 0.33. Campaign B's 45 customers pay 45 × $49 = $2,205, or about 0.49. A signup-optimized report would scale Campaign A; a customer report would scale Campaign B.
Neither figure proves causality, and both cohorts will keep paying or churning after month one. The point is narrower: the event you report and optimize on decides which campaign looks like the winner.
Same spend, different winner
Campaign A
$7.50 per signup → $150 per customer
600 signups, 30 paying customers, $1,470 first-month revenue.
Campaign B
$15 per signup → $100 per customer
300 signups, 45 paying customers, $2,205 first-month revenue.
For B2B, optimize on the sales stage
A B2B product sold through demos has a longer gap between click and money. Most deals close weeks after the first visit, while Meta's delivery learns from conversions that arrive within days of the click. DATALYR's HubSpot setup reflects this: it suggests optimizing Meta on the qualified-lead stage because most deals close after Meta's 7-day window.
A booked call is often the best early signal for a sales-led funnel. It happens within minutes of the visit, it costs the prospect real effort, and booking tools such as Calendly and iClosed can report it from their own systems instead of a thank-you page.
If you run Meta Lead Ads with Instant Forms, Meta offers a separate route: the Conversions API for CRM with the Conversion Leads performance goal. Meta lists requirements for it, including at least 200 leads a month and a target stage that happens within 28 days of the lead.
Send the conversion from the system that knows
A browser thank-you page can fire twice, never load, or fire for a payment that later fails. A payment provider records the payment itself. For a SaaS product billed through Stripe, the first successful payment is the most reliable new-customer signal you have.
DATALYR receives Stripe payments, subscriptions and refunds, links each one to the web visit that started it, and sends the conversion to Meta through a rule. The link depends on the visitor ID reaching Stripe: the Web SDK does this for Stripe Checkout and Payment Links, and you add one field when you create PaymentIntents or Subscriptions yourself.
Keep renewals out of the rule that sends new customers. A renewal is the same customer billed again; sending it as a new purchase teaches the campaign to find people who already pay you.
Read results by paying customer
Ads Manager reports conversions inside Meta's attribution setting. Your billing system reports cash. Expect the two to differ and decide in advance which one settles a budget question.
In DATALYR, revenue comes from the connected payment source, and a renewal is credited to the campaign that acquired the customer. The Conversions column counts acquisitions only, so cost per conversion stays a cost per customer. Optional LTV and LTV ROAS columns show what each campaign's customers have paid to date.
Review campaigns on cost per paying customer and on cohort revenue, then use the cheaper top-of-funnel numbers to diagnose where a funnel leaks.
Related articles.
Conversion tracking ·
Meta Conversions API: setup, deduplication, and verification
Map a real conversion to the correct Meta destination, choose one delivery owner, and verify receipt separately from matching and attribution.
Use cases ·
Web app funnel tracking: connect ad clicks to paid accounts
Map a browser-based app journey from campaign visit to signup, activation, trial, and payment without confusing events with customers.
Measurement ·
CAC vs CPA: distinguish an action from a new customer
Use a worked acquisition funnel to compare cost per action with customer acquisition cost, including repeat purchases, sales costs, and conversion lag.
