> 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

For businesses looking to monitor customer interactions within the e-commerce process through tools like FullStory, safeguarding user privacy is essential. This means ensuring that sensitive data, such as billing information, is not captured.

In the case of PeakCommerce’s online shopping experience, payment details are inputted on a Secure Page, which comes from the integrated payment system (for example, Zuora). To prevent these details from being tracked in your analytics, you can apply a specific CSS class (.fs) to the necessary fields on the Secure Page settings within your payment system.

Should there be a need to omit more information from being recorded during the e-commerce journey on PeakCommerce, this can be accomplished with JavaScript in the e-commerce site template. Here is a sample script that shows how to exclude certain details:

```
$(document).ready(function() { $('#bill_to_email').addClass('fs-exclude'); });
```

For specifying which billing contact details to exclude in the payment phase, the following are effective CSS input selectors. To adjust for “Sold To” contact details, simply change “bill\_to” to “sold\_to”.

```
#bill_to_company
#bill_to_first_name
#bill_to_last_name
#bill_to_email
#bill_to_phone
#bill_to_address1
#bill_to_address2
#bill_to_country
select[name=bill_to_us_state]
select[name=bill_to_ca_state]
#bill_to_province
#bill_to_city
#bill_to_postal_code
```


---

# 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.