This page allows you to ensure that Athos Commerce is using all the right information to power full and reliable functionality on your site. Athos has many helpful features for your ecommerce sites, but in order for these features to utilize your data and show your products, core fields — which serve as "default fields" for Athos — must be configured; these help us to standardize what your data is, what it means, and how to use it.
Here, you will assign fields from your data as core fields so the system can leverage commonly used values across search, autocomplete, and personalization.
Standard Mappings tab
These field labels allow you, the merchant, to tell Athos which field in your data corresponds with the core attributes used to power our features.
Note: Required fields (such as Unique ID and Price) are marked with red asterisks.
To change which of your product feed's fields are assigned as Athos core fields, click the drop-down menu for that field and select which one you'd like to change the assignment to. Filter the list of options by typing part of the field name in the search box that appears.
Unique ID (required field)
The product's ID. Depending on your platform or custom feed, the ID may also be the SKU.
SKU
A string of characters that identifies your product. The SKU field should be unique per product and must be set for Athos's Beacon tracking to work.
Please note: SKU is not marked as a required field, but it should always be set. If you do not have SKUs for your products, this could be set to the product's ID which is typically unique.
Product Name (required field)
The name of your product. This field is used in features such as AutoComplete and Product Recommendations.
Brand
The brand or a manufacturer associated with a product.
Price (required field)
The cost of your product. This field should be set to the final price that customers will see when purchasing your products. This field is used in features such as AutoComplete and Product Recommendations.
Suggest Retail Value
The retail or MSRP price of the product.
Product Description
The description of your product. This can be a long or short description.
Customer Rating
The overall customer review score of a product. This is usually a numeric value.
Number of Reviews
The total amount of times a product has been reviewed by customers.
Popularity
A ranking of how popular a product is, commonly based on how many times that item has been sold. In the AutoComplete feature, it will work as a boost when a shopper searches. Products with more popularity (most to least popular) are shown first and then relevant products. If "Popularity" is not set, the fallback for AutoComplete product ordering is relevancy.
Product URL (required field)
The URL of your product. This field is used in features such as AutoComplete and Product Recommendations.
Image URL (required field)
The image associated with the product. Set this to a thumbnail image field if possible to reduce loading times.
Product Thumbnail Image URL
The image you want to display in search results. This field is used in features such as AutoComplete and Product Recommendations.
Custom Fields
At the bottom of every selection's drop-down menu, there is a field called "Custom". This can be used to map multiple fields, other text, or different URL structures. Any data fields you want to use with the "Custom" option should be surrounded by a percent sign (%).
For example: //www.mycoolwebsite.com/mm5/resize/250x250/%image%
[Admin-only text below. This is hidden to our customers.]
Personalization Mappings tab
The mapping defined here connects the SKU to the ID (for clicks). For all merchants using personalization, field mappings must be set up for Category Name, Category ID, and Brand (found on the Standard Mappings tab) before the feature can be enabled. If the client has a parent/child product structure, a mapping must be set up for the Child SKU field.
When setting up sibling handling for personalization, go to Data > Data Sources and click "Run Check" in the "Check w/ Skip Regen" section.
Also, within personalization field settings, set the Family ID field to the field that is being used to link siblings together. Once the Family ID field is set up, our system will automatically consider sibling groups when analyzing the data and creating recommendations.
Note: The first two fields, Category ID and Category Name, are used together.
Category IDs
The Category ID is used to associate an item with other products in the same category. It is a unique value and is not visible to shoppers.
Note: BigCommerce does not use category names, only category IDs.
Category Names
The Category Name serves as a descriptor for both merchants and shoppers. Sales of specific variants are tracked at a child level. Ecommerce firms generally choose either a child ID or a child SKU for tracking purposes; it is rare for a merchant to use both child ID and child SKU. In the past, the child SKU has been preferable, but the Pixel app may change this preference unless the merchant is reporting sales of child ID versus child SKU.
Child IDs
A child ID is unique to a specific variant within a family ID (a "family" of related products, such as a fitted T-shirt with multiple size and color variants).
Child SKUs
The child SKU is used by personalization, but not by reporting. The legacy workaround in Shopify for this was to pass the first variant SKU in the SKU parameter. That might be the easiest way to fix this for now if they are already sending that elsewhere on their site, although they are overdue for upgrading to checkout extensibility, according to Shopify. The new preferred way to handle this (and the way we do it with our Web Pixel app) is to pass the UID parameter instead of the SKU. This is a bigger change since the UID needs to be added to all events, not just the order confirmation event.
Family ID
A family ID is shared across product variants in the same group. It is used to limit exploded variants (such as SKU + color) in recommendations so that nothing from the same family is shown in recommendations.
Variant Options
This setting is used to combat a very specific problem with siblings. Primarily, it is used for bundle profiles for changing the options in a bundle (such as size or color). It is also used anywhere that is handling exploded variants. Utilizing this field impacts performance, so limit its use to bundling or other uses of exploding variants.
Note: The Family ID and Variant Options work together.
Comments
0 comments
Article is closed for comments.