Home › Meta ads in Singapore

Singapore Compliance · 2026

Why your Meta ads won't run in Singapore — beneficiary, payer & verification

Your ad looks fine, but the ad set targeting Singapore just won't deliver — or Ads Manager blocks it outright asking for a “beneficiary.” Since 2025, every ad reaching a Singapore audience has to name who benefits from it and who pays for it, and the advertiser has to be verified. Here's exactly what that means and how to set it up.

Published September 7, 2026

✓ No credit card  ·  ✓ 5 free campaigns/month  ·  ✓ Dashboard, Google Sheets & your AI assistant


Short answer

To run Meta ads targeting Singapore you must do two things. First, complete advertiser verification in Ads Manager (unless you already have a verified business portfolio that qualifies you to skip it). Second, declare a beneficiary — the person or organization the ad is for — and, in most cases, a payer, on every ad set that reaches Singapore. Miss either and the ad set is rejected or simply never delivers. The disclosure shows in Meta's Ad Library and the ad's info panel, not in the feed.

RequirementWhat it isWhere it lives
Advertiser verificationConfirm your identity / business with MetaAccount (one-time)
BeneficiaryWho the ad is created for and benefitsAd set
PayerWho finances the adAd set
Employment (job ads)Special ad category, on top of the aboveCampaign
Missing any of theseAd set rejected or won't deliverPre-flight

Verification is the account-level gate. Beneficiary and payer are per-ad-set, and Meta enforces them together at creation.

What Singapore actually requires now

Meta rolled this out in 2025 to comply with Singapore's Online Criminal Harms Act. Here's what changed and why your ad stopped.

01

Why does my Meta ad get rejected or won't run when I target Singapore?

Because Singapore is now a regulated location. As of 2025, Meta requires every advertiser reaching a Singapore audience to be verified and to disclose who benefits from and pays for the ad. If your account isn't verified, or the ad set has no beneficiary attached, Meta blocks or fails to deliver it — often with a message pointing at a missing beneficiary or a “regulated category” your setup doesn't satisfy.

This is a transparency rule, not a content rule. There's nothing wrong with your creative or your budget — the ad is missing a required disclosure, and Meta won't serve it to Singapore until that disclosure is present.

02

What is the beneficiary and payer requirement — and who does it apply to?

It applies to all ads targeting Singapore, not just political or financial ones. Providing a beneficiary is mandatory for any ad reaching a Singapore audience; a payer is required in most cases too. The information is stored in Meta's Ad Library for about a year and appears in the ad's “About this ad” info panel, but it does not show inside people's feeds.

The point is public accountability: a Singapore viewer — or a regulator — can look up any ad and see the real organization behind it. That's why Meta gates it behind verification: the names you declare have to be ones you've proven you're entitled to use.

03

What's the difference between the beneficiary and the payer?

The beneficiary is the individual or organization the ad is created for and that benefits from it — usually your business, or your client's business if you're an agency. The payer is whoever finances the ad. They're often the same entity, but not always: if a reseller or agency pays on a client's behalf, the payer is the party that owns the paying business portfolio while the client remains the beneficiary.

When they're the same, you enter the same name twice. When they differ, get it right — this is the exact relationship Meta is asking you to make public.

How to set it up, step by step

Two parts: verify the account once, then attach a beneficiary and payer to each ad set. Do the first and the second becomes a dropdown.

04

How do I complete advertiser verification for Singapore?

Meta prompts eligible accounts inside Ads Manager when Singapore targeting is detected — watch for the notification in Account Quality or the ads composer. Verification confirms who you are and, for a business, that you're authorized to advertise on its behalf. It's a one-time account-level step, but it can take days, so start it before you need to launch, not the morning of.

If you manage several ad accounts under a business portfolio, verify at the portfolio level so the clearance carries across the accounts under it.

05

How do I add the beneficiary and payer to my campaign?

You can set it in two places, and setting the default first saves you repeating it on every launch:

  1. In Ads Manager → Advertising settings, add a default beneficiary and payer for the ad account. Once saved, new ad sets that target Singapore inherit it automatically.
  2. Or set it per ad set at build time — in the ads composer, open the Budget & Schedule step and fill in the beneficiary (and payer) information section for that ad set.
  3. For existing campaigns, edit the ad set in Ads Manager and enter the beneficiary and payer there. Meta requires the pair to be present at ad-set creation or edit — you can't bolt it on after the fact without an edit.

The values you pick from must be identities you've verified — that's why step 04 comes first. An unverified name won't be selectable.

06

I already have a verified business portfolio — do I still need to do all this?

You may be able to skip the separate verification step: accounts with an eligible verified business portfolio often qualify, though Meta may still ask for supplementary information. But the beneficiary and payer disclosure is not optional — even a fully verified advertiser must attach those names to ad sets that reach Singapore. Verification and disclosure are two different requirements; clearing one doesn't clear the other.

Running employment ads in Singapore

Job and recruitment ads carry an extra layer. If you promote hiring in Singapore, this section is for you.

07

I'm running job or recruitment ads in Singapore — what applies to me?

