About Infinity’s Kenshoo Integration

Overview

Infinity’s Kenshoo integration is able to automatically push – via FTP – daily call data to the Kenshoo search marketing dashboards. This ultimately provides paid search teams using Kenshoo the ability to manage PPC bids with visibility of conversions including call based conversions.

With the Kenshoo integration installed, the Infinity tracking code on your website will also capture the KClickID of the visitor (a Kenshoo unique visitor ID), which relates to the ad that brought them there. When a call occurs, it’s tracked against the visitor as normal on the Infinity portal. However, the call data is subsequently passed back to Kenshoo, so that you can see exactly how your campaigns deliver calls.

The Infinity call data will be passed into Kenshoo with the label of 'Call Pass' if the call has been determined as reaching a connected status with Infinity, or 'Call Fail' if the call has not been bridged.

Specifics: What we send to Kenshoo

The Kenshoo FTP report file is a CSV with the following headings. This is the only information at present that we can send into Kenshoo:

• date_time - Start time of call.
• caller_number - Caller ID. Can be empty if needed.
• ct_number - Tracked phone number.
• smb_number - Destination phone number.
• caller_name - Can be empty if needed.
• caller_address - Can be empty if needed.
• call_start - Start time of call.
• call_end - Start time of call.
• call_id - A globally unique ID per call.
• call_status - Either "Answered" or "Not Answered"
• Kenshoo Tracking ID (Cookie ID) - Passed via the URL as k_clickid={kenshoo_cookie}.

The file contains one line (row) per call that took place in the report date range. No aggregation or attribution takes place; we leave it up to Kenshoo to process this internally. The date time format for all fields is d-m-Y H:i:s.
Fields are delimited by a semicolon.

What information should I gather from Kenshoo?

Before beginning the setup of this integration, you need to acquire the following information:

• You’ll need to contact your Account Manager at Kenshoo to get set up with FTP login details. Take note of the FTP username and FTP password; we’ll need these to communicate with your Kenshoo account later on.
• Make sure your Kenshoo account is set up to send the k_clickid parameter in your URLs.
• You will need to let us know at which time each day it is appropriate for us to 'push' the data into Kenshoo via FTP (e.g. 6am) . You may wish to discuss this with your Kenshoo Account Manager before making a decision.
• Finally, make note of your Kenshoo Profile ID.

Setting up the Kenshoo Integration

When you've gathered the information noted in the checklist above, contact the Infinity Support Team, who will be able to configure the integration on your behalf. At this point in time, due to the complexity in setting it up, the feature isn't self-service.

You’ll also need to make sure your Infinity subscription caters for setting up an additional integration. This may be a priced bolt-on for Standard packages, and may be inclusive for Professional and Enterprise packages depending upon the number of integrations you've already activated. For more information, please contact the Infinity Support Team, who will be able to offer advice.

Kenshoo integration: Technical Information

FTP delivery

The Kenshoo reports are sent by FTP to Kenshoo's server. This is defined as the default FTP location in the KenshooFtp plugin, although it can be overridden for testing purposes. The filename format is "{profileID}yyyy_MM_dd.csv"

Tracking IDs

Kenshoo tracking IDs will be provided on landing URLs using the "k_clickid" parameter. This is configured as a pass-through variable for the IGRP (installation) automatically when you set up a Kenshoo integration. The Kenshoo FTP plugin will look for "pt_k_clickid" in the trigger properties in order to extract the Kenshoo tracking ID.

No changes to the Infinity JavaScript tracking code are required to enable Kenshoo integration.

Report dates and Timezones

The integration operates in UTC time, so if you are an international client or clocks have changed due to daylight saving, please consider this.

The Kenshoo FTP plugin is expected to be scheduled and run daily.

The plugin will look at the report run data and extract the previous day's data from the export API, according to the IGRP's (installation's) timezone.

The file is named after the data it contains, not the run date, so a report run on 6th July 2016 will contain data for 5th July 2016 and be named "{profileID}2016_07_05.csv"