> 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/integrating-third-party-analytics-with-peakcommerce.md).

# Integrating Third-Party Analytics with PeakCommerce

Understanding how visitors and customers behave on your storefront and inside your journeys is key to improving conversion and experience. Rather than locking that behavioral data inside PeakCommerce, you can feed it into the product-analytics and data tools your teams already trust — so storefront events sit next to the rest of your reporting and modeling.

## Why connect an analytics tool

* **Deeper user insight** — see the pages customers visit, the plans they consider, and where they hesitate.
* **Data-driven decisions** — inform pricing, packaging, and page design with real behavior.
* **Less friction** — find and fix drop-off points across the buying journey.
* **Custom reporting** — model the metrics that matter most to your business in your own warehouse or analytics workspace.

## What you can connect

PeakCommerce connects to leading analytics and data platforms through the **Analytics & Data** integration category, including **Heap**, **Google Analytics**, **Mixpanel**, **Amplitude**, **Segment**, **Snowflake**, **BigQuery**, **Databricks**, **Looker**, and **Tableau**.

Most product-analytics tools — Heap and Google Analytics among them — work by adding the vendor's tracking snippet to your storefront so the tool auto-captures clicks, page views, and form interactions. You add that snippet once, and it captures activity across your published pages and journeys.

## How to configure

1. In the vendor's tool, get the install snippet or write/measurement key (for example, a Heap project ID or a Google Analytics measurement ID).
2. In PeakCommerce, open the **user menu (bottom-left) → Settings → Tracking Scripts** (under *Developer Tools*) and paste the snippet into **Head scripts** — or into **Body-start scripts** for a `<noscript>` fragment like Google Tag Manager's iframe. Saving requires a **system administrator**, and you are always editing the environment you're signed in to: keep a test container on sandbox and your live container on production, so test traffic never pollutes your production dashboards. See [Tracking Scripts](/product/settings/developer-tools/tracking-scripts.md).
3. *(Optional)* Add finer-grained snippets for funnel goals: a single page's snippet lives in the page editor's **Tracking** panel, a journey's in the journey editor's **Settings** tab, and a single step's in the step editor's **Tracking scripts** section — ideal for firing a distinct conversion event per step of a multi-step flow. These **extend** your tenant-wide scripts unless you switch on **Suppress tenant default**.
4. *(Optional)* To also capture behavior on the **signed-in customer portal**, enable **Customer portal tracking** on the Tracking Scripts page — behind-login pages run no tracking scripts until you deliberately opt in.
5. Publish, then confirm events are arriving in the analytics tool by walking through a journey yourself — **as a visitor or signed-in customer**. Admin, CSR, and operator sessions never execute tenant tracking scripts, so an admin session is the wrong place to verify.

The **Heap** integration has a dedicated, deeper setup guide in the **Integrations** space — start there if Heap is your primary tool.

## Before you go live

* **Mask sensitive data first.** Storefront capture can include form fields, so configure masking before you publish — see [Hiding Payment Details from Analytics](/product/reporting-and-analytics/third-party-analytics/hiding-payment-details-from-analytics.md).
* **Mind privacy and consent.** Auto-capture tools record visitor behavior; make sure your tracking honors the consent and privacy obligations that apply to your customers' regions.

## Related

* [Hiding Payment Details from Analytics](/product/reporting-and-analytics/third-party-analytics/hiding-payment-details-from-analytics.md)
* [Tracking Scripts](/product/settings/developer-tools/tracking-scripts.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/integrating-third-party-analytics-with-peakcommerce.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.