Products and Product Queries#

1. Products in Mergado#

What Is a Product in Mergado#

A product in Mergado is the basic data unit representing an item from your online store. Each product contains various elements that describe its properties – such as the name, price, or EAN. Mergado works with these products, modifies them, and optimizes them before exporting to advertising channels.

• Products are made up of elements that define their properties (e.g., PRODUCTNAME, PRICE, EAN).
• A feed is a file that contains all products and their elements.

Input and Output Data#

The entire process of working with products in Mergado is based on the transformation between two basic data sets – the input and output feed.

• Input feed (input data) – contains the original data that Mergado downloads from your online store and processes further. When searching for products, it is recommended to search in the input, because input feed values are not changed by rules (unless the feed provider modifies them).
• Output feed (modified data) – contains data after modifications made in Mergado Editor. This data is exported to target marketing channels (e.g., Heureka, Google Ads).

Mergado lets you display values from the input feed only, the output feed only, or from both input and output simultaneously when reviewing data.

Loading and Processing Product Data#

Mergado operates on a principle of cyclical data processing that takes place in four steps:

1. Data import – data is downloaded from the input feed into Mergado.
2. Applying rules – most changes and modifications are made in bulk through rules.
3. Export – after processing, the current output feed is generated.
4. Access to the output feed – Mergado records when the advertising channel (e.g., Heureka) downloaded the modified feed.

If a specific product has an error (e.g., an element contains a different value than expected), you can use the “Track product through rules” function. This function shows which rule affected the product and what changes were made.

Difference Between a Product in the Online store and in Mergado#

The online store manages the primary product data, while Mergado is a tool for modifying and optimizing that data for marketing channels. The original data from the online store remains unchanged – Mergado creates a modified version that meets the requirements of each platform.

• Online store – manages the source data used within its own system.
• Mergado – modifies and optimizes data for advertising on comparison engines and marketplaces.

Practical Functions for Working with Products#

On the Products page, Mergado offers several ways to work with data – from manual edits to bulk processing through rules.

One-time Edits#

Manual edits

• Let you modify the values of individual elements directly in the Mergado interface. They are especially suitable for minor or one-time changes.

WYSIWYG editor

• For text elements (e.g., DESCRIPTION), you can use a “What You See Is What You Get” editor that lets you format descriptions using HTML elements. This way, you can edit product descriptions clearly without writing HTML manually.

Manual product hiding

• Useful when working with a smaller number of items that are not suitable for advertising (e.g., products without an EAN or with long delivery times).

Bulk Edits#

• For larger-scale changes (modifying values, rewriting data, or hiding a larger number of products), use rules that are applied to selected groups of products.
• Using bulk edits through rules is much more efficient than manual editing of individual products, and in most cases this approach is recommended.

FAQ#

What is a product in Mergado?#

A product in Mergado is the basic data unit representing an item from your online store. Each product is made up of elements (e.g., PRODUCTNAME, PRICE, EAN) that describe its properties. Mergado works with these products, modifies them, and prepares them for export to advertising channels.

What is a feed?#

A feed is a file that contains all products and their elements. In Mergado, we distinguish between the input feed (data from the online store) and the output feed (modified data ready for export).

What is the difference between the input and output feed?#

The input feed contains the original data downloaded from the online store. The output feed contains data after modifications in Mergado. The output feed is exported to marketing channels such as Heureka or Google Ads.

Can I display input and output feed values simultaneously?#

Yes. Mergado lets you display only input values, only output values, or both simultaneously. This option helps you easily compare what data changed during processing.

How does Mergado process product data?#

Mergado works cyclically in three steps:

1. It imports data from the input feed.
2. It applies rules and modifications.
3. It generates the output feed.

It also records when the advertising channel (e.g., Heureka) downloaded the modified feed.

What should I do when a product behaves differently than expected?#

If a product has an unexpected element value or, for example, appears in the output even though it should have been hidden, use the “Track product through rules” function. It shows which rules affected the product and what changes they made.

What is the difference between a product in the online store and in Mergado?#

The online store manages the original product data, while Mergado modifies and optimizes that data for marketing channels. The original data remains unchanged – Mergado only creates a modified version.

What options are there for editing product data?#

Mergado offers two basic approaches:

• Manual edits – direct editing of values for individual products (suitable for minor changes).
• Bulk edits – using rules applied to entire product queries (recommended approach).

When should I use manual editing and when should I use rules?#

Manual edits are suited for a smaller number of products or one-time changes. Rules are more efficient when working with larger volumes of data or repeated modifications, as they enable automation.

What is the WYSIWYG editor for?#

The WYSIWYG editor (What You See Is What You Get) is used for editing text elements such as product descriptions. It lets you format text (e.g., bold, italic) using HTML tags without writing code manually.

How can I hide a product from the output feed?#

For a smaller number of products, you can use manual hiding directly on the Products page. For a larger quantity of products, use the “Hide product” rule, which is applied to a saved query (e.g., products without an EAN, with low margin, etc.).

Is it possible to see when a channel (e.g., Heureka) downloaded the output feed?#

Yes. Mergado records when the output feed was downloaded, helping you track data updates for individual advertising channels. Information about the last download can be found on the Overview page. More detailed download history is available on the History page after selecting the event type Downloads.

