# Frequently Asked Questions

Canonical: https://support.syte.ai/space/FAQ/

### **Frequently Asked Questions**

#### **Frequently Asked Questions**

**General Information**

**Question?**

**What is Syte Console?**

Answer:

Syte Console is a self-service platform created by Syte to  
allow client’s to manipulate visual product settings to  
improve their results on their websites.

[](/space/ET/2697855214 "https://syte-ai.atlassian.net/wiki/spaces/ET/pages/2697855214")

[](/space/ET/2697855214 "https://syte-ai.atlassian.net/wiki/spaces/ET/pages/2697855214")[**Console | Getting Started**](https://syte-knowledge-center.refined.site/space/ET/2697855214)

 

**Question?**

**What are E-commerce and Interaction Events?**

Answer:

**E-commerce Events:** Trigger events that collect  
data from the client website to calculate revenue.

[**E-Commerce Events**](https://support.syte.ai/space/ET/3482255653/E-Commerce+Events+Overview)

**Interaction Events:** Trigger events that collect  
customer CTR to calculate Syte product  
performance and engagement.

[**Interaction Events**](https://support.syte.ai/space/ET/3482255806/Interaction+Events+Overview)

 

**Question?**

**What IP’s do we need to whitelist?**

Answer:

The required IP address list needed for Syte:

[](/space/ET/2697921153 "https://syte-ai.atlassian.net/wiki/spaces/ET/pages/2697921153")

[](/space/ET/2697921153 "https://syte-ai.atlassian.net/wiki/spaces/ET/pages/2697921153")[**IPs to WhiteList**](https://ip-ranges.syte.ai/)

 

**Question?**

**What are the mandatory fields in feed?**

Answer:

The List of Data Fields that are required can  
be found here:[](/space/ET/2697921130 "https://syte-ai.atlassian.net/wiki/spaces/ET/pages/2697921130")

[](/space/ET/2697921130 "https://syte-ai.atlassian.net/wiki/spaces/ET/pages/2697921130")[**Data Fields**](https://support.syte.ai/space/ET/3482189868/Data+Fields)

**Question?**

**Why is syte\_uuid important?**

Answer:

The **syte\_uuid** is a unique identifier assigned to each user session. It is critical for:  
  
**Revenue tracking** – Ensures accurate attribution of purchases to Syte's features.  
**Personalization** – Allows Syte to provide tailored recommendations based on user behavior.  
**A/B Testing** – Essential for testing different models and configurations. The **session\_id** is also required for accurate A/B test analysis.  
  
**Tags:** syte\_uuid, session\_id, tracking, personalization, A/B testing

**Question?**

**What does Syte track on my website?**

Answer:

Syte tracks user interactions, engagement, and conversion-related events to improve personalization and performance.  
**Tags:** events, tracking, ecommerce, CTR, revenue, privacy, data

**Question?**

**What are the mandatory fields in a feed?**

Answer:

**Mandatory Fields:**  
**Core:** Color SKU, Image URL, Title, Category  
**For Multiple Genders:** Gender  
**For JS Implementation:** Product URL, Currency (if multiple currencies)  
**Highly Recommended:** Parent SKU, Size SKU, Additional Images, Page URL  
**Recommended:** Price (after discount), Original Price, Age Group, Stock Availability, Currency  
**Nice to Have:** Description, Brand, Color, Size  
**For Add-To-Cart Feature:** Color, Size (if relevant)  
  
**Tags:** product feed, fields, SKU, image, category, price, stock

**Question?**

**Does Syte store personal data?**

Answer:

No, Syte does not store personal user data. It only collects anonymized behavioral insights.

  
  
**Tags:** data privacy, GDPR, PII, anonymized data

**Question?**

**Is there a limit to the number of Merchandising rules I can create?**

Answer:

No, but too many rules may contradict each other and impact performance.

  
  
**Tags:** merchandising, rules, strategy, best practices

**Question?**

**Why is my Similar Items carousel showing fewer products than expected?**

Answer:

Possible reasons include insufficient indexed products, merchandising rules, or low-confidence matches.

  
  
**Tags:** carousels, product recommendations, indexing issues

**Question?**

**How long does a feed take to finish indexing?**

Answer:

Indexing time varies depending on feed size, ranging from 30 minutes to a few hours.

  
  
**Tags:** feed indexing, processing time, data updates

**Question?**

**Does Syte track cookies?**

Answer:

Syte does not use cookies for tracking; it relies on session-based identifiers (**syte\_uuid**).  
  
**Tags:** cookies, tracking, syte\_uuid, privacy, data

**Question?**

**How do I test Syte's features before going live?**

Answer:

Clients can use a separate staging Shop ID, which differs from the production Shop ID, to test changes before deploying them to production.  
  
**Tags:** staging, testing, shop ID

**Question?**

**Is it possible to customize the product catalog after it has been indexed?**

Answer:

Yes, you can modify the product catalog by adding, removing, or adjusting product details and columns. Ensure all details you want in the API response are included. Changes will be reflected in the next indexing cycle.  
  
**Tags:** catalog update,product changes,feed modification

**Question?**

**How far in advance should clients notify Syte when adding a new language to their feed?**

Answer:

Clients should inform Syte at least 7 days in advance by updating their CSM or opening a support ticket.  
  
**Tags:** language, translation, localization, update notice

**Question?**

**How can I optimize the relevance of recommendations in my Similar Items carousel or Discovery button?**

Answer:

Several factors can affect the relevance of recommendations in the Similar Items carousel or Discovery button:  
  
**Product Data Quality** – Ensure that the product catalog includes complete and accurate attributes (e.g., color, category, and descriptions) to improve matching.  
  
**Merchandising Rules** – Check if any applied rules are influencing the recommendations. Conflicting rules can lead to unexpected results.  
  
**Indexing Updates** – If recent changes were made to your product feed, allow time for reindexing.  
  
**Algorithm Adjustments** – If relevance issues persist, Syte can fine-tune the recommendation model to better align with your catalog.  
  
If you’re still experiencing issues, please contact Syte Support and provide specific examples.  
  
**Tags:** Similar Items, Discovery Button, Recommendations, Merchandising Rules, Indexing, Product Data, Support Ticket.

**Question?**

**How can I ensure my promoted product appears for a specific search term?**

Answer:

Search results are influenced by several factors:  
  
**Synonym Mapping** – If a keyword has a custom synonym (e.g., "Cobalt" mapped to "blue"), it may return a broader set of results. Adjusting or removing the synonym can refine the results.  
  
**Merchandising Rules** – Multiple rules may be affecting product ranking. Adjusting these rules in the Visual Editor can help prioritize the promoted product.  
  
**Keyword Prioritization** – Ensuring that the promoted SKU is correctly tagged with the desired search term (e.g., "Cobalt sectional") can improve visibility.  
  
**Algorithmic Influence** – Other ranking factors may still be in play, requiring further adjustments.  
  
For best results, review the Visual Editor settings and test the search behavior after making changes.  
  
**Tags:** Search Results, Synonyms, Merchandising Rules, Keyword Prioritization, Visual Editor

**Question:**

**How can I improve the relevance of products suggested in 'Shop the Look'?**

Answer:

**Reference Image Selection:** The model automatically selects a reference image, which may differ from the one expected. This can cause discrepancies between 'Shop the Look' and Similar Items results.

**Product Tagging Issues:** Incorrect tags (e.g., a skirt labeled as 'shoes') can lead to unexpected recommendations. Correcting these tags will improve accuracy.

**Merchandising Rules:** Rules can be applied to prioritize certain products. If the results aren't ideal, refining or adding new rules on Syte’s platform can help.

**Detection Limitations:** If key items (e.g., jeans) aren’t fully visible in the reference image, the model might not recognize them, leading to fewer displayed products.

**Future Enhancements:** Syte is working on a feature that will allow manual selection of the reference image, improving customization and accuracy.

After making adjustments, remember to publish changes in the Platform to apply the updates.

  

**Tags:** Shop the Look, Product Tagging, Merchandising Rules, Visual Editor, Image Detection

**Question:**

**How does 'Shop the Look' determine which products to suggest?**

Answer:

**Reference Image:** The number of products displayed in 'Shop the Look' is dynamic and depends on the reference image. If the model detects only one product in the image, it will return limited results.

**System Limitation:** Currently, the system does not allow setting a minimum number of products, but merchandising rules can help refine recommendations.

  

**Tags:** Shop the Look, Product Display, Image Detection

**Question:**

**How are color variations handled in the Similar Items feature?**

Answer:

**Model Logic:** The Similar Items feature does not return the same parent SKU in different colors due to the model’s logic. However, if each color is assigned a different parent SKU, the system can return them as separate results.

  

**Tags:** Similar Items, Parent SKU, Product Variants, Color Variations, Model Logic

**Question:**

**How do the results of the Discovery Icon (DI) and the Similar Items feature differ?**

Answer:

**Discovery Icon (DI) Logic:** The Discovery Icon (DI) and the Similar Items feature rely on different logic. The DI primarily uses visual similarity from the selected area of the image, while the Similar Items feature considers both visual attributes and category data. As a result, discrepancies may occur if the model identifies a visually similar product that does not belong to the same category.

  

**Tags:** Discovery Icon (DI), Similar Items, Visual Similarity, Category Mapping, Model Logic, Feature Differences

**Question:**

**Is it possible to prevent certain products from being returned in the Similar Items results?**

Answer:

**Merchandising Rules:** Yes, products can be excluded from Similar Items results using merchandising rules. These rules allow specific product types, categories, or attributes to be filtered out based on business needs.

**Customization:** If exclusions are not working as expected, adjustments to the rules or further configuration may be required.

  

**Tags:** Similar Items, Merchandising Rules, Product Exclusion, Filtering, Customization

**Question:**

**How can I refine my search to get more relevant items for a specific product?**

Answer:

**Custom Synonyms:** Irrelevant items may appear in search results due to custom synonym mappings or broad search terms. When a search term is too general, it can pull in a wide range of items.

**Improvement Suggestions:** To improve results, you can remove or refine custom synonyms and adjust merchandising rules to focus on more relevant products.

  

**Tags:** Search Results, Synonyms, Merchandising Rules, Text Search

**Question:**

**How can I improve search results to better match what I’m looking for?**

Answer:

**Merchandising Rules:** If search results aren't fully matching expectations, it may be due to overlapping or conflicting merchandising rules. Multiple rules can affect what is displayed.

**Fine-Tuning Rules:** Fine-tuning these rules and testing results can help narrow down the search to only the most relevant products.

  

**Tags:** Search Results, Merchandising Rules, Search Optimization, Text Search

**Techincal Setup**

**Question?**

**How to open a ticket to Syte Support?**

Answer:

To open a ticket to support please visit this link  
and fill the required information.

[**Syte Support Ticket**](https://syte-knowledge-center.refined.site/space/OWS/2822111236/How+to+Open+and+View+your+Tickets.)

**Question?**

**Is there a limit to number of Merchandising rules to create?**

Answer:

There are no limits to how many Merchandising rules a client  
would like to create, however, too many can also cause  
contradiction with each other which can lead to some  
features to not show the best results.

 

 

**Question?**

**How many times do models get trained?**

Answer:

Syte performs model training for all clients every 2 weeks.  
This is to help improve results of carousels and other  
products by continuously collecting data.

 

**Question?**

**How long does a feed take to finish indexing?**

Answer:

Depending on how large a feed is some indexing times can  
range from 30 minutes to a few hours.

**Question?**

**Why is my A/B test not showing expected results?**

Answer:

Ensure **syte\_uuid** and **session\_id** are correctly assigned, and that variations are properly split.  
  
**Tags:** A/B testing, syte\_uuid, data validation, experiments

**Question?**

**Who is creating the HTML snippet for the client?**

Answer:

Enablement team, based on the Jira task that the Professional Service Manager opens to them.

**Tags:** HTML, integration, enablement, setup

**Question?**

**Who is testing the HTML before sharing it with the client?**

Answer:

Enablement team, as part of their predefined validation process. The Professional Services Engineer will review the final result before sharing it with the client.

**Tags:** HTML validation, enablement, QA

**Question?**

**What is the maximum product catalog indexing frequency supported?**

Answer:

Product catalog updates vary by client needs. Most catalogs are updated twice a day, but the frequency is flexible.

**Tags:** indexing, product update, feed processing

**Question?**

**I have different product catalogs per locale. Can Syte index each feed separately?**

Answer:

Yes, Syte can index different feeds for different geolocations.

**Tags:** multi-locale, regional feeds, localization

**Question?**

**Which file format should I use for the product catalog?**

Answer:

Syte works best with comma-delimited text files (CSV) encoded in UTF-8. The feed can be compressed as .gz, .tar.gz, or .gzip.

**Tags:** file format, CSV, UTF-8, gzip, compressed feed

**Question?**

**What should be included in the product catalog file?**

Answer:

Please refer to [**Product Catalog - Data Fields**](https://support.syte.ai/space/ET/3482189868/Data+Fields) for a detailed list of required fields.

**Tags:** product data, catalog fields, API response

**Question?**

**When is the SFTP update automation process set?**

Answer:

After the initial indexing, Syte works with the client to determine the method, timing, and frequency of updates.  
  
**Tags:** SFTP, automation, data sync, schedule, scheduling, cadence

**Question?**

**How is feed automation set up?**

Answer:

After the first manual feed is indexed, your onboarding manager will coordinate with you to establish automation settings, including method, interval, and frequency.  
  
**Tags:** automation, indexing, scheduled updates, SFTP

**Question?**

**Can Syte index multiple product catalogs for different geolocations?**

Answer:

Yes, Syte supports indexing multiple feeds based on vertical or locale-specific requirements.  
  
**Tags:** multi-locale, regional feeds, localization

> Dynamic module: News (live content)

### News

**CQL:** `type=blogpost`

(No pages or blog posts in this space.)

---
Generated: 2026-09-20T18:36:08.577Z