Identification of products/articles

Elevate unleashes powerful features, but to utilize them, both Engage and Elevate must be able to identify the stock keeping unit (SKU) code of a purchasable item.

In Engage the SKU is a standard article property. Elevate, however, refers to articles as products, and the variations of the products as variants. Each product and variant has a unique key in Elevate. An Elevate variant must have a variantKey value corresponding to the article SKU in Engage.

Tracking events -- product views, product clicks, purchases, adding to favorites -- use the SKU/variantKey to share valuable customer interactions. To be able to exchange such data between Engage and Elevate, both systems need to be able to identify the product code (SKU/variantKey). That’s also the case for purchase data in a transaction for a physical store. The transaction will contain the SKU and/or EAN code.

Here is an example of an Engage productview tracking event:

{
    "t": "productview",
    "i": "art-321-1123",
    "ca": "WOMEN > SHIRTS > Coco ",
    "ci": null,
    "ti": "2022-05-20T18:08:58.926Z",
    "te": "coco",
    "id": "VA507.2050216525",
    "s": "VA507.1012665165",
    "ns": false,
    "ua": "Mozilla/5.0",
    "l": "en-us",
    "re": "https://test.com/en/coco",
    "url": "https://test.com/sv/women/shirts/coco"
}

And this is an example of an Elevate purchase (order) event payload:

{
  "lines": [
    {
      "variantKey": "art-321-1123",
      "quantity": 1,
      "sellingPrice": 60
    }
  ]
}

An AI/ML module will be able to recognize the article with art-321-1123 in both suites and realize it is the same one. Each system can relate to the article if they both use the same SKU / variantKey.