2. The Products Page#

The Products page is the central place where you can review, display, and edit product data. Here you find all items from your feed. You can work with them individually or in groups and verify how rules work. In short, this is where you have full control over what happens with products in Mergado.

Purpose and Functions of the Page#

The main purpose of the Products page is to review data and changes made in the project. Here you find the most important information about feed items, can directly edit their values, or create queries for further work.

Main functions of the page:

• Data display – visual review of products and their values.
• Editing – ability to manually edit a specific element.
• Creating queries – building product groups that rules subsequently work with.
• Debugging – verifying why a product behaves differently than expected (e.g., it appears in the output even though it should be hidden).

Interface Overview and Available Views#

The Products page offers several different views that help you navigate the data and enable quick review of specific information.

View Types

Table View Functions

• The toolbar contains icons for special columns (e.g., image, ID, product name, pinning).
• Preset tabs are available (e.g., pairing, bidding), along with a tab for a custom list of displayed elements.
• In each column header, you can use the X icon for temporary hiding or value sorting (does not apply to special columns).
• Column order can be changed via drag & drop.
• The table can be expanded to full screen, making it easier to work with larger amounts of data.
• Displayed data respects the currently set product filter – allowing you to compare specific elements and products.
• The created table can be exported to CSV exactly as you see it. This file can then be analyzed in a spreadsheet editor or used for import back into another project using the Data file import rule.

Tip! You can change the view mode both for all products and for a specific product.

Data Review and Input vs. Output Comparison#

On the Products page, you see not only the current data but also the differences between what Mergado loaded (input feed) and what it sends on (output feed). This makes it easy to verify whether rule modifications were applied correctly.

Value Display Settings#

Using icons, you can toggle which values are displayed:

