Integration Docs

Introduction

As a general rule, SKUs should be unique and immutable. SKUs should be the same across advertising channels. However, in Finch's experience sometimes SKUs don't match between advertising platforms - for example, SKUs are occasionally different in Google Shopping and Amazon. Additionally, we've seen that migrating ecommerce platforms can change SKUs which strongly hurts campaign performance. For this reason, Finch offers the ability to Map two SKUs to share performance data.

Create a Mapping

Work with your Finch contact to define a SKU mapping. It will either be "Google to non-Google" or "Historic Performance". Once SKU mappings are created they will show up inside the Finch Platform under 'Main >> SKU Mapings'. From there you can upload map files and check the status of existing mappings.

Prepare a file for upload

Prepare a CSV file with two columns. Fill in the "sku" column with the old sku identifier, and the "mapped_sku" with the new sku identifier for the product.

Sending the Feed to Finch

If your SKUs are going to change over time then please consider automatically sending updates. For example, if you get new SKUs regularly and they will have different Google/Non-Google SKUs, then you would want to keep your SKU map up to date.This can be done one of two ways:

  • POSTing the Feed to Finch - This is Finch's preferred method for security reasons.
  • Scheduling the Feed for Download by Finch - This is the simplest method, but requires the feed to be publicly available.

Select one of the following options for more details: