For a campaign that legitimately targets Singapore, complete the verification and transparency steps shown by Meta for the selected ad account, then confirm the intended advertiser and payer. Bind any integration mapping to that exact account. Verification does not establish that a gambling offer is eligible for Singapore; resolve product and market eligibility first.
What to take away
- Confirm the selected ad account before reviewing advertiser or payer status.
- Use the actual advertiser and payer, with the evidence Meta requests.
- Recheck identities after account changes; never infer them from another business portfolio.
Answer the market question first
A verification task can make a campaign feel almost ready even when a more basic decision remains unresolved. Ask the operator's responsible specialist to confirm whether the specific product and advertising activity may target the intended market. Record that decision before configuring a campaign around Singapore.
Keep this article's operational checklist separate from that eligibility decision. An identity being verified is evidence about identity, not a permission slip for every product. If Singapore is not part of the approved campaign plan, correct the plan through the normal review process rather than completing unrelated settings.
Identify who benefits and who pays
Meta now uses advertiser where older guidance said beneficiary. Write the actual arrangement in plain language: whose product is promoted, and who pays? An operator, agency and funding entity can play different roles. Have the responsible people confirm the answer before entering names into a verification flow.
Keep legal names consistent with the supporting records. Do not choose an entity simply because it already appears in a dropdown. The selected identity should describe the real arrangement, and the team should be able to explain it without relying on an old campaign's settings.
Open the exact ad account
Record the account identifier before opening Meta's verification and transparency settings. Check it again before saving. This small habit matters when an agency manages several businesses with similar display names or switches between accounts during a support call.
Follow the current steps presented by Meta and note which identity is pending, accepted or requires more information. A completed business portfolio task elsewhere does not tell you what this account currently accepts. Verify the intended account directly instead of borrowing a screenshot from another setup.
Keep integration mappings tied to the account
For API-based campaign preparation, store the account identifier with the selected regional identities and the time they were checked. Meta's official SDK exposes regional regulation identity fields on ad sets. The presence of those fields does not remove the need to validate the selected values in the actual account context.
Treat copying an identity from another account or business portfolio as an unverified change. Resolve the applicable identities for the intended account and confirm them through the supported flow. Do not select the first available value simply to make a required field nonempty.
- Account identifier matches the campaign's intended account.
- Advertiser and payer match the documented business arrangement.
- Required verification is complete or explicitly marked pending.
- The integration sends the reviewed values for this exact setup.
- Any failed or unreadable check remains unresolved until confirmed.
Diagnose the message without guessing
Capture the exact error, account identifier and action being attempted. Distinguish a missing identity from an identity that is still pending, and both from a field that the integration failed to send. Each issue belongs to a different owner and needs different evidence.
Compare the intended configuration with the saved campaign setup. If the UI and integration disagree, ask the implementation owner to investigate the mapping and current API behavior. Keep credentials and identity documents out of ordinary logs; a support note usually needs status and identifiers, not secret material.
Make the final handoff explicit
Record which account was checked, who confirmed the business identities and which configuration was submitted. If an account, payer or business arrangement changes, review the mapping again before using it for new campaigns. A copied campaign should not silently carry an obsolete identity choice.
Keep verification status separate from ad review and campaign performance in your launch note. The buyer needs to know what is ready and what remains unresolved. Clear ownership makes this manageable: the business confirms the entities, the account owner handles verification, and the implementation owner checks the configuration.
Quick questions
Can we reuse identities from another business portfolio?
Do not infer eligibility from another portfolio or account. Check the identities accepted for the exact account used by the campaign and confirm that they describe the real advertiser and payer.
Does verification allow a casino to advertise in Singapore?
No. Verification does not decide product or market eligibility. Obtain the appropriate operator review of that separate question before planning the campaign.
What if Meta still asks for verification?
Check the selected account, the specific identity status and the values used by the campaign. Send the exact message to the responsible owner instead of changing unrelated creative or repeatedly copying the setup.
Sources & further reading
A clearer way to run your Meta workflow.
Bring your account setup, campaigns and reporting into Advellar.
Create your workspace