Wish list implementation

Many of our partners have historically approached Wishlist with a simple "tag and blast" methodology (which is full of downsides/assumptions), but here at ReSci we built a powerful solution that:

• Could take into account a user's dynamic preferences over time.
• Track items that a user adds to wishlists, likes, or favorites.
• Seamlessly integrate this data in Cortex's existing AI stages for unique personalization.

This article is intended to help prospective/existing partners launch our Wishlist features inside of Cortex.

• Key data needed and why
• How to integrate: Custom vs. Shopify vs. Magento:
  • Key  concept that applies to each integration route
  • Custom partners
  • Shopify partners
  • Magento partners

Key data needed and why

The data needed is extremely straightforward and intuitive (documentation), but a quick summary:

1. item_record_id - RS needs to know what item is being liked or wishlisted.

2. user_record_id - RS needs to know who is doing the liking or waitlisting.

3. active - RS needs to know if an item is on or off the user's wishlist.

   • Items may be fulfilled or de-listed by the user.

   • Knowing what items have been waitlisted over time (even if de-activated) further gives our AI models information on what types of users are interested in what types of products.

How to integrate: Custom vs. Shopify vs. Magento:

Key Concept that applies to each integration route:

• • The final information built needs to be dropped on an FTP nightly to RS.

  • Reach out to your OE or Technical Support representative if you have questions on how to do this/where to drop the file.

    • Article on how to set up an FTP transfer is here.

    • Your OE/Tech Support may setup the pickup in a specific FTP path, so be sure to coordinate with the RS team.

Custom partners

• item_record_id corresponds to record_id in the Items file.
• user_record_id corresponds to record_id in the Users file.
• active will correspond to how you store data on likes/waitlists.

Tech Example: if you have one DB column that tracks likes and another DB column that tracks waitlist and those had values of "Y" or "N", you would set active = "1" to use for that item if the user has a "Y" value in either column for the item.

Shopify partners

• Please see Shopify Liquid Documentation for reference.
• item_record_id corresponds to variant.id in Shopify.
• user_record_id corresponds to customer.id in Shopify.
• active will need custom mapping similar to section #2.

Magento partners

• item_record_id corresponds to entity_id of the item.
• user_record_id always is the MD5 hash of the email.
• active will need custom mapping similar to section #2.