Picture the stack of self-guided tour brochures sitting at your welcome center. You ordered 2,000 in the spring. By fall, 1,400 are gone. How many became walking tours? How many are in a recycling bin in Akron?

You don’t know. Neither does your funder.

This is the core problem with heritage tourism program evaluation, and it’s not unique to small organizations. A 2025 USGS report reviewing visitation estimation practices across seven federal land management agencies found that counting visitors is still an unresolved challenge at every level of the field - with inconsistent methods, varying definitions of what constitutes a “visit”, and significant uncertainty in reported numbers even for agencies with substantial resources. Counting the total number of visits is described as inherently challenging, and the report notes that while automated counters work reasonably well for defined entry points, the approach breaks down for dispersed recreation areas with multiple access points. A self-guided walking tour through a historic district fits that second category precisely.

Congress took this seriously enough to act on it. The EXPLORE Act, signed in 2024, specifically requires that agencies report accurate annual visitation data consistently across units of federal recreational lands and waters - which is itself an acknowledgement that they currently don’t.

What This Means for Heritage Grant Reporting

Federal and state heritage grants don’t typically ask for the same sophisticated engagement analytics you’d expect from a digital marketing campaign. The NPS Heritage Partnership Program’s 2024 summary data reports on metrics like partner organizations engaged, volunteer hours contributed, historic sites preserved, and capacity-building assistance provided to other organizations. Visitor counts, where they appear at all, are aggregate estimates at the regional level.

But that doesn’t mean your visitor data doesn’t matter. Grant reporting requires that every figure trace back to a source. Audit trail requirements mean every reported figure must trace back to source data - and this is where manual, spreadsheet-based reporting falls most visibly under scrutiny. “Approximately 900 visitors” is fine as a narrative flourish. It’s a liability if someone asks how you arrived at it and the answer is “we counted the brochures left over”.

The practical issue for program reporting is consistency over time. A defensible number collected using a documented methodology (even an imperfect one) is more useful across grant cycles than a better estimate you can’t reproduce. Funders evaluating renewals want to see that you’re measuring the same things the same way, and that your numbers are moving in a direction you can explain.

Where Self-Guided Content Creates a Specific Gap

Self-guided tours are among the hardest heritage programs to document. There’s no ticket, no sign-in sheet, no interpreter counting participants. A PDF downloaded from your website may have been used at every stop on the route, or opened once and closed. You genuinely cannot tell.

This isn’t a minor inconvenience; it’s a cumulative reporting problem. Organizations that can’t document their self-guided programming tend to either underreport it in grant narratives or avoid quantifying it all, which makes it look like a lower priority than it actually is. Over time, programming that isn’t measured tends not to get funded.

The USGS report notes that emerging methods like geolocated social media and mobile device location data are informative but no single data source is accurate enough to substitute for on-the-ground counts across a wide range of site types. Which means: if you want reliable visitor data for your self-guided content, you need to build data collection into the delivery mechanism itself.

What Digital Delivery Changes

When self-guided tour content is delivered as a mobile web experience rather than a PDF or printed brochure, visitor interactions generate data automatically - timestamps, stop-level engagement, geographic origin data - without any staff effort. Every session becomes a data point with a source you can cite.

This doesn’t make your reporting perfect. Geographic data inferred from device behavior has known limitations. Session data can’t tell you how deeply someone engaged with the content at each stop. But it gives you something auditable: a count with a methodology behind it, collected consistently, that you can compare against itself year over year.

Platforms built specifically to accommodate heritage tourism, including DestinationHub, are designed to surface this kind of program-level analytics - not generic web traffic data, but stop-by-stop engagement metrics tied to the specific content you’ve invested in producing.

A Practical Starting Point

If your self-guided programming can’t produce auditable data right now, the goal before your next grant cycle isn’t perfection, it’s documentation. Pick a method, write it down, apply it consistently, and note its limitations in your narrative. A count with acknowledged methodology gaps is more defensible than an estimate with none.

And if you’re sitting on existing written tour content in print or PDF, it’s worth asking whether the delivery format is the reason you can’t measure it - and whether that’s a problem you can solve.