Tangiblee will crawl your website to collect all necessary product data and imagery by default.
Alternatively, if you do not prefer the default crawling methodology for any reason, Tangiblee can access and collect all necessary product data and imagery through a product feed. For more information please see details below:
What information does Tangiblee need in order to receive your Product Feed?
- Feed Access credentials (if required):
a. Access URL
b. Username and Password
c. Port Number
d. Protocol (http, ftp, or sftp) - Feed management details:
a. How often is your feed updated?
b. Is it actively managed? - IP Whitelisting
a. Please inform us if any whitelisting is required so we can share with you all relevant Tangiblee-side IP addresses. - SKU Confirmation
a. For reporting purposes, Tangiblee must confirm that the SKUs found in the product feed match the e-commerce transaction SKUs pushed through the Thank You Page (or Order Confirmation Page).
b. It is best if you provide a list of sample SKUs from your GA so that we can confirm the SKUs found in the feed are the same. *If easier, you may share GA Access with our team and we will review.
What criteria is to be provided within the Product Feed?
|
Category
|
Field
|
Description
|
Requirement
|
|
Product Information
|
SKU URL
|
Direct link to the product on your website
|
Required
|
| |
Product Image URL(s)
|
Direct link(s) to all images of the product on your website (Note: these links should open a photo of the product directly when opened in a web browser, not a link to your website)
|
Required
|
| |
Client SKU ID
|
The SKU ID* for a particular product or product variant
|
Required
|
| |
Product Title
|
Name of the product as shown on the PDP
|
Required
|
| |
Product Description
|
Description of the product as shown on the PDP
|
Required
|
|
Product Characteristics
|
Product Category
|
Category to which said product belongs (Ex: Earrings, Necklaces, or Rings)
|
Required
|
| |
Product Sub-category
|
Sub-сategory to which said product belongs (Ex: Engagement rings)
|
If relevant
|
| |
Gender
|
The Gender that the product is marketed towards or mapped to, by default
|
If relevant
|
| |
Product Length (in)
|
Available product dimensions from the Product Detail Page (PDP) - if a product doesn’t have length, this field becomes optional
|
Required
|
| |
Product Width (in)
|
Available product dimensions from the Product Detail Page (PDP) - if a product doesn’t have width, this field becomes optional
|
Required
|
| |
Product Depth (in)
|
Available product dimensions from the Product Detail Page (PDP)- if a product doesn’t have depth, this field becomes optional
|
Required
|
| |
Material/Color
|
Material and Color if specified on the PDP
|
Required
|
| |
Collection
|
The Collection that said product is mapped to
|
If relevant
|
| |
Brand
|
The Brand of said product
|
If relevant
|
|
Compare with
|
Relative SKU IDs
|
SKU IDs of products to compare the main PDP SKU to
|
If relevant
|
|
Stacking. Single-category
|
Stackable products
|
SKU IDs of products from the same product category
|
This or the field below is required
|
| |
Stackable Categories/ Sub-categories / Collections
|
URLs of pages with products that need to be added to single-category stackable items
|
This or the field above is required
|
|
Stacking. Multi-category
|
Stackable products
|
SKU IDs of products from product categories supported by Multi-category stacking:
- Rings
- Bracelets
- Watches
- Earrings
- Necklaces
- Pendants
- Brooches
|
This or the field above is required
|
| |
Stackable Categories/ Sub-categories / Collections
|
URLs of pages with products that need to be added to multi-category stackable items
|
If multi-category stacking is enabled for your website
|
|
Stock
|
Inventory status
|
In stock/ Out of stock
|
If products listed in the feed are both in and out of stock
|
|
Price
|
|
Price as shown on the PDP
|
Required
|
*If you are wanting Tangiblee to cover all variations of a particular SKU, then all SKUs should be placed in the feed (i.e. one row in the feed sheet represents only one product in our system). Examples of variations include additional colors or sizes. All of these variations must be added to the feed.
Note: Please share any naming conventions that differ from the above criteria to ensure proper integration.
