Google Analytics
Best for
Website/app owner analytics: traffic, funnels, and campaign performance.
Not built for
Showing every end customer their own personal page analytics inside your SaaS.
Multi-Tenant Geolocation Analytics for SaaS
Show every customer where their visitors come from with one script + one widget
GeoPulse is a client-facing analytics tool for SaaS products that offer personal customer pages, including link-in-bio pages, countdown pages, forms, digital cards, and portfolios.
Install one lightweight script on those pages and embed one widget in your app so each customer can see their own visitor location, source, device, and trust signals. GeoPulse handles geo enrichment, tenant isolation, and privacy-safe IP processing so you can ship in under 10 minutes.
No cookies required
One-line script collection
Embeddable geo analytics widget
What Each Tool Is For
Google Analytics and Plausible vs GeoPulse
Google Analytics and Plausible are mainly for the owner of a website/app. GeoPulse is for the owner's end customers, so each customer can see analytics for their own personal share page.
Plausible
Best for
Simple analytics for a site/app owner who wants a clean dashboard.
Not built for
Per-customer analytics dashboards for dynamic personal share pages.
GeoPulse
Best for
End-customer analytics for personal share pages (link-in-bio, countdown, forms, cards, portfolios).
How it works
Each customer can see who viewed their page, from where, and key metrics like device, network, and security.
Built For
SaaS with personal share links
Link-in-bio, countdown/timer, form, digital card, and portfolio page products.
Collection
Script + Pixel + API
Unify web, email, and backend geo events in one pipeline.
Data Model
User-level multi-tenancy
User A and User B data stay isolated by default.
Privacy
Privacy-safe processing
IP masking and compliance-ready handling before storage.
Founder Journey
From Setup to End-User Insights
Two core steps: add one script to collect data, then embed one widget to show each customer their geo analytics. Optional API/pixel support is included for more sources.
Core Step 1
Install the Tracking Script
Drop one script on your page template to capture views, time, source, and location context automatically.
One-line install
Dynamic-page friendly
One-line script install
<script src="https://geopulse.io/tracker.js"
data-key="PUBLIC_KEY"
data-sub="public_profile"
async></script>Optional Sources
Add Email and Backend Events
Send pixel or API events through the same project when you want geo insights from emails or backend flows too.
Email pixel
Backend API
Optional event sources
<img src="https://geopulse.io/api/p.gif?key=PUBLIC_KEY&sub=email_newsletter&m_campaign=spring_launch&m_plan=pro" width="1" height="1" />
POST /api/log
Authorization: Bearer PRIVATE_KEY
{
"ip": "x.x.x.x",
"project_id": "123",
"sub_project": "checkout",
"metadata": {
"campaign": "spring_launch",
"plan": "pro",
"segment": "trial",
"device": "desktop",
"industry": "saas"
}
}Core Step 2
Embed the Geo Analytics Widget
Add prebuilt components to your dashboard so each paying user can see who viewed their page, from where, and when.
Client-facing
Theme controls
Client dashboard component
import { GeoMap } from '@geopulse/react';
<GeoMap
apiKey="PUBLIC_KEY"
region:true
source:true
ip_type:true
ip_trust:true
metadata:true
display_mode:true
date_range:true
start_date:01012025 // MMDDYYYY
end_date:01012026 // MMDDYYYY
only_chart:false
/>Geo Demo
Analytics UI Your Customers Can Use
This is an early preview, not the final product. The production version will be similar in direction, with a more polished experience and expanded capabilities.
Layer Intensity
Customize View
Map Data 漏2026
Country
Active Users
-
Germany 860
-
United States 623
Demo UI for Your Dashboard
This is how the analytics section can look when integrated in your app.
Location Overview
- Location Mapping馃嚭馃嚫 United States 路 California 路 San Francisco 路 94103
- Precise Visualization37.7749, -122.4194 city 路 39.80, -98.50 country
- Timezone Intelligence8:00 PM PST local peak (from 04:00 UTC)
Network Overview
- Provider TrackingComcast 路 Comcast Cable Communications
- Connection QualityMobile 31% 路 Broadband 64% 路 Satellite 5%
Business Traffic
- Company IdentificationApple, Microsoft, Salesforce office traffic
- Domain Associationapple.com 路 microsoft.com 路 salesforce.com
- Usage ClassificationBusiness 44% 路 Education 13% 路 Government 9% 路 Residential 34%
Security & Velocity
- Request FrequencyAvg 12/min 路 Peak 57/min at 8:00 PM
- Fraud DetectionVPN/Proxy 8.9% 路 Tor 0.6% 路 Malicious Bots 2.1%
- Abuse Scoring24/100 (Low-Medium) 路 83 IPs matched risk feeds
Device Split
- Device MixDesktop 54% 路 Mobile 36% 路 Tablet 10%
What GeoPulse Includes
A Product Structure That Scales
01
Collect
JS tracker, 1x1 email pixel, and direct backend API.02
Process
Tenant-aware routing, IP masking, and metadata enrichment.03
Present
Embeddable map widgets and country/city insights for end users.Multi-Tenant Project Engine
- Dynamic project provisioning per customer
- Sub-project namespacing for feature-level analytics
- Hard data isolation between clients
Triple-Threat Data Collectors
- JS tracker for web apps and SPAs
- 1x1 tracking pixel for email and markdown
- Direct backend API for server-side logging
- Metadata tags for campaign, plan, segment, and custom fields
UI-as-a-Service Components
- Interactive world map widget
- Top countries and cities panels
- Source breakdown charts and live theming
- Configurable filter controls and metadata-driven slices
Privacy-First Architecture
- IP masking/anonymization before storage
- No-cookie tracking model
- Compliance-ready architecture notes
Problem + Solution + Use Cases
What GeoPulse Solves for SaaS Founders
The Problem
- Your Pro users ask: who viewed my page, from where, and at what time?
- Building multi-tenant analytics from scratch takes weeks of senior engineering.
- Raw IP handling creates GDPR and privacy/compliance pressure.
- Scaling to millions of hits across thousands of pages is expensive and complex.
The GeoPulse Solution
- One script tag collects geo events from every shareable page.
- One embeddable widget shows geo insights inside your existing dashboard UI.
- Tenant-safe isolation ensures each customer only sees their own analytics.
- Privacy-first pipeline handles IP masking, enrichment, and compliance-sensitive processing.
- Infrastructure is built to ingest and query high-volume hit traffic reliably.
Use Cases
Where Teams Use GeoPulse
SaaS Pro Dashboards
Show each paying user where their page visitors are coming from in real time.
Shareable Page Products
Add geo analytics to link-in-bio pages, shareable countdown/timer links, form pages, digital cards, and portfolio links.
Agency White-label Reporting
Give each client isolated geo reporting without building custom analytics infra.
Email Campaign Geography
Track geo performance from email opens when JavaScript cannot run on the page.
Launch & Market Expansion
Identify top countries for product launches and localization priorities.
Risk & Trust Signals
Use IP type and trust filters to support fraud checks and abuse workflows.
Build vs Buy Snapshot
Build internally
- Build collection, geo enrichment, and dashboard UI from scratch
- Implement multi-tenant access control and strict data isolation
- Own GDPR/privacy risk and ongoing infra scaling costs
Use GeoPulse
- One script for collection, one widget for client-facing analytics
- Tenant-safe architecture included from day one
- Privacy-first geo pipeline managed for you
Early Access
If your users ask "who viewed my page and from where?", GeoPulse is built for you.
Coming Soon