Two things stack. Job and recruitment ads are an Employment special ad category anywhere Meta operates — you declare the campaign as Employment, which restricts age, gender and detailed targeting to prevent discrimination. On top of that, because the ad reaches Singapore, it also needs the beneficiary and payer disclosure and a verified advertiser behind it.

So a Singapore recruitment campaign is Employment at the campaign level and beneficiary/payer at the ad-set level, at the same time. Missing either one is enough to stop delivery, and they fail for different reasons — worth checking both when a hiring campaign won't run.

08

What's the difference between a special ad category and a regulated category?

A special ad category — Employment, Housing, Credit, Financial products, Social issues/elections/politics — is about what the ad is about, and it limits how you can target. A regulated location like Singapore is about where the ad runs, and it requires transparency about who's behind the ad. They're set in different places and enforced independently.

Special ad categoryRegulated location (Singapore)
Triggered byAd topic (e.g. hiring)Audience location
Set atCampaign levelAd-set level (beneficiary/payer) + account verification
Main effectTargeting restrictionsPublic disclosure of who benefits/pays
ExampleEmploymentBeneficiary + payer for SG

A Singapore job ad hits both at once. That's the combination people trip over most.

Everything above you can set by hand, one campaign at a time. Automating or scaling Singapore ads is where it gets sharp.

If you build Singapore campaigns in bulk, from a sheet, or through an API or AI assistant, the beneficiary and payer have to be attached to every ad set programmatically — and Meta rejects the ad set the moment one is missing. Adbloop passes the verified beneficiary and payer through on creation and validates the Employment + Singapore combination before it reaches Meta — one launch or 150 at once.

See how the pre-flight check works →

Free plan · no card · every campaign lands paused until you approve it.

When it fails without telling you

Some of these show a clear error. The dangerous ones don't — the ad set just quietly never serves to Singapore.

09

Why does my Singapore ad publish but never actually deliver? Silent

Sometimes Meta returns a clear “beneficiary required” error, and you fix it. The harder case is the one that saves cleanly and just doesn't run — an ad set that targets Singapore among other countries, where the rest deliver and the Singapore portion silently stalls because the disclosure was inherited incorrectly or dropped. No banner, no email; your spend simply comes in short of plan.

The defence is the same as for every silent Meta failure: validate the full requirement at build time — verified advertiser, beneficiary and payer present on the ad set, Employment set if it's a job ad — instead of discovering a week later that Singapore never spent.

A documented case: a Singapore recruitment ad set with no beneficiary attached

Build an Employment campaign, target Singapore, and create the ad set without a beneficiary and payer. Depending on how it's built, Meta either rejects the ad set on creation with a regulated-category error, or — when the account carries a stale default — accepts it and then under-delivers the Singapore audience.

Anyone building one campaign by hand in Ads Manager is walked through the beneficiary field. Anyone duplicating a non-Singapore campaign, importing a sheet, or creating through an API will hit the rejection — or worse, the silent version — unless the beneficiary and payer are passed through explicitly on every ad set.

Adbloop treats the beneficiary and payer as required inputs for Singapore ad sets and passes your verified identities straight through to Meta at creation.

Adbloop · reproduced against live ad accounts on Meta Marketing API v25.0
10

Why do I get regulated-category errors when creating Singapore campaigns through an API or tool? Silent

Because the beneficiary and payer aren't a single free-text field — Meta expects the verified identities to be attached to each ad set, and it enforces the pair together at creation. A tool that doesn't carry those values through will have every Singapore ad set bounce, even though the same setup works fine for other countries.

If you're integrating Meta's API yourself, the two things to get right: obtain the verified beneficiary and payer identity IDs from the account's Singapore verification, and attach both to the ad set on create (not the campaign). Send only one, or put them on the wrong object, and Meta rejects it.

Adbloop's API and MCP accept the beneficiary and payer per campaign and apply them to the Singapore ad set automatically — see the AI assistant or start free.

Which other countries require this?

Singapore isn't alone. If you advertise across Asia-Pacific or Europe, you'll meet the same requirement under different names.

11

Do other countries need a beneficiary and payer too?

Yes. Meta enforces beneficiary and payer disclosure across a growing list of regulated locations, with the exact rule varying by country:

LocationRequirement
European UnionMandatory on all ads
SingaporeBeneficiary mandatory on all ads; payer in most cases; advertiser verification required
TaiwanMandatory; extra payer detail for financial-services ads
AustraliaRequired for financial-services ads
ThailandVerification expanding; required for flagged accounts and certain ad types
India, BrazilRequired for flagged accounts or specific ad types (e.g. securities/investment)

The trend is one-directional: more markets, more often. Building the beneficiary/payer step into how you launch now means the next country to switch on is a settings change, not a fire drill.

Requirements summarised from Meta's advertiser guidance and third-party compliance references as of 2026; Meta updates these rules periodically, so confirm the current requirement for your target market in Ads Manager before launch.

Launch in Singapore without the guesswork

Singapore's rules aren't hard once — they're hard every time, on every ad set, across every launch, and they fail quietly when you scale. Adbloop carries your verified beneficiary and payer through to Meta, validates the Employment + Singapore combination before it publishes, and lands every campaign paused so nothing spends until you approve it — from a dashboard, Google Sheets, or Claude and ChatGPT.