AffStackDev Gate Manager / Targeting & geography
Show each gate where it belongs.
Combine clear page scope with conditions for the visitor, content, request, time and store. Keep exceptions explicit.
Free plugin · All features included · Free Gate Manager license
Start with pages and paths
Choose all public pages with exclusions, or only included paths. Target an exact path or its descendants, decide whether the homepage is included, and keep policy, login and exit pages reachable.
Search the site for relevant content and retain readable rule summaries as you build. A basic path exclusion takes precedence over advanced targeting.
Build a focused set of conditions
Content and visitor
Use page or product IDs, post types, taxonomies, logged-in state, roles, capabilities or a specific user.
Requests and return visits
Use query parameters, referring domains, ordinary cookies or the new/returning visitor marker for audience targeting.
Time and prerequisites
Choose weekdays, time windows and date boundaries, or use another gate’s current grant to sequence a journey.
Combine conditions with ALL or ANY, nest groups and invert a group when needed. Choose what should happen when a fact is unavailable, then compare matching and non-matching scenarios in Simulator.
Use a location source that fits the site
Choose visitor selection, a trusted Cloudflare country header, WooCommerce shipping destination or local geolocation, a local MaxMind database, or a developer adapter. Decide whether visitors may supply missing details or replace a detected location.
Location eligibility can require allowed countries and regions. Geography is off by default, and a missing location does not satisfy that access requirement. A detected or selected location is not independent proof of residency.
Make store conditions part of the journey
WooCommerce adds product, variation, category, tag, SKU, attribute, cart and customer-history conditions. Use these alongside the gate’s requirement to decide when purchase validation applies.