Essential recommendations for configuring Priority Protect based on your use case.

Scheduled Priorities

Best for: Product launches, flash sales, ticket releases, limited drops

Configuration

Capacity Settings

• Set max concurrent visitors to 60-70% of tested capacity

Activation Timing

• Activate 30-60 minutes before event start
• Enable pre-admission (30 min default) to manage early arrivals

Matching Conditions:

Be specific to avoid catching unintended pages:

✅ GOOD: domain:shop.example.com AND url:/limited-edition/product-123 ❌ AVOID: domain:shop.example.com (catches entire site)

Always-On Priorities

Best for: Consistently high-traffic pages, checkout protection, ongoing ticket sales

Configuration

Capacity Settings

• Unexpected peaks and traffic surges

Activation Strategy

• Priority will be enabled automatically when the number of visitors on your website reach the threshold configured for this priority (maximum Concurrent Visitors)

Matching Conditions:

Target full domain or specific high-traffic sections:

✅ GOOD: domain:www.example.com

✅ GOOD: domain:tickets.example.com AND url:/checkout

Priority Rank and Matching Order

When a visitor arrives, Priority Protect evaluates priorities in rank order from lowest to highest. The first priority that matches is applied.

📘

Critical Rule Once a priority matches, evaluation stops. No other priorities are checked, even if they might also match.

Rank 100: domain:shop.example.com AND url:/limited-edition
Rank 200: domain:shop.example.com AND url:/checkout  
Rank 300: domain:shop.example.com

Visitor goes to shop.example.com/limited-edition: ✅ Rank 100 matches → This priority is applied ⏭️ Ranks 200 and 300 are never evaluated

Best Practice: Order from Specific to General

Always structure your ranks this way:

1. Low ranks (100-500): Time-Based priorities with specific URLs
2. Mid ranks (600-800): Time-Based priorities with broader matching
3. High ranks (900+): Always-On priorities (broadest matching)

📘

Why Always-On Should Be Last Always-On priorities typically have broader matching conditions (entire domains or large URL patterns). If placed at a low rank, they will "catch" all traffic and prevent more specific Time-Based priorities from ever matching.

Ranking Strategy

Use increments of 100 to allow inserting new priorities later. Reserve Low Ranks for Critical Events

✅ Good: 100, 200, 300, 400 ❌ Avoid: 1, 2, 3, 4 (no room to insert between)