Below is a list of and description of each data filetype that you can send to ReSci via the SFTP:
Items
These would be the products that you sell and want our AI to optimize as recommendations to your users in emails:
- Standard e-commerce clothing company: Shoes, Shorts, Tops, etc...
- Subscription business: Items that can be given in a subscription offering/box.
Context on select fields
- Active - Controls whether items are allowed to be recommended in your emails, effectively serving as your "on" and "off" switch for items.
- Item_URL - If an item is recommended in an email, it will typically need to be clicked upon and this URL is where the user will be directed to.
- Item_type - How items can be grouped together for use in our item_targeting feature (similar to Categories), and for special AI customizations this field could be leveraged to serve certain items only to certain users. For example:
- If item_type = "Canada", these items would only be served to Users that also have a corresponding datapoint tagged "Canada."
- If you are a Subscription business offering stand-alone products vs subscription products (e.g. monthly box), you may leverage this field to distinguish between your item types.
- Discuss with your Onboarding Engineer how to best set this up.
- Image_list - Items will be in your emails, so make sure they look good and you use the best/consistent images.
Users
These are all of your purchasers and newsletter subscribers, essentially a list of every person that can and cannot be emailed.
- Example: Even if a person is unsubscribed, data about them is still valuable and they may end up browsing onsite and giving our AI information.
Context on select fields
- birthday - Required to use Birthday stage in Cortex.
- registration_source - Required to get lead scoring features inside of Cortex.
- unsubscribe_link - Typically not needed because RS has it's own unsub link, but clients looking to be the unsub system of record can use their own instead.
- custom fields - We can support custom attributes and dynamic segmentation of these values, but it does require additional setup/implementation on the RS side.
- Contact your Account Executive if you would like to add these to your Cortex platform.
Categories
Similar to "item_type", serves to help our AI models understand how your items are grouped together and enables you to use category based recommends in Cortex.
- Example: A makeup company may have Categories of "eyelashes," "face," "lipstick," etc...
The only consideration is that the record_id in this table is what will be used in Items/Order_items columns when designating what categories Items fall into.
Orders
The information about what people have bought, fairly standard.
Context on select fields
- user_record_id - Be sure this matches your record_id in the Users file.
- order_status - In your order data you may have various status strings "returned," "canceled," "pending," etc...
- You have the option of telling RS which ones should be revenue attributing in our dashboard vs. not.
- Example: Make sure "canceled" orders don't count towards any $$$ totals
- Your Onboarding Engineer would then make sure your system is setup correct based on your unique statuses.
- For Magento/Shopify this is already automated.
Order_Items
Similar to Orders, but even more straightforward as this is just giving more details and quantity of the orders. Just make sure your order_record_id maps properly to your Orders file and item_record_id maps properly to your Items file.
Subscriptions
Only useful for companies that are pure Subscription (e.g. only offering a monthly box) or Hybrid Subscription (box + one-off products). Think of this as a subset of the Users table as all Subscribers here would exist in the Users table, but everyone in the Users table would not exist here.
- Example: Not everyone in the Users table has bought the product.
Context on select fields
- user_record_id - Be sure this matches your record_id in the Users file
- status - This can be used as a flexible field for segmentation, as you can put any value you want and group your subscribers into them for specific targeting
- Typically values such as "Active", "Paused", "Canceled"
- trial - If you don't do any trial offerings, just default to 0
- churned - Typically related to the status of "Canceled", set to 1 if the subscription is terminated
Item Reviews
Not required, consider this a bonus table to make our AI even smarter if you have the data! Most of these fields are straightforward, and similar to other tables just make sure that user/item record_ids properly link to other files.
User Wish Lists
Similar to Item Reviews in that it is not required, but can enhance performance of our Price Drop and Back in Stock campaigns. Data would essentially tell us what Users are have expressed explicit interest in what items, and fields are straightforward similar to item reviews.
 |
Need more help? Please see our articles about file schemas, and about Historical files or daily files for E-Commerce, Subscription businesses. |
Comments
0 comments
Please sign in to leave a comment.