What's new in Indivd: 2 April 2026

This is a larger-than-usual release covering seven months of development. Most of the work happened under the surface: rebuilding how data moves through the platform so everything loads faster, stays more accurate, and handles edge cases your locations were already hitting. On top of that foundation, you now have new advanced visitor analytics features, new settings for visitor qualification, improved control over who in your team sees what, and a wider API for connecting Indivd to your other tools.

Check out what's new:

• Data quality and reliability
• Advanced visitor analytics
• Visitor qualification settings
• User access and permissions
• Locations and opening hours
• People Counter
• API and integrations
• Speed and performance
• Maintenance

Data quality and reliability

• More accurate averages in summary widgets. Previously, gap-filled data (estimates used to cover periods when cameras were offline) could be mixed into your summary averages without being clearly separated. This is now fixed. When you look at an average in a summary widget, it reflects real data only, keeping your numbers trustworthy for decisions.
• Hourly metrics corrected for multiple locations. Hourly bounce rate and drop-in rate data was returning incorrect results when you had more than one location selected. Both are now fixed, so comparisons across locations are reliable at the hourly level.
• Business hours filtering restored. Filtering metrics by business hours was temporarily disabled during infrastructure work. It is fully re-enabled, meaning your data reflects actual opening hours again rather than including overnight or pre-open periods.
• Camera uptime data now gap-filled. System and camera uptime metrics now benefit from the same gap-filling logic as your visitor data. Short periods of connection downtime are handled consistently, so your reliability view is complete rather than showing blank gaps.
• Cross conversion data corrected. A bug was causing visitors who had visited both zones in a cross conversion analysis to be incorrectly excluded from the results. This is now fixed. If you use cross conversion to understand how visitors move between zones, your numbers are now accurate.
• Drop-in rate corrected in the dashboard. A mismatch between how drop-in rate was calculated in different parts of the platform has been resolved. The number you see in your dashboard now matches what the API returns.
• Dwell time filtering fixed. An issue with how filtered dwell time data was being aggregated has been resolved, making filtered dwell time breakdowns more accurate.
• Visitor tracking stays live without interruption. Previously, certain background processes could stall and required a system restart to recover, creating gaps in your visitor and line-cross data. The platform now detects and recovers from these situations automatically, so your data keeps flowing without manual intervention.
• Zone counts and line counts now stay in sync. Indivd measures visitors using both zone-based detection and line-crossing counts. In some cases these two methods could drift apart over time, producing small inconsistencies across different views of the same location. They are now synchronized, so the numbers tell a consistent story wherever you look.
• Re-identification accuracy improved. The system that recognizes when the same visitor moves between zones has been improved. Your cross-zone visitor journeys, qualified visitor counts, and funnel data are more accurate as a result, particularly in locations with complex layouts or high traffic.

Advanced visitor analytics

• Ideal Customer Profile (ICP). You can now identify which visitors best match your ideal customer profile and understand how your location performs at attracting and retaining them. Rather than treating all visitors equally, ICP lets you focus your decisions on the visitors who matter most to your business.
• Qualified visitors. Qualified visitor tracking is now available, giving you a clearer picture of how many visitors in your location are genuinely engaged, not just passing through. For stores, this is the difference between footfall and real commercial opportunity. For malls and airports, it shows how many visitors are actually reaching your commercial areas.
• Visitor value. You can now connect visitor behavior directly to revenue potential, seeing what a zone visit is worth based on conversion rates and average order value. This turns your visitor data into a business case: how much revenue is a layout change worth, which zone is underperforming relative to its traffic, and where is the biggest untapped opportunity?
• Demographics. Demographic insights are now available, letting you understand the composition of your visitors and how different groups behave across your location. Use this to make more informed decisions about product mix, staffing, and how you target different visitor segments.

These features are available upon request. Reach out to your personal Indivd contact or email hello@indivd.com to get started.

Visitor qualification settings

• Average order value per location, zone, and organization. You can now set an average order value directly in settings for each zone, location, or your whole organization. This feeds into funnel and conversion analysis so you can see not just how many visitors engaged, but what that engagement is worth in revenue terms. For stores, this means estimating the value of a zone's conversion rate. For malls and airports, it means putting a number on how much traffic to a specific shop or commercial area is actually translating into.
• Automatic qualification settings. You can now configure automatic visitor qualification rules at the organization, location, and zone level. Once set, Indivd applies your qualification thresholds consistently without manual intervention, so your qualified visitor counts are always based on the same criteria across your portfolio. You can also set a minimum threshold per zone to control what counts as a meaningful visit.
• Qualification settings visible in the locations table. Average order value and automatic qualification status are now shown as columns in the locations table, so you can see your settings across all locations at a glance without opening each one individually.

