How to privacy-scrub json events for analytics pipelines
- Step 1Export sample analytics events — Copy a batch of representative analytics events from your Segment debugger, Amplitude event explorer, or a short capture from your analytics SDK console logging.
- Step 2Identify fields to scrub — Common PII fields in analytics events: email, name, phone, ip, userId (if it is a real email), address, postalCode. Fields to keep: anonymousId, event, timestamp, sessionId, deviceType, country.
- Step 3Apply the filter and review the output — Paste the events and run the filter. Verify that user identification fields are absent while event signal fields (page path, button name, funnel step) are preserved for analytics.
- Step 4Implement in your analytics middleware — Mirror the scrub logic in your Segment middleware plugin, Amplitude enrichment function, or a pre-send event transformer. The key list from this tool becomes your privacy filter configuration.
Frequently asked questions
Should I remove userId from analytics events for GDPR compliance?+
It depends on what userId contains. If userId is a real email address, it is PII and should be replaced with a pseudonymous internal ID. If userId is an opaque UUID with no PII content, it can be retained for user-level analytics. Always use pseudonymous identifiers (UUID or hashed ID) rather than email addresses as analytics user identifiers.
How do I handle Segment Identify calls that explicitly contain user traits like email?+
Segment Identify events are designed to carry user traits including email. For GDPR-compliant analytics, either: (1) only Identify in your own data warehouse and never forward to Segment, or (2) use Segment's Privacy Portal to create field-level masking rules that strip email from Identify events before they are forwarded to downstream destinations.
Are the analytics event payloads uploaded to JAD Apps?+
No. Processing runs entirely in your browser. Analytics event data including user identifiers, IP addresses, and behavioral data are never transmitted to JAD Apps servers.
Privacy first
Conversion runs locally in your browser. No file is uploaded — only metadata counters are saved for signed-in dashboard stats.