In digital marketing, we often use time on page as a key performance indicator (KPI). The logic makes sense—if someone spends more time on your site, they must be engaged, right? Studies have linked higher time on site to increased conversions, better brand recall, and higher return visit rates.
But there’s a catch. The numbers you see in your analytics platform might not tell the full story.
The Privacy Factor: Why Your Data May Be Incomplete
Over 80% of web traffic today comes from users with advanced privacy settings enabled. Some of these settings are user-controlled, but others—such as Apple’s strict privacy policies—are built directly into the operating system.
For example, Apple’s Intelligent Tracking Prevention (ITP) blocks certain tracking scripts by default. This means that many users never send a “page close” or “second interaction” event back to your analytics platform. And without that final timestamp, analytics tools often record the session as zero seconds—even if the user was actively engaged with your content.
The Impact: High Bounce Rates and “Zero-Second” Visits
If a visitor lands on your page, reads your content for two minutes, and then leaves without clicking another page, analytics tools might log this as a bounce with zero seconds spent on site. That’s because most analytics systems measure time by comparing timestamps between page events (e.g., Page A to Page B). If there’s no second page event, there’s no way to calculate elapsed time. Setting up an event like scroll or page close may not be enough. Apple has already anticipated these kinds of work around.
As a result, you may see:
- Unusually high bounce rates, even if users are actually reading your content.
- A significant portion of traffic showing 0 seconds on page, when in reality, many of those users are engaged.
What Can You Do?
While you can’t change how privacy settings work, you can take steps to get a clearer picture of user engagement:
- Use Engagement-Based Metrics – Instead of relying solely on time on page, look at metrics like scroll depth, video plays, or interaction events to understand user behavior.
- Implement “Heartbeat” Tracking – Some analytics platforms allow you to fire an event every few seconds to capture active engagement. This can help measure time more accurately on many devices but won’t override Apple’s ITP. If a high percentage of traffic on the website is from Apple devices, this may not help.
- Watch for Trends, Not Absolutes – Even if the exact numbers aren’t perfect, trends over time still provide valuable insight into how your content performs.
The Bottom Line
Time on page is an important metric, but privacy settings and tracking limitations mean that what you see in analytics isn’t always reality. A high bounce rate doesn’t always mean users aren’t engaged—sometimes, it just means they left no trace.
References
Apple’s Intelligent Tracking Prevention (ITP) is a privacy feature built into Safari and WebKit, designed to limit cross-site tracking and reduce the ability of advertisers and analytics platforms to track users across the web.
Here are some official and authoritative sources that explain ITP in detail:
- Apple’s Official WebKit Blog on ITP
- Apple frequently updates details about ITP on the WebKit blog.
- Link: https://webkit.org/blog/
- Example post: Full Third-Party Cookie Blocking and More
- Apple’s Developer Documentation on Privacy and Tracking
- Link: https://developer.apple.com/documentation/safari
- This covers privacy features, tracking prevention, and how developers can work within Apple’s privacy framework.
- Mozilla’s Explanation of ITP (for Context on Privacy Features)
- While this is not Apple-specific, Mozilla has covered ITP in discussions of tracking prevention.
- Link: https://developer.mozilla.org/en-US/docs/Web/Privacy/ITP
These references should provide you with technical details and official Apple documentation about how ITP works and why it impacts analytics tracking.