LogoLogo
Support
Product Discovery Developer Guide
Product Discovery Developer Guide
  • Product Discovery Developer Guide
  • πŸ›’Item catalog management
    • What is the Items API?
    • How to work with Items
      • Item Schema
        • Attributes
        • Nested Item Schemas
        • Using the Item Schema API
        • DefaultLocale API
        • Onboarding on/migrating to Fredhopper
        • List of Reserved Attributes
      • Category Tree
        • Using the Category Tree API
        • Onboarding on XO
      • Item Catalog
        • Using the Catalog API
      • Items
        • Using the streaming Items API
        • Using the batch Items API
    • Step by Step guide
      • Step by step guide for Fredhopper customers
    • Feedback
      • Using the Feedback API
    • Authorization to APIs
    • Troubleshooting API errors
  • 🎯XO Recommendations
    • Introduction
    • Using the Recommendations API
    • Setting up the Chrome extension
    • Micro-segmentation
    • XO Legacy APIs
  • πŸ”ŽXO Search
    • Introduction
    • Getting started
    • API Reference
      • Search API
      • Autocomplete API (Beta)
      • Product Suggest API
    • API Parameters
      • Search
      • Pagination
      • Faceting
      • Sorting
      • Grouping
      • Filtering
      • Disable features
      • Response mask
      • Context
    • Configuration limitation
  • πŸ§ͺA/B testing
    • Fredhopper A/B testing
      • Integration steps for a non-caching solution
      • Integration steps for a caching solution
        • Java SDK Integration
          • Setup
          • Retrieve running A/B tests - Java SDK
          • Filter and request variant - Java SDK
          • Extending the SDK
        • Manual A/B tests integration
          • Retrieve running A/B tests
          • Filter out irrelevant A/B tests
          • Assign variants to user
          • Request variant for page
        • Limitations and Best Practices
  • πŸ“šResources
    • Glossary
    • Best Practices
      • Tracker Best Practices
      • Items API Best Practices
      • Fredhopper Data Configuration Best Practices
      • Fredhopper Query Response Best Practices
      • Fredhopper Merchandising Studio Best Practices
    • Privacy Notice
  • Archived Pages
    • FHR Tracking plan
    • XO Tracking plan
    • The Tracking API and JS Library
      • What to Track
        • Generic Actions
          • View
          • Click
          • Add to Cart
          • Remove from Cart
          • Purchase
        • Custom Actions
      • Initializing the JavaScript Library
      • REST API Technical Documentation
Powered by GitBook

Copyright @ 2024 Crownpeak Technology, Inc. All rights reserved.

On this page
  • XO Enrichment
  • Important to know
  1. Item catalog management
  2. How to work with Items
  3. Category Tree

Onboarding on XO

PreviousUsing the Category Tree APINextItem Catalog

Last updated 7 months ago

XO Enrichment

When a Category Tree is configured on a CIDP environment with an XO destination, we automatically create up to 5 attributes to reflect the category levels.

As an example, let’s say an item X has 2 category paths:

  • Men > Clothing > Jacket

  • Sales > Men > Clothing > Jacket

It would result in the following attributes automatically added to your items in XO:

"enrichments_category_paths_level1": ["Men", "Sales"], "enrichments_category_paths_level2": ["Clothing", "Men"], "enrichments_category_paths_level3": ["Jacket", "Clothing"], "enrichments_category_paths_level4": ["Jacket"]

Important to know

  • The category name values that are extracted from the Category Tree configuration are the values corresponding to the that is configured for the environment.

  • If the customer has not set up a default locale (mandatory when using XO),

    • By default we try to retrieve the values matching the locale en_GB

    • and if there is no matching value we retrieve the category id instead.

  • It means every environment where a Category Tree is configured should have the additional item attributes populated on the items in XO.

πŸ›’
default locale