Skip to main content

Meta Thailand ads: support verified Beneficiary/Payer identities when creating new Ad Sets

Feature Request

Hi Zernio team,

We found another blocking issue when creating new Meta Ad Sets targeting Thailand：

The ad account already has verified Beneficiary and Payer identities configured in Meta. Zernio now supports:

regionalRegulatedCategories: ["THAILAND_UNIVERSAL"]

but it does not currently expose Meta’s regional_regulation_identities field when creating the Ad Set.

As a result, Meta still rejects new Thailand Ad Sets even though the ad account itself is already verified.

Could you please add support for regionalRegulationIdentities in the Zernio Ad creation flow and pass the Beneficiary/Payer IDs through to Meta’s regional_regulation_identities field?

Ideally, Zernio should also expose the verified regulatory identities available on the selected ad account, so the existing default Beneficiary/Payer can be automatically reused without requiring the user to configure it again.

If no verified identity exists, please return a clear actionable error.

This would fully unblock new Thailand Ad Set creation through Zernio.

Thanks A LOT！

Posted by alan xu ·
Status: Completed1 comment

Log in to comment and vote

Comments1

  • Miquel Palet López

    Team•

    Sep 4

    Hey!

    We shipped support for regionalRegulationIdentities across all Meta ad creation flows (standalone, boost, CTWA, and multi-creative).


    How to use it:

    When creating an ad set targeting Thailand, pass both fields:

    { "regionalRegulatedCategories": ["THAILAND_UNIVERSAL"], "regionalRegulationIdentities": { "universal_beneficiary": 123456789, "universal_payer": 123456789 } }

    The values are the numeric entity IDs from your Meta verification setup (the same ones you see in Ads Manager under Beneficiary/Payer).


    Auto-reuse of defaults: If your ad account already has default Beneficiary/Payer configured in Meta Ads Manager, you can omit regionalRegulationIdentities entirely and just pass regionalRegulatedCategories. Meta will auto-fill the identities from your account defaults.


    Exposing verified identities via API: Unfortunately Meta does not provide a read API for the verified regulatory identities on an ad account (unlike DSA, which has readable account-level defaults). This means we can't surface a "list your available identities" endpoint on our side. The numeric entity IDs need to come from your Meta Ads Manager settings, or you can rely on the auto-fill behavior described above.


    If no verified identity exists: Meta rejects the ad set creation with a clear error, which we pass through as-is.


    API reference: https://docs.zernio.com/ad-campaigns/create-standalone-ad