For connecting to owlcure mailing, you need to provide several feeds with customers, products and orders data. Based on these data owlcure mailing is predicting which products could be interesting for users. This specification is the just general interface, for each customer there could be another data which are unique in their custom solution.
Contain information about products which will be used in email templates in automatically generated email parts.
We use same XML feed as heureka specified here.
You can add voluntary tags for us.
Please add this tag to the items which are not supposed to be imported to app due to possible trouble. In format 1 for adult products and 0 for safe products.
To this tag, you can add information about price before sale if the product is discounted.
If the product is usually sold repatetly, you can specify the average interval between orders of one piece of product.
Average rating of the product. Generally the float number from 0 to 5.
The number of people who rates product.
If you have several variants of the same product, you can join them by ITEMGROUP_ID.
Name of ITEMGROUP joined by ITEMGROUP_ID.
Current quantity of product in inventory. Value is strictly an integer.
For additional parameters like size, web labels, etc. You have to specify PARAM_NAME and VAL. In below example, you can see two size parameters (L, XL) and web label 'Best sell'.
Feed of users is used for sending emails and algorithms counted with users data.
The best way how to create import with users is with random part of the name. There also should be the GET parameter ‘days’ which specified from how many previous days are data downloaded.
For example http://www.mywebsite.com/e3242mads343k-users.php?days=7 should return users who were created or modified in the past week.
The root element of XML file. Contains all users.
The element contains data for the user.
Unique identification of the user.
First name and last name of the user.
Birthdate of the user. In format YYYY-MM-DD.
Sex of user. In format M or F.
Email address of the user.
Date and time when the user was registered to the newsletter. In format YYYY-MM-DD hh:mm:ss.
Name of the group, where user will be assigned.
Orders feed should contain information about orders for providing enough data to learn our algorithms predict similarities among products.
Best way how to create import with orders is with random part of name. There also should be the GET parameter ‘days’ which specified from how many previous days are data downloaded.
For example http://www.mywebsite.com/e3242mads343k-orders.php?days=7 should return orders who were created or modified in past week.
Root element of XML file. Contains all orders.
Element contains data for order.
Unique identification of order.
Date and time of finished order. In format YYYY-MM-DD hh:mm:ss.
Identification of user who finished order.
Element contains all things in order.
Contain one item in order.
Identification of item.
Price of one piece of item paid in order.
Number of pieces of item in order.
Percentage of sale when the item was on sale.
It should be in the similar format like orders feed but only with orders which weren’t finished. It also contains these other elements.
Best way how to create import with abandoned cart is with random part of name. There also should be the GET parameter ‘days’ which specified from how many previous days are data downloaded.
For example http://www.mywebsite.com/e14542mads283k-abandoned-carts.php?days=7 should return orders who were created or modified in past week.
Date and time of last modification of the order. In format YYYY-MM-DD hh:mm:ss.
URL where the user can find this unfinished order in his basket.