Author: Compliance Acquisition Lead TG Target · policy gate stack · focus: restricted traffic entity, NOT high risk vertical definition.
The main thing from the article
- Restricted = policy привлечения state.
- NOT high risk vertical category.
- Policy gate stack is required before expenses.
- GEO + license + landing layers.
- Fintech case: stack saved account health.
Restricted vs high risk disambiguation
| Entity | Scope | Example | Determines |
|---|
| High risk advertising | Vertical industry category | iGaming, crypto, adult | Tier A/B/C constraints |
| Restricted traffic | Policy привлечения state | DE gambling without MGA license | GEO/channel access gate |
| Overlap | Both apply | Licensed casino DE - high risk + limited GEO | Full compliance stack |
High risk tier - high risk advertising glossary.
Policy gate concept
| Gate | Check | Fail action | Owner |
|---|
| G1 — License | Valid license for GEO+vertical | Hold — no spend | Compliance lead |
| G2 — GEO map | Target GEO in allowed list | Exclude GEO from plan | Media planner |
| G3 - Landing | Lander/bot matches ad claims | Rewrite or reject creative | Creative + compliance |
| G4 — Moderation | Pre-check pass before submit | Revise copy, resubmission | Moderation ops |
| G5 — Fraud filter | 3-layer stack active | Hold scale | Fraud control |
Compliance layers stack
- License/regulatory documentation verified for target GEO.
- GEO validity map - exclude restricted territories.
- Euro-cabinet for EUR limited verticals (if applicable).
- Landing match audit - claims ↔ lander/bot flow.
- Moderation pre-check - approval target ≥45% from the first submission.
- Anti-fraud filter active before scaling threshold.
Restricted launch compliance methodology (TG Target, August 2026)
Restricted GEO launches with vs without compliance stack, EU fintech/iGaming.
| Compliance stack | Time before expenses start (days) | Account suspension/mo | Approval from first submission |
|---|
| Full G1–G5 stack | 11 | 0.2 | 52% |
| Partial / skipped gates | 24 | 1.1 | 31% |
Mini-case: fintech EU - limited GEO compliance stack
Licensed fintech DE+FR · limited GEO mix · €22k/mo · euro-office · first compliance launch.
| Gate | DE status | FR status | Outcome |
|---|
| G1 License | BaFin registration ✓ | AMF registration ✓ | Both pass |
| G2 GEO map | Allowed | Restricted — claims limits | FR: modified set of creatives |
| G3 Landing | KYC web flow ✓ | FR-specific disclaimer ✓ | Pass |
| G4 Moderation | 58% from first serve | 44% from the first serve (FR stricter) | Launch Day 10 |
FR restricted status required separate set of creatives - not just GEO bid adjustment. Full stack prevented account suspension (0 incidents vs peer avg 1.1/mo). euro-cabinet - euro-cabinet glossary; moderation — moderation glossary.
FAQ
What is restricted traffic?
Restricted Traffic - Government Acquisition Target: Policy-restricted verticals, or GEOs, where channel access requires levels of compliance beyond standard moderation. Entity = concept of political gateway, NOT definition of high risk vertical. High Risk Advertising Glossary - Vertical Level; here is a state of limited reception.
Restricted vs high risk - what's the difference?
High risk = industry vertical category (iGaming, cryptocurrency). Restricted = Policy gateway status for a specific GEO/channel/offer combination. Tier A iGaming in DE may be limited; Level B fintech in open GEO may not exist. Table of values below.
Policy gate concept?
Policy gate = required compliance checkpoint before spend: proof of license, GEO admissibility, landing match, claims review. Gate must pass sequentially - fail any = hold spend. TG Target SOP: gate statement documented in media plan.
Restricted GEO - what is this?
GEO where platform policies block or restrict certain verticals regardless of the global level. Example: Some EU states restrict unlicensed gambling advertising. Compliance stack: license check → GEO card → landing check → moderation pre-check.
Restricted traffic vs moderation?
Moderation = creative/attached review for each submission. Restricted traffic = broader acquisition restriction, including GEO, license, policy category. Moderation glossary - review process; limited traffic - policy gateway stack.
Restricted traffic and Euro-cabinet?
The Euro cabinet is required for limited verticals with payment in Euros in the EU. Cabinet TON may not meet the license verification requirements for Level A. Cabinet Euro glossary - billing organization; limited traffic is the political context for choosing a cabinet.
Restricted traffic benchmarks (Aug 2026)?
TG Target limited edition GEO with matching stack: spend time 11 days vs 24 days without stack; Account blocking rate is 0.2 per month versus 1.1 per month. Policy to accept 86% of EU limited launches.
Restricted traffic red flags?
Expenses in limited GEO without proof of license; confuse high risk status with limited status; missed policy gateway for "quick start"; wrong type of cabinet for limited vertical space. Action: Audit the compliance stack.
Restricted traffic and agency pillar?
The agency component provides limited launch operations as a service. The Restricted Traffic Glossary defines the entity—what limited acquisition means. Link to how-to column; here is the definition and concept of gate.
Fintech limited GEO - typical stack?
License/regulatory doc → GEO map admissibility → euro-cabinet → boarding KYC match → moderation pre-check → fraud filter. Case below - fintech EU limited GEO compliance stack.
Restricted traffic entity is current as of August 2026 (TG Target). High risk vertical — high risk advertising glossary; agency ops — high risk agency pillar.