BUG - Back In Stock Subscribe event incorrectly has product tags appended to Categories

No, I do not believe the other post is related.

Almost everything is working as described, except “Product Tags”.  Ill explain further…

We send to Klaviyo the following payload

const options = {
          method: 'POST',
          headers: {
            accept: 'application/json',
            revision: new String(revision),
            'content-type': 'application/json'
          },
          body: JSON.stringify({
            data: {
              type: 'back-in-stock-subscription',
              attributes: {
                channels: ['EMAIL'],
                profile: {
                  data: {
                    type: 'profile',
                    attributes: {
                      email: new String(input_email)
                    }
                  }
                }
              },
              relationships: {
                variant: {
                  data: {
                    type: 'catalog-variant',
                    id: new String('$shopify:::$default:::' + variant_id)
                  }
                }
              }
            }
          })
        };

This creates the back in stock subscription event on the profile designated.  

In that event, it details information about the product and variant to which was subscribed.  This includes the following fields:

productID, productName, categories, platform, channels, variantId, variantName, SKU, price.

All of that information is correct, except categories.  The field “categories” contains information from the product’s collection (accurate), but also contains the product’s tags information (inaccurate).  The field “Tags” is not present.

Expected

It is expected that the field categories contains the product collection information, and not the product tags information.  Additionally, the field tags should be present on the profile event, which contains the product tags information.

Here is my thought process:

Shopify stores these 2 pieces of information separately: collections and tags.

Klaviyo has two matching fields: categories and tags. 

Instead of combining these into one field, why not leave them separated?

The issue it causes is hours lost trying to figure out why every other property in the segment filter correctly maps over.  Only to realize that the Tags field shown below will never have anything, and the tags field was somehow appended to the “categories” field.

I have a workaround, which is to use categories for both, but it certainly seems like a bug.