• only input values (->]),
• only output values ([->),
• or input and output simultaneously (->][->).

If you choose to display both values at the same time, Mergado highlights the differences:

• red – removed values,
• green – newly added values.

Hidden Elements#

The page also shows hidden elements that are not part of the output feed but exist in the input data. In the interface, they appear in gray. If you do not want to see them, you can turn off the “Show hidden” option. It is recommended to enable this option especially when the input and output formats differ and you need to review the original input data.

Product Search – Input vs. Output#

When filtering products and creating queries, you can choose whether to search by values from the input or output feed.

• Generally, it is recommended to search in the input, because these values are not changed by rules.
• However, if you work with an element that is created only after modification (e.g., g:id), you need to switch the search to the output.

Manual and Bulk Editing#

Most changes in Mergado are made in bulk using rules, but in some cases it makes sense to edit just a few products manually. On the Products page, you can make quick manual changes for individual products and their elements.

Manual Editing#

• Element values can be changed directly in the Products page interface.
• Mergado always displays the original and new value, making it easy to review changes.
• This function is ideal for minor fixes or testing rules.

Description Editing (WYSIWYG Editor)#

For text elements like DESCRIPTION or SHORT_DESCRIPTION, a WYSIWYG editor (What You See Is What You Get) is available. You can write in plain text or in formatting mode (bold, italic, etc.). After saving, the text is converted to HTML supported by advertising systems.

Integration with the Rules and Elements Pages#

The Products page works closely with other parts of Mergado – primarily the Rules and Elements pages.

Connection to Rules#

• From queries created on the Products page, you can easily create rules that act on them.
• To review how individual rules affect products, you can use the Elements view or the “Track product through rules” function. This function displays an overview of all changes that individual rules made to the product.
• It is ideal for debugging when a product does not behave as expected (e.g., the resulting element value is different from what you assumed).

Connection to Elements#

• On the Elements page, you can add, hide, or edit (manually created) elements, which then also appear on the Products page.
• Hidden elements appear in gray on the Products interface to make it clear they are not exported.
• Using the Elements page, you can also search for duplicates – select an element (e.g., PRODUCTNAME), display its values, and navigate to the Products page with an automatically created duplicate query.

FAQ#

1. What is the Products page and what is it for? The Products page is the central place for reviewing, displaying, and editing product data in Mergado. It lets you work with individual products or groups of products, track how rules affect them, and verify data correctness in the feed. At the top, there is also a search field used for creating product queries.

2. What are the main functions of the Products page? The page lets you display data, make manual element edits, create product queries, and review how values change after rules are applied. It also serves for troubleshooting product issues (debugging).

3. What types of views does the page offer? Four basic views are available:

• Previews – quick product overview similar to advertising channels.
• Elements – detailed view of products by individual elements.
• Images – display of main and supplementary images.
• Table – clear data display with filtering, sorting, and export options.

4. How can I adjust which columns are visible in the table view? Columns can be added or hidden using tabs and the toolbar. The order can be changed via drag & drop. Temporary column hiding is done using the X icon in the header.

5. Can the table be exported outside of Mergado? Yes. The table can be exported as a CSV file exactly as you see it. This file can be used, for example, in Excel, Google Sheets, or for import into another project using the Data file import rule.

6. How do I identify differences between the input and output feed? On the page, you can toggle between displaying input feed values, output feed values, or both simultaneously. Differences are highlighted in color – red for removed values, green for newly added ones.

7. What are hidden elements and how do I display them? Hidden elements are data not exported to the output feed but present in the input data. In the interface, they appear in gray. If you want to see them, enable the “Show hidden” option.

8. When should I search products in the input and when in the output? Usually, it is best to search products in the input, since this data is not changed by rules. If you are looking for elements that are created only after modification, switch the search to the output feed.

9. Can I edit data directly on the Products page? Yes. Element values can be manually changed directly in the interface. Mergado always displays the original and new values so you can easily review changes.

10. What is the WYSIWYG editor for? The editor lets you clearly edit text elements such as product descriptions (DESCRIPTION, SHORT_DESCRIPTION). It supports text formatting (bold, italic, etc.) and saves the resulting text as HTML recognized by advertising systems.

11. How does the Products page relate to the Rules page? From queries created on the Products page, you can create rules that act on those products. To review their effect, you can use the “Track product through rules” function, which shows what changes the rules made.

12. How does the Products page relate to the Elements page? On the Elements page, you can add, hide, or edit elements that you can then work with in Rules.

13. What should I do when a product in the output appears differently than expected? Use the “Track product through rules” function. It displays an overview of all rules that affected the product and helps identify which rule caused the unwanted change.

3. Searching and Product Queries#

Searching and creating queries are among the most important functions on the Products page. They let you easily filter, group, and manage products by precisely defined conditions. Queries then serve as the basis for applying rules, hiding products, or targeting campaigns in advertising channels.

Product Queries#

Every filter you create can be saved as a product query. Queries are used for applying rules, analyzing data, and for automations.

Types of queries:

• Temporary queries – used only in the current context, e.g., for a quick review.
• Saved queries – remain available for repeated use and appear in the Saved Queries section. For each, you can see the number of products and the number of rules that work with the query.

How Searching Works#

On the Products page, you can search for products by values in individual elements (e.g., PRICE, PRODUCTNAME, EAN). Two methods are available:

• Simple interface – a click-based method suitable for everyday work.
• Custom MQL query – text-based search with advanced syntax and the ability to combine multiple conditions.

Searching is clear even when working with hundreds or thousands of products. Every filter you create can be saved as a product query and further used in rules.

Searching in Input and Output Data#

When filtering, it is crucial whether you are searching for products in the input or output feed. The correct data source choice affects search results and further work with queries.

• Searching in input – the default mode; searches by original data from the online store, which is not changed by rules.
• Searching in output – used when you need to filter by elements created only during modifications in Mergado.

A crossed-out circle marks elements that do not exist in the input data. Mergado creates these elements through the converter, so you cannot search them when input data is displayed.

Example: Your input is a Heureka feed and you are creating a feed for Google. If you search by ITEM_ID, stay with searching in the input. If you work with g:id, switch to the output.

Working with Conditions (Operators)#

Every filter or query is a combination of conditions in the format: <element> <operator> <value>

Supported Operators#

• CONTAINS – contains text
• NOT CONTAINS – does not contain text
• = – equals
• != – does not equal
• ~ – contains regular expression
• !~ – does not contain regular expression
• <, >, <=, >= – number comparison
• IN – is included in a list
• NOT IN – is not included in a list
• IS EMPTY – is empty
• IS NOT EMPTY – is not empty
• AND, OR – logical combination of conditions

If the element name contains non-alphanumeric characters, enclose it in square brackets: [Element name] = "blue"

Operator Descriptions and Examples:

a. Operator: Contains / Does Not Contain Text

Description:

• Searches for the specified value within a string. The value is not case-sensitive.

Examples:

• You are looking for refurbished products in the feed.
  • Condition: NAME_EXACT CONTAINS "refurbish"
  • In words: the product name contains the value “refurbish”
    • you only need to write part of the word without the ending – this covers the full spectrum: refurbished, refurbishing, etc.
• You are looking for categories that do not contain the value “christmas” or “holiday”
  • Condition: CATEGORY NOT CONTAINS "christmas" OR CATEGORY NOT CONTAINS "holiday"
  • In words: the category element does not contain the value “christmas” or “holiday”

Watch out for: Searching for the full value instead of a key term; e.g., “Refurbished notebooks” will not capture other refurbished products.

b. Operator: Equals / Does Not Equal

Description

• Searches for an exact match in the element. The value is not case-sensitive.

Examples:

• You are looking for all products from manufacturer AB Porzellan.
  • Condition: PRODUCER = "AB Porzellan"
  • In words: the PRODUCER element equals the value “AB Porzellan”.
• You are looking for products that are not made of porcelain.
  • Condition: PARAM { NAME = "Material" } | VALUE != "Porcelain"
  • In words: the parameter named “Material” has a value that does not equal “Porcelain”.

Watch out for:

• Searched terms like “red” may have multiple forms in the feed (reddish, etc.).
• If you only provide part of a string, the result may differ from expectations – be mindful of whether you want an exact match or only partial text.

c. Operators for Comparing Numeric Values (<, >, <=, >=)

Description

• Compare numeric element values (greater, less, greater or equal, less or equal). These only work for elements with numeric values.

Examples:

• You are segmenting products into different price tiers.
  • Condition: PRICE_VAT > 200 AND PRICE_VAT <= 1000
  • In words: the price is greater than 200 and less than or equal to 1000.
• You want to hide cheap products.
  • Condition: PRICE_VAT < 200
  • In words: the price is less than 200.

Watch out for:

• If you create multiple price segments, make sure the boundary prices do not cause the same product to fall into two segments at once.

d. Operators: Contains / Does Not Contain Regular Expressions

Description

These operators use regular expressions for searching. They allow, for example:

• starts with / does not start with – the searched expression starts with a specific value,
• ends with / does not end with – the searched expression ends with a specific value,
• character count equals – the number of characters in the element equals a given value,
• character count is greater than – the number of characters is greater than a given value,
• character count is less than – the number of characters is less than a given value.

Examples:

• You are looking for products that start with the phrase “Gift vouchers”.
  • Condition: NAME_EXACT ~ "^Gift vouchers"
  • In words: the product name starts with the phrase “Gift vouchers”.
• You are looking for products where the EAN element has fewer than 13 or more than 13 characters.
  • Condition: EAN ~ "(?s)^.{0,12}$" AND EAN ~ "(?s)^.{14,}$"
    • Note: This condition can be easily set up using the simple interface.
  • In words: the number of characters in the EAN element is either fewer than 13 or more than 13.
• The number of characters in the EAN element equals 8.
  • Condition: EAN ~ "(?s)^.{8}$"
    • Note: This condition can be easily set up using the simple interface.
  • In words: the number of characters in the EAN element equals 8.

Watch out for:

• We recommend trying multiple variants of the searched expression to ensure you cover all variations of the searched value.

e. Operators by List

Description

• Use these when products have no common feature but you want to select a specific set of items. You can enter or paste multiple values into the field at once, each on a new line – e.g., IDs, EANs, names, manufacturers. Values can be copied directly from another table, e.g., from Excel or Google Sheets.

Examples:

• You need a query of top products that have no common denominator.
  • Condition: ITEM_ID IN ("1"; "2"; "6"; "9")
  • In words: I am looking for products with ITEM_ID from the given list.
• You are looking for categories except certain specific ones (your feed has over 50 categories).
  • Condition: ITEM_ID NOT IN ("Clearance"; "Used goods"; "Open-box items")
  • In words: I am looking for all categories except those listed.

Watch out for:

• The simple interface for this condition offers a text field that opens as a modal window. You need to enter each value on a separate line, without any separators.
• There can be thousands of unique values to search by.
• Empty lines are automatically removed after saving the query.

f. Operator: Is / Is Not Empty

Description

• Used to find products where the selected element is empty or, conversely, filled. For this condition, simply choose the element you are examining and select whether it should be empty or not.

Example:

• You are looking for products with an empty BRAND element.
  • Condition: BRAND = ""
  • In words: the BRAND element is empty.
• You are looking for products with a filled energy label.
  • Condition: ENERGY_CLASS != ""
  • In words: the energy label element is not empty.

Combining Conditions#

Conditions can be freely combined using AND, OR and parentheses, e.g.: (PRICE > 500 AND BRAND = "Nike") OR CATEGORYTEXT CONTAINS "Sport"

Basic Search#

In the simple interface, just select an element, set a condition, and enter a value. You can add more rows by clicking the “+” icon. You can also choose whether the next row will be on the same level or as a nested condition.

Examples:

• PRICE > 1000 – displays products more expensive than 1000.
• PRODUCTNAME CONTAINS "t-shirt" – finds all products with this term in the name.
• [CATEGORYTEXT] CONTAINS "Electronics" – finds products from the given category.
• (PRICE > 100 AND BRAND = "Bose") OR CATEGORYTEXT CONTAINS "Speaker" – example of a condition with a nested condition.

What Values Can Be Entered in the “Value” Field#

• a text or numeric value – e.g., Car, 1000,
• a regular expression – e.g., ^\d{8}$ for an EAN of exactly 8 digits,
• another element – if you want to compare values between two elements (e.g., PRODUCTNAME does not contain BRAND).

Advanced Search with MQL#

For more complex queries, use MQL (Mergado Query Language) – a text-based interface that provides full control over conditions. Activate MQL by switching from the simple search using the “Custom MQL query” option.

Example MQL queries:

• PRICE > 1000 AND BRAND = "Nike" – Products with the Nike brand that are more expensive than 1000.
• (PRICE > 500 AND BRAND = "Nike") OR CATEGORYTEXT CONTAINS "Sport" – Nike products more expensive than 500, or products from categories whose name contains “Sport”.
• PRICE_VAT > "500" AND CATEGORYTEXT ~ "hoodie" AND MANUFACTURER = "Adidas" – Items more expensive than 500, in a category containing the word “hoodie”, made by Adidas.
• NAME_EXACT CONTAINS "children's swing" AND PARAM { NAME = "Shape" } | VALUE = "round" AND PARAM { NAME = "Material" } | VALUE = "solid wood" – The name contains “children’s swing” and the Shape parameter equals “round” and the Material parameter equals “solid wood”.

To verify whether a specific product falls into the query, add the condition: AND ITEM_ID = "123"

Example: ((PRICE > 500 AND BRAND = "Nike") OR CATEGORYTEXT CONTAINS "Sport") AND ITEM_ID = "123"

• Instead of 123, enter the product ID. If the product appears, the query includes it.

Using Regular Expressions (RegEx)#

You can use regular expressions for precise text filtering, e.g., by pattern in the name or by EAN code length.

Examples:

• Products whose name contains variations of the word “blue”: PRODUCTNAME ~ "blu."
• Checking EAN length:
  • exactly 8 digits: ^\d{8}$
  • 8 or 12–14 digits: ^(\d{8}|\d{12,14})$

Using the markers ^ (start) and $ (end) ensures the exact text length is checked, not just a part of it.

Verifying and Using Queries#

After creating a query, you can:

• use it immediately in rules (e.g., Hide product),
• save it for later use,
• or reload and modify its conditions.

To verify that a product actually falls into a query:

1. On the Products page, load the query.
2. Switch to the MQL interface and add the condition AND ITEM_ID = "123". If the product appears, the query includes it.

To easily and quickly find out which queries a product belongs to and which hiding rule hides it:

1. On the Products page, find the product.
2. Navigate to the Queries tab for the product (from the available tabs: Preview, Elements, Images, Queries, and Track product).
3. A table with existing queries that the product currently belongs to will appear.
4. For each query, on the right side there is either:
   1. information that the query is not included in any hiding rule, or
   2. the name and link to the hiding rule that contains the query.

Creating and Editing a Query from the Rule Form#

Mergado lets you create or edit a query directly from a new rule form, or when editing an existing rule. This is useful when you are setting up a rule and realize you do not have a suitable product query yet, or you need to modify an existing query.

Steps to create a new query from the rule form:

1. On the Rules page, create a new rule or edit an existing one.
2. In the rule form, in the Query field, select the last option “Create new query” from the dropdown.
3. A side panel with a simplified Products page will slide in from the right, where you can enter the condition and query name.
4. After saving the query, the side panel will close and the new query will be automatically selected in the Query field of the rule form.

Steps to edit a query from the rule form:

1. On the Rules page, create a new rule or edit an existing one.
2. In the rule form, in the Query field, find the existing query you need to modify in the dropdown and click the pencil icon.
3. A side panel with a simplified Products page and the selected query will slide in from the right.
4. Modify the query condition as needed.
5. After saving the changes, the side panel will close and the modified query will remain selected in the Query field.

Summary#

Operators and conditions let you target specific product groups very precisely. With the right combination of conditions, regular expressions, and lists, you can create queries on which rules and automations can be safely and efficiently applied.

FAQ#

What is the difference between searching and product queries?#

Searching lets you filter products by specified conditions. A query is a saved filter that you can reuse or apply rules to. Queries are permanent and clearly available in the Saved Queries section, while searching serves as temporary data work.

When should I search in input data and when in output data?#

Most of the time, it is recommended to search in input data, because they are not affected by rules. Use output data when you work with values that Mergado creates only during the transformation for the output feed.

What does the red crossed-out circle symbol next to an element mean?#

This symbol marks elements that do not exist in the input data and were created by the converter or user for the output element. You cannot search these elements when input feed searching is enabled. When you switch to output searching, this symbol disappears.

What operators can I use when creating queries?#

Operators for working with text, numbers, regular expressions, value lists, and empty values are available. These include CONTAINS, =, !=, <, >, ~, IN, IS EMPTY, or their negations. Operators can be combined using AND, OR, and parentheses.

What are square brackets for in element names?#

Square brackets must be used when the element name contains a space or other non-alphanumeric characters. You can also use them for elements without special characters – it makes autocompletion easier and reduces the risk of incorrect queries.

How do I find out whether an element value is empty or filled?#

For checking empty or unfilled values, use the IS EMPTY and IS NOT EMPTY conditions. They are suitable, for example, for finding products with a missing manufacturer, category, or other important data.

How can I search by multiple values at once?#

Use the IN or NOT IN operators. Enter values into the list field, each on a separate line. This method is suitable for queries that do not share a common feature (e.g., selecting top products or manually chosen categories).

How do regular expressions work in searching?#

Regular expressions enable advanced filtering, for example, by text pattern or string length. For an exact match, you need to use the start and end markers (^ and $). This ensures that only values matching the exact format are returned.

When should I use simple search and when MQL?#

Simple search is ideal for everyday work and basic filtering. MQL is suited for more complex queries, combining multiple conditions, comparing elements, or detailed use of regular expressions.

How do I find out whether a product actually belongs to a query?#

On the Products page, load the query, switch to MQL mode, and add the condition AND ITEM_ID = "product ID". If the product appears, it belongs to the query. If not, the query conditions do not match it. Alternatively, you can find the product and open its Queries tab on its card, where you will see all queries it currently belongs to.

How do I find out which queries a product belongs to?#

On the Products page, open the Queries tab for the product. A list of all queries the product currently belongs to will appear, including information about whether any of these queries is used in a hiding rule. This helps especially when you have multiple hiding rules in the project or hide multiple product queries in a hiding rule, and you do not know which query and hiding rule is hiding a specific product.

Is it possible to create a query directly when setting up a rule?#

Yes. In the rule form, you can choose the option to create a new query. A side panel will open where you enter conditions and a query name. After saving, the query is automatically inserted into the rule form.

Can I edit an existing query directly from a rule?#

Yes. By clicking the pencil icon next to the query name in the rule form, you open a side panel with the query’s conditions. Edit it and after saving, the changes are immediately reflected in the rule.

What are the most common mistakes when working with queries?#

Common mistakes include searching in the wrong data source (input vs. output), not using square brackets for elements with spaces, incorrect use of regular expressions without ^ and $, or overlapping multiple conditions leading to unexpected results.

What are queries most commonly used for?#

Queries form the basis for filtering, hiding products, adjusting prices, adding information, data quality control, and campaign targeting in individual advertising channels. They are one of the most important tools in Mergado.

4. Product Data Modifications#

In Mergado, you can change product data either manually or in bulk through rules. Manual edits are suited for individual products or smaller groups of items, while rules are designed for large-scale and repeated changes across the entire feed.

Manual Editing#

Manual changes are ideal for a smaller number of products where creating a separate rule would not be efficient. Values can be edited directly on the Products page in the Elements view.

Quick Value Editing#

• Edit an element value by clicking the pencil icon. Modify the value, then click Save.
• Mergado always displays the original and new value, so you can easily review what changed.
• If you want to propagate these manually edited values to the output feed, you need to regenerate the feed. Applying rules is not necessary in this case.
  • After editing data, a special rule also appears in the rules list on the Rules page. The rule cannot be edited, only turned off.
  • You can, however, filter all manually edited products on the Products page. Below the search field, click Show -> With manual changes

This editing method is suitable, for example, for testing or fixing minor data errors.

Description Editing with the WYSIWYG Editor#

For text elements like product descriptions (DESCRIPTION, SHORT_DESCRIPTION), Mergado offers a WYSIWYG editor (What You See Is What You Get). It lets you work with text conveniently and clearly, without needing to know HTML code. However, edits can only be made for specific products – bulk editing is not available.

How the Editor Works#

• Open the editor by clicking the pencil icon next to a specific element.
• You can edit the value in two modes:
  1. Plain view – shows raw text with HTML tags (e.g., <strong>New arrival</strong>).
  2. Formatted view – shows the resulting formatted text (e.g., New arrival).
• After saving, you will see the original and new version. The new version is displayed with HTML tags. To export changes to the output feed, you need to regenerate the feed.

After saving, the text is stored with the corresponding HTML tags, which are supported by most advertising systems. This allows you, for example, to highlight keywords or structure longer descriptions.

Bulk Edits Through Rules#

Most changes in Mergado are made in bulk through rules. Rules let you automate modifications across hundreds or thousands of products and are the primary tool for feed optimization.

How Rules Work#

• Rules are applied either to all products or to specific product queries created on the Products page.
• After saving a query, go to the Rules page where you choose the rule type (e.g., value rewrite, calculation, product hiding, etc.).

Typical Rule Examples#

1. Hide Product

The “Hide product” rule completely removes an item from the output feed (but the products remain in the Mergado catalog marked as hidden and can be unhidden and exported again at any time). It is used, for example, for products:

• with long delivery times (e.g., DELIVERY_DATE > 10),
• with low margins,
• or that are not suitable for advertising (e.g., weapons in Google Ads).

It can also be used for time-based hiding – for example, seasonal products.

2. Calculating New Values

The “Calculation” rule type is used for creating or recalculating values, for example, to calculate margin. Example: Formula for calculating margin: ((%Selling_price% - %Purchase_price%) / %Selling_price%) * 100 The result is saved to a new element (e.g., MARGIN), which you can then use further in rules or queries.

3. Data File Import

If your input feed is missing important information (e.g., margins, stock levels, parameters), you can add it using the “Data file import” rule. This way, you can attach data from an external source to your products – typically in CSV or XML format.

Track Product Through Rules#

If a product behaves differently than expected (e.g., it appears in the output feed even though it should have been hidden), use the “Track product through rules” function.

• Apply the function to a specific product (you can also select multiple products at once).
• After rules are applied, a link to a page showing all rules that affected the product appears, including a description of the changes.
• This helps you easily identify which rule caused the unexpected change.
• The link to this page can also be found later in the event history – in the left project menu, select History and search for the specific rule application.

Before using this function, we recommend verifying that the product actually belongs to the query the rule is applied to.

Summary#

Product data editing in Mergado is flexible – it can be done manually or in bulk. Manual editing is suited for minor interventions, corrections, and testing. Rules, on the other hand, ensure consistent and large-scale modifications across the entire feed. Features like the WYSIWYG editor or the track-through-rules function enable efficient data control and management.

FAQ#

When should I use manual edits instead of rules?#

Manual edits are suited for a smaller number of products or one-time changes where creating a separate rule would not make sense. They are also good for quick testing.

Does propagating manually edited values require applying rules?#

Yes. Even a manual edit of a single element value for one product creates an automatic rule of the Manual Changes type called Direct element editing of products, which must be applied for the changes to reach the output feed.

Where do I find information about which products have manual changes?#

Manually edited products can be displayed on the Products page using Show –> With manual changes. At the same time, a system rule of the Manual Changes type appears in the rules list, representing the edit record.

What should I do if manual edits are not being reflected in the export?#

Check whether the output feed has been regenerated. If the feed was not regenerated after editing, the changes will not appear in the export.

Can I use the WYSIWYG editor to edit texts in bulk?#

No. The WYSIWYG editor is only for editing individual products. Bulk text changes must be made through rules. If you need to edit descriptions in larger quantities, you can use the Mergado Sources extension, which lets you get structured and optimized texts via ChatGPT.

What HTML elements does WYSIWYG support?#

It supports basic HTML tags accepted by advertising systems (e.g., bold text, italic, paragraphs).

What does it mean that a system rule is created after a manual edit?#

It is an internal record that logs the manual edits performed. It cannot be edited or have its behavior changed – it can only be temporarily or permanently turned off.

Can I find out what rule affected a specific product and how it affected it?#

Yes. The Track product through rules function serves this purpose. It displays an overview of all rules that modified the product and a precise description of the changes made.

Where do I find the rule tracking history if I want to view it later?#

In the left menu, open the History page and search for the specific rule application by date and time. From there, you can click through to the processing detail.

How do I know that a rule is not working correctly?#

If the resulting values in the output feed do not match expectations, first verify whether the product actually belongs to the query used by the rule. If so, use the track-through-rules function to identify the rule that made the change.

Can rules affect values that I edited manually?#

Yes. If a rule targets the same element, it can overwrite the manually edited value. In this case, we recommend protecting the value through proper rule structure or adjusting queries so the overwrite does not occur.

5. Product Authorization#

Product authorization is a feature that provides more precise control over which products are exported to the output feed. It works as an alternative to hiding rules. When authorization is enabled, newly imported products are loaded into the project but will not be exported until the user manually approves them. The feature always applies to a specific project.

Enabling the Product Authorization Feature#

Product authorization can be enabled in two ways:

• when creating a new project:
  • In the last step of the wizard, in the Summary section, you will find the Enable product authorization option. Simply check the checkbox.
• in an existing project:
  • Go to the left menu Settings –> General project settings.
  • In the Basic information section, you will find the Enable product authorization checkbox.
  • The feature can be turned off the same way. After turning it off, you need to regenerate the project.

Project Behavior with Authorization Enabled#

Newly created project

• After enabling the feature for a new project, all products receive the Pending approval status.
• The output feed will be empty until some products are approved.

Existing project

If you enable authorization later:

• all existing products receive the Approved status,
• all newly imported products will have the Pending approval status and will not be exported until the user manually approves them.

Working with Product Authorization#

After activating the feature, a new Product Authorization section appears on the Products page in the project. Here you find a table view of all products and quick filtering by approval status.

The table contains, for example:

• the date of the product’s first import,
• name, ID, price, category,
• the current authorization status.

Each product can have one of three statuses:

• Approved
• Rejected
• Pending approval

Filtering lets you display:

• all products,
• only approved,
• only rejected,
• or only products pending approval.

Using the Filter button, you can open the standard form with MQL conditions and combine the authorization status filter with filtering by name, price, category, brand, and other product information.

Approving or Rejecting Products#

Products can be approved or rejected manually:

1. select products using checkboxes (one or more),
2. the Approve and Reject buttons become active,
3. click the desired action,
4. changes take effect after the project is regenerated.

Rejected products appear on the Products page as “Rejected product.” Their values are displayed in gray, and the product has an Approve button available for quick export permission.

Product Authorization vs. Hiding Rules#

Product authorization and hiding rules solve a similar problem – they decide what gets exported to the output feed. However, they work fundamentally differently:

Product authorization

• blocks only newly imported products,
• approval or rejection is always performed manually by the user,
• does not depend on product elements or their values.

Hiding rule

• hides products based on conditions (e.g., price, margin, availability),
• the query is evaluated during each regeneration,
• products can automatically become visible again if they stop meeting the condition.

In simple terms:

• authorization hides all new products,
• a hiding rule hides products meeting a condition.

Export Behavior in Relation to Authorization and Rules#

A product will not be exported if:

• it has Pending approval or Rejected status, and is not hidden by a rule,
• it has Approved status but is hidden by a rule,
• it has Pending approval or Rejected status and is also hidden by a rule.

A product will be exported if:

• it has Approved status and is not hidden by any rule.

Summary#

Product authorization ensures that new products reach the output feed only after manual approval. This gives the user full control over which items can start being advertised. The feature can be enabled in both new and existing projects and is easily combined with hiding rules. Authorization is ideal for cases where you need to prevent automatic publication of new inventory.

FAQ#

What is the purpose of product authorization?#

Authorization is used for manually controlling which products are exported to the output feed. New products are only exported after the user approves them.

Where can I enable product authorization?#

Either when creating a new project in the Summary step, or in an existing project in Settings –> General project settings.

What happens to products if I enable the feature in an existing project?#

All existing products are set as approved. Newly imported products will have the Pending approval status.

How can I see the authorization status of individual products?#

In the special Product Authorization section, you will find an overview with the status Approved, Rejected, or Pending approval.

How do I approve or reject multiple products at once?#

Select products using checkboxes and then click the Approve or Reject button. Changes take effect after the project is regenerated.

What happens to a rejected product?#

The product will not be exported and will appear in the product list as rejected. It can be manually approved at any time.

Can product authorization and hiding rules be combined?#

Yes. Authorization only handles the product’s approval status, while hiding rules work with values in product elements. Both features can operate simultaneously.

What is the main difference between authorization and the Hide product rule?#

Authorization hides all new products regardless of their properties. A hiding rule hides products based on conditions and can automatically unhide them.

Can a product be approved and still not be exported?#

Yes. If it is approved but also falls under a hiding rule, it will not reach the output feed.

How do I find out why a product is not being exported?#

Check its authorization status and also verify whether it is hidden by a hiding rule. Both conditions can block export.

Is it always necessary to regenerate the project after approving products?#

Yes. Approval or rejection takes effect only after the output feed is regenerated.

Can I turn off product authorization later?#

Yes. It can be turned off in the project settings. After turning it off, the project needs to be regenerated for the change to take effect.

6. Export and Working with Data Outside Mergado#

This section describes ways to export product data from Mergado to external files. You can use export either as a one-time action for quick data review, or create a new permanent output feed available via a URL address.

Export to CSV (One-time File)#

If you need to review data outside Mergado or create a simple report, you can download products as a CSV file directly from the Products page. This export is suitable for manual review, analysis, or import into other tools (e.g., Excel, Google Sheets), and you can fully customize what gets exported to the CSV.

How to Export Data from the Table#

One-time export is done from the Table view.

1. On the Products page, use a filter to set which products you want to export (e.g., all or just a saved query).
2. In the Table view, select which columns (elements) you want to include.
3. Click Download CSV and select the export type:
   1. Input elements
   2. Output elements
   3. Output elements including hidden ones
   4. Columns from table (recommended – exports exactly what you see)
4. The CSV file downloads to your computer and you can open it in a spreadsheet editor.

Note: If your project or table contains a large number of products, the table export may not complete. In that case, we recommend creating the export as a new project (see below).

Choosing Columns and Order#

Before exporting, you can customize which elements (columns) will be in the CSV:

• You can choose from existing presets, e.g., Pairing, Bidding, which have pre-configured elements.
• If the presets do not work for you, choose the Custom option, where you can select any columns.
• Using drag & drop, you can change their order.
• Click on “Download CSV” and then select “Selected columns”
• The CSV will export exactly the columns visible in the current view.

Exporting Only Some Products#

If you do not need to export the entire feed, you can choose to download only products from a specific saved query to CSV. This gives you an overview of just the part of the inventory you are interested in (e.g., products without EAN, products on sale, etc.).

Export to a New Project (CSV via URL)#

If you want the CSV to be permanently available via a URL address, you can create a new project that generates an output feed in CSV format.

How to Create an Output Project#

1. Create a new project in Mergado.
2. As the data source, use your product feed and select the correct input format.
3. Set the output format to Plain CSV.

This creates a project that regularly generates an up-to-date CSV feed available via URL – ideal, for example, for automatic data processing or sharing with partners.

Format and Delimiter Settings#

When creating a CSV project, you can specify which delimiter to use (e.g., comma or semicolon). The new CSV will load all elements from the original feed, which you can then modify and customize as needed.

Selecting and Hiding Elements#

To keep your CSV output clear, you can choose which elements (columns) should appear in the resulting feed.

Steps:

1. On the Elements page, select one or more elements you do not want in the CSV.
2. Check the “Hide” option.
3. After regenerating the feed, the selected elements will not appear in the CSV.
4. Using the Sort function, you can also customize the column order and keep the export clear.

A CSV feed created this way contains only relevant data and can serve as an input source for other systems (e.g., reporting, warehouse systems, BI tools, etc.).

Summary#

Mergado offers two main ways to export data:

• One-time export to CSV – ideal for quick data review, working in Excel, or occasional analysis.
• Export to a new project (CSV via URL) – suitable for permanent and automated data processing outside Mergado.

By customizing columns, hiding elements, and configuring the format, you can easily get exactly the CSV output you need.

FAQ#

What is the difference between a one-time export and export via a new project?#

A one-time export downloads a CSV directly from the table and is for quick review or data analysis. Export via a new project creates a permanent CSV feed available at a URL, suitable for automations and regular data updates.

What should I do if the one-time export does not complete?#

You are probably working with a large number of products. In this case, we recommend creating a new output project with CSV format, which can handle the export even for very large feeds.

How do I control which columns appear in the CSV?#

In the Table view, select the displayed columns and set their order. If you use the “Columns from table” export type, the CSV will contain exactly what you see and have set up.

Can I export only a specific group of products?#

Yes. Simply load a saved query in the top filter or create a new one, and then download the CSV. The exported file will contain only products from that query.

How do I hide columns I do not want to export from the CSV?#

On the Elements page, check the “Hide” option for the element. After regenerating the project, these elements will not appear in the output CSV feed.

Where do I set the delimiter for CSV output?#

The delimiter is set when creating a new project if you choose Plain CSV as the output format. You can choose, for example, a comma or semicolon.

Is the CSV feed updated automatically?#

Yes. The CSV output created through a new project is updated during each data regeneration, just like any other output feed in Mergado.

Does the output CSV contain all elements from the feed?#

Yes, the output CSV contains all elements from the input feed, unless you hide them yourself on the Elements page.

Can I use the CSV output as input for another Mergado project?#

Yes. A CSV feed available at a URL can be used as an input data source for other projects or automations.

Do products in the export always stay in the same order?#

You determine the column order through element order settings. Row order corresponds to the order of products generated in the feed – Mergado does not guarantee it as stable if the input feed itself changes, and the user cannot change it.