User access and permissions

• Search and sort in the user list. You can now filter and sort the list of users in your organization. For teams with many users across multiple locations, this makes it significantly faster to find a specific person or check who has access to what.
• Security improvement: location data is now strictly isolated. A security fix ensures that users can only access data for the locations they are permitted to see. Previously, under certain conditions, a user could retrieve metrics from locations outside their access. This is now blocked.

Locations and opening hours

• Locations that close after midnight now handled correctly. If your location's closing time falls after midnight (for example, a bar or late-night food outlet closing at 01:00), the platform now understands this correctly. Previously, closing times after midnight could be misread as closing the following day, which affected business hours filtering and metric calculations.
• Opening hours update more reliably. The process for syncing opening hours from Google has been improved to process all your active locations by default. Previously, updates could be inconsistent across locations. Your opening hours data is now more reliably kept up to date.
• Location settings load faster. Locations, zones, and the People Counter editor all load noticeably faster following a rebuild of how data is fetched in the background. For organizations with many locations or zones, the improvement is significant.
• Cache issues resolved in location settings. Changes you made to location settings were sometimes not visible immediately, requiring a page refresh to see the update. This is now fixed: edits take effect straight away.

People Counter

• More camera detail in People Counter settings. The People Counter settings table now includes six additional columns: Camera Model, Port, Stream Location, Stream Proxy, Custom ID, and Description. This makes it easier to identify and manage individual cameras, especially for larger installations where keeping track of each camera's setup matters for troubleshooting and onboarding.
• People Counter foldout now closes correctly. A bug where the add-camera foldout stayed open when navigating away from the People Counter editor has been fixed. The editor now behaves as expected when moving between sections.

API and integrations

• Camera metrics and system metrics now available via the public API. If your team connects Indivd data to a BI tool, data warehouse, or custom dashboard, you can now pull camera uptime and system reliability metrics through the same API you use for visitor data. This means you can build a complete operational picture in your own tools, not just visitor numbers but also the reliability of the data collection behind them.
• Expanded data available via API. The API now covers zone visits, bounce rate, line crosses, camera uptime, user and organization management, and real-time updates for bounce rate and zone visits. If you are building integrations or exporting data for deeper analysis, significantly more of the platform is now accessible programmatically.
• Passing-by lines available via API. Zone data returned by the API now includes passing-by line configuration. If you are integrating drop-in rate or funnel data into external tools, you now have the full context of how those metrics are defined at each zone.
• Timezone and filtering support in API responses. API responses now respect per-request timezone settings and support advanced filtering and aggregation. Data you pull via the API now aligns correctly with your local time, removing the need to handle timezone conversion yourself.
• Custom IDs now optional in organization settings. Setting a custom ID for your organization is no longer mandatory. This removes a friction point for teams that do not use custom IDs in their integrations.

Speed and performance

• The platform is significantly faster across the board. A large part of this release was rebuilding how data is fetched throughout the platform, moving to a more efficient approach that reduces how much work happens each time you load a page or switch between views. The result is faster load times in Settings, the dashboard, Locations, Zones, and the People Counter editor. The improvement is most noticeable in larger organizations with many locations, zones, or cameras.
• The System Dashboard is now powered by a faster data engine. The System Dashboard (introduced in the September 2025 release) has been moved to a faster underlying database optimized for time-series data. Camera uptime, system uptime, and FPS metrics now load and update more quickly, and gap-filling works correctly in the dashboard view.
• Camera crashes eliminated for affected hardware. A specific issue in how video streams were processed was causing some cameras to crash and stop recording on certain hardware setups. This has been fixed. Cameras that were previously unstable now stay online, meaning fewer data gaps and less need for manual intervention from your team or ours.
• Infrastructure security improvements. Security headers and authentication tokens are now correctly preserved when the platform redirects between services. This prevents edge cases where a session could appear to drop during normal navigation. A separate critical security vulnerability was also identified and patched in November 2025.

Maintenance

• Fixed daily rollup calculations that were producing incorrect totals under certain timezone conditions.
• Fixed timezone handling across summary queries to ensure consistent results regardless of your location's timezone.
• Fixed DST (daylight saving time) transition handling for camera metrics and system metrics, so data around clock changes is no longer affected.
• Resolved an issue where the currency shown in location forms defaulted to the first organization in the list rather than the selected organization.
• Fixed zone visit totals in the REST endpoint to always return the correct total value.
• Removed a stale cache that was causing incorrect data to appear after editing organization settings.
• Fixed public API response merging to return complete and correctly structured data.