> For the complete documentation index, see [llms.txt](https://docs.peakcommerce.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.peakcommerce.com/product/reporting-and-analytics/third-party-analytics/hiding-payment-details-from-analytics.md).

# 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

* [Heatmap Privacy](/product/settings/access-security/heatmap-privacy.md)
* [Integrating Third-Party Analytics with PeakCommerce](/product/reporting-and-analytics/third-party-analytics/integrating-third-party-analytics-with-peakcommerce.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.peakcommerce.com/product/reporting-and-analytics/third-party-analytics/hiding-payment-details-from-analytics.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.