Scaling a dating app on Meta runs in a fixed order: permission, measurement, then budget. Meta allows dating ads only with prior written permission and an 18+ audience, and its public pages don't say how permission maps to ad accounts, so confirm coverage for each account before it spends. Optimize for the deepest event that still gives each ad set enough conversions to exit learning, often registration before trial or subscription. Measure iOS through Aggregated Event Measurement (AEM) or SKAdNetwork (SKAN) and web funnels through the pixel and Conversions API, keep creative free of fake profiles and implied matches, and judge campaigns on refund-adjusted subscription cohorts, not installs.
Permission first: what must be in place before you scale
Ads for online or offline dating, matchmaking or dating facilitation need prior written permission, requested through Meta's dating form, and Meta aims to decide within 30 days. Every dating ad must target people 18 or older. Meta won't allow ads for dating based on financial transactions, such as mail-order brides, for affairs or infidelity, or for connections with fictitious people, and creative can't carry a sexually suggestive emphasis. Ads for social apps without matchmaking elements aren't dating ads. Our dating ads authorization guide covers eligibility and the request.
Permission is not the same as account coverage. Meta's public pages explain who needs permission and how to ask, not how a grant maps to ad accounts, and ad review can include a check of advertiser permissions. Before any account runs dating ads, whether it is new, opened for another market or an agency account shared through partner access, confirm with Meta that your permission covers it and keep the answer on file. Don't test coverage by launching: Meta says editing or deleting a rejected ad doesn't remove the violation.
Ad review can also cover the destination an ad sends people to, so the app, site and sign-up flow have to be ready before the first ad goes live, not just before budgets rise. Each brand and market should have these in place:
- Written permission, noting the business portfolio and accounts it covers
- An 18+ sign-up flow, terms of service and a privacy policy
- Reporting, blocking and any verification you advertise, live in the app
- Local legal checks on dating services and subscriptions in each market
Choosing the optimization event: install, registration or subscription
Revenue in a dating app sits several steps after the install, and Meta's standard events cover those steps: CompleteRegistration for a completed registration, StartTrial for a free trial and Subscribe for a paid subscription, the last two with optional value, currency and predicted_ltv. Optimize too shallow and you risk buying installs that never finish a profile; too deep and an ad set may never reach the roughly 50 weekly conversions Meta ties to exiting learning.
Treat event choice as a ladder. Launch a new app, brand or market on the deepest event that still gets that volume, often registration, and move to trial start or subscription as weekly counts allow. Keep one definition of each event across the Facebook SDK, your mobile measurement partner and the Conversions API, and across markets, or campaigns stop being comparable. Our mobile apps and app install playbook covers the mechanics.
Maximize value of conversions needs an event that sends value and currency, and for in-app purchase value Meta currently requires at least 15 in-app purchases with values in the last 7 days; access can take a few weeks after you qualify. In a SKAN configuration the option works only for purchase events with value sets, so decide early whether subscription revenue will reach Meta as a purchase event. Events sent through AEM don't need the option switched on.
Measuring app and web funnels: SDK, SKAN and the Conversions API
Every iOS 14+ app promotion campaign uses one of two campaign attribution methods. AEM, which Meta is gradually extending to app promotion campaigns, lets eligible apps run them without configuring SKAN events. It reports close to real time, uses 1-day, 7-day or 28-day click for installs and 1-day or 7-day click for app event and value optimization, and offers breakdowns such as age, country and placement. Reporting for Android doesn't depend on SKAN.
For SKAN campaigns, Meta reports results at least 24 hours late, dated by arrival and aggregated at campaign level. Apple's conversion windows run from first launch: days 0 to 2, 3 to 7 and 8 to 35. Ads Manager includes only first postbacks that carry a fine value, later windows arrive as coarse values through the Ads Insights API, and SKAN measures nothing after day 35, so a subscription that follows a trial of three days or more reports late and coarse. Our SKAdNetwork guide covers schema design.
If you also run a web funnel, with sign-up or checkout on the site, send those events from the pixel and through the Conversions API with the same event_id and event_name, which Meta uses to deduplicate within 48 hours, and send trial and subscription events from your back end once billing confirms them. Web events no longer need event prioritization under AEM. Our conversions API setup guide walks through the payload.
Dating data also carries a sensitive-data risk. Meta's Business Tools Terms bar sharing data that includes or is based on sensitive information, including anything defined as sensitive by applicable law, and the names and criteria you set for events, conversions and custom audiences must not reflect or imply it. Many privacy laws treat sexual orientation, religion and ethnicity as sensitive, so keep them, and proxies such as a 'seeking' preference, out of event names, parameters and audience rules.
Creative that converts within Meta's dating rules
Meta's best-practices article for dating ads says ads implying you can meet or connect with someone must not position that person sexually, and it still lists blurred or pixelated images and selfies among things it generally doesn't allow, though the current Transparency Center text no longer names them. Meta's adult nudity policy also bars near-nudity and sexually suggestive activity in ads. Where Meta's pages differ, brief to the stricter one.
Ads must not assert or imply a viewer's personal attributes, such as religion, age, sexual orientation or gender identity, and Meta's Help Center list adds color, national origin, sex and family status. Describe the service, never the viewer: Meta's dating examples accept 'Date Hindu singles online!' and 'A service for seniors' but reject 'Are you single & Christian?' and 'Meet other seniors.' Translation can turn a neutral line into a claim about the reader, so check localized copy too; our personal attributes guide has more rewrites.
For creator content, Meta's branded content policies require the branded content tool, written permission from Meta for a dating business partner and an 18+ audience for those posts, and creators must make any disclosures the law requires. Because dating ads can't suggest viewers will connect with fictitious people, brief creators not to present themselves as someone viewers can date. Our guide to Facebook ads whitelisting and partnership ads covers permissions and setup.
The rule that shapes conversion creative most is the ban on fictitious connections: no fake profiles, invented chat notifications or match alerts, and nothing suggesting the viewer will match with the person shown. Real members can appear with written consent, and models only if they are never presented as members or matches. Testimonials must come from real users, and in the US an FTC rule from 2024 bans fake testimonials, including ones attributed to people who don't exist, such as AI-generated ones. Angles that stay inside the rules:
- Screen recordings of onboarding, prompts and the matching flow
- Safety and verification features, shown as they actually work
- Positioning that says who the service is for, not who the viewer is
- Offers that state what's free and the price after the trial
Age floors, audiences and market-by-market expansion
Set the age floor as a control, not a suggestion. With Advantage+ audience, Minimum age sits under audience controls, and Meta says a minimum age set there can't be overruled, while audience suggestions don't always constrain delivery. Advantage+ audience doesn't let you select a minimum age under 18 anyway. Where local law or your own terms set a higher age, use it, and check duplicated and imported ad sets too.
Meta is also gradually rolling out account controls in Advertising settings: allowed locations, a minimum age for age-restricted businesses, brand-protection exclusions and placement exclusions. They apply to every campaign in the ad account and can't be changed during campaign creation, a useful backstop on dating accounts. Setting them needs access to Advertising settings, so on partner-shared accounts agree up front who sets and checks them.
Audiences start broad. From January 19, 2022, Meta removed detailed targeting options tied to sensitive topics such as health, race or ethnicity, religion and sexual orientation, 'LGBT culture' and 'Catholic Church' among them. Niche dating brands reach their people through creative that says who the service is for, plus their own data: engagement and website custom audiences, customer lists used with customers' permission and lookalikes built from them.
Expand one market or language cluster at a time. Location controls keep Advantage+ audience inside your chosen locations unless you opt to reach more people likely to respond, so leave that off where permission, law or moderation coverage is market-specific. For iOS 14+ campaigns, Meta suggests grouping countries into tiers or by language instead of a campaign per country, and not targeting one country from several campaigns.
Subscription economics: trials, LTV and ROAS targets
Set targets from the back end forward. Start with net revenue per paying subscriber over a fixed horizon: what subscribers actually pay across the first charge and renewals, minus app-store commission, taxes and refunds. That caps what you can pay per subscriber inside your payback window, and your own funnel rates turn it into ceilings for cost per trial and per registration. Our unit economics guide covers the CAC and LTV side.
An illustrative example, not a benchmark: if a subscriber nets $30 over the first 90 days and you want 90-day payback, you can pay up to $30 per paying subscriber. If your own data shows one in four trials converting, that is $7.50 per trial start; if one in three registrations starts a trial, $2.50 per registration. Replace every input with your own cohorts by market and platform.
Platform ROAS is an early read. AEM app event results use 1-day or 7-day click windows, and SKAN reporting in Ads Manager mostly reflects the first conversion window. Renewals, refunds and disputes arrive later. Apple handles refunds on App Store purchases, requested through Apple support, its self-service tool or a card issuer; on web checkouts you are the merchant, so complaints can become card disputes. Judge campaigns on refund-adjusted cohort revenue at fixed horizons, such as day 30 and 90; our chargebacks and disputes guide covers the risk.
Subscription terms are policed on several fronts. Apple asks apps to describe what users get for the price before asking them to subscribe. Google Play requires a trial's length, price, conversion timing and cancellation steps up front, and bans annual plans that headline a monthly price and incompletely localized terms. Meta's Prohibited Commercial Practices standard, which ads must also follow, covers subscriptions without clear disclosure of terms, unauthorized charges and ignored refund policies. Make the ad say what the paywall says.
Comments, user safety and brand protection
Dating ads can attract comments that need fast handling: scam links, fake-profile spam, contact details, sexual remarks, harassment and complaints about billing or fake accounts. Meta says ads can be reviewed again at any time and that it may consider customer feedback when evaluating ads, and its dating guidance notes that overly sexual or suggestive ads draw more negative feedback. Its Prohibited Commercial Practices standard adds that persistent negative feedback about issues such as unauthorized charges or unclear subscription terms can lead to restrictions, so hiding a complaint doesn't fix what caused it.
The product has to back the ads. Apple requires apps with user-generated content to filter objectionable material, act on reports promptly, let users block abusive users and publish contact details. Meta's commercial practices standard covers fraudulent attempts to start online romances that offer or ask for money. If ads promote verification or safety, those features must work as shown, and a wave of scam comments is a prompt to check the app for the same accounts.
Comments sit with the Facebook Page or Instagram account the ad runs from, and Meta Business Suite's Inbox collects comments from connected accounts in one place. On Instagram, Hide unwanted comments, Hide spam and a Hidden Words list filter what appears, and a manually hidden comment stays visible only to you and the commenter. Set rules before launch, in every language you advertise in:
- Hide spam, scams, contact details, sexual content and slurs
- Answer billing and refund questions, then move them to support
- Escalate impersonation, threats and any sign of a minor
- Log recurring complaints by ad, market and language
- Rework creative that keeps drawing sexual or hostile comments
Account structure and capacity for multi-market dating apps
Structure accounts by brand, app or market so billing, spend limits, results and permission coverage stay separate. For iOS 14+ campaigns the binding limit is the app: Meta's Help Center allows up to 24 such campaigns per app, so extra ad accounts add no iOS 14+ campaign capacity for the same app. Meta also says campaigns below about 88 installs a day will probably see null conversions in reporting, another reason to consolidate.
More accounts are not a way around rejections. Meta's inauthentic behavior policy bars using inauthentic assets, including business manager accounts, to evade enforcement. Review can weigh compliance history, and severe or repeated violations can restrict the business portfolio, ad account, Page and the profiles of the people advertising. When a dating ad is rejected, fix the copy, creative or landing page, or request another review in Business Support Home; don't relaunch it from another account.
If you need more capacity once permission is in place, Power Ads supplies Meta agency ad accounts for teams spending roughly $100k or more a month: created in its business portfolio, shared into your Business Manager through partner access, unlimited and paid with its corporate cards. Power Ads deducts 4% from each top-up and charges no setup or monthly fee. It doesn't apply for dating permission, write ads or run campaigns. Before any new account goes live, confirm:
- Meta has confirmed your dating permission covers this ad account
- The account can access the business portfolio permitted to advertise the app
- Account controls, where available, set for minimum age and locations
- Event names and parameters free of sensitive data
- Localized copy checked and moderators assigned per language
Key takeaways
- Meta allows dating ads only with prior written permission and 18+ targeting, and its public pages don't map permission to ad accounts, so confirm coverage for every account, partner-shared ones included.
- Optimize for the deepest event that still gets ad sets out of learning, often registration before trial or subscription, and keep event definitions identical across the SDK, your MMP and the Conversions API.
- On iOS, AEM reports close to real time while SKAN is delayed, aggregated and blind after day 35, so judge campaigns on your own refund-adjusted subscription cohorts.
- Creative must never show fake profiles, invented testimonials or implied matches, and copy, translations included, must describe the service rather than the viewer.
- Clear trial and renewal terms and honored refunds protect revenue and account standing, since Meta can act on persistent complaints about unclear subscriptions or unauthorized charges.
- Extra ad accounts add capacity, not permission: violations follow the business and the people behind it.
FAQ
Does Meta's dating permission cover all my ad accounts?
Meta's public dating pages don't say how permission maps to individual ad accounts, and ad review can include a check of advertiser permissions. Before any account runs dating ads, including accounts opened for new markets and partner-shared agency accounts, confirm with Meta that your permission covers it and keep the answer on file. Launching to find out risks rejections that stay on your record.
Which optimization event should a dating app use on Meta?
Use the deepest event that still collects enough conversions to exit the learning phase, which Meta ties to about 50 a week. That often means registration first, then trial start or subscription as volume grows. Value optimization needs events with value and currency, and in-app purchase value currently requires at least 15 in-app purchases with values in the last 7 days.
How does Meta moderate dating ads?
Every dating ad goes through ad review, mostly automated, which can cover images, video, text, targeting, the destination and advertiser permissions. Most ads are reviewed within 24 hours, and any ad can be reviewed again after it goes live. Meta may also weigh customer feedback and an advertiser's compliance history. If an ad is rejected, fix it or request another review in Business Support Home.
How should you moderate comments on dating ads?
Moderate from the Facebook Page and Instagram account the ads run from, using Meta Business Suite's Inbox to see comments in one place and Instagram's Hide unwanted comments, Hide spam and Hidden Words filters. Hide spam, scams, contact details and sexual content quickly, answer billing complaints before moving them to support, and escalate impersonation or any sign of a minor.
Can creators promote a dating app on Instagram?
Yes, within Meta's branded content rules. Creators must use the branded content tool, the dating business must hold Meta's written permission to promote online dating, and the posts must target people 18 or older. Creators also need to make any legally required disclosures, and because dating ads can't suggest viewers will meet fictitious people, they shouldn't present themselves as someone viewers can date. Partnership ads then run that content from your ad account.
Do agency ad accounts change the rules for dating ads?
No. Agency accounts sit in the provider's business portfolio, but dating ads from them still need Meta's written permission, 18+ targeting and compliant creative, and you should confirm that your permission covers each account before launch. Power Ads supplies Meta agency ad accounts only; it doesn't apply for dating permission, write ads or run campaigns.
Sources
- transparency.meta.com/policies/ad-standards/restricted-goods-services/dating-ads
- facebook.com/business/help/765622867361201
- facebook.com/business/help/528007798183873
- facebook.com/business/help/2557868957763449
- transparency.meta.com/policies/ad-standards/objectionable-content/privacy-violations-personal-attributes
- transparency.meta.com/policies/ad-standards/objectionable-content/adult-nudity-and-sexual-activity
- facebook.com/business/news/removing-certain-ad-targeting-options-and-expanding-our-ad-controls
- facebook.com/business/help/204798856225114
- facebook.com/business/help/1210227555661027
- facebook.com/business/help/975570072950669
- transparency.meta.com/policies/ad-standards/business-assets/inauthentic-behavior
- developers.facebook.com/docs/meta-pixel/reference
- facebook.com/business/help/581721639581617
- facebook.com/business/help/571188993373447
- facebook.com/business/help/670955636925518
- facebook.com/business/help/721422165168355
- facebook.com/business/help/3499572073626051
- facebook.com/business/help/584603712214119
- developer.apple.com/documentation/storekit/receiving-postbacks-in-multiple-conversion-windows
- developers.facebook.com/docs/marketing-api/conversions-api/deduplicate-pixel-and-server-events
- facebook.com/legal/terms/businesstools
- facebook.com/business/help/221149188908254
- ftc.gov/news-events/news/press-releases/2024/08/federal-trade-commission-announces-final-rule-banning-fake-reviews-testimonials
- facebook.com/business/help/793748385630490
- facebook.com/business/help/938372127764391
- facebook.com/business/help/1438478636941047
- facebook.com/business/help/651033805513936
- developer.apple.com/app-store/review/guidelines
- support.google.com/googleplay/android-developer/answer/9900533
- developer.apple.com/documentation/storekit/handling-refund-notifications
- transparency.meta.com/policies/ad-standards/deceptive-content/prohibited-commercial-practices
- transparency.meta.com/policies/community-standards/prohibited-commercial-practices
- facebook.com/business/help/294426838452244
- help.instagram.com/700284123459336
