### Start Local Storefront Preview (Shell)

Source: https://experienceleague.adobe.com/en/docs/commerce/optimizer/use-case/admin-use-case

Launches the local development server to preview storefront changes. This command is executed in the terminal within your IDE. Ensure Node.js and npm are installed and configured correctly.

```shell
npm start
```

--------------------------------

### Example config.json for Commerce Optimizer (JSON)

Source: https://experienceleague.adobe.com/en/docs/commerce/optimizer/use-case/admin-use-case

This is an example of a `config.json` file after updating it with specific Adobe Commerce Optimizer values. It includes placeholders for `ACO-tenant-id` and `celport-catalog-view-id` which need to be replaced with your actual instance details.

```json
{
  "ac-price-book-id": "west_coast_inc",
  "ac-source-locale": "en-US",
  "commerce-endpoint": "https://your-commerce-optimizer-instance.com/api/v1/tenant/YOUR_TENANT_ID",
  "ac-view-id": "YOUR_CATALOG_VIEW_ID"
}
```

--------------------------------

### Commerce Optimizer Tenant ID Example (Text)

Source: https://experienceleague.adobe.com/en/docs/commerce/optimizer/use-case/admin-use-case

This snippet shows an example URL for the Adobe Commerce Optimizer UI, highlighting the tenant ID. The tenant ID is a unique identifier for your Commerce Optimizer instance and is crucial for configuration.

```text
https://experience.adobe.com/#/@commerceprojectbeacon/in:XDevkG9W6UbwgQmPn995r3/commerce-optimizer-studio/catalog
```

--------------------------------

### AEM Assets Source Configuration for Commerce Optimizer (JSON)

Source: https://experienceleague.adobe.com/en/docs/commerce/optimizer/setup/product-visuals

This JSON configuration defines the source for AEM Assets images within the Commerce Optimizer. It specifies the locale and the layer name ('AEM-Assets') to ensure these images are applied as an overlay on the base product catalog.

```json
{
  "source": {
    "locale": "en-US",
    "layer": "AEM-Assets"
  }
}
```

--------------------------------

### Update Catalog Service Configuration in config.json

Source: https://experienceleague.adobe.com/en/docs/commerce/optimizer/storefront

This JSON snippet shows how to configure the Catalog Service (cs) section within the `config.json` file. It requires the catalog view ID and price book ID for your Adobe Commerce Optimizer instance. The locale is set to 'en-US'.

```json
"cs": {
   "AC-View-ID": "{catalogViewId}",
   "AC-Source-Locale": "en-US",
   "AC-Price-Book-ID": "{priceBookId}"
 }
```

--------------------------------

### Commerce Optimizer Catalog View Configuration

Source: https://experienceleague.adobe.com/en/docs/commerce/optimizer/use-case/admin-use-case

Specifies the catalog view configuration for the Adobe Commerce Optimizer. This includes the commerce endpoint URL for API interactions and a unique identifier for the specific view. Essential for fetching and displaying product catalog data.

```json
{
  "ac-price-book-id": "west_coast_inc",
  "ac-source-locale": "en-US"
}

// Catalog view header values:
// - `commerce-endpoint`: "https://na1-sandbox.api.commerce.adobe.com/Fwus6kdpvYCmeEdcCX7PZg/graphql"
// - `ac-view-id`:`"9ced53d7-35a6-40c5-830e-8288c00985ad"
```

--------------------------------

### Commerce Optimizer Configuration JSON

Source: https://experienceleague.adobe.com/en/docs/commerce/optimizer/use-case/admin-use-case

This JSON object defines the public configuration for the Adobe Commerce Optimizer. It includes API endpoints for commerce core and general commerce operations, as well as headers and analytics-related settings such as currency, environment, store details, and website information. This configuration is essential for connecting and operating the optimizer with Adobe Commerce.

```json
{
  "public": {
    "default": {
      "commerce-core-endpoint": "https://www.aemshop.net/graphql",
      "commerce-endpoint": "https://na1-sandbox.api.commerce.adobe.com/{{ACO-tenant-id}}/graphql",
      "headers": {
        "cs": {
          "ac-view-id": "{{celport-catalog-view-id}}",
          "ac-price-book-id": "east_coast_inc",
          "ac-source-locale": "en-US"
        }
      },
      "analytics": {
        "base-currency-code": "USD",
        "environment": "Production",
        "store-id": 1,
        "store-name": "ACO Demo",
        "store-url": "https://www.aemshop.net",
        "store-view-id": 1,
        "store-view-name": "Default Store View",
        "website-id": 1,
        "website-name": "Main Website"
      }
    }
  }
}
```

--------------------------------

### Update Storefront `config.json` with Celport Catalog View ID

Source: https://experienceleague.adobe.com/en/docs/commerce/optimizer/use-case/admin-use-case

This snippet shows the relevant section of the `config.json` file where you need to update the `ac-view-id` to point to your Celport catalog. Ensure you replace the placeholder ID with your actual Celport catalog view ID.

```json
{
  "public": {
    "default": {
    "commerce-core-endpoint": "https://www.aemshop.net/graphql",
    "commerce-endpoint": "https://na1-sandbox.api.commerce.adobe.com/Fwus6kdpvYCmeEdcCX7PZg/graphql",
    "headers": {
       "cs": {
          "ac-view-id": "9ced53d7-35a6-40c5-830e-8288c00985ad"

```

--------------------------------

### Commerce Optimizer Analytics Configuration

Source: https://experienceleague.adobe.com/en/docs/commerce/optimizer/use-case/admin-use-case

Defines the analytics settings for the Adobe Commerce Optimizer. Includes base currency, environment, store identification, and website details. This configuration is crucial for tracking and reporting commerce activities.

```json
{
  "analytics": {
    "base-currency-code": "USD",
    "environment": "Production",
    "store-id": 1,
    "store-name": "ACO Demo",
    "store-url": "https://www.aemshop.net",
    "store-view-id": 1,
    "store-view-name": "Default Store View",
    "website-id": 1,
    "website-name": "Main Website"
  }
}
```

--------------------------------

### Enable Facet Filtering with Metadata API

Source: https://experienceleague.adobe.com/en/docs/commerce/optimizer/merchandising/facets/add

This snippet demonstrates how to enable an attribute to be used as a facet in Adobe Commerce Optimizer by setting the 'filterable' parameter to true using the Metadata API. This is useful when an attribute is not directly available in the UI for facet creation. Ensure the catalog is synchronized after making changes.

```json
{
  "filterable": true
}
```

=== COMPLETE CONTENT === This response contains all available snippets from this library. No additional content exists. Do not make further requests.