---
title: Commerce Connect 13 + ODP
slug: commerce-connect-13/docs/commerce-connect-13-odp
docTags:
createdAt: 2026-07-23T09:44:51.000Z
---
:::hint{type="info"}
**Note**
This integration exports data from Commerce Connect 13 and imports it into Optimizely Data Platform (ODP)
:::
To integrate Commerce Connect 14 with ODP, use one of the following:
- [Commerce Connect + ODP](docId\:lcPRGjAMoRCh7XTHB5G9x) (recommended)
- [Commerce Connect 13 or 14 + ODP](docId\:PSSC0uOUeWxJZsM3nfSdg)
Optimizely Commerce Connect 13 contains an Optimizely Data Platform (ODP) export job to export data, including orders, customers, and products, to ODP.
## Setting keys
1. `episerver:odp.ExportCatalog` – Export products to ODP. The default is true.
2. `episerver:odp.ExportCustomers` – Export customers to ODP. The default is true.
3. `episerver:odp.ExportOrders` – Export orders to ODP. The default is true.
4. `episerver:odp.IncludeProducts` – Include products and variations and packages. The default is true.
5. `episerver:odp.ProductBatchSize` – Batch size when sending products to ODP. The default is 50.
6. `episerver:odp.OrderBatchSize` – Batch size when sending orders to ODP. The default is 50.
7. `episerver:odp.CustomerBatchSize` – Batch size when sending customers to ODP. The default is 50.
## MarketKey settings
The `MarketKey` settings define the collection of `MarketKey`, which the ODP job uses to get Commerce Connect's data to ODP. `MarketKey` contains 3 properties:
1. `MarketId` – ID of the market, such as US or SWE, to filter Orders or Products when collecting data.
2. `AccessKey` – ODP’s credential.
3. `EndpointUrl` – The URL that receives the data from Commerce Connect.
You can use one of two formats to set the `MarketKey` collection.
### Format 1
```javascript
```
```javascript
```
### Format 2: Added from Customized Commerce 13.37.0
- Support catalog setting with one or multiple values – When a catalog is present:
- The job checks if there are any `LineItem` in the order that belongs to a catalog, then filters the orders by catalog.
- The job filters products by catalogs.
- The job sends customers to every endpoint or access key because customers are unrelated to catalogs.
- Configuration setting format – The job uses `scope` to create a group, which is any valid string used as a setting
- Keys – `Catalogs` and `MarketIds` keys containing multiple catalog names or market IDs are separated by **;**.
**Examples of format setting**
1. **Empty catalog** – This format can replace the old setting format.
```javascript
```
```javascript
```
1. **One catalog**
```javascript
```
```javascript
```
1. **Multiple catalogs**
```javascript
add key="episerver:odp.EndpointUrl.Alias1" value="Alias1_endpoint"/>
```