Geographic Targeting Reference Geographic Targeting Reference
  1. Zype
  2. Manage Content
  3. Content Rules

Geographic Targeting Reference

This reference article describes all geographic match types supported in Content Rule Profiles, how geo resolution works, and notes on availability by region.

Match Types Reference

Global

Matches all viewers regardless of their geographic location. Use Global as a catch-all rule — typically as the final rule in a profile to deny or allow everyone who was not matched by a more specific rule above it.

✅  Tip: Example: Allow DMA 532 in Rule 1, then Deny Global in Rule 2. Anyone not in DMA 532 is denied.

Country

Restricts or allows access based on the viewer’s country, identified via IP geolocation. Enter standard ISO 3166-1 alpha-2 country codes (e.g., US, GB, CA, DE).

Availability: All regions.

State

Targets a specific state, province, or territory within a country. Enter the state/province abbreviation or full name as recognized by the geo source (e.g., NY, California, Ontario).

Availability: All regions where IP geolocation resolves to subdivision level.

City

Targets a specific city. City resolution depends on the geo data source and may not be available for all locations. Enter the city name as it appears in the geo database.

Availability: Where the geo source supports city-level resolution.

Zip Code

Targets US ZIP codes for precise, hyper-local restriction. Enter 5-digit ZIP codes (e.g., 12207 for downtown Albany, NY). Multiple ZIP codes can be entered in a single rule by pressing Enter after each.

Availability: US only in Phase 1. International postal code support is planned for a future release.

DMA Code (Designated Market Area)

Targets US broadcast market areas as defined by Nielsen. DMAs represent regional television markets and are commonly used for broadcast rights and local content licensing compliance. Enter the numeric DMA code (e.g., 532 for Albany-Schenectady-Troy, NY; 501 for New York City; 803 for Los Angeles).

Availability: US only.

Resolution method: Zype uses a ZIP-to-DMA mapping as the primary resolution method (fast, cacheable). When ZIP data is unavailable (e.g., on mobile apps), device GPS (lat/long) is used as a fallback to determine the viewer’s DMA via polygon mapping.

ℹ️  Note: On mobile Apps Creator apps (iOS and Android), DMA rules require location permission from the viewer. See Mobile Location Enforcement for Apps Creator for details.

IP Address

Restricts or allows access based on the viewer’s IP address. Enter specific IP addresses or CIDR ranges. Useful for allowing access to internal testers, office networks, or blocking known problematic IP ranges.

Availability: All regions.

Region

Uses predefined or custom regional groupings as defined in Zype Apps Creator. Regions represent logical groupings of geographic areas (e.g., “Northeast US” or “EMEA”) that your team has configured in Apps Creator.

Availability: All regions. Groupings are equivalent in Zype Apps Creator.

How Geographic Resolution Works

When a viewer attempts to play content, Zype determines their location using the following resolution chain:

  • IP geolocation (primary method for web and CTV): determines country, state/province, city, ZIP code, and DMA.
  • Device GPS / lat-long (mobile apps, when location permission is granted): used to derive DMA via polygon mapping when ZIP is unavailable.
  • Geo provenance is logged with each playback request for support and debugging purposes.
ℹ️  Note: If geo data is insufficient to evaluate a rule (e.g., ZIP code cannot be resolved), Zype falls back to the next available resolution method. If no location can be determined, the rule is treated as non-matching and evaluation continues to the next rule.

Rule Evaluation Order

Rules within a profile are evaluated top-to-bottom. The first rule that matches determines the outcome. If no rule matches, the default behavior is to allow playback.

🚨  Important: When both a video profile and a playlist profile apply to a request, a Deny from either profile results in a Deny. The most restrictive policy always wins across profile sources.

 

Related Articles

  • How to Create and Manage Content Rule Profiles
  • How to Use the Test Content Rules Tool
  • Mobile Location Enforcement for Apps Creator

Was this article helpful?

0 out of 0 found this helpful

Articles in this section