Meta gambling ad permission: prepare a clear application

Separate three different decisions

Use three rows in your launch tracker: business identity, gambling permission and ad review. Give each row its own evidence and status. The distinction prevents a common handoff error: someone completes an identity step and the next team assumes the entire campaign is approved.

Ask the person reporting progress to name the decision they received. Was an entity verified, was a permission request answered, or did a particular ad complete review? Precise language is useful when several brands share a media team and each launch has a different set of open questions.

Build a small, consistent evidence pack

Prepare an internal index before uploading anything. It should connect the legal operator, customer-facing brand, product and destination. If an agency is applying on behalf of an operator, make that relationship easy to understand. The index is your working document, not a substitute for Meta's required fields.

• Operating entity and the spelling used in official records.
• Brand names, destination URLs and the product being promoted.
• Licensing or other eligibility evidence requested in the current flow.
• Intended markets and the compliance contact responsible for them.
• Relevant asset identifiers and a clear agency authorization trail.

Resolve contradictions before submission

Compare the application draft with the website footer, contact details, offer terms and business records. A trading name can differ from a legal name, but the relationship should be understandable. Ask the operator to resolve inconsistent information at its source instead of writing a clever explanation around it.

Check dates and versions as well as names. An old attachment may describe a previous domain or business arrangement. Keep the final submission pack in a controlled business folder with access limited to the people handling the application. Avoid spreading identity documents through ordinary campaign chat threads.

Submit once the story is coherent

Start in Authorizations and Verifications in Meta Business Suite and open the online gambling and gaming request. Follow the current application fields and evidence requirements. Authorization applies to specific ad account IDs, so identify the intended accounts accurately and retain the submitted version and any case reference.

Choose one person to coordinate follow-up. If a reviewer asks for clarification, answer that question with the relevant evidence and note what changed. Avoid several team members sending different explanations. Do not build a launch date around an assumed approval time; plan creative preparation separately from the permission decision.

Read the decision before calling it complete

Turn the response into a usable record. Note the entity, product, destinations, markets and assets it actually identifies, plus any conditions or follow-up actions. Where the scope is unclear, ask through the appropriate Meta support route rather than extending the meaning yourself.

Do not assume a new ad account inherits coverage because it is visible in the same business portfolio. Equally, do not assume that an agency's prior work settles a different operator's request. Verify the intended setup against the decision you have, and retain the evidence used for that check.

Make change review part of campaign operations

Set a review trigger when the operating entity, product, destination or market changes. The purpose is to ask whether the existing evidence still describes the campaign. A new creative color does not need the same internal review as a new commercial offer or destination.

Meta does not allow online gambling ads to target anyone under 18; a market can require a higher minimum age. Have the responsible specialist confirm the intended audience and market requirements. Give the buyer a clear launch instruction and supporting record, rather than asking them to interpret legal scope under deadline.