Analytics & Zero-PII Telemetry
Monitor your international conversion lift with lightweight, real-time edge telemetry that respects user privacy with strict zero-PII compliance.
Core Conversion Metrics
Fires when an eligible visitor in Tier 2, Tier 3, or an override country views your localized discount banner.
Recorded when a visitor clicks “Apply Discount” or copies the coupon code to their clipboard.
The percentage of visitors who engaged with the coupon after seeing the localized banner (Clicks / Impressions * 100).
Counts proxy or cloud hosting visitors (AWS, GCP, DigitalOcean) who attempted to access discounted pricing.
High-Velocity Telemetry Pipeline
Traditional analytics tools slow down user interactions with blocking requests. ParityEdge uses non-blocking browser primitives:
Asynchronous Event Dispatch (`navigator.sendBeacon`)
Dispatches a minimal text/plain event beacon asynchronously in the browser background without blocking page unloads or UI interactions.
Sub-Millisecond Edge Memory Buffering (`POST /v1/event`)
The edge engine increments in-memory edge counters in milliseconds and responds immediately with 204 No Content.
Scheduled Rollup Aggregation
A scheduled background worker aggregates buffered counts into persistent project analytics for permanent dashboard charts.
Zero-PII Privacy & GDPR Compliance Guarantee
ParityEdge is strictly designed with a Zero-Personally Identifiable Information (Zero-PII) architecture:
- Zero IP Persistence: Visitor IP addresses are inspected ephemerally in RAM at the global edge for country lookup and never stored in any database.
- Zero Cookie Tracking: No tracking cookies, third-party session identifiers, or fingerprinting scripts are placed on visitor devices.
- GDPR & CCPA Compliant by Default: Because no personal data is collected or transferred, no cookie consent banners are triggered.
Rate Limits & 429 Responses
To protect edge infrastructure and ensure fair access across all projects, the analytics endpoint enforces two independent rate limits.
| Layer | Scope | Limit |
|---|---|---|
| IP-level (WAF) | Per visitor IP | 100 req / min |
| Project-level (Worker) | Per project ID | 500 req / min |
What happens when a limit is hit
- The edge returns
HTTP 429 RATE_LIMIT_EXCEEDEDwith aRetry-After: 60header. - The ParityEdge SDK silently absorbs 429s — your visitors' checkout experience is never disrupted.
- Only analytics event beacons are affected. Discount lookups (
/v1/lookup) use a separate quota. - Limits reset automatically every 60 seconds. No manual intervention is needed.
When would I see a 429?
Normal production traffic — even high-volume sites with thousands of concurrent visitors — stays well within the 500 events/min per-project limit. You would only encounter a 429 if your site is experiencing a sudden traffic spike that exceeds typical patterns, or if you are load-testing with a script that fires many events in a tight loop. In either case, the SDK handles it gracefully with no user-facing impact.
Next: Troubleshooting & FAQs
Common questions regarding domain whitelisting, fail-open guarantees, and local debugging.