Introducing variable scan frequencies

Since 2017, Campnab scans have run at a set of frequencies. Our pay-per-use scans ran every 60 (Good), 15 (Better), and 5 (Awesome) minutes. For monthly and annual plans, these frequencies shifted to every 15, 10, and 5 minutes.

Many of our scans have been running more frequently than we stated publicly. For example, Yosemite scans have been operating every 2 minutes on the Awesome tier for two years. We just didn’t make a big deal out of this.

Debating the frequency of scans

Scan frequency and delivery are challenging topics. Some would love for us to scan parks every few seconds. Doing so isn’t practical for a few reasons. First, each scan takes time to run, be sorted (e.g., checking data against members’ parameters and filters), and then get queued for delivery.

Another issue with scanning every few seconds is that doing so would put unnecessary pressure on booking systems. Since the beginning of our service, we’ve worked to benefit parks and the third-party booking systems they use to manage campsite reservations. We want to help them sell more campsite reservations so more campers get out camping.

The third consideration is that not all parks require high-frequency monitoring. Yosemite is fiercely competitive—even if you use Campnab to scan it for canceled reservations. Arches is challenging but doable. Meanwhile, Sowchea Bay (my favorite) is easy to book through a campsite cancellation alert. So, the scan rate for Yosemite should be higher than Arches, and Sowchea Bay’s should be far lower.

Contemplating a responsive solution

Although we appreciate that most campers want the fastest scans possible, we feel it essential to operate responsibly. I guess it’s a bit like driving. Just because you can drive 120 MPH doesn’t mean you should. So, we’ve asked how to serve all of our members best—and do so in a considerate manner.

For the past weeks, we removed mention of scan frequency on our pricing page. A few of you have asked why. The answer is that we’ve been trying to shape and explain our new approach fittingly. If you check that page now, you’ll see that scan frequencies are referenced in broad terms of “frequent”, “boosted”, and “priority”.

Essentially, we’re moving away from one set schedule for all scans on a tier. Now, we’ll use a general rate for most scans but ratchet up the frequency for some popular parks. This approach will result in a range for scans to operate within, even when on the same tier.

Our new variable scan frequencies

The good news is that our scans and alerts are running faster across the board. We start with pay-per-use scans that have been updated to match the frequency of their corresponding plan rates. For example, a Good tier pay-per-use scan used to run every 60 minutes. It now runs every 10 to 15 minutes—just like scans on Good-tier plans.

Our Better tier scans now run a little faster (every 5 – 9 minutes). On the Awesome tier and above, scans run every 1 – 4 minutes. Again, these rates will vary based on the park. So, while we check Yosemite every minute on the Awesome tier, Arches will get checked every 3 minutes on that same tier. As time passes, we’ll dial in these frequencies based on demand.

We want you to receive alerts in a timely fashion. We also need to make this happen in a way that considers the parks and booking systems we all rely on. This variable scan frequency approach seems like a good way to achieve both goals.

Additional considerations

Although folks often ask for faster scans, their own response times can limit results. For example, members sometimes tell us a campsite was booked once they clicked through on the alert. When I check, I often see that they waited several minutes—sometimes hours—to click through on a notification. Setting a custom ringtone for campsite alerts can remind you to act quickly.

Also, our scan schedules are not to the second. Instead, these frequencies represent general timing that shifts a few seconds this way or the other. Since we started, we’ve sent over 5,000,000 alerts. Delivering this many alerts takes a lot of processing and isn’t without its challenges. There can be issues with booking systems, queuing backlogs, and even deliverability issues with your cell service provider. So, expect some amount of variation.

My last note on this matter is that sometimes scan frequency doesn’t matter that much. Consider California State Parks, which locks some canceled reservations for future release (these often state a set release time, which is typically off by up to 30 minutes). With unlock alerts, scan frequency matters less, given that these alert commonly arrive hours in advance of the site’s release.

That’s all folks!

Wow! That was a whopper of an article, wasn’t it? My wife often starts to fade off when I carry on for too long. I hope I didn’t lose you in the same way with this post. In any event, Eric S. and I feel pretty good about the approach we’ve outlined here. If you have any questions or concerns about what we’re doing, I encourage you to let us know via email.

Back to Blog index