Overview
Caps are your financial safety net. They allow you to set strict limits on how much traffic, revenue, or payout an Offer can generate within a specific timeframe.
You can apply Caps at three levels:
Why Your Caps Might Leak
Understanding the Processing Delay (And How to Protect Your Budget)
๐ What Actually Happens During High Traffic
Enter your actual budget limit and traffic volume to calculate the safest cap setting.
- Always set caps 10-15% lower than your true budget limit
- Higher traffic = bigger buffer needed (50+ conversions/hour = 15-20% buffer)
- Monitor the Pacing Report to catch approaching limits early
- Enable Cap Threshold Alerts at 80-90% to get advance warnings
- Review "Pending" conversions that came in during the delay window
Cap Types: Hard Caps vs. Soft Caps
Choose the enforcement method that fits your needs.
Hard Caps
Soft Caps
Rules of Precedence (Which Cap Wins?)
It is common to have multiple caps running at once (e.g., a Partner Cap AND an Offer Cap). The Golden Rule: The system respects whichever cap is Reached First.
โก Interactive Precedence Simulator
Now that you understand precedence, here's a quick reference table:
At A Glance: Cap Scopes
Step-by-Step Configuration
Learn How to Create and Configure Offer Groups โ
Proactive Monitoring: Alerts & Pacing
Don't wait until the traffic stops to find out you hit a cap.
Reference: Time Durations
How Everflow calculates timeframes:
Troubleshooting "Over Cap" Errors
When a cap is reached, data changes. Here is how to diagnose it.
๐ Cap Issue Diagnostic Tool
Select what happened, and we'll show you exactly what caused it and how to fix it.