---
schema_version: "1"
id: add0bf47786da155a63c4e6047f5ba604c635349cda6ef1cb3d8b5ec867c2f62
title: Kenshoo API Connector
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/mktg/264-0-0/mcidp_data_streams_api_connect_kenshoo.md
canonical_url: https://help.salesforce.com/s/articleView?id=mktg.mcidp_data_streams_api_connect_kenshoo.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: ef2d7345ca3ba90e22cd0ebe20d5409f16836a252bf4931260289ee7c370db33
description: Kenshoo provides digital marketing solutions in Search, Social, and Display.
products:
  - Marketing
  - Marketing Cloud Intelligence
release: "264"
---
# Kenshoo API Connector

Kenshoo provides digital marketing solutions in Search, Social, and Display.

- **Channel**: Search, Social, Display
- **Lag**: 1 Day

## Prerequisites

Provide a valid username and password, and a Kenshoo Account ID (also known as KS ID or Server Number).

The Server Number can be found within the URL string used to log into Kenshoo. For example, if your URL string is KS1234.kenshoo.com, your Server Number is 1234. There are occurrences where Kenshoo provides their customers with "masked URLs" (for example, name.kenshoo.com). In these situations contact your Kenshoo representative to obtain your Server Number.

## Setup

The Kenshoo connector is a report based connector meaning that upon set up you’ll need to select a report from the ‘Report’ drop-down populated with report name values. The report name values will be of actual reports already created on Kenshoo.

Next, under the ‘Extended Properties’ section, choose the Data Stream Type with which to map your data, as well as enter all the Field Names (or Column Headers) separated by a comma, as they appear in Kenshoo for the selected report.

To get a list of the field names for the above report quickly and accurately, download the report from the Kenshoo UI, copy the column row, replace the tabs with a comma and paste it back in the above box.

When the date range is selected for the Initial Data Fetch (or in routine processing thereafter) Marketing Cloud Intelligence Data Pipelines will process the report in question for the relevant date ranges using the API.

## How to Map

When in the mapping stream, there are two entities that to pay special attention to: Date, and Currency

For the date value to be parsed by Marketing Cloud Intelligence Data Pipelines correctly, use the following formula in the mapping: PARSEDATE(csv\[‘datefield'\],'yyyy-MM-dd hh:mm:ss')

Another potential date format could be PARSEDATE(csv\[‘kn.day'\],'MM/dd/yyyy')

If you want the platform to consider the source currency to make any currency conversion calculations correctly, make sure that this field is included in the list of fields and make sure you map it to the Intelligence Data Pipelines ‘Currency’ field. Alternatively, search for the unmapped ‘Currency’ field, then assign the currency value from the Default Value dropdown to select the appropriate currency value and click ‘Set’

## How to QA Your Data

For a certain report, process it in the Kenshoo UI for the required date range and then process the relevant stream in Marketing Cloud Intelligence Data Pipelines for the exact same date range. Then create a Report/Pivot table within Marketing Cloud Intelligence Data Pipelines containing the exact same Dimensions and Measurements for the same date range. Start off by simply comparing the Measurement totals and make sure those are aligned. Next, to make sure that you’ve mapped correctly in terms of Entity relationships, filter the Kenshoo report for a certain Dimension value and make sure that the list of associated Dimensions seen in the Kenshoo report corresponds to that seen in Intelligence Data Pipelines when the same filtering is applied. Also, under the above filtering, make sure that the metric values are aligned as well.

## Known Issues

- This connector might be a bit slow to process (as per Kenshoo’s API processing time) however this isn’t indicative of any issues and actual stream failure rates should be relatively low.
- Keep in mind that if the source report has more than one tab, the platform will always take the first tab therefore use CSV reports or single sheet reports.