---
schema_version: "1"
id: 1447a2dbaacc8958705ef709ac89e2bcb435ecf1c0f711b1063fff9231b4ebb6
title: Caching with A/B Testing for B2C Commerce
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/cc/264-0-0/b2c_caching_with_ab_testing.md
canonical_url: https://help.salesforce.com/s/articleView?id=cc.b2c_caching_with_ab_testing.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 6b3bb2e1cd6a3aeeeb13ee1ddb9c574bb236d0b4bebf2a3950bdc75cbb4dd4a7
description: Salesforce B2C Commerce provides different page caching configurations.
products:
  - Commerce
  - B2C Commerce
release: "264"
---
# Caching with A/B Testing for B2C Commerce

Salesforce B2C Commerce provides different page caching configurations.

If you apply personalized prices in an A/B test via promotions, use the personalization parameter `<varyby="price_promotion">` in the iscache tag of the corresponding templates. Using this parameter make sure that the personalized pages cache properly. We recommend, as a best practice, that you cache whenever possible. Uncached catalog, product, or search pages - whether A/B testing pages or regular pages - aren’t recommended because they degrade performance.

For example, use the following in your template if you apply personalized prices in an A/B test via promotions:

```markup
<iscache type="relative" minute="30" varyby="price_promotion"/>
```

By definition, the control group must contain no customization. If you introduce a custom experience for a control group, the pipeline/template containing the customization is no longer cacheable.