Anonymous Web Tracking Challenges in Next.js and Expo with Supabase

Hey everyone, I'm currently architecting a platform for local businesses using a Next.js (Web) and Expo (Mobile) Monorepo with Supabase as the backend.

I’ve hit a wall with Profile View Tracking.

The setup:

• We track events like profile_view, whatsapp_click, etc., into a user_activity table.
• We use a Daily Aggregation Cron Job (at 2 AM) to crunch raw events into a profile_analytics_daily table for the business dashboard.

The problem: On Mobile, it’s smooth - users are mostly authenticated or have a persistent device ID. But on Web, it’s a mess.

1. Anonymous Traffic: Most users land via SEO and aren't logged in. I'm using localStorage for session_id, but it feels fragile.
2. Data Parity: The dashboard shows inconsistent numbers between Web and App views. It feels like the Web tracking triggers are either getting blocked by ad-blockers or missing the 'Aggregation' window.

My questions for the experts here:

• Are you using Next.js Middleware to track views server-side to bypass ad-blockers?
• How do you handle real-time 'Teasing' stats for business owners vs. the aggregated 'Deep' analytics?
• Is there a better way to handle session_id for anonymous SEO traffic that doesn't rely on flaky client-side storage?

Would love to hear how you handled the 'Web vs App' data sync in your startups!