Hiding Payment Details from Analytics
When you track the buying experience with analytics, heatmap, or session-replay tools, those tools should never capture sensitive data — payment details or personally identifiable information. PeakCommerce is built so that protection happens by design, with an extra control for the fields you choose to keep private.
Why this matters
Auto-capture analytics tools record what visitors see and do, which can include form contents. Letting card numbers, bank details, or PII flow into a third-party analytics or replay tool creates compliance exposure (PCI, privacy regulation) and risk you don't want sitting in someone else's data store.
How PeakCommerce protects payment data
Card and bank details are never on your page to capture. Payment fields are entered on the billing provider's secure hosted payment page (for example, Zuora's), rendered in an isolated iframe. PeakCommerce — and therefore any analytics or replay tool running on your storefront — never sees those values, so there's nothing to capture in the first place.
You control what else is masked. For everything PeakCommerce does render — contact and billing fields, custom inputs — you can exclude specific regions from capture.
How to mask additional fields
Masking is configured under Settings → Access & Security → Heatmap Privacy. There you provide masked selectors — CSS selectors (one per line) identifying the elements to keep out of capture. Matching elements are dropped at capture time and wiped from snapshots before anything leaves the browser, so sensitive contact or billing fields stay out of recordings while you still measure the rest of the journey.
You can set masked selectors as a tenant-wide default and add journey-specific selectors where a particular flow needs extra protection.
Gotchas
Add masks before you publish, not after. Anything captured before a selector is in place is already recorded; configure masking ahead of your first live traffic.
Match the real elements. A selector that doesn't match an on-page element masks nothing — verify masking on a live page after publishing.
Hosted payment fields don't need a selector. Because they live in the billing provider's iframe, they're already outside capture — masked selectors are for the PeakCommerce-rendered fields around them.
Related
Last updated
Was this helpful?