Data extractor
Manipulate your products data for better facets, merchandising and search relevance
Antanas Bakšys avatar
Written by Antanas Bakšys
Updated over a week ago

The Data Extractor feature allows to extract data as custom fields.

What problem does it solve?

Many clients store product attributes in Tag1 or other fields together with other attributes. This way they can’t use it in facets, merchandising and other areas. This feature allows to generate attributes as separate fields that can later be used in Search & Categories.

Use cases today:

  • Create more facets

  • Merchandise by various attributes e.g. promotion type

  • Add as Searchable Fields for better search relevance

  • Building custom frontend template elements

Usage Guidelines

  1. Decide what attributes you would like extract to separate data field

  2. Go to Catalog Explorer → Settings → Data Extractor

  3. Name new your new data extractor e.g. Attributes from Tag1

  4. Select a field where your desired attributes are placed now

  5. Write a separator - a character that separates attribute’s name from the value

    1. e.g. if the attribute is Style:Oversized, then your separator is :

  6. It’s useful to extract more attributes to be available for you but you can also specify optional settings to extract something even more specific

    1. If you’d like to extract only Style attribute, Name Filter should be set Style

    2. If you’d like to extract only certain attribute values e.g. Oversized, Value Filter should be set Oversized

Once data extractor is created, new data fields will be available after the next re-index which happens 4 times a day. To know when it’s available and to use it in search, you should:

  1. Go to Search & Categories → Settings → Indexed Fields and add the new field, that you’ve created

  2. When it’s added, you should wait for another re-index

  3. Finally, your new attributes can be used in facets, merchandising, and searchable fields

Sometime later this data will be also available for the rest of the Nosto Platform.

Did this answer your question?