Casino promotion across Tier 2-3: platform rules, the funnel, and your own numbers
Advertising a casino runs into a list of countries long before anyone works out a cost per click. Google publishes that list: every country carries its own set of permitted products and its own licensing requirement for the operator. Indonesia is not on it at all, which means certification is off the table there.

The country list decides before the budget does
Google's gambling policy rests on four conditions at once: the advertiser follows local law, targeting covers permitted countries only, the landing page carries responsible gambling information, and the content is not aimed at minors. On top of that sits certification, and only the advertiser can pass it.
Then comes the country detail, which bites harder than any bid. South Africa allows lotteries and sports betting: a lottery operator is licensed by the National Lotteries Commission, a bookmaker by a provincial regulator. Thailand allows lotteries and betting on horse racing, and the operator there has to be a state-run entity. The Philippines opens up casino games, bingo, lotteries and betting, yet the operator still needs a state licence or state ownership.
Where a product is missing from a country's list, it cannot be advertised there at all: no certification is even possible, and the policy says so in plain words. A casino app aimed at Indonesia falls apart before the first ad goes up, because Indonesia is not on the list. No account fixes that.
The order of work follows from that. You look at the operator's licence first, open the country list second, and the overlap of those two is the geo you can actually buy for.
| Country | Products allowed | Operator requirement |
|---|---|---|
| Philippines | Casino games, bingo, lotteries, sweepstakes, sports betting | State-run operator or a state licence |
| South Africa | Lotteries, sports betting | Lotteries licensed by the National Lotteries Commission, sports betting by a provincial regulator |
| Kenya | Lotteries, sports betting, online casino games | Licence from the Betting Control and Licensing Board plus a separate permission to advertise |
| Thailand | Lotteries, horse-racing betting | Operator must be a state-run entity |
| Indonesia | Country is not on the list | Cannot be advertised, no certification |
Affiliate sites run under their own rules
Aggregator and affiliate sites that describe or compare operators sit in a policy bucket of their own: online gambling-promoting content. That bucket, though, is not open everywhere: where a country has no entry for such content, it cannot be advertised there.
Two conditions bind the destination itself. It must not offer gambling services, and it must not link out to gambling services it owns. Beyond that it cannot promote activity which fails the country-specific requirements for the geo it targets, so somebody else's licence does nothing for an affiliate page.
Certification runs one way per account, meanwhile: either online gambling or social casino content. Running both themes means running separate accounts, and that is worth designing in before the first of them builds any history.
Telegram Ads does not take this category
Clause 5.6 of the platform's policies shuts the door: ads must not promote gambling, gaming or casino activity involving real money, prizes or goods of any value, online or off. Sports betting, lotteries, bingo and fantasy sports are listed as examples, and right after them come tips, odds and odds calculators.
The format is rather narrow as well, and worth knowing up front: ad text of up to 160 characters including spaces, plus a button. Only one link may sit in that text. Line breaks, bullets and numbered lists are out, so are URL shorteners, and the destination has to work - a bot answering commands, a site that opens.
None of that empties the channel. For the products next door, a tracker or a course or a buyer's tool, it stays open, and that is where its real audience sits anyway.
What an App campaign actually buys
In an App campaign you supply the text, a starting bid, a budget, and the languages and locations. From there the system tests asset combinations built from that text, your images and video, and the assets on your store listing. That is the entire input.
Delivery runs wide: Google Search and search partners, Google Play across search results, the related-apps block and the homepage, YouTube, the Display Network including Gmail and mobile sites, and Discover. You cannot subtract just one placement from that mix.
There are three campaign types: installs, in-app engagement, and pre-registration. Here the type matters more than the bid: a campaign built for installs honestly delivers installs, while a paying player is what the in-app action campaign goes looking for. Still, that action has to reach Google before anything can optimise toward it.
Postbacks and the conversion window, or why numbers disagree
When a conversion happens, the network's or advertiser's server sends the tracker an HTTP request, and that request is the postback. Keitaro records the conversion from two mandatory parameters: the click id and the status. Without a status, or with one the tracker cannot map, the request is dropped in silence.
The second source of disagreement lives in the ad account. In Google Ads the conversion window is the period after an ad interaction during which a conversion gets recorded; by default it runs 30 days, and each conversion action is set separately. Once it drops to seven days, anything later just never reaches the report.
Keitaro adds the S2S postback by itself once a traffic source is picked. By hand you set the URL, the sending method - which the source itself tells you - and the statuses that trigger it. Until those three line up, the argument about twenty conversions in the account against twelve in the tracker just does not get settled by bidding.
What has to be ready before the first ad
Two pieces of paper get checked before launch: the advertiser's certification and the operator's licence for the exact country the ads will run in. Without them the campaign lives only until the first review.
Responsible gambling information on the landing page is a policy requirement. Checking it works better through someone else's eyes: open the page the way a person in that geo will, on a phone and in their language.
By this point the tracker already takes conversions - postback wired, statuses mapped, the conversion window set to the same value in the account and in the tracker. In advance you build the report with source, campaign and creative breakdowns, because reading it starts on day one.
What moves the numbers in the creative
Local language carries a clip further than editing really does. When a clip is shot on a phone, subtitled in the language of the geo, and carries a face the audience already trusts, it outlives stock footage by weeks.
Variations are easy to mass-produce with generative models: background, framing, colour grade. Volume beats polish here. The cut-off threshold is something the buyer sets for themselves, from their own report.
One figure out of that report is worth more than any market range, because it belongs to your offer, your geo and your week. Since it was taken on a different offer in a different month, somebody else's benchmark will not hold a budget plan together.
Where the setup breaks
The landing page breaks first. Without responsible gambling information it is out of policy, and swapping the creative does nothing about that.
Then comes a licence that does not match the country of delivery. An operator without the right licence will not pass certification, however many accounts sit in reserve.
There is tagging, too, and it fails quietly. When source, campaign and creative never make it into the link, the postback comes back without a click id, and the traffic pools into one heap where no breakdown can be built at all.
Last to fall is copy that promises a win outright. The rule is written about meaning, so rewording it changes nothing.
FAQ
How do I check whether an offer can be advertised in a given country?
Open Google's gambling policy and find the country in the list. It states which products are allowed and what the operator's licence has to be. If the product is not listed, it cannot be advertised there and certification for it is not issued.
Why do the ad account and the tracker report different conversion counts?
Usually the conversion window and the statuses disagree. The account counts a conversion inside its own window; the tracker records it from a postback carrying a click id and a status, and a request without a status is dropped. Line up the settings first, compare numbers after.
Does Telegram Ads work for an operator's offer?
No. Clause 5.6 of the platform's policies bans ads for gambling, casinos, sports betting, lotteries and bingo, along with tips and odds. For a tracker, a course or a buyer's tool the channel stays open.
Which goal should an App campaign optimise for?
The one that matches the money. An install campaign optimises toward installs; an in-app action campaign optimises toward the event you send it. The event has to reach Google first, otherwise there is quite simply nothing to optimise against.
Sources
- Gambling and games - Google Ads policy: countries, products, certification
- Telegram Ads policies: clause 5.6 on gambling
- About App campaigns: what you set and where the ads run
- About conversion windows in Google Ads
- Keitaro postback: click id and conversion status
- Keitaro S2S postbacks: URL, method and statuses
Disclaimer: this is B2B experience from the advertiser/partner side, working within platform rules and the law; this site does not advertise gambling services to consumers.
I can do this on your product
I consult on acquisition, funnels and retention - including hard verticals.
