---
schema_version: "1"
id: d44a4a383d3b1b7aeaa53277dd33c4ed4395e684898ef698470c17b83cb0d1fa
title: isanalyticsoff Element
collection: developer
version: current
locale: en-us
portal_url: https://docs.salesforce.com/developer/current/en-us/commerce-cloud/b2c-commerce/guides/isml/b2c-isanalyticsoff.md
canonical_url: https://developer.salesforce.com/docs/commerce/pwa-kit-managed-runtime/guide/b2c-isanalyticsoff.html
source_site: developer.salesforce.com
content_type: documentation
content_hash: 6685648526673cfa9db761abe490e7ba2324e37f5fa8a77b8f251804f5ae3289
products:
  - Composable Storefront
  - Salesforce APIs
---
# isanalyticsoff Element

Each HTML page served by B2C Commerce includes a JavaScript snippet for analytics and active merchandising tracking purposes. If you must disable this tracking because it causes problems with your site, do so for the entire site by entering a Customer Support ticket, or include the `<isanalyticsoff/>` element at the end of one or more templates to disable analytics at the page level.

## Syntax

```
<isanalyticsoff/>
```

## Purpose

**important:** Use this element only for single pages and only for an emergency situation. Although the element is part of the API, it can prevent the correct tracking of analytics and active merchandising data.

## Example

This is an example of a JavaScript snippet added to the end of a template to collect B2C Commerce analytics:

```javascript
<!-- B2C Commerce Analytics code 1.0 -->
<script type="text/javascript"
 src="/on/demandware.static/Sites-BV-Site/-/default/v1315220487813/internal/jscript/dwanalytics.js">
</script>
<script type="text/javascript">
//
<!-- /* <![CDATA[ */
 try{ var trackingUrl = "http://us.dv.dev1.our.customer.bestcustomer.it/on/demandware.store/Sites-BV-Site/default/__Analytics-Tracking";
 var dwAnalytics = dw.__dwAnalytics.getTracker(trackingUrl);
 if (typeof dw.ac == "undefined") { dwAnalytics.trackPageView();
 } else { dw.ac.setDWAnalytics(dwAnalytics);
 } }catch(err) {}; /* ]]> */ // --> </script>
 <isanalyticsoff/>
```

In this case, the tracking code is considered a cross-site scripting threat if you use an HTTPS iframe and generate this iframe via ISML. Add the `<isanalyticsoff/>` element at the end of one or more templates to disable B2C Commerce analytics at the page level, thereby preventing the threat.