` has an `id` attribute containing the value `top-pager` in the following code snippet: ``` ``` If you find a suitable tag ID that uniquely identifies the tag containing the data you want to extract, you can use the rule box **HTML getElementById**. 2\. A tag's nameThe tag named `

` in the following code snippet: ```
- ...
- ...
``` If you find the name of a suitable tag that contains the data you want to extract, you can use the rule box **HTML getElementByTagName**. 3\. XpathAn Xpath is the full path to a chosen element in the code structure. Find the needed tag in the developer's panel of your browser, open the context menu, and select **Copy XPath**. For example, the first `

` tag in the following code snippet has the Xpath `/div/ul/li[1]`. ``` ``` If you find the needed Xpath that identifies the location of the code element containing the data you want to extract, you can use the rule box **HTML getElementByXpath**. Sometimes, the crawled code of your product page can differ from the code of that page accessed on your live website in the developer's panel of your browser. The Xpaths may vary as well. To get the Xpath to the needed element in your crawled code, you can: Copy your crawled code and paste it into a local file on your computer. Save the file as an HTML. Open the HTML file in your browser and proceed using the developer's panel. HTML getElementById [#html-getelementbyid] The rule box **HTML getElementById** extracts data from HTML code using a specific ID defined in a tag. If the rule box doesn't find the provided tag ID in a value, it empties the value. Take the steps from [Add a rule box](/docs/help-center/add-a-rule-box) to add the **HTML getElementById** rule box. UUID-c58eff60-b735-6a0a-6b54-966fceb83b3b

UUID-c58eff60-b735-6a0a-6b54-966fceb83b3b

In **ID**, enter the tag ID that uniquely identifies the tag containing the data you want to extract. Select **Save**. For example, you have the following values in the **html\_code** attribute and want to extract product names from these HTML bodies. You can achieve this with the **HTML getElementById** rule box by entering `productName` as the tag ID: | **html\_code** (before) | **html\_code** (after) | | ------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------- | | `

Flat leather sandals with a bow

` | `Flat leather sandals with a bow` | | `

High-heel sandals with a buckle

` | `High-heel sandals with a buckle` | HTML getElementByTagName [#html-getelementbytagname] The rule box **HTML getElementByTagName** extracts data from HTML code using a specific name of a tag. If the rule box doesn't find the provided tag name in a value, it empties the value. Take the steps from [Add a rule box](/docs/help-center/add-a-rule-box) to add the **HTML getElementByTagName** rule box. UUID-be39c819-274d-93d6-2705-34847e4ff514

UUID-be39c819-274d-93d6-2705-34847e4ff514

In **Tagname**, enter the name of the tag containing the data you want to extract. If a value contains multiple matches of the defined tag, you can enter a number in **Occurance** to let the rule box know which occurrence of the defined tag you want to extract: * Enter *0* or leave the field empty to extract the first occurrence of the tag. * Enter *1* to extract the second occurrence of the tag. If a value contains only one occurrence of the provided tag name, but you want to extract the second one, the rule box empties the value. Select **Save**. For example, you have the following values in the **html\_code** attribute and want to extract product names from these HTML bodies. You can achieve this with the **HTML getElementByTagName** rule box by entering `div` as the tag name: | **html\_code** (before) | **html\_code** (after) | | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------- | | `

Flat leather sandals with a bow

High-heel sandals with a buckle

` | `Flat leather sandals with a bow` | | `

High-heel sandals with a buckle

` | `High-heel sandals with a buckle` | HTML getElementByXpath [#html-getelementbyxpath] The rule box **HTML getElementByXpath** extracts data from HTML code using the Xpath leading to the element in the code that stores your data. If the rule box doesn't find the provided Xpath in a value, it empties the value. Take the steps from [Add a rule box](/docs/help-center/add-a-rule-box) to add the **HTML getElementByXpath** rule box. UUID-65380f3f-7f69-1d2c-3bcd-94e4c3c9b3d8

UUID-65380f3f-7f69-1d2c-3bcd-94e4c3c9b3d8

In **XPath**, enter the path leading to the element in the code that contains the data you want to extract. If a value contains multiple matches of the defined path, you can enter a number in **Occurance** to let the rule box know which occurrence of the defined path you want to extract: * Enter *0* or leave the field empty to extract the first occurrence of the path. * Enter *1* to extract the second occurrence of the path. If a value contains only one occurrence of the provided path, but you want to extract the second one, the rule box empties the value. Select **Save**. For example, you have the following values in the **html\_code** attribute and want to extract product names from these HTML bodies. You can achieve this with the **HTML getElementByXpath** rule box by entering `//div/h1` as the Xpath: | **html\_code** (before) | **html\_code** (after) | | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------- | | `

Flat leather sandals with a bow

High-heel sandals with a buckle

` | `Flat leather sandals with a bow` | | `

High-heel sandals with a buckle

` | `High-heel sandals with a buckle` | Further work with the crawled data [#further-work-with-the-crawled-data] After extracting the needed data using the rule box category *Work with HTML*, you may need to drill further into your HTML data. For example, you can extract data via split strings or regex. Extract data via split strings [#extract-data-via-split-strings] To split the HTML code into bits and preserve only the needed parts of it, you can use the following split string rule boxes: * **Split String** splits a string into parts and removes the unneeded parts. * **Split String for PLA** splits a string into parts and removes the unneeded parts. If the rule box finds no splitter character in a string, it empties the string. * **Split String & Filter** splits a string into parts, removes the unneeded data, and trims the length of your resulting values according to a character limit. * **Split String and Count Items** splits a string into parts, counts them, and replaces the current value with the number of data parts found in it. See [Change string length](/docs/help-center/add-a-rule-box/find-the-needed-rule-box-category/change-string-length) for more information on split string rule boxes. Extract data via regex [#extract-data-via-regex] To search your HTML data for information that matches specific search patterns defined using regular expressions, you can use the following regex rule boxes: * **Preg Replace** searches your data for regex matches and replaces the matches with values of your choice. * **Preg Match** searches your data for a regex match, preserves the matching part of the data, and removes the rest of the string. The **Preg Match** rule box stops scanning a string as soon as it finds a match, so the rule box saves only the first match if there are multiple matches in a string. * **Preg Match All** has the same functionality as the **Preg Match** rule box, but it lets the platform find and preserve multiple regex matches within a string. * **Set Value if Match (Regex)** specifies the values of one attribute based on the results of a regex search performed in another attribute. See [Rule box category Use regular expressions](/docs/help-center/add-a-rule-box/find-the-needed-rule-box-category/rule-box-category-use-regular-expressions) for more information on regex rule boxes. # Rule box category Change string length import { Callout } from "fumadocs-ui/components/callout"; import { Step, Steps } from "fumadocs-ui/components/steps"; Introduction [#introduction] The category *Change string length* contains all rule boxes that can help you control the length of your attribute values based on word or character count. Knowing the length of your values, you can cut or extend your values with the rule boxes in this category. UUID-65f0405d-da6d-e821-bc09-72b617ce31cf

UUID-65f0405d-da6d-e821-bc09-72b617ce31cf

This category can be divided into several subgroups. In the following sections, you can learn how to use the rule boxes of each subgroup: * [Count the number of characters or words](#section-idm234409194566318) * [Cut or extend text based on string length](#section-idm234409196982844) * [Extract specific parts of values with split string rule boxes](#section-idm232221351802675) * [Add a static or dynamic value if it fits a character limit](#section-idm23440920712381) Count the number of characters or words [#count-the-number-of-characters-or-words] The category *Change string length* contains the rule boxes **Character count** and **Word count** to let you count the number of characters and words in your attribute values. Character count [#character-count] The **Character count** rule box counts the number of characters or bytes in a text value and overwrites the current value with the result. You can also find out the number of characters in your attribute values using the *Length Distribution* section of the Analyzer feature. See [Analyze your data in Data View](/docs/help-center/map-and-optimize-your-data/data-view/analyze-your-data-in-data-view). Take the steps from [Add a rule box](/docs/help-center/add-a-rule-box) to add the **Character count** rule box. UUID-12e41df3-ff2a-c0a7-c876-8160a7fd14ab

UUID-12e41df3-ff2a-c0a7-c876-8160a7fd14ab

In the drop-down menu, choose whether the rule box should count and output the number of bytes or characters. Select **Save**. For example, you have the following values in the **color** attribute. See how the **Character count** rule box counts the number of characters and overwrites the current values with the result if you select *character* in the drop-down menu: | **color** (before) | **color** (after) | | ------------------ | ----------------- | | *black* | `5` | | *red* | `3` | | | `0` | Word count [#word-count] The **Word count** rule box counts the number of words in a text value and overwrites the current value with the result. Take the steps from [Add a rule box](/docs/help-center/add-a-rule-box) to add the **Word count** rule box. UUID-da6c616d-be5c-5b84-2fcf-1f62aebe4d9c

UUID-da6c616d-be5c-5b84-2fcf-1f62aebe4d9c

Select **Save**. For example, you have the following values in the **color** attribute. See how the **Word count** rule box counts the number of words and overwrites the current values with the result: | **color** (before) | **color** (after) | | ------------------ | ----------------- | | *black and white* | `3` | | *red* | `1` | | | `0` | Cut or extend text based on string length [#cut-or-extend-text-based-on-string-length] The rule box category *Change string length* contains the rule boxes **Cut first characters**, **Cut last characters**, **Cut last words**, **Extend Text**, **Trim Category Tree**, **Trim to 70 characters**, and **Trim to 150 characters** to let you reduce or increase the length of text values in your site. You can also use the *Shorten Text* and *Lengthen Text* data services to achieve similar results. See [Shorten, lengthen, or create text from attributes with AI data services](/docs/help-center/import-data-feeds/enhance-your-import-data-through-data-services/generate-and-transform-content-with-ai-data-services/shorten-lengthen-or-create-text-from-attributes-with-ai-data). Cut first characters [#cut-first-characters] The **Cut first characters** rule box removes a desired number of characters at the beginning of your text values, including when it means cutting off a part of a word. This rule box can be useful if you need to meet a length limit for an attribute's values or remove the same part of text added at the beginning of all values. You can also use the *Shorten Text* data service to achieve similar results. See [Shorten, lengthen, or create text from attributes with AI data services](/docs/help-center/import-data-feeds/enhance-your-import-data-through-data-services/generate-and-transform-content-with-ai-data-services/shorten-lengthen-or-create-text-from-attributes-with-ai-data). Take the steps from [Add a rule box](/docs/help-center/add-a-rule-box) to add the **Cut first characters** rule box. UUID-05fa25e8-7133-b2c2-18b6-7e0591808641

UUID-05fa25e8-7133-b2c2-18b6-7e0591808641

In the **Use** drop-down menu, choose whether the rule box should cut the number of characters or bytes at the beginning of each value. In the input field, enter a desired number of characters or bytes that the rule box should cut off. If a value is shorter than the number of characters in this field, the rule box empties the value. Select **Save**. For example, you have the following values in the **title** attribute and want to cut off the first 15 characters in each value because the sale is over. You can achieve this with the following setup of the **Cut first characters** rule box: UUID-934d5df9-2380-5b27-6b3f-cb80b7c92cf0

UUID-934d5df9-2380-5b27-6b3f-cb80b7c92cf0

| **title** (before) | **title** (after) | | ----------------------------- | ----------------- | | *SALE! 50% OFF! Socks* | `Socks` | | *50% OFF Cap* | \[empty] | | *SALE! 50% OFF! Pajama Pants* | `Pajama Pants` | Cut last characters [#cut-last-characters] The **Cut last characters** rule box does a hard cut when a text value reaches a desired character limit, including when it means cutting off a part of a word. This rule box can be useful if you need to meet a length limit for an attribute's values. You can also use the *Shorten Text* data service to achieve similar results. See [Shorten, lengthen, or create text from attributes with AI data services](/docs/help-center/import-data-feeds/enhance-your-import-data-through-data-services/generate-and-transform-content-with-ai-data-services/shorten-lengthen-or-create-text-from-attributes-with-ai-data). Take the steps from [Add a rule box](/docs/help-center/add-a-rule-box) to add the **Cut last characters** rule box. UUID-2b0db040-b024-abdd-b2af-7ae9be11cab7

UUID-2b0db040-b024-abdd-b2af-7ae9be11cab7

In **Cut last characters if length exceeds ... characters**, enter a desired character limit to let the rule box cut off all following characters when a text length reaches the limit. Select **Save**. For example, you have the following values in the **title** attribute and want each value to stay within the limit of 15 characters. You can achieve this with the **Cut last characters** rule box by entering `15` as the limit: | **title** (before) | **title** (after) | | -------------------------------------- | ----------------- | | *Red Socks* | `Red Socks` | | *Pillow Case with Fluffy Eco-Feathers* | `Pillow Case wit` | | *Pajama Pants for Kids* | `Pajama Pants f` | Compare these results to how the **Cut last words** rule box works. See [Cut last words](#N1720605542410). Cut last words [#cut-last-words] The **Cut last words** rule box cuts off all words that exceed a desired character limit in a text value and ensures your text values don't break off in the middle of a word, unlike the **Cut last characters** rule box. This rule box can be useful if you need to meet a length limit for an attribute's values. You can also use the *Shorten Text* data service to achieve similar results. See [Shorten, lengthen, or create text from attributes with AI data services](/docs/help-center/import-data-feeds/enhance-your-import-data-through-data-services/generate-and-transform-content-with-ai-data-services/shorten-lengthen-or-create-text-from-attributes-with-ai-data). Take the steps from [Add a rule box](/docs/help-center/add-a-rule-box) to add the **Cut last words** rule box. UUID-06f1e62a-5944-7e86-7034-dc3cad4df473

UUID-06f1e62a-5944-7e86-7034-dc3cad4df473

In **Cut last words if length exceeded**, enter a desired character limit to let the rule box cut off all words outside the character limit. Select **Save**. For example, you have the following values in the **title** attribute and want each value to stay within the limit of 15 characters. At the same time, you need each value to end with a full word. You can achieve this with the **Cut last words** rule box by entering `15` as the limit: | **title** (before) | **title** (after) | | -------------------------------------- | ----------------- | | *Red Socks* | `Red Socks` | | *Pillow Case with Fluffy Eco-Feathers* | `Pillow Case` | | *Pajama Pants for Kids* | `Pajama Pants` | Compare these results to how the **Cut last characters** rule box works. See [Cut last characters](#N1720606785014). Extend Text [#extend-text] The **Extend Text** rule box lets you increase the length of a text value by setting a desired character limit and, if a value is shorter, filling the rest of it with a desired text until it reaches the limit. If a value doesn't reach the character limit with the added text string, the rule box repeats the string as many times as necessary to reach the character limit. This rule box can be useful if you need to meet a minimum length requirement for an attribute's values. You can also use the *Lengthen Text* data service to achieve similar results. See [Shorten, lengthen, or create text from attributes with AI data services](/docs/help-center/import-data-feeds/enhance-your-import-data-through-data-services/generate-and-transform-content-with-ai-data-services/shorten-lengthen-or-create-text-from-attributes-with-ai-data). Take the steps from [Add a rule box](/docs/help-center/add-a-rule-box) to add the **Extend Text** rule box. UUID-f871c649-603a-08eb-a2e7-325a1e312235

UUID-f871c649-603a-08eb-a2e7-325a1e312235

In **length of the output string**, enter a desired character limit that the rule box should meet when adding and repeating a string. If a current value exceeds the character limit you set in this field, the Extend Text rule box doesn't add any text to the value and doesn't cut it to fit the limit. In **fill character(s)**, enter the string you want the rule box to add and repeat in your text value until it reaches the desired character limit. In the drop-down menu, select where you want to add the string within the value: 1. *left* adds the string at the beginning of the current value. 2. *right* adds the string at the end of the current value. 3. *both* adds the string both at the beginning and end of the current value. Select **Save**. For example, you have the following values in the **short\_description** attribute and want each value to be exactly 30 characters long. Some values are shorter than that, so you want to add a piece of text to extend the length of those values and reach the desired 30-character limit. You can achieve this with the following setup of the **Extend Text** rule box: UUID-c3c5bea0-6786-5985-c3d6-c1b71a50a42c

UUID-c3c5bea0-6786-5985-c3d6-c1b71a50a42c

| **short\_description** (before) | **short\_description** (after) | | -------------------------------------- | -------------------------------------------------------------------------------------------------------------------- | | *Red Socks* | `Red Socks. Next-Day Shipping.` There is a space character at the end of the value. | | *Pillow Case with Fluffy Eco-Feathers* | *Pillow Case with Fluffy Eco-Feathers* | | *Pajama Pants for Kids* | `Pajama Pants for Kids. Next-Da` | Trim Category Tree [#trim-category-tree] The **Trim Category Tree** rule box cuts off category items at the `>` delimiter if they exceed a defined character limit. This rule box can be useful if you need to meet a length limit for the **category** attribute. Take the steps from [Add a rule box](/docs/help-center/add-a-rule-box) to add the **Trim Category Tree** rule box. UUID-ff558197-72c7-db52-7bf8-10696917d0d1

UUID-ff558197-72c7-db52-7bf8-10696917d0d1

In **Cut last categories at the delimiter '>' if length exceeds ... characters**, enter a desired character limit for your categories. Select **Save**. For example, you have the following values in the **category** attribute and want each value to stay within the limit of 50 characters. You can achieve this with the **Trim Category Tree** rule box by entering `50` as the limit: | **category** (before) | **category** (after) | | ------------------------------------------------------- | -------------------------------------------- | | *Apparel & Accessories > Shoe Accessories* | `Apparel & Accessories > Shoe Accessories` | | *Home & Garden > Linens & Bedding > Bedding > Blankets* | `Home & Garden > Linens & Bedding > Bedding` | | *Apparel & Accessories > Clothing > Underwear & Socks* | `Apparel & Accessories > Clothing` | Trim to 70 characters [#trim-to-70-characters] Google accepts values for the **brand** attribute if they are no longer than 70 characters. The **Trim to 70 characters** rule box does a hard cut when a text value reaches a 70-character limit, including when it means cutting off a part of a word. Take the steps from [Add a rule box](/docs/help-center/add-a-rule-box) to add the **Trim to 70 characters** rule box. UUID-e57cd4e0-6ab4-3ffb-f6fc-f13612a65225

UUID-e57cd4e0-6ab4-3ffb-f6fc-f13612a65225

Select **Save**. For example, you have the following values in the **brand** attribute and want each value to stay within the limit of 70 characters. You can achieve this with the **Trim to 70 characters** rule box: | **brand** (before) | **brand** (after) | | ----------------------------------------------------------------------------- | ----------------------------------------------------------------------- | | *Natural History Museum and Royal Philharmonic Orchestra (RPO) Collaboration* | `Natural History Museum and Royal Philharmonic Orchestra (RPO) Collabo` | | *Harley-Davidson Motor Company* | `Harley-Davidson Motor Company` | Trim to 150 characters [#trim-to-150-characters] Google accepts values for the **title** attribute if they are no longer than 150 characters. The **Trim to 150 characters** rule box does a hard cut when a text value reaches a 150-character limit, including when it means cutting off a part of a word. Take the steps from [Add a rule box](/docs/help-center/add-a-rule-box) to add the **Trim to 150 characters** rule box. UUID-ad2b540f-32b4-f6b0-1cd9-53bb01238cd0

UUID-ad2b540f-32b4-f6b0-1cd9-53bb01238cd0

Select **Save**. For example, you have the following values in the **title** attribute and want each value to stay within the limit of 150 characters. You can achieve this with the **Trim to 150 characters** rule box: | **title** (before) | **title** (after) | | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- | | *Kitchen Container for Organic Waste - Pine Wood & Stainless Steel for Organic Leftovers - Dishwasher-Safe - Removable Lid - Removable Insert* | `Kitchen Container for Organic Waste - Pine Wood & Stainless Steel for Organic Leftovers - Dishwasher-Safe - Removable Lid - Removable Insert` | | *Medium-Size Kitchen Bin for Compost with Lid Indoor 8L - Green Plastic Container for Organic Waste - Ventilation Holes Preventing Humidity Build-Up and Odor Spreading to Kitchen* | `Medium-Size Kitchen Bin for Compost with Lid Indoor 8L - Green Plastic Container for Organic Waste - Ventilation Holes Preventing Humidity Build-Up a` | Extract specific parts of values with split string rule boxes [#extract-specific-parts-of-values-with-split-string-rule-boxes] The category *Change string length* contains the rule boxes **Split String**, **Split String for PLA**, **Split String & Filter**, and **Split String and Count Items** to let you shorten the values of attributes containing category paths, lists, or other data types that involve multiple data points. Using these rule boxes, you can split each text value into data points using a delimiter and preserve only the needed parts of the value in an attribute. All split string rule boxes follow a specific method of numbering data points within strings using delimiters. This method supports both positive and negative numbers. For example, when applying any split string rule box to the category path *Animals & Pet Supplies > Pet Supplies > Dog Supplies > Dog Beds*, the platform assigns the following numbers to each step of the category path: | Positive numbers | `0` | `>` | `1` | `>` | `2` | `>` | `3` | | ---------------- | ------------------------ | -------------- | -------------- | ---------- | --- | --- | --- | | Category path | `Animals & Pet Supplies` | `Pet Supplies` | `Dog Supplies` | `Dog Beds` | | | | | Negative numbers | `-4` | `-3` | `-2` | `-1` | | | | Using these numbers and the greater-than sign (`>`) as a delimiter in a split string rule box, you can let the platform know which data points you want to retrieve and what character splits the string into data points. You can use both positive and negative numbers of data points in a split string rule box. However, if you need to retrieve a couple of data points at the end of a string, and the strings in your attribute don't always have the same number of data points, you should use negative numbers. Split String [#split-string] The **Split String** rule box uses delimiters and analyzes the values of an attribute to extract and save only those parts of the values you need. Take the steps from [Add a rule box](/docs/help-center/add-a-rule-box) to add the **Split String** rule box. UUID-49d0e3b4-b1c9-17d7-6dc6-2fec021ef7e5

UUID-49d0e3b4-b1c9-17d7-6dc6-2fec021ef7e5

UUID-c406e167-c05d-58f4-f0eb-cc2e05827e15

| **category** (before) | **category** (after) | | ----------------------------------------------------------------- | --------------------------------------- | | *Animals & Pet Supplies > Pet Supplies > Dog Supplies > Dog Beds* | `Animals & Pet Supplies > Pet Supplies` | | *Home & Garden > Linens & Bedding > Bedding > Blankets* | `Home & Garden > Linens & Bedding` | | *Apparel & Accessories > Clothing* | `Apparel & Accessories > Clothing` | The **Split String** rule box can also let you extract information from a long text. For example, you want to extract product colors from the **description** attribute where all descriptions use the same template: *The manufacturer uses only natural and hypoallergenic materials to produce these \[products]. Colors available: color1, color2, and color3. Size range: size1, size2, and size3*. You can extract colors from these descriptions with the following setup of two **Split String** rule boxes: UUID-b670fb29-c734-4fbb-2920-3e54fca4616d

UUID-b670fb29-c734-4fbb-2920-3e54fca4616d

There is a space character at the end of the input value `Colors available:`. | **description** (before) | **description** (intermediate values before applying the second rule box) | **description** (after) | | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------- | | *The manufacturer uses only natural and hypoallergenic materials to produce these dog beds. Colors available: black, gray, white, green, yellow, and lilac. Size range: XS, S, M, L, XL, and XXL* | `The manufacturer uses only natural and hypoallergenic materials to produce these dog beds. Colors available: black, gray, white, green, yellow, and lilac` | `black, gray, white, green, yellow, and lilac` | | *The manufacturer uses only natural and hypoallergenic materials to produce these dog blankets. Colors available: brown, gray, green, and blue. Size range: XS, S, L, and XXL* | `The manufacturer uses only natural and hypoallergenic materials to produce these dog blankets. Colors available: brown, gray, green, and blue` | `brown, gray, green, and blue` | | *The manufacturer uses only natural and hypoallergenic materials to produce these climbing trees for cats. Colors available: beige, gray, white, black, and brown. Size range: M, L, and XL* | `The manufacturer uses only natural and hypoallergenic materials to produce these climbing trees for cats. Colors available: beige, gray, white, black, and brown` | `beige, gray, white, black, and brown` | Split String for PLA [#split-string-for-pla] The **Split String for PLA** rule box uses delimiters and analyzes the values of an attribute to extract and save only those parts of the values you need. If the rule box finds no delimiter in a value, it empties the value to prevent you from sending incorrect data to your export channels. Take the steps from [Add a rule box](/docs/help-center/add-a-rule-box) to add the **Split String for PLA** rule box. UUID-e21eff4c-924c-4bb7-0f0c-9fa69e4d4ce7

UUID-e21eff4c-924c-4bb7-0f0c-9fa69e4d4ce7

Enter the delimiter character that splits your string into multiple data points in **Splitter**. The platform never displays the splitter in the output if you extract only one data point from the value. To see the splitter in the output value, you need to extract at least two data points. In **From**, enter the number of the data point from which the platform should start extracting information. The expected input format for this field is a digit.See the [previously shown numbering example](#informaltable-idm243305572252982) to identify the number of your desired data point. If you enter `0` in **From**, the platform starts extracting information from your first data point and, after finding no splitter character in the string, returns the entire string as if it consisted of one data point only.To have the Split String for PLA rule box empty the values that contain no splitter characters, specify any number in **From** but for `0` and negative numbers. Enter how many data points you want the platform to extract from your values in **Items**.The expected input format for this field is a digit. Only positive numbers are acceptable. If you leave **Items** empty, the platform extracts all data points of the string, starting with the data point specified in **From**. Select **Save**. Google accepts the following values for the **gender** attribute: | Rule box and setup | **category** (before) | **category** (after) | | ---------------------------------------------------------------------------------------- | ----------------------------------------------------------------- | ----------------------------- | | UUID-30a50b3a-04fb-3872-9c57-da7960601f4a

UUID-30a50b3a-04fb-3872-9c57-da7960601f4a

UUID-3463db31-426b-e339-e9a6-6adfda07009a

| *Animals & Pet Supplies > Pet Supplies > Dog Supplies > Dog Beds* | `Pet Supplies > Dog Supplies` | | *Apparel & Accessories > Clothing > Activewear* | `Clothing > Activewear` | | | *Arts & Entertainment --- Event Tickets* | | | See [Split String](/docs/help-center/add-a-rule-box/find-the-needed-rule-box-category/change-string-length#section-idm4613280768827233045222567009) for more information. Split String & Filter [#split-string--filter] The **Split String & Filter** rule box uses delimiters and analyzes the values of an attribute to extract and save only those parts of the values you need. Additionally, it lets you limit the length of your resulting value. If the resulting value exceeds its maximum length, the rule box doesn't leave chunks of data points in the value. If a part of a data point doesn't fit into the character limit, the platform omits the data point from the resulting value entirely. Take the steps from [Add a rule box](/docs/help-center/add-a-rule-box) to add the **Split String & Filter** rule box. UUID-ce86f5c2-cbd2-c99e-7d6f-950703e81dea

UUID-ce86f5c2-cbd2-c99e-7d6f-950703e81dea

Enter the delimiter character that splits your string into multiple data points in **Splitter**. The platform never displays the splitter in the output if you extract only one data point from the value. To see the splitter in the output value, you need to extract at least two data points. In **From**, enter the number of the data point from which the platform should start extracting information. The expected input format for this field is a digit.See the [previously shown numbering example](#informaltable-idm243305572252982) to identify the number of your desired data point. Enter how many data points you want the platform to extract from your values in **Items**.The expected input format for this field is a digit. Only positive numbers are acceptable. If you leave **Items** empty, the platform extracts all data points of the string, starting with the data point specified in **From**. In **Max Length**, specify a character or byte limit for your resulting value. In **Limit by**, select between *Characters* and *Bytes*. Select *Bytes* in the **Limit by** to avoid rejection by the target system that has a byte limit, or if your attribute values contain non-ASCII characters, such as accents or language-specific characters. For example, Amazon Vendor has a 250-byte keyword limit for attribute value sizes, especially for generic keyword attributes. Select **Save**. Compare the output values of the **Split String** and **Split String & Filter** rule boxes applied to the same **category** attribute: | Rule box and setup | **category** (before) | **category** (after) | | ---------------------------------------------------------------------------------------- | ------------------------------------------------------------------------ | ------------------------------------------------------ | | UUID-28f12385-28fb-14ef-13aa-7f294be5ff65

UUID-28f12385-28fb-14ef-13aa-7f294be5ff65

| *Animals & Pet Supplies > Pet Supplies > Dog Supplies > Dog Beds* | `Animals & Pet Supplies > Pet Supplies > Dog Supplies` | | *Apparel & Accessories > Clothing > Activewear* | `Apparel & Accessories > Clothing > Activewear` | | | *Arts & Entertainment > Concerts, Shows, & Other Events > Event Tickets* | `Arts & Entertainment > Concerts, Shows, & Other Events > Event Tickets` | | | UUID-96c13fd3-f9c1-60ee-4541-1934efe96a2b

UUID-96c13fd3-f9c1-60ee-4541-1934efe96a2b

| *Animals & Pet Supplies > Pet Supplies > Dog Supplies > Dog Beds* | `Animals & Pet Supplies > Pet Supplies` | | *Apparel & Accessories > Clothing > Activewear* | `Apparel & Accessories > Clothing > Activewear` | | | *Arts & Entertainment > Concerts, Shows, & Other Events > Event Tickets* | `Arts & Entertainment` | | See [Split String](#section-idm4613280768827233045222567009) for more information. Split String and Count Items [#split-string-and-count-items] The **Split String and Count Items** rule box analyzes the values of an attribute to split them into separate data points and count how many data points each value contains. The rule box uses a delimiter to count the number of data points within a value and overwrites the value with the resulting total. Take the steps from [Add a rule box](/docs/help-center/add-a-rule-box) to add the **Split String and Count Items** rule box. UUID-11fae5b8-793f-4bf9-b916-e104e0f6782f

UUID-11fae5b8-793f-4bf9-b916-e104e0f6782f

In **Please select Separator!**, enter the character that splits your value into data points. If a value doesn't contain the defined delimiter character, the rule box considers it a value with one data point and outputs `1`. Select **Save**. For example, you have the following values in the **category** attribute and want to learn how many category items each product's category has. You can achieve this with the **Split String and Count Items** rule box by entering `>` as the delimiter: | **category** (before) | **category** (after) | | ----------------------------------------------------------------- | -------------------- | | *Animals & Pet Supplies > Pet Supplies > Dog Supplies > Dog Beds* | `4` | | *Home & Garden > Linens & Bedding > Bedding > Blankets* | `4` | | *Apparel & Accessories > Clothing* | `2` | | *Apparel & Accessories \~ Clothing* | `1` | Add a static or dynamic value if it fits a character limit [#add-a-static-or-dynamic-value-if-it-fits-a-character-limit] The category *Change string length* contains the rule boxes **Add Value if Fits** and **Add Column if Fits** to let you add a static or dynamic value to an attribute if the current value can fit the added string without exceeding a character limit. See [Find the needed rule box category](/docs/help-center/add-a-rule-box/find-the-needed-rule-box-category#section-idm234375746102324) for a definition of static and dynamic values. Add Value if Fits [#add-value-if-fits] The **Add Value if Fits** rule box lets you add a word or phrase to your current values if the overall length of the resulting value doesn't exceed a desired character limit. Take the steps from [Add a rule box](/docs/help-center/add-a-rule-box) to add the **Add Value if Fits** rule box. UUID-d19b7987-387a-3995-c613-cf5a513c7353

UUID-d19b7987-387a-3995-c613-cf5a513c7353

In **Mode**, select where you want to add a string within the current value: 1. *append* adds the string at the end of the current value. To separate it from the rest of the text, add a space character at the beginning of your input in **Text**. 2. *prepend* adds the string at the beginning of the current value. To separate it from the rest of the text, add a space character at the end of your input in **Text**. Enter the string you wish to append or prepend to your current values in **Text**. Enter the desired character limit in **Max Length**. If a current value exceeds the character limit you set in this field, the Add Value if Fits rule box doesn't add any text to the value and doesn't cut it to fit the limit. Select **Save**. For example, you have the following values in the **title** attribute and want to add *ORDER NOW* at the end of each title if the overall length of the resulting value doesn't exceed 150 characters. You can achieve this with the following setup of the **Add Value if Fits** rule box: UUID-65e964d4-41f7-51e4-797a-687bb50361e0

UUID-65e964d4-41f7-51e4-797a-687bb50361e0

A space character at the beginning of the input in **Text** separates the added text from the current value. | **title** (before) | **title** (after) | | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | *Kitchen Container for Organic Waste - Pine Wood & Stainless Steel for Organic Leftovers - Dishwasher-Safe - Removable Lid - Removable Insert* | `Kitchen Container for Organic Waste - Pine Wood & Stainless Steel for Organic Leftovers - Dishwasher-Safe - Removable Lid - Removable Insert ORDER NOW` | | *Medium-Size Kitchen Bin for Compost with Lid Indoor 8L - Green Plastic Container for Organic Waste - Ventilation Holes Preventing Humidity Build-Up and Odor Spreading to Kitchen* | `Medium-Size Kitchen Bin for Compost with Lid Indoor 8L - Green Plastic Container for Organic Waste - Ventilation Holes Preventing Humidity Build-Up and Odor Spreading to Kitchen` | The value *Medium-Size Kitchen Bin for Compost with Lid Indoor 8L - Green Plastic Container for Organic Waste - Ventilation Holes Preventing Humidity Build-Up and Odor Spreading to Kitchen* exceeds the 150-character limit, so the rule box doesn't add the text *ORDER NOW*. Add Column if Fits [#add-column-if-fits] The **Add Column if Fits** rule box lets you add the values of another attribute to your current values if the overall length of the resulting value doesn't exceed a desired character limit. Take the steps from [Add a rule box](/docs/help-center/add-a-rule-box) to add the **Add Column if Fits** rule box. UUID-1ae19eba-fa82-0349-d8bf-512f61bab877

UUID-1ae19eba-fa82-0349-d8bf-512f61bab877

Select the attribute you want to add to your current values in **Column**. In **Mode**, select where you want to add the values of the chosen attribute within the current values: 1. *append* adds the string at the end of the current value. 2. *prepend* adds the string at the beginning of the current value. In **Max Length**, specify a character limit for the resulting values. Optionally, you can add some text before or after the added attribute value: 1. Enter the desired text in the input field **your text**. 2. Open the drop-down menu on the left to select *Text Before* or *Text After* and choose whether to add the text before or after the added attribute value. Select **Save**. For example, you have the following values in the **title** attribute and want to add the color of the product at the end of each title if the overall length of the resulting value doesn't exceed 150 characters. You can achieve this with the following setup of the **Add Column if Fits** rule box: UUID-2770bcff-fd1f-6823-c802-5da7488fd83f

UUID-2770bcff-fd1f-6823-c802-5da7488fd83f

| **color** (no changes) | **title** (before) | **title** (after) | | ---------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | *Green* | *Kitchen Container for Organic Waste - Pine Wood & Stainless Steel for Organic Leftovers - Dishwasher-Safe - Removable Lid - Removable Insert* | `Kitchen Container for Organic Waste - Pine Wood & Stainless Steel for Organic Leftovers - Dishwasher-Safe - Removable Lid - Removable Insert - Green` | | *Orange* | *Medium-Size Kitchen Bin for Compost with Lid Indoor 8L - Green Plastic Container for Organic Waste - Ventilation Holes Preventing Humidity Build-Up and Odor Spreading to Kitchen* | *Medium-Size Kitchen Bin for Compost with Lid Indoor 8L - Green Plastic Container for Organic Waste - Ventilation Holes Preventing Humidity Build-Up and Odor Spreading to Kitchen* | The value *Medium-Size Kitchen Bin for Compost with Lid Indoor 8L - Green Plastic Container for Organic Waste - Ventilation Holes Preventing Humidity Build-Up and Odor Spreading to Kitchen* is over 150 characters long, so the rule box doesn't append the value *Orange* from **color**. # Rule box category Clean up values import { Callout } from "fumadocs-ui/components/callout"; import { Step, Steps } from "fumadocs-ui/components/steps"; Introduction [#introduction] The category *Clean up values* contains all rule boxes that can help you detect and remove irregularities in your data. For example, you can filter GTINs, separate words, decode HTML and Base64, translate colors, remove consecutive whitespace, or remove whitespace at the beginning and end of the value. Besides that, you can detect and extract values using the rule boxes in this category. UUID-c22c19dd-e3c0-ba4e-ca3a-ffb00112b202

UUID-c22c19dd-e3c0-ba4e-ca3a-ffb00112b202

This category can be divided into several subgroups. In the following sections, you can find how to use the rule boxes of the *Clean up values* category: * [Detect and extract information from an attribute](#section-idm232219360551454) * [Filter GTINs](#section-idm232219357000848) * [Decode special characters and remove HTML tags](#section-idm232219357363796) * [Add or remove spaces](#section-idm23221948603919) * [Remove parentheses and translate colors](#section-idm234379320036808) Detect and extract information from an attribute [#detect-and-extract-information-from-an-attribute] The rule box category *Clean up values* contains the rule boxes **Detect and Extract Value**, **Detect Brand**, and **Detect Color**. Using this rule box category, you can extract product information, such as brand or color, from one attribute into another. You can also detect and extract other desired values using lists. Detect and Extract Value [#detect-and-extract-value] You can find desired values in an attribute and extract them into another attribute. Using a *Standard Inclusion/Exclusion* list, the **Detect and Extract Value** rule box finds a match in a product's value and adds it to the attribute where you apply the rule box. The platform goes through the terms on your list in the order you added them to the list. First, the platform looks for a match of the first term. If it finds a match for this term in a product's value, it extracts the match to the attribute where you apply the **Detect and Extract Value** rule box. Then, the platform moves on to the next product. Once it scans all products for a match of the first term, it moves on to the second term on your list to see if the products with no match of the first term contain a match of the second term. This process finishes when the platform has scanned all terms on your list. It may finish earlier if the platform finds matches for all your products before reaching the end of the list. Before adding and setting up this rule box, you must go to **Lists** from your site's main menu and create a *Standard Inclusion/Exclusion* list with the values you want to extract. See [Exclude products with the Standard Inclusion/Exclusion list](/docs/help-center/map-and-optimize-your-data/lists/exclude-products-with-the-standard-inclusion-exclusion-list). The order of the values in your list determines which values the platform adds to the attribute where you apply the rule box. Take the steps from [Add a rule box](/docs/help-center/add-a-rule-box) to add the **Detect and Extract Value** rule box to the attribute where you want to add the extracted values. UUID-bf76e41f-c0b6-bd91-57fd-a5fa82f4a50a

UUID-bf76e41f-c0b6-bd91-57fd-a5fa82f4a50a

In **Input Column**, select the attribute where you want to search for matches. This drop-down list shows attributes available at the previous stage. In **Detection List**, select the Standard Inclusion/Exclusion list you created for the values you want to detect and extract. In **Mode**, select how you want to add the extracted values in your current attribute: 1. *assign* completely overwrites the current value with the extracted value. 2. *append* adds the extracted value at the end of the current value. 3. *prepend* adds the extracted value at the beginning of the current value. In **Match Type**, select how the platform should extract the values from your list: * *term can occur anywhere* takes the detected match from any place within the selected attribute's values, even if it is part of a word. * *just entire word* takes the detected match only if it matches an entire word within the selected attribute's values. * *content starts with* takes the detected match if it is at the start of the selected attribute's values, even if it is part of a word. * *content starts with entire word* takes the detected match only if it matches an entire word at the start of the selected attribute's values. In **Case**, select whether the matches should be case-sensitive: * *insensitive* ignores the case of text values when matching them to the values on the list. * *sensitive* checks if the case of the text values in the current attribute matches the case of the values on the list and extracts values only if the case matches. In **On No Match**, select what should occur if there is no match: * *set Empty* empties the value. * *set Original Value* doesn't change the current value. Select **Save**. For example, you have a *Standard Inclusion/Exclusion* list with the following values: * *purses* * *shoes and socks* * *sock* If a term on the list matches an entire word in the **short description** attribute values in the import stage, you want to extract it into the **description\_keywords** attribute in the intermediate stage. You add the **Detect and Extract Value** rule box to the **description\_keywords** attribute and set it up as follows: UUID-64f6af67-9cf2-db16-471d-510e9b8c4f4e

UUID-64f6af67-9cf2-db16-471d-510e9b8c4f4e

Here is the data in your attributes after applying the rule box: | **short description** (no changes) | **description\_keywords** (before) | **description\_keywords** (after) | | ---------------------------------------- | ---------------------------------- | --------------------------------- | | *socks, shoes* | | | | *shoes and socks here* | | `shoes and socks` | | *it is a set of socks, pants, and shoes* | | | The values *socks, shoes* and *it is a set of socks, pants, and shoes* match the value *sock* from the list, but the rule box doesn't extract them into the attribute **description\_keywords** because they match a part of a word instead of an entire word. Detect Brand [#detect-brand] The **Detect Brand** rule box detects brands in one attribute and extracts them into another attribute. This rule box scans an attribute's values for a match of brand names stored in our database and adds the matches into the attribute where you apply the rule box. Take the steps from [Add a rule box](/docs/help-center/add-a-rule-box) to add the **Detect Brand** rule box. UUID-196c6ed0-85e1-205b-9ff1-d880ff4e8c2f

UUID-196c6ed0-85e1-205b-9ff1-d880ff4e8c2f

Select the attribute that contains the brand information in the **Column** drop-down list. In **Output**, select what you want to do with the extracted brand values in your current attribute: 1. *assign* completely overwrites the current value with the detected brand value. 2. *append* adds the detected brand value at the end of the current value. 3. *prepend* adds the detected brand value at the beginning of the current value. 4. *remove* deletes the detected brand value from the current value. In **On No Match**, select what should occur if there is no brand match in your values: * *leave old value* doesn't change the current value. * *set empty* empties the value. Select **Save**. For example, you have the following values in your **title** attribute and want to extract the brands mentioned in the titles into the **brand** attribute. You can achieve this with the following setup of the **Detect Brand** rule box: UUID-9fd17349-c7af-2a96-f7b6-e8e852b952dd

UUID-9fd17349-c7af-2a96-f7b6-e8e852b952dd

| **title** (no changes) | **brand** (before) | **brand** (after) | | ---------------------- | ------------------ | ----------------- | | *Nike sneakers* | | `Nike` | | *acer laptop* | *Asus* | `acer` | | *Gucci suit* | *Prada* | `Gucci` | Detect Color [#detect-color] The **Detect Color** rule box detects colors in one attribute and extracts them into another attribute. This rule box scans an attribute's values for a match of color names stored in our database and adds the matches into the attribute where you apply the rule box. Take the steps from [Add a rule box](/docs/help-center/add-a-rule-box) to add the **Detect Color** rule box. UUID-e65ab51b-7500-f159-4895-0059fec2c877

UUID-e65ab51b-7500-f159-4895-0059fec2c877

Select the attribute that contains the color information in the **Column** drop-down menu. In **Output**, select what you want to do with the extracted color values in your current attribute: 1. *append* adds the detected color value at the end of the current value. 2. *prepend* adds the detected color value at the beginning of the current value. 3. *assign* completely overwrites the current value with the detected color value. 4. *remove* deletes the detected color value from the current value. In **Language**, select which language your colors are in. The options are German, English, Spanish, French, Italian, Dutch, and Thai. If you select *all*, the rule box detects color names matching colors in any of these languages. In **On No Match**, select what should occur if there is no color match in your values: * *leave old value* doesn't change the current value. * *set empty* empties the value. Select **Save**. For example, you have the following values in your **title** attribute and want to extract the colors mentioned in the titles into the **color** attribute. You can achieve this with the following setup of the **Detect Color** rule box: UUID-59874d52-e4f6-22a5-2211-4b083cc2c7f1

UUID-59874d52-e4f6-22a5-2211-4b083cc2c7f1

| **title** (no changes) | **color** (before) | **color** (after) | | ---------------------- | ------------------ | ----------------- | | *Nike sneakers blue* | | `blue` | | *acer laptop silver* | *gray* | `silver` | | *Gucci suit black* | *dark* | `black` | Filter GTINs [#filter-gtins] Most exports require each product to have a valid product identifier, such as Global Trade Item Number (GTIN). GTIN is a unique and internationally recognized product identifier. The **Filter GTINs** rule box detects invalid GTINs via a checksum digit and deletes them. Take the steps from [Add a rule box](/docs/help-center/add-a-rule-box) to add the **Filter GTINs** rule box. UUID-f6978e32-5bf9-aa80-0d42-e9dd3266bffa

UUID-f6978e32-5bf9-aa80-0d42-e9dd3266bffa

Select one of the options in the **Advanced Behavior** drop-down menu to fix your values and make them valid GTINs: * *Fill up to 14 digits* adds one or more zeros at the beginning of the value until the value length reaches 14 digits. * *Fill up to 13 digits* adds one or more zeros at the beginning of the value until the value length reaches 13 digits. * *Trim leading zeroes* removes all zeros from the beginning of the value. * *Leave unchanged* keeps the original value. Select **Save**. For example, you have the following values in your **GTIN** attribute. You want to remove all invalid GTINs and ensure all valid GTINs are 14 digits long. You can achieve this with the **Filter GTINs** rule box by selecting *Fill up to 14 digits* as the advanced behavior: | **GTIN** (before) | **GTIN** (after) | | ----------------- | ---------------- | | *811571013579* | `00811571013579` | | *198002236142* | `00198002236142` | | *194743857492* | | The rule box checks if the GTINs are valid and adds zeros at the beginning of a value if the length of a valid GTIN is less than 14 characters. If a GTIN is invalid, the rule box empties the value. Decode special characters and remove HTML tags [#decode-special-characters-and-remove-html-tags] The rule box category *Clean up values* contains the rule boxes **Fix and Decode HTML**, **Decode base64 content**, and **Remove HTML Tags**. If you have pieces of code or HTML tags left in your data, you can convert them into readable text using these rule boxes. Fix and Decode HTML [#fix-and-decode-html] If your values have broken or encoded HTML tags, such as `&` or `ß` instead of `&` or `ß`, the **Fix and Decode HTML** rule box converts them into regular text characters. Take the steps from [Add a rule box](/docs/help-center/add-a-rule-box) to add the **Fix and Decode HTML** rule box. UUID-150d9e7f-9ce2-e1ac-e20b-d8810ab4ea59

UUID-150d9e7f-9ce2-e1ac-e20b-d8810ab4ea59

Select **Save**. For example, you have the following values in your **category** attribute and want to fix the broken characters. You can achieve this with the **Fix and Decode HTML** rule box: | **category** (before) | **category** (after) | | ------------------------------------------------------- | ------------------------------------------------------- | | *Home & Garden > Linens & Bedding > Bedding > Blankets* | `Home & Garden > Linens & Bedding > Bedding > Blankets` | | *Apparel & Accessories > Clothing > Activewear* | `Apparel & Accessories > Clothing > Activewear` | | *Apparel & Accessories > Clothing > Underwear & Socks* | `Apparel & Accessories > Clothing > Underwear & Socks` | Decode base64 content [#decode-base64-content] If your values have broken or encoded base64 tags, the **Decode base64 content** rule box converts them into readable text. For example, you can convert *VGV4dCBFeGFtcGxl* into `Text Example`. To use the **Decode base64 content** rule box, you first should prepend the values in your attribute with `base64:`. See [Add static or dynamic values](/docs/help-center/add-a-rule-box/find-the-needed-rule-box-category/add-static-or-dynamic-values#section-idm243451095559490). Take the steps from [Add a rule box](/docs/help-center/add-a-rule-box) to add the **Decode base64 content** rule box. UUID-f86cbadc-f065-fd71-7a0e-0c18a3010862

UUID-f86cbadc-f065-fd71-7a0e-0c18a3010862

Select **Save**. For example, you have the following values in your **category** attribute and want to decode them from base64 into regular text. You can achieve this with the **Decode base64 content** rule box: | **category** (before) | **category** (after) | | --------------------------------------------------------------------------------- | -------------------------------------------------------------------------- | | *base64:SG9tZSAmIEdhcmRlbiA+IExpbmVucyAmIEJlZGRpbmcgPiBCZWRkaW5nID4gQmxhbmtldHM=* | `Home & Garden > Linens & Bedding > Bedding > Blankets` | | *base64:QXBwYXJlbCAmIEFjY2Vzc29yaWVzID4gQ2xvdGhpbmcgPiBBY3RpdmV3ZWFy4oCL* | `Apparel & Accessories > Clothing > Activewear` | | *QXBwYXJlbCAmIEFjY2Vzc29yaWVzID4gQ2xvdGhpbmcgPiBVbmRlcndlYXIgJiBTb2Nrcw==* | `QXBwYXJlbCAmIEFjY2Vzc29yaWVzID4gQ2xvdGhpbmcgPiBVbmRlcndlYXIgJiBTb2Nrcw==` | Remove HTML Tags [#remove-html-tags] The **Remove HTML Tags** rule box removes any leftover HTML tags, such as *\

* or \<\br>, from your attributes. Take the steps from [Add a rule box](/docs/help-center/add-a-rule-box) to add the Remove HTML Tags rule box. Select Save. For example, you have the following values in the description attribute and want to extract text from these HTML bodies. You can achieve this with the Remove HTML Tags rule box: | description (before) | description (after) | | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `

Flat leather sandals with a bow

` | `Flat leather sandals with a bow` | | `

High-heel sandals with a buckle

` | `High-heel sandals with a buckle` | | `

Power Smoothie - Start the day with an energy boost.

5 reasons to buy it:

Gluten free,
Vitality,
Iron and Calcium,
100% organic,
Brazilian fruits: Acai (29%), Grape (25%), Mango (18%), Banana (17%), Pineapple (11%).

` | `Power Smoothie - Start the day with an energy boost. 5 reasons to buy it: Gluten free, Vitality, Iron and Calcium, 100% organic, Brazilian fruits: Acai (29%), Grape (25%), Mango (18%), Banana (17%), Pineapple (11%).` | Add or remove spaces [#add-or-remove-spaces] The rule box category *Clean up values* contains the rule boxes **Remove Consecutive Whitespace**, **Remove Spaces At Beginning and End (Trim)**, and **Separate Words**. If your attribute values have more or less space than necessary, you can use these rule boxes to clean up the text. Remove Consecutive Whitespace [#remove-consecutive-whitespace] If you have more than one consecutive space character between words, the **Remove Consecutive Whitespace** rule box removes excessive space. The words should remain separated with only one space. You can also remove or replace space using the **Text Replace** rule box. See [Text Replace](/docs/help-center/add-a-rule-box/find-the-needed-rule-box-category/replace-values#N1658483877601). Take the steps from [Add a rule box](/docs/help-center/add-a-rule-box) to add the **Remove Consecutive Whitespace** rule box. UUID-58133870-d472-f59b-f3a9-5d254e1432f4

UUID-58133870-d472-f59b-f3a9-5d254e1432f4

Select **Save**. For example, you have the following values in your **category** attribute and want to remove the extra spaces. You can achieve this with the **Remove Consecutive Whitespace** rule box: | **category** (before) | **category** (after) | | ------------------------------------------------------- | ------------------------------------------------------- | | *Home & Garden > Linens & Bedding > Bedding > Blankets* | `Home & Garden > Linens & Bedding > Bedding > Blankets` | | *Apparel & Accessories > Clothing > Activewear* | `Apparel & Accessories > Clothing > Activewear` | | *Apparel & Accessories > Clothing > Underwear & Socks* | `Apparel & Accessories > Clothing > Underwear & Socks` | Remove Spaces At Beginning And End (Trim) [#remove-spaces-at-beginning-and-end-trim] The **Remove Spaces At Beginning and End (Trim)** rule box removes unnecessary space characters at the beginning or end of your attribute's values. Take the steps from [Add a rule box](/docs/help-center/add-a-rule-box) to add the **Remove Spaces At Beginning And End (Trim)** rule box. UUID-83ed221d-d326-52e7-8d0d-1f95080ede96

UUID-83ed221d-d326-52e7-8d0d-1f95080ede96

Select **Save**. For example, you have the following values in your **description** attribute and want to remove the extra spaces. You can achieve this with the **Remove Spaces At Beginning and End (Trim)** rule box: | **description** (before) | **description** (after) | | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | *The manufacturer uses only natural and hypoallergenic materials to produce these dog beds. Colors available: black, gray, white, green, yellow, and lilac. Size range: XS, S, M, L, XL, and XXL* | `The manufacturer uses only natural and hypoallergenic materials to produce these dog beds. Colors available: black, gray, white, green, yellow, and lilac. Size range: XS, S, M, L, XL, and XXL` | | *The manufacturer uses only natural and hypoallergenic materials to produce these dog blankets. Colors available: brown, gray, green, and blue. Size range: XS, S, L, and XXL* There is additional whitespace at the beginning and end of this value. | `The manufacturer uses only natural and hypoallergenic materials to produce these dog blankets. Colors available: brown, gray, green, and blue. Size range: XS, S, L, and XXL` | Separate Words [#separate-words] If the text in your values uses the camel case, where the second word starts with a capital letter without a space to separate it from the first word, such as *brownShoes*, the **Separate Words** rule box removes the camel case. Take the steps from [Add a rule box](/docs/help-center/add-a-rule-box) to add the **Separate Words** rule box. UUID-aa413d6e-c306-f689-bc58-d911960dd06d

UUID-aa413d6e-c306-f689-bc58-d911960dd06d

Select **Save**. For example, you have the following values in your **description** attribute and want to separate the words in the camel case. You can achieve this with the **Separate Words** rule box: | **description** (before) | **description** (after) | | -------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------- | | *TheManufacturerUsesOnlyNaturalAndHypoallergenicMaterialsToProduceTheseDogBeds.* | `The Manufacturer Uses Only Natural And Hypoallergenic Materials To Produce These Dog Beds.` | | *ColorsAvailable: black, gray, white, green, yellow, and lilac.* | `Colors Available: black, gray, white, green, yellow, and lilac.` | Remove parentheses and translate colors [#remove-parentheses-and-translate-colors] The rule box category *Clean up values* contains the rule boxes **Remove Terms in Brackets** and **Translate Colors** to let you remove all terms in brackets from your texts and translate your color values into different languages. Remove Terms in Brackets [#remove-terms-in-brackets] The **Remove Terms in Brackets** rule box deletes text in parentheses from your values. It removes the text in brackets and the brackets themselves. Take the steps from [Add a rule box](/docs/help-center/add-a-rule-box) to add the **Remove Terms in Brackets** rule box. UUID-2727407c-de1c-d923-a282-3d2e0a4e2295

UUID-2727407c-de1c-d923-a282-3d2e0a4e2295

Select **Save**. For example, you have the following values in your **description** attribute and want to remove all text in brackets. You can achieve this with the **Remove Terms in Brackets** rule box: | **description** (before) | **description** (after) | | ---------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------- | | *This is a great T-shirt, the very best (endorsed by world-famous jazz saxophonist Joshua Redman) one there is.* | `This is a great T-shirt, the very best one there is.` | | *All reviewers note the high quality of the material ().* | `All reviewers note the high quality of the material .` | If unneeded spaces remain in the value after applying this rule box, you can remove them with the **Text Replace** rule box by, for example, searching for `.` or `,` preceded with a space character and replacing them with `.` or `,`. See [Text Replace](/docs/help-center/add-a-rule-box/find-the-needed-rule-box-category/replace-values#N1658483877601). Translate Colors [#translate-colors] The **Translate Colors** rule box detects colors in your values and translates them into English, German, French, Italian, Spanish, or Dutch. If you need to translate more than just color values, you can use a dedicated data service. See [Translate your feed with the Google Translate and Google Translate (Advanced) data services](/docs/help-center/import-data-feeds/enhance-your-import-data-through-data-services/generate-and-transform-content-with-ai-data-services/translate-your-feed-with-the-google-translate-and-google-tra). Take the steps from [Add a rule box](/docs/help-center/add-a-rule-box) to add the **Translate Colors** rule box. UUID-443b929c-6d0b-a768-c62f-1781a7f79c50

UUID-443b929c-6d0b-a768-c62f-1781a7f79c50

In **Source Language**, select the language of your current values: * *English* * *German* * *French* * *Italian* * *Spanish* * *Dutch* In **Target Language**, select the language you want to translate your colors into. * *English* * *German* * *French* * *Italian* * *Spanish* * *Dutch* Select **Save**. For example, you have the following values in your **title** attribute and want to translate the colors mentioned in the values into German. You can achieve this with the **Translate Colors** rule box by selecting relevant source and target languages: | **title** (before) | **title** (after) | | ---------------------------- | ----------------------------- | | *Sandals - green - size 39* | *Sandals -*`grün`*- size 39* | | *Sneakers - white - size 40* | *Sneakers -*`weiß`*- size 40* | | *Clogs - purple - size 44* | *Clogs -*`lila` -*size 44* | # Rule box category Work with date & time import { Callout } from "fumadocs-ui/components/callout"; import { Step, Steps } from "fumadocs-ui/components/steps"; Introduction [#introduction] The category *Work with date & time* contains all rule boxes that can help you convert date formats, set timestamps, and add values to your attributes based on a desired date and time. UUID-993c5dca-855d-209c-20ce-464991dab65b

UUID-993c5dca-855d-209c-20ce-464991dab65b

This rule box category contains the following rule boxes: * [Convert Datetime Format](#section-idm232219797422684) changes the date and time format. * [Convert to Timestamp](#section-idm232219797133078) converts a date to a timestamp. * [Limited Time Only](#section-idm232219797927674) adds a temporary text or discount based on a date. * [Set Column by Time](#section-idm232219797657656) assigns, appends, or prepends another attribute's value based on a date. * [Set Timestamp](#section-idm232219797000323) adds the current date and time to an attribute. * [Set Value by Datetime](#section-idm4524692355780834317490833812) assigns a value based on comparing the date in the attribute with today's or another date. Another option to work with time-bound values is to schedule rule boxes. See [Advanced rule box options](/docs/help-center/add-a-rule-box/advanced-rule-box-options). Convert Datetime Format [#convert-datetime-format] The **Convert Datetime Format** rule box changes the format of your date and time values. Take the steps from [Add a rule box](/docs/help-center/add-a-rule-box) to add the **Convert Datetime Format** rule box. UUID-fe626c46-5331-f2b1-45d4-54f91bf7f891

UUID-fe626c46-5331-f2b1-45d4-54f91bf7f891

In **Source Format**, enter your current date format. See [PHP: date - Manual](https://www.php.net/manual/en/function.date.php) for the supported formats. If you want to convert your date format into a Unix timestamp, the attribute where you apply the rule box must contain the full date and time, including hours, minutes, and seconds. If it doesn't, the platform uses the provided date elements and adds the hours, minutes, and seconds of the moment when you saved the rule box or your last site run.To assume the missing time elements, the rule box uses the GMT zone and the `H:i:s` time format. In **Target Format**, enter the desired date and time format. For example, enter `U` to convert your regular date format into a Unix timestamp. See [PHP: date - Manual](https://www.php.net/manual/en/function.date.php) for other supported formats. Select **Save**. For example, the values in your **date** attribute are in one format, and you want to convert them to another format. You can achieve this with the following setups of the rule box **Convert Datetime Format**: | Rule box setup | **date** (before) | **date** (after) | | --------------------------------------------------------------------------------------- | ------------------- | ---------------- | | UUID-aeb0ec2a-3e71-259f-df3d-54f97d09598f

UUID-aeb0ec2a-3e71-259f-df3d-54f97d09598f

| `20230525 18:05:45` | `25-05-2023` | | UUID-b25b82d4-c787-f076-d31f-3fc55947a86a

| `20230525 18:05:45` | `1685030745` | | UUID-24e70aff-c9ae-83b7-23aa-7c65fe01b967

| `20230525` | `1685008255` | The last row shows how the rule box works if your current value doesn't include hours, minutes, and seconds. Namely, it uses the moment when you saved the rule box, which was at 09:50:55 GMT+0000. Convert to Timestamp [#convert-to-timestamp] The **Convert to Timestamp** rule box converts a date or a date-related text into a Unix timestamp using your current time zone. Examples of strings you can convert into timestamps using this rule box: * *now* * *June 2, 2023* * *next Thursday* See [PHP: strtotime - Manual](https://www.php.net/manual/en/function.strtotime.php) for the supported string formats you can convert into a timestamp. If the rule box doesn't support the date and time format of a value, it empties the value. To add the **Convert to Timestamp** rule box: Take the steps from [Add a rule box](/docs/help-center/add-a-rule-box) to add the **Convert to Timestamp** rule box. UUID-2c295020-0536-cd0a-1da1-e84f79145025

UUID-2c295020-0536-cd0a-1da1-e84f79145025

Select **Save**. For example, you have the following values in the **date** attribute and want to convert them all to timestamps. You can achieve this with the **Convert to Timestamp** rule box: | **date** (before) | **date** (after) | | --------------------- | ---------------- | | *01.02.2023 10:48:01* | `1675244881` | | *01.02.2023* | `1675206000` | | *now* | `1721399979` | | *June 2, 2023* | `1685656800` | | *2025-04-10 22:00:18* | `1744315218` | | *last Thursday* | `1721253600` | The rule box uses your time zone to create timestamps, which in this example is GMT+1. If your values contain only a date without the exact time, such as *01.02.2023* instead of *01.02.2023 10:48:01*, the rule box **Convert to Timestamp** works as follows: * Assumes the time is `00:00` in your current time zone. * Converts the given date and the assumed time into the GMT zone. * Converts the full date and time in the GMT zone to a timestamp. This is why the full date and time *01.02.2023 10:48:01* in the GMT+1 time zone has the timestamp `1675244881`, but the same date without the time converts to `1675206000`. Limited Time Only [#limited-time-only] The **Limited Time Only** rule box temporarily changes a value in the attribute. This rule box can change a value by applying a discount, assigning a new value, and appending or prepending a string to a value. You can set the start and end dates or use dates stored in other attributes to create the timeframe when the platform should apply the desired changes. Take the steps from [Add a rule box](/docs/help-center/add-a-rule-box) to add the **Limited Time Only** rule box. UUID-383fb13b-90fc-61fd-6cc0-06005f374fa9

UUID-383fb13b-90fc-61fd-6cc0-06005f374fa9

Use one of the following options to define the start date for applying the changes to your attribute: 1. Select a relevant attribute that stores the needed date in **Start Date via Column**.If you add your rule box in the intermediate stage, only import-stage attributes are available in this drop-down menu. If you add it in the export stage, only intermediate-stage attributes are available. 2. Enter a static date manually in **set Start Date**. For both options, your dates must be in the format *Y-m-d*, for example, *2024-01-31*. See [Convert Datetime Format](#section-idm232219797422684) to change the date format if needed. Use one of the following options to define the end date for applying the changes to your attribute: 1. Select a relevant attribute that stores the needed date in **End Date via Column**.If you add your rule box in the intermediate stage, only import-stage attributes are available in this drop-down menu. If you add it in the export stage, only intermediate-stage attributes are available. 2. Enter a static date manually in **set End Date**. For both options, your dates must be in the format *Y-m-d*, for example, *2024-01-31*. See [Convert Datetime Format](#section-idm232219797422684) to change the date format if needed. Choose how you want to change the values in your attribute: 1. If you want to add certain text to your attribute, enter the desired text in **Text** and choose how you want the rule box to add this text in **Mode**: 2. *assign* completely overwrites the current value with the desired text. 3. *append* adds the desired text at the end of the current value. 4. *prepend* adds the desired text at the beginning of the current value. 5. To add a discount to your attribute, enter the needed amount in **Discount** without the percent symbol (`%`). Select **Save**. For example, you have the following values in the **price** attribute and want to add a 30% discount to the prices of your products based on the start dates in **discount\_date**. The end of the sale should be on August 7, 2024. You can achieve this with the following setup of the **Limited Time Only** rule box: UUID-70347f29-d8bc-945d-c1e8-a919a878f537

UUID-70347f29-d8bc-945d-c1e8-a919a878f537

| **discount\_date** (no changes) | **price** (before) | **price** (after) | | ------------------------------- | ------------------ | ----------------- | | *2024-07-10* | *300* | `210` | | *2024-07-22* | *34* | `23.8` | | *2024-08-22* | *3* | `3` | You apply the **Limited Time Only** rule box on July 22, 2024. Set Column by Time [#set-column-by-time] The **Set Column by Time** rule box assigns, appends, or prepends a value from another attribute based on a date-and-time condition. A date and time condition works as follows: . In the rule box setup, you choose a date attribute and select whether the date in that attribute should be in the past, future, or now to meet the desired date and time condition. . If the date meets the desired date and time condition, the platform assigns, appends, or prepends a value from a selected attribute to the current attribute. The **Set Column by Time** rule box may be helpful when launching a sale. Take the steps from [Add a rule box](/docs/help-center/add-a-rule-box) to add the **Set Column by Time** rule box. UUID-70d9039a-8226-9435-fce3-d01ec04290c2

UUID-70d9039a-8226-9435-fce3-d01ec04290c2

In **Source Column**, choose your date attribute. In **Time Format**, enter the format used in your date attribute. See [PHP: date - Manual](https://www.php.net/manual/en/function.date.php) for the supported formats. In the drop-down menu, select your desired date and time condition: * *in the future* applies the change if the current value contains a future date. * *in the past* applies the change if the current value contains a past date. * *now* applies the change if the current value contains today's date. In **Column**, select the attribute that stores the values you want to add. In **Mode**, choose how you want to modify your current values if the date attribute meets the desired date and time condition: 1. *assign* overwrites the current value with the value of the attribute chosen in [see the relevant section](#N1685975454647). 2. *append* adds the value of the attribute chosen in [see the relevant section](#N1685975454647) at the end of the current value. 3. *prepend* adds the value of the attribute chosen in [see the relevant section](#N1685975454647) at the beginning of the current value. Select **Save**. For example, you are selling a popular sneaker model, but a newer one will drop soon, and you have that date in **release\_date**. Once the new sneaker model becomes available, you want to announce a sale and append a short text from the **sale\_promo\_text** attribute to the title of the older sneakers in **product\_title**. You can achieve this with the following setup of the **Set Column by Time** rule box: UUID-1945b157-00ab-e9e2-98da-2cd352672af6

UUID-1945b157-00ab-e9e2-98da-2cd352672af6

| **release\_date** (no changes) | **sale\_promo\_text** (no changes) | **product\_title** (before) | **product\_title** (after) | | ------------------------------ | ---------------------------------- | -------------------------------- | ----------------------------------- | | *2024-07-21* | *25% OFF* | *FIRE Sneakers 2023, Brown* | `FIRE Sneakers 2023, Brown 25% OFF` | | *2024-10-03* | *25% OFF* | *FIRE Sneakers 2023, Orange* | `FIRE Sneakers 2023, Orange` | | *06.07.2024* | *25% OFF* | *FIRE Sneakers 2023, Pale Green* | `FIRE Sneakers 2023, Pale Green` | The platform checks whether the new sneakers' release date in **release\_date** has passed. As soon as that date passes, the platform appends the text from **sale\_promo\_text** to the title of your product. You apply the **Set Column by Time** rule box on July 22, 2024. Set Timestamp [#set-timestamp] The **Set Timestamp** rule box overwrites the values in an attribute with the current date and time in a desired time zone and format. See [PHP: date - Manual](https://www.php.net/manual/en/function.date.php) for the supported formats. This rule box renews the timestamp every time you run the site or refresh Data View. Take the steps from [Add a rule box](/docs/help-center/add-a-rule-box) to add the **Set Timestamp** rule box. UUID-97b88a22-bcc4-2101-ea4d-08e7ea225359

UUID-97b88a22-bcc4-2101-ea4d-08e7ea225359

In **Format**, enter the date format that the rule box should use to add the current date and time to your attribute. See [PHP: date - Manual](https://www.php.net/manual/en/function.date.php) for the supported formats. To add a Unix timestamp instead of standard date formats, enter `U`. In **Timezone**, select the needed time zone. Select **Save**. For example, you have the following values in the **date** attribute and want to overwrite them with today's date in the format *DD.Mon YYYY*. You can achieve this with the **Set Timestamp** rule box by entering `d.M Y` in **Format** and choosing the needed timezone: | **date** (before) | **date** (after) | | ----------------- | ---------------- | | *2024-07-21* | `22.Jul 2024` | | | `22.Jul 2024` | | *06.07.2024* | `22.Jul 2024` | You apply the **Set Timestamp** rule box on July 22, 2024. Set Value by Datetime [#set-value-by-datetime] The **Set Value by Datetime** rule box compares a date value in an attribute with today's or another date to assign a new value based on the comparison. It follows this algorithm to compare dates and assign new values: | If | `today or another date` | **\<** | `date in the attribute`, | then | assign a new value. | | -- | ----------------------- | ------ | ------------------------ | ---- | ------------------- | You can choose other inequality symbols, not only the less-than sign (**\<**). Take the steps from [Add a rule box](/docs/help-center/add-a-rule-box) to add the **Set Value by Datetime** rule box. UUID-33269b39-0fed-9fe2-f5f7-aa4ede7987d5

UUID-33269b39-0fed-9fe2-f5f7-aa4ede7987d5

Enter the date format used in your attribute in **Date Format**. See [PHP: date - Manual](https://www.php.net/manual/en/function.date.php) for the supported formats. In **Operator**, choose an operator to compare the dates in your values to a desired date specified in Set Days: * `<` means the date specified in Set Days should be less than the date in the attribute. * `<=` means the date specified in Set Days should be less than or equal to the date in the attribute. * `>=` means the date specified in Set Days should be greater than or equal to the date in the attribute. * `>` means the date specified in Set Days should be greater than the date in the attribute. In **Set Days**, define the date you want to compare your current values to by entering `-` or `+` and a number of days: * Enter `+0` to compare your date values to today's date. * Enter `+1` to compare your date values to tomorrow's date. * Enter `-1` to compare your date values to yesterday's date. In **Set value**, enter the value you want to assign in the current attribute if a date in the attribute matches the set condition. Select **Save**. For example, you have the following values in the **manufactured\_on** attribute and want to overwrite them with the value *incorrect* if the date in the attribute is later than last Friday, July 19, 2024. You can achieve this with the following setup of the **Set Value by Datetime** rule box: UUID-6ac20b24-4407-3a32-7347-c1d0984dda71

UUID-6ac20b24-4407-3a32-7347-c1d0984dda71

| **manufactured\_on** (before) | **manufactured\_on** (after) | | ----------------------------- | ---------------------------- | | *2024-07-21* | `incorrect` | | *2024-07-19* | *2024-07-19* | | *06.08.2024* | *06.08.2024* | | *2024-07-16* | *2024-07-16* | | *2024-10-03* | `incorrect` | You apply the **Set Value by Datetime** rule box on Monday, July 22, 2024. # Rule box category Use lists import { Step, Steps } from "fumadocs-ui/components/steps"; Introduction [#introduction] The category *Use lists* contains the rule boxes that can apply a list you created in **Lists** to a relevant attribute within your site. To use the rule boxes of this category, you first need to create a list. See [Lists](/docs/help-center/map-and-optimize-your-data/lists). You can collect all the search terms in a list and then use a list in a needed rule box to replace, categorize, include, or exclude items. Use the rule boxes with lists when you have more than 30 terms. Also, you can reuse lists across multiple sites, making changes in one place. UUID-14ea8b3b-995b-1221-d1e7-c21900644920

UUID-14ea8b3b-995b-1221-d1e7-c21900644920

This category can be divided into several subgroups. In the following sections, you can find how to use list-based rule boxes to perform the following actions: * [Replace values with list-based rule boxes](#section-idm234388372362115) * [Categorize and map values to classifications with lists-based rule boxes](#section-idm234388380919298) * [Include or exclude products with list-based rule boxes](#section-idm234388357357836) * [Detect and extract information from an attribute with list-based rule box](#section-idm234391477524279) Replace values with list-based rule boxes [#replace-values-with-list-based-rule-boxes] The *Use lists* rule box category contains the replacement rule boxes to let you replace certain values based on a condition. If you need to replace a large number of values in your data, you can add them to a list and apply one of the following rule boxes that will search for and replace parts of your data in bulk: * [Replacement](#section-idm234389788424418) applies a replacement list to substitute the matching complete words in the value with the mapped terms from the list. * [Replacement Sensitive](#section-idm234389854406382) applies a replacement list to substitute the matching parts of a word in a value, a complete word, or an entire value with the terms from the list. * [Taxonomy Mapping](#section-idm234390016150987) applies a Partner Taxonomy Mapping list to substitute the entire value or only a part of the value with the terms from the list. This rule box works best if you need to replace category terms according to your export partner taxonomy. Replacement [#replacement] The **Replacement** rule box substitutes the matching complete words within a value with the mapped terms from the list. If you need also to choose whether the matches should be case-sensitive and whether to leave the original value or empty the value if there’s no match in a value, use the [Replacement Sensitive](#section-idm234389854406382) rule box. Go to **Lists** from your site's main menu and add all terms you need to replace to the *Standard*, *Dynamic*, or *Attribute-based Replacement* list. See [Lists](/docs/help-center/map-and-optimize-your-data/lists#section-idm13275861981064) to choose a required type. Take the steps from [Add a rule box](/docs/help-center/add-a-rule-box) to add the **Replacement** rule box. UUID-d0e0dda6-63bb-6602-bc48-c305ca34e080

UUID-d0e0dda6-63bb-6602-bc48-c305ca34e080

Choose the appropriate replacement list from the **Select an Option** drop-down menu. Select **Save**. For example, you want to replace the size abbreviations with whole words. You can achieve this by adding these terms to the replacement lists and setting up the **Replacement** rule box as follows: UUID-a50b7e0d-0817-16f4-42e0-bb86ff243d1e

UUID-a50b7e0d-0817-16f4-42e0-bb86ff243d1e

UUID-3ed4289f-5e25-24ff-2876-561458108dd8

| **size** (before) | **size** (after) | | ----------------- | ---------------------------- | | *S* | `small` | | *M* | `medium` | | *L size* | `large size` | | *S*, *M*, *XL* | `small, medium, extra large` | The rule box changes all matching values, even if they are parts of the value. For example, *L size* changes into `large size`. *S, M, XL* changes into `small, medium, extra large`. Replacement Sensitive [#replacement-sensitive] The **Replacement Sensitive** rule box lets you substitute the matching parts of a word in a value, a complete word, or an entire value with the terms from the list. Go to **Lists** from your site's main menu and add all terms you need to replace to the *Standard*, *Dynamic*, or *Attribute-based Replacement* list. See [Lists](/docs/help-center/map-and-optimize-your-data/lists#section-idm13275861981064) to choose a required type. Take the steps from [Add a rule box](/docs/help-center/add-a-rule-box) to add the **Replacement Sensitive** rule box. UUID-90737d62-f2ea-aaa1-43dd-66ba489a96e7

UUID-90737d62-f2ea-aaa1-43dd-66ba489a96e7

Choose the appropriate replacement list from the **Select an Option** drop-down menu. Select between *Case Sensitive* and *Case Insensitive* if the search needs to consider capitalization. Select between full and partial word matches from the drop-down: * *Exact Word* replaces a word only if it's a complete word that matches the search term. For example, if the value is *Texting is a good idea* and the list should replace *Texting* with `TESTING`, the result should be `TESTING is a good idea`. * *Not Exact Word* replaces a word even if only a part of the word matches the search term. For example, if the value is *Texting is a good idea* and the list should replace *Text* with `TEST`, the result should be `TESTing is a good idea`. Select the result you want to have in case of no match: * *Set Value if No Match* leaves the original value. * *Set Empty if No Match* empties the value. Select **Save**. For example, you need to correct a mistake in the description and replace all forms of the word `text` to `test`. You can achieve this by adding these terms to a replacement lists and setting up the **Replacement Sensitive** rule box as follows: UUID-23455ce4-14e1-c273-4ec8-fcb8cfb2e872

UUID-23455ce4-14e1-c273-4ec8-fcb8cfb2e872

UUID-787dcdb1-8547-05df-be1d-a0cc0a4a8ea1

| **description** (before) | **description** (after) | | ------------------------------------------- | ------------------------------------------- | | *Texting cosmetics. Not texted on animals.* | `Testing cosmetics. Not tested on animals.` | The setting *Not exact Word* lets the rule box change all matching parts of words. Selecting *Exact Word* in the rule box settings changes only the entire word within the value. Taxonomy Mapping [#taxonomy-mapping] The **Taxonomy Mapping** rule box lets you replace your categories with categories from a partner's taxonomy, such as categories of Google Merchant Center, Amazon, eBay, and other channels. Matching a partner taxonomy ensures that your product categorization is correct. The replacement happens if the replacement term matches the entire value. Go to **Lists** from your site's main menu and add all terms you need to replace to the *Partner Taxonomy Mapping* list. See [Replace attributes with Partner Taxonomy Mapping list](/docs/help-center/map-and-optimize-your-data/lists/replace-attributes-with-partner-taxonomy-mapping-list) list. Take the steps from [Add a rule box](/docs/help-center/add-a-rule-box) to add the **Taxonomy Mapping** rule box. UUID-8d10ee6a-de75-c1b4-5ed4-22e2bdcc8217

UUID-8d10ee6a-de75-c1b4-5ed4-22e2bdcc8217

Choose a list from the **Select an Option** drop-down menu. In **Case Sensitivity**, choose *Match Sensitive* to perform a case-sensitive search in the attribute's values or *Match Insensitive* to ignore the case of the values. In **On No Match**, choose what should happen if there is no match with the values of the list: * *set to empty string* empties the value. * *set original value* leaves the original value. The checkbox **New taxonomy values should act as not matched, as log as there is no value assigned to them** lets you treat newly imported values: * *selected* – new unmatched values stay unchanged in the attribute. * *unselected* – new unmatched values stay unchanged, or the platform replaces them to empty values if you selected *set to empty string* in **On No Match**. Select **Save**. For example, you want to replace your current category names with partner taxonomy. You can achieve this by adding these terms to a Partner Taxonomy Mapping list and setting up the **Taxonomy Mapping** rule box as follows: UUID-16baef34-2ec9-9848-acc9-ef34688d3b15

UUID-16baef34-2ec9-9848-acc9-ef34688d3b15

UUID-d7b136a7-bde9-0fe7-d078-343f19567beb

| **category** (before) | **category** (after) | | ---------------------------- | ------------------------------- | | *Shampoo* | `Beauty > Hair care` | | *Lipsticks* | `Beauty > Decorative cosmetics` | | *Lip balms* | | | *Shampoo, conditioner, mask* | | The rule box replaces only the entirely matching values. That's why the values *Lip balm* and *Shampoo, conditioner, mask* are empty. Categorize and map values to classifications with lists-based rule boxes [#categorize-and-map-values-to-classifications-with-lists-based-rule-boxes] The *Use lists* rule box category contains the categorization and mapping rule boxes to let you assign categories to the products and replace your custom categories with terms specific to a needed classification system. * [Classification Mapping](#section-idm234390064730298) applies the Classification Mapping list to the values of the **category** attribute to replace its values with the terms specific to a needed classification system, such as the ETIM classification. See [Set up the Classification Mapping list](/docs/help-center/map-and-optimize-your-data/lists/set-up-the-classification-mapping-list). * [Categorize by Keywords](#section-idm234390064916242) assigns a category based on the keywords found in the connected attribute. Classification Mapping [#classification-mapping] The **Classification Mapping** rule box replaces your current category values with the categories specific to the required classification system. Go to **Lists** from your site's main menu and add all terms you need to replace to the *Classification Mapping list*. Take the steps from [Add a rule box](/docs/help-center/add-a-rule-box) to add the **Classification Mapping** rule box. UUID-2d055cc3-6ba4-8b43-2a3b-21846705daf8

UUID-2d055cc3-6ba4-8b43-2a3b-21846705daf8

Choose the list from the **List** drop-down menu. In **Case Sensitivity**, choose *Match Sensitive* to perform a case-sensitive search in the attribute's values or *Match Insensitive* to ignore the case of the values. In **On No Match**, choose what should happen if there is no match with the values of the list: * *set to empty string* makes the cell empty * *set original value* leaves the original value Select **Save**. For example, you want to replace your current categories with categories used in the ETIM-9.0 classification. You can achieve this by adding these terms to the *Classification Mapping* list and setting up the **Classification Mapping** rule box as follows: UUID-a243f654-817d-c0a6-57c8-b9904b112e0d

UUID-a243f654-817d-c0a6-57c8-b9904b112e0d

UUID-528e3f00-664d-2512-f093-f605afade731

| **category** (before) | **category** (after) | | --------------------- | -------------------- | | *Heating* | `EC011686` | | *Ventilation* | `EC011606` | | *Tools* | `EC000181` | | *Water taps* | | In this example, the rule box replaces matching values with ETIM 9.0 classification categories and makes values that don't match empty. Categorize by Keywords [#categorize-by-keywords] The **Categorize by Keywords** rule box uses a replacement list to assign a category based on the keywords found in the needed attribute, such as **description** or **title**. This rule box can be useful if you don't need categorization for any specific classification system but want to create your categories based on the existing product titles or descriptions. The rule box can scan large texts to find the keywords and assign a corresponding category based on the highest score. The scoring rules are as follows: * If there is no match, the output is empty. * The text should have all the words from the search term in the replacing list. * The order of the words in the text doesn't matter. * Text matching is case-insensitive; for example, `blue` matches `Blue`. * The repeating words are counted only once. For example, `women’s shoes, ladies’ shoes, girls’ shoes` matched against `women's shoes, ladies' shoes` would score 3: `women's`, `ladies'`, `shoes`. * Only whole words match: the word `shoe` doesn't match `shoes`. * Every word, including 1-letter words, counts. For example, `Three Men in a Boat: To Say Nothing of the Dog` matched against `a dog` will result in a score of 2: `a` and `dog`. Create a list of terms you need to replace using the *Standard* or *Dynamic Replacement* list. See [Lists](/docs/help-center/map-and-optimize-your-data/lists#section-idm13275861981064) to choose a required type. In Dataflow, connect from import to intermediate the attribute containing keywords to the attribute where you want to store categories. For example, you can connect **description** to **category**. Take the steps from [Add a rule box](/docs/help-center/add-a-rule-box) to add the **Categorize by Keywords** rule box to the attribute where you want to store categories. UUID-79f32524-c06a-4485-99fa-12c8dc3dea7c

UUID-79f32524-c06a-4485-99fa-12c8dc3dea7c

In **Search in Column**, select an attribute where you want to search for the keywords from the list. Choose the replacement list from the **List** drop-down menu. Select **Save**. For example, you want to create categories based on the existing product descriptions. You can achieve this by adding terms to the replacement lists and setting up the **Categorize by Keywords** rule box as follows: UUID-adfd1235-4cc5-2fcb-ddd4-6594e4edb4eb

UUID-adfd1235-4cc5-2fcb-ddd4-6594e4edb4eb

UUID-fb1c2cc2-50de-a5a4-8761-6d997e56ad55

| **description** | **category** (before) | **category** (after) | | ------------------------------------------------------------------------ | --------------------- | -------------------- | | *Women's Top, Classic Cut, Basic Short Sleeve Crop Top, Crew Neck, Blue* | *clothes* | `Tops & T-Shirts` | | *Women's Top, Casual Cut, Basic Short Sleeve, Crew Neck, White* | *clothes* | `Tops & T-Shirts` | | *Women's Top, Basic Long Sleeve Crop Top, V-Neck, Red* | *clothes* | `Long Sleeves` | | *Women's Dress, Basic Long Sleeve, V-Neck, White* | *clothes* | `Long Dresses` | | *Women's Dress, Long, White* | *clothes* | `Long Dresses` | | *Women's Dress* | *clothes* | | In this example, the rule box replaces existing category values with the categories in the replacement list and makes values that don't match empty. The matching and category assignment is based on the scoring rules. In this example, the category with more unique words in the text wins. Also, when the number of unique words is equal, the exact match wins. For example, the fourth row contains two matches for two categories: `Long Sleeve` and `Dress Long`. The *Long Dresses* category wins as the keywords match exactly the search term in the list. In case of the *Long Sleeve* win, the text should contain `Top Long Sleeve`. UUID-cb753548-9295-de47-8a75-1213e8ce1cd6

UUID-cb753548-9295-de47-8a75-1213e8ce1cd6

Include or exclude products with list-based rule boxes [#include-or-exclude-products-with-list-based-rule-boxes] The *Use lists* rule box category contains the blacklist and whitelist rule boxes to let you exclude or include products during export if an attribute contains matches with the terms on the *Inclusion/Exclusion* list. * **Blacklist** excludes products from export if their attribute's values contain a term that matches the term in the selected *Inclusion/Exclusion* list. * **Blacklist Entire Word** excludes products from export if their attribute's entire values match a term in the selected *Inclusion/Exclusion* list. * **Negative Blacklist** excludes products from export if their attribute doesn't contain values that match a term in the selected *Inclusion/Exclusion* list. If you need to include certain products during export or protect specific terms from exclusion, use the **Whitelist** rule box. See [Include or exclude products](/docs/help-center/add-a-rule-box/find-the-needed-rule-box-category/include-or-exclude-products) to set up these rule boxes. Detect and extract information from an attribute with list-based rule box [#detect-and-extract-information-from-an-attribute-with-list-based-rule-box] The *Use lists* rule box category contains the detect and extract rule boxes to let you find desired values in an attribute and extract them into another attribute. Using a *Standard Inclusion/Exclusion* list, the **Detect and Extract Value** rule box finds a match in a product's value and adds it to the attribute where you apply the rule box. See [Clean up values](/docs/help-center/add-a-rule-box/find-the-needed-rule-box-category/clean-up-values) to set up the rule box. # Rule box category Google Merchant Center import { Callout } from "fumadocs-ui/components/callout"; import { Step, Steps } from "fumadocs-ui/components/steps"; Introduction [#introduction] The category *Google Merchant Center* contains all rule boxes that can help you prepare your product data for GMC. This category lets you set age groups, availability, conditions, gender, expiration dates, size types, and size systems to values accepted by Google. Some rule boxes in this category only apply to specific sales verticals. For example, the **Set Size Type** or **Set Gender** rule boxes mainly relate to clothing retailers. UUID-137581ee-8133-7652-0528-22f2da75e4a4

UUID-137581ee-8133-7652-0528-22f2da75e4a4

Select a link to go to the section describing the needed rule box: * [Set Age Group](#section-idm232221321747321) * [Set Age Group by Regex](#section-idm234388217401983) * [Set Availability](#section-idm232221322027537) * [Set Availability by Stock](#section-idm234388218581794) * [Set Condition](#section-idm232221322125998) * [Set Condition by Regex](#section-idm234388221071861) * [Set Expiration Date](#section-idm232221322333827) * [Set Gender](#section-idm232221322548479) * [Set Gender by Regex](#section-idm234388225267714) * [Set Identifier Exists](#section-idm4551344488440033327155444251) * [Set Size System](#section-idm234388228536953) * [Set Size Type](#section-idm232221322913584) * [Set Size Type by Regex](#section-idm2343882284476) * [Split String for PLA](#section-idm243441251445678) * [Translate Google Category](#section-idm23222132313624) Some rule boxes in this category use regular expressions (regex). See [Rule box category Use regular expressions](/docs/help-center/add-a-rule-box/find-the-needed-rule-box-category/rule-box-category-use-regular-expressions) to learn about regex. You can use the *Regex generator* available in these rule boxes to get a regex suggestion that suits your use case: Select a necessary rule box. Select **>\_** in a rule box and describe the result you want to achieve in the **Regex generator** window. Select **Generate**. Select **copy** below the **Answer** field. UUID-f2365ea1-4696-e83e-cf7c-29bfed0d3276

UUID-f2365ea1-4696-e83e-cf7c-29bfed0d3276

Paste the copied answer into the regex field of the rule box. Set Age Group [#set-age-group] Google accepts the following values for the **age\_group** attribute: * *adult* * *kids* * *infant* * *toddler* * *newborn* With the **Set Age Group** rule box, you can replace your current values with one of the valid age groups accepted by Google: Take the steps from [Add a rule box](/docs/help-center/add-a-rule-box) to add the **Set Age Group** rule box. UUID-e704c8d3-9d99-6d38-226c-e3e9b25e5b79

UUID-e704c8d3-9d99-6d38-226c-e3e9b25e5b79

Select the needed age group value from the drop-down menu. Select **Save**. For example, you have varying non-valid values in the **age\_group** attribute, and you want to change them all to the valid value *toddler*: | **age\_group** (before) | **age\_group** (after) | | ------------------------------------ | ---------------------- | | *children between 1 and 3 years old* | `toddler` | | *1-3 year olds* | `toddler` | | *toddlers* | `toddler` | Set Age Group by Regex [#set-age-group-by-regex] Google accepts the following values for the **age\_group** attribute: * *adult* * *kids* * *infant* * *toddler* * *newborn* With the **Set Age Group by Regex** rule box, you can use regular expressions to search your current values for matches and replace them with corresponding valid age groups accepted by Google. Once the **Set Age Group by Regex** rule box finds a regex match in a value, it changes the entire current value to the corresponding value accepted by Google. If one value contains multiple regex matches related to different age groups, the rule box assigns the age group related to the first regex match within the value. If the rule box doesn't find a regex match in a value, it assigns the value `adult` to make sure your **age\_group** attribute contains only valid entries. Take the steps from [Add a rule box](/docs/help-center/add-a-rule-box) to add the **Set Age Group by Regex** rule box. UUID-c327fa66-c78e-e181-1433-ae5b2e7602d2

UUID-c327fa66-c78e-e181-1433-ae5b2e7602d2

In **Adult**, **Kids**, **Infant**, **Toddler**, and **Newborn**, enter regular expressions to search your values and replace the matching parts with a relevant age group value. Use the *Regex generator* by selecting **>\_** to get a regex suggestion. Select **Save**. For example, you have different non-valid values in the **age\_group** attribute, and you need to assign a valid age group to each product based on its current value. UUID-b90c4c3c-3e62-704c-94ae-a1db74d933eb

UUID-b90c4c3c-3e62-704c-94ae-a1db74d933eb

With the regular expressions `/(women|female|men|male|adult|adults)/g` and `/(children|child|kid|kids|boy|girl|boys|girls)/`, you can search your current values for the possible alternatives to the valid *adult* and *kids* values and then change the current values to the appropriate valid age group. | **age\_group** (before) | **age\_group** (after) | | ----------------------- | ---------------------- | | *women* | `adult` | | *all ages* | `adult` | | *children, men* | `kids` | Set Availability [#set-availability] Google accepts the following values for the **availability** attribute: * *in stock* * *out of stock* * *preorder* * *backorder* With the **Set Availability** rule box, you can replace your current values with one of the valid availability types accepted by Google: Take the steps from [Add a rule box](/docs/help-center/add-a-rule-box) to add the **Set Availability** rule box. UUID-9386b85c-0f94-8911-7570-819855a5cee0

UUID-9386b85c-0f94-8911-7570-819855a5cee0

Select the relevant availability type from the drop-down menu. Select **Save**. For example, you have different non-valid values in the **availability** attribute, and you want to change them all to the valid value *in stock*: | **availability** (before) | **availability** (after) | | ------------------------- | ------------------------ | | *available* | `in stock` | | *available for purchase* | `in stock` | | *in stock* | `in stock` | Set Availability by Stock [#set-availability-by-stock] Google accepts the following values for the **availability** attribute: * *in stock* * *out of stock* * *preorder* * *backorder* With the **Set Availability by Stock** rule box, you can use your **stock** attribute to automatically set your **availability** attribute to one of the valid availability types accepted by Google: Take the steps from [Add a rule box](/docs/help-center/add-a-rule-box) to add the **Set Availability by Stock** rule box. UUID-e2d476a8-9f85-3c94-515c-3001b56b7750

UUID-e2d476a8-9f85-3c94-515c-3001b56b7750

Select the attribute with the stock information from the drop-down menu. This menu shows the attributes of the previous stage. Select **Save**. For example, you have your stock levels in the **stock** attribute, and you want to set your **availability** attribute to *in stock* or *out of stock* based on the stock level. UUID-510dc098-5211-d0ce-3644-099504e9d782

UUID-510dc098-5211-d0ce-3644-099504e9d782

You add the **Set Availability by Stock** rule box to the **availability** attribute to let it change your current values in the following way: | **stock** (no changes) | **availability** (before) | **availability** (after) | | ---------------------- | ------------------------- | ------------------------ | | *45* | *available* | `in stock` | | *0* | *no longer available* | `out of stock` | | *2* | *last items left* | `in stock` | Set Condition [#set-condition] Google accepts the following values for the **condition** attribute: * *new* * *refurbished* * *used* With the **Set Condition** rule box, you can replace your current values with one of the valid conditions accepted by Google: Take the steps from [Add a rule box](/docs/help-center/add-a-rule-box) to add the **Set Condition** rule box. UUID-8a6968bc-6fb0-24e6-55f7-6dcb4172c394

UUID-8a6968bc-6fb0-24e6-55f7-6dcb4172c394

Select the relevant condition type from the drop-down menu. Select **Save**. For example, you have varying non-valid values in the **condition** attribute, and you want to change them all to the valid value *new*: | **condition** (before) | **condition** (after) | | ---------------------- | --------------------- | | *good as new* | `new` | | *signs of use* | `new` | | *new* | `new` | Set Condition by Regex [#set-condition-by-regex] Google accepts the following values for the **condition** attribute: * *new* * *refurbished* * *used* With the **Set Condition by Regex** rule box, you can use regular expressions to search your current values for matches and replace them with corresponding valid conditions accepted by Google. Once the **Set Condition by Regex** rule box finds a regex match in a value, it changes the entire current value to the corresponding value accepted by Google. If one value contains multiple regex matches related to different condition types, the rule box assigns the condition type related to the first regex match within the value. If the rule box doesn't find a regex match in a value, it assigns the value `new` to make sure your **condition** attribute contains only valid entries. Take the steps from [Add a rule box](/docs/help-center/add-a-rule-box) to add the **Set Condition by Regex** rule box. UUID-2fcf4179-be09-516d-20b2-f78224b71e89

UUID-2fcf4179-be09-516d-20b2-f78224b71e89

In **New**, **Used**, and **Refurbished**, enter regular expressions to search your values and replace the matching parts with a relevant condition value. Use the *Regex generator* by selecting **>\_** to get a regex suggestion. Select **Save**. For example, you have different non-valid values in the **condition** attribute, and you need to assign a valid condition type to each product based on its current value. UUID-f6ea2b4b-2add-607f-dcc3-cd396a2549c8

UUID-f6ea2b4b-2add-607f-dcc3-cd396a2549c8

With the regular expressions `/(from manufacturer|packaged|new)/`, `/(use|used)/`, and `/(refurbished|repaired|returned)/`, you can search your current values for the possible variants of the valid *new*, *used*, and *refurbished* values and then change the current values to the appropriate valid conditions. | **condition** (before) | **condition** (after) | | ---------------------- | --------------------- | | *returned, new* | `new` | | *signs of use* | `used` | | *brand new* | `new` | Set Expiration Date [#set-expiration-date] With the **Set Expiration Date** rule box, you can add an expiration date to the **expiration\_date** attribute as accepted by Google. In this rule box, you set the number of days left until the expiration date of an offer, and the rule box adds the corresponding date in the *YYYY-MM-DD* format to every product in the attribute. Take the steps from [Add a rule box](/docs/help-center/add-a-rule-box) to add the **Set Expiration Date** rule box. UUID-37056ad8-08af-4316-cf66-b76fe83076f7

UUID-37056ad8-08af-4316-cf66-b76fe83076f7

In **Days to expire**, enter the number of days left until the offer or product expires. You can enter no more than 31 days in the Set Expiration Date rule box starting from today. If you add 32 days or more, it results in an empty value. Select **Save**. For example, you have varying non-valid date formats in the **expiration\_date** attribute, with all your products expiring at the same time (in 8 days). You can change all your expiration dates to the valid date format by entering `8` in **Days to expire**. | **expiration\_date** (before) | **expiration\_date** (after) | | ----------------------------- | ---------------------------- | | *July 9, 2024* | `2024-07-09` | | *09.07.2024* | `2024-07-09` | | *07/09/2024* | `2024-07-09` | Set Gender [#set-gender] Google accepts the following values for the **gender** attribute: * *unisex* * *female* * *male* With the **Set Gender** rule box, you can replace your current values with one of the valid gender options accepted by Google: Take the steps from [Add a rule box](/docs/help-center/add-a-rule-box) to add the **Set Gender** rule box. UUID-2e6889d5-ca4e-5277-c225-c1f190f44788

UUID-2e6889d5-ca4e-5277-c225-c1f190f44788

Select the relevant gender option from the drop-down menu. Select **Save**. For example, you have varying non-valid values in the **gender** attribute, and you want to change them all to the valid value *unisex*: | **gender** (before) | **gender** (after) | | ------------------- | ------------------ | | *men, women* | `unisex` | | *all* | `unisex` | | *women, men* | `unisex` | Set Gender by Regex [#set-gender-by-regex] Google accepts the following values for the **gender** attribute: * *unisex* * *female* * *male* With the **Set Gender by Regex** rule box, you can use regular expressions to search your current values for matches and replace them with corresponding valid gender options accepted by Google. You need to provide regex only for *male* and *female* gender options. Products with no matches of these regular expressions get the value *unisex*. Once the **Set Gender by Regex** rule box finds a regex match in a value, it changes the entire current value to the corresponding value accepted by Google. If one value contains multiple regex matches related to different gender options, the rule box assigns the gender option related to the first regex match within the value. Take the steps from [Add a rule box](/docs/help-center/add-a-rule-box) to add the **Set Gender by Regex** rule box. UUID-2b456d92-8247-aefc-3827-aa03c011381b

UUID-2b456d92-8247-aefc-3827-aa03c011381b

In **Male regex** and **Female regex**, enter regular expressions to search your values and replace the matching parts with a relevant gender option. Use the *Regex generator* by selecting **>\_** to get a regex suggestion. Select **Save**. For example, you have different non-valid values in the **gender** attribute, and you need to assign a valid gender option to each product based on its current value. UUID-21962417-b03c-608c-d6ae-1927afe88673

UUID-21962417-b03c-608c-d6ae-1927afe88673

With the regular expressions `/\b(?:women|female|F)\b/` and `/\b(?:men|male|M)\b/`, you can search your current values for the possible variants of the valid *female* and *male* values and then change the current values to the appropriate valid gender option. The products that don't contain regex matches get the value *unisex*. | **gender** (before) | **gender** (after) | | ------------------- | ------------------ | | *women* | `female` | | *men and women* | `male` | | *M* | `male` | | *all* | `unisex` | Set Identifier Exists [#set-identifier-exists] Google uses the **identifier\_exists** attribute to see whether unique product identifiers (UPIs) are available for your product based on the values in the **brand**, **gtin**, **mpn**, and **category** attributes. See [Identifier exists](https://support.google.com/merchants/answer/6324478?hl=en#zippy=%2Cproducts-without-gtins-mpns-brands) for more information. With the **Set Identifier Exists** rule box, you can add the valid *true* or *false* values to your **identifier\_exists** attribute based on the contents of your **category** value. If an identifier (a brand, MPN, or GTIN) exists for a product, the **identifier\_exists** attribute stays empty, which equals *true* when exporting it to Google Merchant Center. If there is no identifier for a product, the attribute has the value *false*. Take the steps from [Add a rule box](/docs/help-center/add-a-rule-box) to add the **Set Identifier Exists** rule box. UUID-20483046-a56e-a622-9846-83896e0acf09

UUID-20483046-a56e-a622-9846-83896e0acf09

Select your category attribute from the drop-down menu. This menu shows the attributes of the previous stage. Select **Save**. Set Size System [#set-size-system] Google accepts the following values for the **size\_system** attribute: * *US* * *UK* * *EU* * *DE* * *FR* * *JP* * *CN* * *IT* * *BR* * *MEX* * *AU* With the **Set Size System** rule box, you can replace your current values with one of the valid size system options accepted by Google. Take the steps from [Add a rule box](/docs/help-center/add-a-rule-box) to add the **Set Size System** rule box. UUID-97c9be59-d4a9-99e6-b9e3-232fb57ab776

UUID-97c9be59-d4a9-99e6-b9e3-232fb57ab776

Select the relevant size system from the drop-down menu. Select **Save**. For example, you have varying non-valid values in the **size\_system** attribute, and you want to change them all to the valid value *UK*: | **size\_system** (before) | **size\_system** (after) | | ------------------------- | ------------------------ | | *United Kingdom* | `UK` | | *UK* | `UK` | | *Britain* | `UK` | Set Size Type [#set-size-type] Google accepts the following values for the **size\_type** attribute: * *regular* * *petite* * *plus* * *big* * *tall* * *maternity* With the **Set Size Type** rule box, you can replace your current values with one of the valid size types accepted by Google. Take the steps from [Add a rule box](/docs/help-center/add-a-rule-box) to add the **Set Size Type** rule box. UUID-0478d8b8-c0a0-365b-84dd-427642d9e664

UUID-0478d8b8-c0a0-365b-84dd-427642d9e664

Select the relevant size type from the drop-down menu. Select **Save**. For example, you have varying non-valid values in the **size\_type** attribute, and you want to change them all to the valid value *regular*: | **size\_type** (before) | **size\_type** (after) | | ----------------------- | ---------------------- | | *regular fit* | `regular` | | *usual* | `regular` | | \[empty] | `regular` | Set Size Type by Regex [#set-size-type-by-regex] Google accepts the following values for the **size\_type** attribute: * *regular* * *petite* * *plus* * *big* * *tall* * *maternity* With the **Set Size Type by Regex** rule box, you can use regular expressions to search your current values for matches and replace them with corresponding valid size types accepted by Google. Once the **Set Size Type by Regex** rule box finds a regex match in a value, it changes the entire current value to the corresponding value accepted by Google. If one value contains multiple regex matches related to different size types, the rule box assigns the size type related to the first regex match within the value. If the rule box doesn't find a regex match in a value, it assigns the value `regular` to make sure your **size\_type** attribute contains only valid entries. Take the steps from [Add a rule box](/docs/help-center/add-a-rule-box) to add the **Set Size Type by Regex** rule box. UUID-8c3dd378-da2c-5922-d419-cc2e75c24640

UUID-8c3dd378-da2c-5922-d419-cc2e75c24640

In **Regular**, **Petite**, **Plus**, and **Maternity**, enter regular expressions to search your values and replace the matching parts with a relevant size type. Use the *Regex generator* by selecting **>\_** to get a regex suggestion. Select **Save**. For example, you have different non-valid values in the **size\_type** attribute, and you need to assign a valid size type to each product based on its current value. UUID-f8625106-73e4-b712-8fcf-e1afa65b8ead

UUID-f8625106-73e4-b712-8fcf-e1afa65b8ead

With the regular expressions `/(regular|reg|usual)/`, `/(petite|smaller)/`, `/(plus|bigger)/`, and `/(maternity)/`, you can search your current values for the possible variants of these valid size types and then change the current values to the appropriate valid size types. | **size\_type** (before) | **size\_type** (after) | | ----------------------- | ---------------------- | | *one size* | `regular` | | *maternity clothes* | `maternity` | | *petite, regular* | `regular` | Split String for PLA [#split-string-for-pla] See [Change string length](/docs/help-center/add-a-rule-box/find-the-needed-rule-box-category/change-string-length#section-idm232221351802675) for more information on split string rule boxes. The **Split String for PLA** rule box uses delimiters and analyzes the values of an attribute to extract and save only those parts of the values you need. If the rule box finds no delimiter in a value, it empties the value to prevent you from sending incorrect data to your export channels. Take the steps from [Add a rule box](/docs/help-center/add-a-rule-box) to add the **Split String for PLA** rule box. UUID-e21eff4c-924c-4bb7-0f0c-9fa69e4d4ce7

Enter the delimiter character that splits your string into multiple data points in **Splitter**. The platform never displays the splitter in the output if you extract only one data point from the value. To see the splitter in the output value, you need to extract at least two data points. In **From**, enter the number of the data point from which the platform should start extracting information. The expected input format for this field is a digit.See [this numbering example](/docs/help-center/add-a-rule-box/find-the-needed-rule-box-category/change-string-length#informaltable-idm243305572252982) to identify the number of your desired data point. If you enter `0` in **From**, the platform starts extracting information from your first data point and, after finding no splitter character in the string, returns the entire string as if it consisted of one data point only.To have the Split String for PLA rule box empty the values that contain no splitter characters, specify any number in **From** but for `0` and negative numbers. Enter how many data points you want the platform to extract from your values in **Items**.The expected input format for this field is a digit. Only positive numbers are acceptable. If you leave **Items** empty, the platform extracts all data points of the string, starting with the data point specified in **From**. Select **Save**. Google accepts the following values for the **gender** attribute: | Rule box and setup | **category** (before) | **category** (after) | | ---------------------------------------------------------------------------------------- | ----------------------------------------------------------------- | ----------------------------- | | UUID-30a50b3a-04fb-3872-9c57-da7960601f4a

| *Animals & Pet Supplies > Pet Supplies > Dog Supplies > Dog Beds* | `Pet Supplies > Dog Supplies` | | *Apparel & Accessories > Clothing > Activewear* | `Clothing > Activewear` | | | *Arts & Entertainment --- Event Tickets* | | | See [Split String](/docs/help-center/add-a-rule-box/find-the-needed-rule-box-category/change-string-length#section-idm4613280768827233045222567009) for more information. Translate Google Category [#translate-google-category] Google accepts only a predefined list of values in the **category** attribute. You can use a *Partner Taxonomy Mapping* list to ensure your **category** attribute contains values accepted by Google. See [Replace attributes with Partner Taxonomy Mapping list](/docs/help-center/map-and-optimize-your-data/lists/replace-attributes-with-partner-taxonomy-mapping-list) for more information. With the **Translate Google Category** rule box, you can translate your Google categories from one language to another. You can also change your Google categories in any language to the associated category IDs, which are the same for all languages. The rule box empties the values in those products that contain invalid categories. Take the steps from [Add a rule box](/docs/help-center/add-a-rule-box) to add the **Translate Google Category** rule box. UUID-032b21ed-f260-b5ca-c653-bb858d62d9fb

UUID-032b21ed-f260-b5ca-c653-bb858d62d9fb

In **Source Format**, select the current language and country of your Google categories.Choose *id* if your category attribute contains category IDs instead of spelled-out category names. In **Target Format**, select the language and country you want to translate your Google categories into.Choose *id* if you want to transform your spelled-out category names into category IDs. You can remove all invalid categories from your category attribute without translating them by selecting the same languages in **Source Format** and **Target Format**. Select **Save**. For example, your **category** attribute contains valid Google categories for the US in English, and you need to translate them into valid Google categories in German. | **category** (before) | **category** (after) | | ------------------------------------------------------- | ----------------------------------------------------------------- | | *Apparel & Accessories > Shoe Accessories > Slippers* | \[empty] | | *Home & Garden > Linens & Bedding > Bedding > Blankets* | `Heim & Garten > Bett- und Haushaltswäsche > Bettwäsche > Decken` | | *Apparel & Accessories > Clothing > Underwear & Socks* | `Bekleidung & Accessoires > Bekleidung > Unterwäsche & Socken` | If you select *id* in **Target Format** for the same use case, the rule box outputs the following: | **category** (before) | **category** (after) | | ------------------------------------------------------- | -------------------- | | *Apparel & Accessories > Shoe Accessories > Slippers* | | | *Home & Garden > Linens & Bedding > Bedding > Blankets* | `1985` | | *Apparel & Accessories > Clothing > Underwear & Socks* | `213` | # Add icons and clipart to your image template import { Callout } from "fumadocs-ui/components/callout"; import { Step, Steps } from "fumadocs-ui/components/steps"; Introduction [#introduction] In Image Designer, you can add different elements to your existing product images and enhance the design of your image templates with an extensive collection of icons and clipart. Add an icon [#add-an-icon] Go to **Designer** from your site's main menu. Select the **Insert** tab. Open the **Icon Font** section. UUID-32a12029-2121-bc66-a9e1-7fe67928b131

UUID-32a12029-2121-bc66-a9e1-7fe67928b131

Drag a selected icon into the image preview area. Customize the corresponding icon layer in the *Layers* tab as desired. See [Icon layer settings](#section-idm4508754744604833635044576811). Select the floppy disk icon in the upper toolbar to save the changes. Icon layer settings [#icon-layer-settings] The Image Designer adds icons as *Icon* layers in the Layers tab. You can edit the icon with the following settings: * **X** and **Y**: Set icon coordinates to place your icon on the template. You can also drag the layer in the image preview area to achieve the same result. * **width**: Define the width of the output icon. * **height**: Define the height of the output icon. * **Rotation (deg)**: Define the rotation degree of the output icon. * **Stroke color**: Choose the color of the icon borders in the color picker. * **Stroke width**: Define the width of the icon borders. * **Transparency**: Select the transparency of the icon borders on a scale from 0% to 100%, where 0% means no transparency and 100% means fully transparent icon borders. * **Font color**: Define the icon color in the color picker. * **Font size**: Define the icon size in pixels. * **Font Transparency**: Select the icon transparency on a scale from 0% to 100%, where 0% means no transparency and 100% means a fully transparent icon. * **Horizontal alignment**: Choose the type of horizontal alignment. * **Vertical alignment**: Choose the type of vertical alignment. * **Render background**: Add a background color to the whole icon layer. * **Partial background**: Add a background color to the inserted icon only. * **Text Shadow**: Add a shadow to your icon. UUID-f8a4df7c-a617-f1e7-abea-08ddb3b8d1f6

UUID-f8a4df7c-a617-f1e7-abea-08ddb3b8d1f6

Add a clipart [#add-a-clipart] Go to **Designer** from your site's main menu. Select the **Insert** tab. Open the **Clipart** section. UUID-b331e8ab-ff76-f0e3-2312-c9fdda5ae041

UUID-b331e8ab-ff76-f0e3-2312-c9fdda5ae041

Drag a selected clipart element into the image preview area. Customize the corresponding image layer in the *Layers* tab as desired. See [Clipart layer settings](#section-idm232335342469844). Select the floppy disk icon in the upper toolbar to save your template. Clipart layer settings [#clipart-layer-settings] The Image Designer adds clipart elements as *Image* layers in the Layers tab. You can edit the clipart with the following settings: * **X** and **Y**: Set image coordinates to place your clipart on the template. You can also drag the layer in the image preview area to achieve the same result. * **width**: Define the width of the output image. * **height**: Define the height of the output image. * **Transparency**: Change the transparency of the clipart image on a scale from 0% to 100%, where 0% means no transparency and 100% means a fully transparent clipart image. * **Rotation (deg)**: Define the rotation degree of the output image. * **Crop Mode**: Cut off the sides, top, and bottom of the image. * **Slicing**: Activate **Slicing** to cut the image and then confirm the slicing. * **Source**: Insert an URL of the additional image from outside your feed. To change the URL, select the **Change URL** button and enter a new image URL. * **Reset filters**: Reset all your filter settings for a layer. * **brightness**: Increase the image brightness. * **hue**: Change the image coloring. * **grayscale**: Convert your image to black and white. * **invert**: Invert the colors by moving the slider to the right. * **contrast**: Increase the image shades. * **saturate**: Increase the image saturation. * **sepia**: Add a sepia filter to the image. * **blur**: Blur the image. UUID-89c90afa-d633-9fc1-cf25-4503291f6ddd

UUID-89c90afa-d633-9fc1-cf25-4503291f6ddd

# Add a rating to your image template import { Callout } from "fumadocs-ui/components/callout"; import { Step, Steps } from "fumadocs-ui/components/steps"; Introduction [#introduction] In Image Designer, you can add a rating to your image template and choose its design and shape, such as stars, concentric circles, a progress bar, and a Tripadvisor-branded rating. Each rating design type has some common and specific settings. Add a rating [#add-a-rating] Go to **Designer** from your site's main menu. Select the **Insert** tab. Open the **Elements** section. Drag the **Rating** element into the image preview area. Customize the rating layer in the *Layers* tab as desired. See [Rating layer settings](#section-idm23233535117954). Select the floppy disk icon in the upper toolbar to save the changes. Rating layer settings [#rating-layer-settings] The Image Designer adds a rating as *Rating* layer in the Layers tab. You can edit the rating layer with the following settings: Common rating settings [#common-rating-settings] All rating design types share the following settings: * **Input**: Select the attribute that contains the rating for products. If the attribute has an ex (**✘**) before its name, the product you are currently editing in Image Designer has an empty value in that attribute.If the attribute has a checkmark (**✔**) before its name, the product has a relevant value in the attribute. UUID-efdd5efd-7b8e-7710-2fb0-972145dcae27

UUID-efdd5efd-7b8e-7710-2fb0-972145dcae27

* **Rating type**: Select the type of rating you want to use. * **Default value**: Enter the default static value for the rating score if needed. * **X** and **Y**: Set rating area coordinates to place your rating on the image template. You can also drag the layer in the image preview area to achieve the same result. * **width**: Define the width of the entire rating area. * **height**: Define the height of the entire rating area. * **Stroke color**: Choose the color of the rating symbols' borders in the color picker. * **Stroke width**: Define the width of the rating symbols' borders. * **Transparency**: Select the transparency of the rating symbols' borders on a scale from 0% to 100%, where 0% means no transparency and 100% means fully transparent borders. Star rating settings [#star-rating-settings] The star rating has all common settings and the following additional ones: * **Full star color**: Define the color for the inner part of the full rating symbol. * **Transparency**: Select the transparency for the inner part of the full rating symbol on a scale from 0% to 100%, where 0% means no transparency and 100% means a fully transparent rating symbol. * **Empty star color**: Define the color of the empty rating symbols. * **Transparency**: Select the transparency of the empty rating symbols on a scale from 0% to 100%, where 0% means no transparency and 100% means a fully transparent empty rating symbol. * **Don't fill empty**: Check this box to make empty stars transparent. * **Inner Radius**: Define the radius if you want the rating area to be angled. Concentric circles rating settings [#concentric-circles-rating-settings] The concentric circles rating consists of the outer and inner circles and has all common settings and the following additional ones: * **Fill**: Define the color for the inner part of the full rating symbols. * **Don't fill**: Check this box to make empty circles transparent. * **Transparency**: Select the transparency for the inner part of the full rating symbols on a scale from 0% to 100%, where 0% means no transparency and 100% means a fully transparent rating symbol. * **Inner margin**: Define the size of the inner circles. * **Spacing**: Define the distance between the circles. * **Rotation (deg**): Define the rotation degree of the rating area. Progress bar rating settings [#progress-bar-rating-settings] * **Fill**: Define the color of the inner or outer bar part. * **Don't fill**: Check this box to make the empty bar part transparent. * **Transparency**: Select the transparency of the inner or outer progress bar rating on a scale from 0% to 100%, where 0% means no transparency and 100% means a fully transparent progress bar. * **Inner margin**: Define the size of the inner circles. * **Rotation (deg)**: Define the rotation degree of the rating area. Tripadvisor rating settings [#tripadvisor-rating-settings] The Tripadvisor rating has the following settings: * **Input**: Select the attribute that contains the rating for products. If the attribute has an ex (**✘**) before its name, the product you are currently editing in Image Designer has an empty value in that attribute.If the attribute has a checkmark (**✔**) before its name, the product has a relevant value in the attribute. UUID-efdd5efd-7b8e-7710-2fb0-972145dcae27

* **Default value**: Enter the default static value for the rating score. * **X** and **Y**: Set the rating area coordinates to place your rating on the template. You can also drag the layer in the image preview area to achieve the same result. * **width**: Define the width of the rating area. * **height**: Define the height of the rating area. # Add a rectangular element to your image template import { Step, Steps } from "fumadocs-ui/components/steps"; Introduction [#introduction] In Image Designer, you can add a rectangular element to your image template as a background for text or other design elements. Add a rectangular [#add-a-rectangular] Go to **Designer** from your site's main menu. Select the **Insert** tab. Open the **Elements** section. Drag the **Rect** element into the image preview area. Customize the corresponding Rect layer in the *Layers* tab as desired. See [Rect layer settings](#section-idm232335338592873). Select the floppy disk icon in the upper toolbar to save the changes. Rect layer settings [#rect-layer-settings] The Image Designer adds rectangular elements as *Rect* layers in the Layers tab. You can edit the Rect layer with the following settings: * **X** and **Y**: Set the element's coordinates to place your rectangular on the image template. You can also drag the layer in the image preview area to achieve the same result. * **width**: Define the width of the rectangular. * **height**: Define the height of the rectangular. * **Fill color**: Choose the color of the internal part of the rectangular in the color picker. * **Fill transparency**: Change the transparency of the rectangular on a scale from 0% to 100%, where 0% means no transparency and 100% means a fully transparent rectangular. * **Stroke color**: Choose the color of the borders of the rectangular element in the color picker. * **Stroke width**: Choose the width of the borders of the rectangular element. * **Transparency**: Change the transparency of the borders on a scale from 0% to 100%, where 0% means no transparency and 100% means fully transparent borders. * **Radius X** and **Radius Y**: Round the angles of the rectangular. * **Rotation (deg)**: Define the rotation degree of the rectangular. UUID-1c98f507-6bee-df81-ca24-a8998ea226fc

UUID-1c98f507-6bee-df81-ca24-a8998ea226fc

# Image Designer interface & overview import { Callout } from "fumadocs-ui/components/callout"; import { Step, Steps } from "fumadocs-ui/components/steps"; How to navigate and access Image Designer [#how-to-navigate-and-access-image-designer] Please loging into the Productsup platform. Next, please do: Go to a desired Site in your Organization. Open the site's main menu on the left. Access **Image Designer**.

Image Designer interface [#image-designer-interface] Image Designer consists of: * Toolbar * Image preview * Editing tabs

Toolbar [#toolbar] The Image Designer toolbar buttons allow you perform the following:

* The **Preview Product** arrows take you to the next or the previous product in your feed. Use it to preview how the designs apply to the images. * The **Search by** allows you find a specific product in the feed and preview the design instanteniously. You might want to search by SKU, ID, GTIN/EAN code, or even a Title, Theme, Product Line - the search is flexible, it will return all the matching products, and you can use the Preview Product arrows again to view all the images and decide if you are happy with the design. * The zoom-in (**+**) and zoom-out (**-**) buttons let you increase or decrease the image preview size. * The **"Eye" icon** lets you show or hide elements that are out of the design template frames. * The **Copy and Paste icons** let you copy and insert a selected layer. * The **Save**, **Undo** and **Redo** buttons perform the respective actions. Revert & repeat actions apply to your last actions, and you can choose a specific action from the drop-down menu. Image preview [#image-preview] The area below the toolbar displays a selected product image and all the applied layers. You can move, resize, and rotate the layers over the image as desired. Image Designer lets you preview only the first 50 images of your feed. If you fish to preview a specific product, please use **Search by** feature in the Toolbar. Editing tabs [#editing-tabs] On the right side of the Toolbar, you can find four (4) Editing tabs: Editing tabs in Image Designer

. **Layers** is a list of transparent sheets that lets you edit separate design elements. See [Layers tab](#section-idm4582673833624033646784373035) for more details. . **Insert** represents different sets of elements - such as text, images, shapes, clipart, and icons, and the image uploader. All of these you can embed into an image template. See [Insert tab](#section-idm46014041341712336467936016) for more details. . **Templates** is a collection of the default templates offered by the Productsup platform and your custom templates. See [Templates tab](#section-idm4542019716217633646814511053) for more details. . **Settings** for the entire template. See [Settings tab](#section-idm4542019719320033646859333642) for more details. Layers tab [#layers-tab] Layers are the first tab in the Image Designer. Layers are transparent sheets that let you edit separate design elements. Every new element you add to the template in Image Designer appears as a separate layer. Actions with Layers [#actions-with-layers] You can perform the following actions with layers: * Change a layer position in the list by dragging and dropping it with the help of the left handle. Re-position layer in Image Designer

* Rename layers with the "pen" icon. * Link and move several layers simultaneously. To do so, select the link icon for each necessary layer. * Hide a layer with the "eye" icon to reveal the layer beneath it. * Delete a layer with the "bin" icon. Actions with layers

Layer types [#layer-types] Image Designer creates the following layer types when dragging elements from the *Insert* tab to the image template preview area. Each layer type has its specific settings. * **Rect**, or Rectangular is a layer for the *Rect* element from *Elements*. * **Text** is a layer for the *Text* element from *Elements*. * **DynamicText** is a layer for the *Dynamic Text* element from *Elements* or a clipart item from *Clipart*. * **Image** is a layer for the *Image from URL* element from *Elements*. * **DynamicImage** is a layer for the *Dynamic Image* element from *Elements*. * **CustomImage** is a layer for images uploaded in *Your Custom Images*. * **Icon** is a layer for an icon selected from *Icons*. * **Rating** is a layer for the *Rating* element from *Elements*. Insert tab [#insert-tab] Insert is the second tab in the Image Designer. Insert lets you add shapes, descriptions, graphical elements, clipart, and icons or upload custom images. You can drag and drop a necessary element to the preview area. Each added element creates an individual layer in the Layers tab, where you can edit it. The Insert tab consists of the following sections:

* **Elements** is a set of graphic elements, texts, and custom images. * **Clipart** is a set of clipart images. * **Icon Font** is a set of icons. * **Your Custom Images** is a tool for uploading and saving images in a library. Templates tab [#templates-tab] Templates is the third tab in the Image Designer. It consists of two sections: * **Global Templates** - a set of default image templates offered as an example by Productsup. It might be easier to start up with selecting pre-saved Global templates, edit those, and later save them as your custom templates. * **Your Templates** is a list of your custom image templates. You can edit, rename, or delete your custom templates, copy them to another Site, or share them over the Projects or for the entire Organization. You can also switch between the All, Intermidiate level, or Export level templates here. Templates tab

Settings tab [#settings-tab] Settings is the fourth tab in the Image Designer. They apply to your entire active design template: . Select the **Stage the template will be implemented on** in Productsup: * choose **Intermediate Level** to make import-stage columns available for your template's dynamic text and image layers; * choose **Export Level** to make intermediate-stage columns available for your template's dynamic text and image layers. Stage setting

. Add a **Grid** to align elements in the preview. You can select the variants: `None`, `10`, and `60`. The grid appears only during editing and doesn't appear on the final image. Grid 60 setting applied in the Image Designer

Grid 60 setting applied in the Image Designer

. Change the **Canvas** settings - choose the Background as HEX or RGB code or the Template size to ensure the format meets the requirements of the export channel. The **Template Size** drop-down shows pre-defined template types and sizes in pixels. Canvas setting in the Image Designer

. Apply **SVG filters** to all the layers simultaneously: * **Reset filters** resets all your filter settings for a layer. * **Brightness** increases the image brightness. * **Hue** changes the image coloring. * **Grayscale** converts your image to black and white. * **Invert** inverts the colors. * **Contrast** increases the image shades. * **Saturate** increases the image saturation. * **Sepia** adds the sepia filter to the image. * **Blur** softens the image. SVG filters applied in the Image Designer

SVG filters applied in the Image Designer

# Add static or dynamic text to your image template import { Callout } from "fumadocs-ui/components/callout"; import { Step, Steps } from "fumadocs-ui/components/steps"; Introduction [#introduction] In Image Designer, you can add static or dynamic text to your image template. Dynamic text is the value that the platform takes from an assigned column in your feed. Add a static text [#add-a-static-text] Go to **Designer** from your site's main menu. Select the **Insert** tab. Open the **Elements** section. Drag the **Text** element from the *Elements* section to the image preview area. Customize the corresponding Text layer in the *Layers* tab as desired. See [Static text layer settings](#section-idm353363502702036). Select the floppy disk icon in the upper toolbar to save your template. Add a dynamic text [#add-a-dynamic-text] Go to **Designer** from your site's main menu. Select the **Insert** tab. Open the **Elements** section. Drag the **Dynamic Text** element into the image preview area. Customize the corresponding DynamicText layer in the *Layers* tab as desired. See [Dynamic Text layer settings](#section-idm232335350868781). Select the floppy disk icon in the upper toolbar to save changes. Text settings [#text-settings] Static text layer settings [#static-text-layer-settings] The Image Designer adds a static text as *Text* layer in the Layers tab. You can edit the static text with the following settings: * **X** and **Y**: Set text area coordinates to place your text on the image template. You can also drag the layer in the image preview area to achieve the same result. * **width**: Define the width of the text. * **height**: Define the height of the text. * **Rotation (deg)**: Define the rotation degree of the text. * **Stroke color**: Choose the color of the text borders in the color picker. * **Stroke width**: Define the width of the text borders. * **Transparency**: Select the transparency of the text borders on a scale from 0% to 100%, where 0% means no transparency and 100% means fully transparent text borders. * **Font color**: Define the text color in the color picker. * **Font size**: Define the text size in pixels. * **Font Transparency**: Select the transparency of the text on a scale from 0% to 100%, where 0% means no transparency and 100% means fully transparent text. * **Line height (px)**: Define the line height in pixels. * **Text**: Add the static text. * **Superscript currency symbol and fractional** checkbox lets you superscript the currency symbol preceding the price and the fractional part of the price. You can use it only for the price attributes. * **Font family**: Choose between 800 different fonts from the [Google Fonts project](https://fonts.google.com/) or [Add custom text fonts](#section-idm4589732831417634241544667666). * **Font decorations**: Define the font decorations such as bold, italics, underline, or strikethrough. * The strikethrough font decoration applies to the entire value rather than a part of it, such as *"This is value"*. * **Horizontal alignment**: Choose the type of horizontal alignment. * **Vertical alignment**: Choose the type of vertical alignment. * **Word Spacing (px)**: Change the spacing between the words by filling in the number of pixels. * **Character Spacing (px)**: Change the spacing between the characters by filling in the number of pixels. * **Render background**: Add a background color to the whole text area. * **Partial background**: Add a background color to the inserted text only. * **Text Shadow**: Add a shadow to your text. UUID-cb7d5ece-e5b8-3dac-299c-4dc7e8f56a32

UUID-cb7d5ece-e5b8-3dac-299c-4dc7e8f56a32

Dynamic Text layer settings [#dynamic-text-layer-settings] The Image Designer adds a dynamic text as *DynamicText* layer in the Layers tab. You can edit the dynamic text with the following settings: * **Input**: Select the attribute that contains the value you want to use as dynamic text. If the attribute has an ex (**✘**) before its name, the product you are currently editing in Image Designer has no value in that attribute. If you choose an attribute with an empty value, Image Designer displays the warning text `DYNAMIC TEXT - NO VALUE IN SELECTED COLUMN` in the product's image preview. However, if you send an image with an empty value to an export channel, the platform removes the warning text and displays a blank value instead.If the attribute has a checkmark (**✔**) before its name, the product has a relevant value in the attribute. UUID-efdd5efd-7b8e-7710-2fb0-972145dcae27

* **Max length**: Define the max length of the text. * **X** and **Y**: Set text area coordinates to place your text on the template. You can also drag the layer in the image preview area to achieve the same result. * **width**: Define the width of the text. * **height**: Define the height of the text. * **Rotation (deg)**: Define the rotation degree of the text area. * **Color**: Choose the color of the text. * **Stroke color**: Choose the color of the text borders in the color picker. * **Stroke width**: Define the width of the text borders. * **Transparency**: Select the transparency of the text borders on a scale from 0% to 100%, where 0% means no transparency and 100% means fully transparent text borders. * **Font color**: Define the text color in the color picker. * **Font size**: Define the text size in pixels. * **Font Transparency**: Select the transparency of the text on a scale from 0% to 100%, where 0% means no transparency and 100% means fully transparent text. * **Line height (px)**: Define the line height in pixels. * **Superscript currency symbol and fractional** checkbox lets you superscript the currency symbol preceding the price and the fractional part of the price. You can use it only for the price attributes. * **Font family**: Choose between 800 different fonts from the [Google Fonts project](https://fonts.google.com/) or [Add custom text fonts](#section-idm4589732831417634241544667666). * **Font decorations**: Define the font decorations such as bold, italics, underline, or strikethrough. * The strikethrough font decoration applies to the entire value rather than a part of it, such as *"This is value"*. * **Horizontal alignment**: Choose the type of horizontal alignment. * **Vertical alignment**: Choose the type of vertical alignment. * **Multiline**: Activate this button to write text in more than one row. * **Word Spacing (px)**: Change the spacing between the words by filling in the number of pixels. * **Character Spacing (px)**: Change the spacing between the characters by filling in the number of pixels. * **Render background**: Add a background color to the whole text area. * **Partial background**: Add a background color to the inserted text area. * **Text Shadow**: Add a shadow to your text. UUID-17ac5ecc-6805-66cc-dd02-d19d8d8a5149

UUID-17ac5ecc-6805-66cc-dd02-d19d8d8a5149

Add custom text fonts [#add-custom-text-fonts] You can add custom text fonts used by your brand to make consistent design of your images. The font files you wish to upload must be one of the supported formats: *.otf*, *.woff*, or *.woff2*. To add custom fonts for texts in Image Designer: Add static or dynamic text as described in [Add a static text](#section-idm4542019718984033646934368685) or [Add a dynamic text](#section-idm4582677451142433646935232175). In **Layers** in the right panel, select the **Font family** drop-down menu. Scroll down in the menu and select **More Fonts**. UUID-87778bfd-85af-6b07-2fde-f77192f99b7c

UUID-87778bfd-85af-6b07-2fde-f77192f99b7c

In the **Font Selector** pop-up window, select **Add custom font**. UUID-f388ace4-0b61-ea06-df53-a6de15c73e2c

Drag and drop the font files to the upload area or select the highlighted area to choose a file from your computer. Select **OK**. UUID-36a9b5e3-f744-30df-5c65-0bf290332e8f

UUID-36a9b5e3-f744-30df-5c65-0bf290332e8f

For each uploaded font, in **Font Name**, enter a font name that should include the font variant, such as `Roboto regular` or `Arial italic`. Accurate labeling helps you distinguish among the added fonts. UUID-826ddc18-75c1-fd4f-808f-e376515ee76f

UUID-826ddc18-75c1-fd4f-808f-e376515ee76f

In **Font Variant**, add the corresponding font variant such as `regular`, `bold`, or `italic`. If you leave the field empty, the platform considers the font as regular. Select the terms and conditions checkbox to confirm your right to use and distribute the uploaded fonts in your projects. Select **Add Fonts**. The new fonts are now available for use in your designs. To find and use your custom fonts, in the text layer, select the **Font family** drop-down menu, and select a needed font in **Your Selected Fonts**. # Image Designer import { Callout } from "fumadocs-ui/components/callout"; Introduction [#introduction] Image Designer - editing mode, full page view

Image Designer - editing mode, full page view

Image Designer is a Productsup image-editing application that helps you enhance images in your product feed within the platform. At scale. You can mix several images, overlay the descriptions, add a logo, price, or discount label to your images. Apply the same design template to all the images in your product feed or a certain selection of products. This is controlled by the *Use Image Designer Template* rule box in Dataflow and Data View. Image Designer supports the following image formats: * Input: JPG, JPEG, and PNG. * Output: JPG and PNG. What you can do with Image Designer [#what-you-can-do-with-image-designer] Image Designer helps you edit images in the following ways: * [Create and apply custom image templates](/docs/help-center/map-and-optimize-your-data/image-designer/create-and-apply-custom-image-templates.mdx). * [Add a new image](/docs/help-center/map-and-optimize-your-data/image-designer/add-a-new-image-to-your-image-template). * [Add static or dynamic text](/docs/help-center/map-and-optimize-your-data/image-designer/add-static-or-dynamic-text-to-your-image-template). * [Add icons and clipart images](/docs/help-center/map-and-optimize-your-data/image-designer/add-icons-and-clipart-to-your-template). * [Add product rating/reviews](/docs/help-center/map-and-optimize-your-data/image-designer/add-rating-to-your-template). * [Add a rectangular element](/docs/help-center/map-and-optimize-your-data/image-designer/add-a-rectangular-element-to-your-template). * [Search and preview any product in your feed](/docs/help-center/map-and-optimize-your-data/image-designer/search-for-a-product-in-the-image-designer-preview.mdx). For a walkthrough of the Image Designer application and features, read [Image Designer interface & overview](/docs/help-center/map-and-optimize-your-data/image-designer/interface-image-designer). How to obtain Image Designer access [#how-to-obtain-image-designer-access] Image Designer is an additional service that requires contract amendment. However, you can test it with limited access without activating the full version. In the limited version, you can see and try the same features as in the full version, but apply the template only to a limited number of images. | Full Image Designer | Limited Image Designer | | -------------------------------------------------------------------- | ------------------------------------------------------------------------------ | | Apply the templates to all products in the feed. | Apply the templates only to 50 random products. | | Apply the templates with the rule box *Use Image Designer Template*. | Apply the templates with the rule box *Use Image Designer Template (limited)*. | To activate the full version of Image Designer, reach out to your Customer Success Manager or contact [support@productsup.com](mailto:support@productsup.com). # Create and apply custom image templates import { Callout } from "fumadocs-ui/components/callout"; import { Step, Steps } from "fumadocs-ui/components/steps"; Introduction [#introduction] Productsup provides a collection of pre-designed global templates to let you edit your product images in Image Designer. The global templates are available to all customers. Instead of creating a template from scratch, you can select a needed global template and edit it with the tools of Image Designer. You can choose from the following global templates: * Dynamic Multiple Images * Dynamic Long * Close-Up Material * Side Slant * Sale * Dynamic Three Images * Dynamic * Blank Image * Three (3) Travel templates Create a custom image template [#create-a-custom-image-template] Go to **Designer** from your site's main menu. Select the **Templates** tab. Select a desired template from **Global Templates**. Customize the template in the *Layers*, *Insert*, and *Settings* tabs. Select the floppy disk icon in the upper toolbar to save your custom template. Once created, the template automatically shows up in the *Your Templates* section of the *Templates* tab. By default, your product image preview area shows the first image from your current site feed, and you can preview only one image at a time. Select another product image using the **Preview Product** arrows in the Image Designer toolbar. The preview shows an image placeholder if your feed has no images. Edit your custom templates [#edit-your-custom-templates] Go to **Designer** from your site's main menu. Select the **Templates** tab. Select a desired template from **Your Templates**. UUID-1e4895fc-5cba-6d92-cf41-1280ef24017b

UUID-1e4895fc-5cba-6d92-cf41-1280ef24017b

In the *Your Templates* section, you can do the following actions with your templates: * Rename a template: Go to the **Templates** tab. Scroll down to the *Your Templates* section. Select the pen icon next to the template's default name and enter the desired name. Select the checkmark icon (**✔**) to confirm. Select **Save**. * Delete a template: Go to the **Templates** tab. Scroll down to the *Your Templates* section. Open the drop-down menu of the needed template's area on the right. Select **Delete**. Select **OK** in the pop-up window to confirm your action. * Copy a template to another site: Go to the **Templates** tab. Scroll down to the *Your Templates* section. Open the drop-down menu of the needed template's area on the right and choose **Copy To Another Site**. UUID-73cc549e-8b5d-a4b3-11ed-c924884196ba

UUID-73cc549e-8b5d-a4b3-11ed-c924884196ba

Choose a site in the *Select Site* pop-up and select **OK**. * Make a template available for a project or the entire organization. Go to the **Templates** tab. Scroll down to the *Your Templates* section. Open the drop-down menu of the needed template's area on the right and choose a needed level. UUID-1c1517d3-a573-2292-6e72-d6ac237c1e38

UUID-1c1517d3-a573-2292-6e72-d6ac237c1e38

Apply image templates to your product images [#apply-image-templates-to-your-product-images] To export your edited images to the destination, you need to apply the templates with a rule box: Go to **Data View** from the site's main menu. Select **Edit** in the necessary image column. Select **Add Box** and search for the *Use Image Designer Template* rule box. UUID-d685ec30-1fa5-7ed5-90b8-f88d9104d90f

UUID-d685ec30-1fa5-7ed5-90b8-f88d9104d90f

The limited Image Designer version lets you use only the *Use Image Designer Template (limited)* rule box. With this rule box, you can test the functionality with a limited number of images. Select the needed template from the **Template** drop-down menu. Select **Save**. When you modify images, they go through the Productsup image servers. Each time you change and apply a template, the URL of the exported image changes and starts with `https://gfx.productsup.io/`. # Search and preview any product in the Image Designer import { Callout } from "fumadocs-ui/components/callout"; import { Step, Steps } from "fumadocs-ui/components/steps"; Introduction [#introduction] By default, the Image Designer preview shows the first 50 products of your product feed, and you can move between them with the **Preview Product** arrows. The Product Search feature lets you jump straight to a specific product instead of paging through the list. You can search by **any product attribute**, such as ID, SKU, GTIN, Title, etc - no limitation here. The search is case-insensitive and supports partial values, and the preview navigates to the products that match your query. How to search for a product in the Image Designer preview [#how-to-search-for-a-product-in-the-image-designer-preview] Go to **Designer** from your site's main menu. Select an attribute in the drop-down next to **Search by** in the upper toolbar. For example, `sku`. Enter a full or partial value in the search input and select the magnifying glass icon.

Use the **Preview Product** arrows to move between the matching products. The counter below the arrows shows your position in the search results, for example, `Match 1 of 1`. The preview shows the selected product with all layers of your template, so you can check how the template renders for that exact product before saving it. Clear the search input to return to the default preview of your feed's products. When to use the Product Search [#when-to-use-the-product-search] The product search is useful in the following scenarios: * You run prioritized product campaigns, such as hero SKUs or limited assortments, and need to verify the template on the exact products of the campaign. * Your feed is large or contains duplicates, and the product you want to preview is not among the first products of the feed. * You use your own prioritization logic and want to confirm which product variant the template picks up. # Add a new image to your image template import { Callout } from "fumadocs-ui/components/callout"; import { Step, Steps } from "fumadocs-ui/components/steps"; Introduction [#introduction] In Image Designer, you can apply images over your existing product image using one (1) of the following ways: . Upload a static image file to the platform image library and use it for all templates within the site where you uploaded it. See [Add a static image](#section-idm4631011274931233646918317425). . Add an image via the URL of the storage that contains the image. See [Add an image via the URL](#section-idm4631011230899233646920029781). . Add a dynamic image from a selected column in your feed. See [Add a dynamic image](#section-idm4582677101676833646919969093). Add a static image [#add-a-static-image] You can upload images from your computer and use them for all templates within the site where you uploaded them. You can find all uploaded images in the **Your Custom Images** section of the Insert tab. To add an image: Go to **Designer** from your site's main menu. Open the **Insert** tab. Scroll down to the section **Your Custom Images**. Upload images by dragging them into the upload area or selecting **Or click here to upload**. UUID-ffe9e39c-6e90-8767-00df-b6107464e849

UUID-ffe9e39c-6e90-8767-00df-b6107464e849

To see the uploaded image details, select **Show Upload Details**. Drag the uploaded image to the image preview area. Customize the corresponding custom image layer in the *Layers* tab. See [Set up an image layer](#section-idm4556118247084833685000640929). UUID-476486cd-bc56-69a0-b4d2-6b7a26c2ab27

UUID-476486cd-bc56-69a0-b4d2-6b7a26c2ab27

Select the floppy disk icon in the upper toolbar to save the changes. Add an image via the URL [#add-an-image-via-the-url] You can upload images via the URL of the storage that keeps them. Go to **Designer** from your site's main menu. Open the **Insert** tab. Open the **Elements** section. Drag the **Image from URL** element into the image preview area. Enter the image URL in the pop-up window and select **Add**. Customize the corresponding image layer in the *Layers* tab as desired. See [Set up an image layer](#section-idm4556118247084833685000640929). UUID-89c90afa-d633-9fc1-cf25-4503291f6ddd

Select the floppy disk icon in the upper toolbar to save the changes. Add a dynamic image [#add-a-dynamic-image] You can add an image from a selected column in your feed. Go to **Designer** from your site's main menu. Open the **Insert** tab. Open the **Elements** section. Drag the **Dynamic Image** element into the image preview area. Customize the corresponding Image layer in the Layers tab as desired. See [Set up an image layer](#section-idm4556118247084833685000640929). UUID-a749cfda-9c67-b342-82c6-6efd616bc69a

UUID-a749cfda-9c67-b342-82c6-6efd616bc69a

Select the floppy disk icon in the upper toolbar to save the changes. Set up an image layer [#set-up-an-image-layer] Whenever you add an image to the image template, the platform creates a new layer and gives it a name according to its type and order. To locate a necessary layer, go to the **Layers** tab and select one of the following: * For a static image, select the corresponding layer named such as `CustomImage: Layer-XX`. * For an image added via URL, select the corresponding layer named such as `Image: Layer-XX`. * For a dynamic image, select the corresponding layer named such as `DynamicImage: Layer-XX`. To edit your image layer, set up the following: The settings of all image types are almost the same. The difference is only in the **Input** and **Source** fields. * (For Dynamic Image layer only) **Input**: Select the attribute that contains the value you want to use as a dynamic image. If the attribute has an ex (**✘**) before its name, the product you are currently editing in Image Designer has no image.If the attribute has a checkmark (**✔**) before its name, the product has a relevant image in the attribute. UUID-efdd5efd-7b8e-7710-2fb0-972145dcae27

* **X** and **Y**: Set image coordinates to place your image on the template. You can also drag the layer in the image preview area to achieve the same result. * **width**: Define the width of the image. You can also change the image size right in the image preview area. * **height**: Define the height of the image. You can also change the image size right in the image preview area. * **Transparency**: Set the transparency of the image on a scale from 0% to 100%, where 0% means no transparency and 100% means a fully transparent image. * **Rotation (deg)**: Define the rotation degree of the image. * **Crop Mode**: Cut off the sides, top, and bottom of the image. * **Slicing**: Slice the image into pieces. * **Source**: To change the image, do one (1) of the following actions depending on the image layer type: * For *CustomImage* layers, choose the needed image from the drop-down menu to change an image. * For *Image* layers, select the **Change URL** button and enter the URL of a new image. * **Reset filters**: Reset all your filter settings for this layer. * **brightness**: Increase the image brightness. * **hue**: Change the image coloring. * **grayscale**: Convert your image to black and white. * **invert**: Invert the colors. * **contrast**: Increase the image shades. * **saturate**: Increase the image saturation. * **sepia**: Add a sepia filter to the image. * **blur**: Blur the image. # Advanced rule box options import { Callout } from "fumadocs-ui/components/callout"; import { Step, Steps } from "fumadocs-ui/components/steps"; Introduction [#introduction] While optimizing your product data with the help of rule boxes in Data View or Dataflow, you can apply the following advanced options to rule boxes: * [Pause a rule box](#N1659614411807) * [Delete a rule box](#N1659614423545) * [Duplicate a rule box](#section-idm232219334686326) * [Apply rule boxes to segments](#section-idm4496911623404833190509284293) * [Schedule rule boxes to run at a specific time](#section-idm232219334970168) UUID-82bb89f2-4daf-1585-0a9b-daa4e5ff9418

UUID-82bb89f2-4daf-1585-0a9b-daa4e5ff9418

Also, you can copy and apply rule boxes across multiple sites with the Bulk Option functionality. See [Apply rule boxes in bulk across multiple sites](#section-idm232217535173292) for more information. Pause or delete a rule box [#pause-or-delete-a-rule-box] To terminate the effect of a rule box, you may pause or delete it. Pause a rule box [#pause-a-rule-box] To temporarily pause a rule box and re-activate it later: Go to **Data View** from the site's main menu. Choose the needed export or the intermediate stage in the dropdown on the left. Select **Edit** in the attribute's column where you have a rule box. Select the wrench icon 🔧 in the top right-hand corner of the rule box. Select the **pause (||)** icon. UUID-27a5b4c4-7d09-1c77-34a5-f20eabd9a132

UUID-27a5b4c4-7d09-1c77-34a5-f20eabd9a132

Select **Save**. To activate the rule box again, repeat the previous instructions and select the play icon **(▶︎)** in [step 5](#N1659514972415). Delete a rule box [#delete-a-rule-box] To remove the rule box: Go to **Data View** from the site's main menu. Choose the needed export or the intermediate stage in the dropdown on the left. Select **Edit** in the attribute's column where you have a rule box. Select the wrench icon 🔧 in the top right-hand corner of the rule box. Select the red **trash** icon. Select **Save**. Duplicate a rule box [#duplicate-a-rule-box] To apply the same rule box several times for the same attribute, but with slightly different settings, you can duplicate a rule box and its settings. To duplicate a rule box: Go to **Data View** from the site's main menu. Choose the needed export or the intermediate stage in the dropdown on the left. Select **Edit** in the attribute's column where you have a rule box. Select the wrench icon 🔧 in the top right-hand corner of the rule box. Select the **duplicate** icon. UUID-41cada18-d075-f5dd-7f0a-ebbe6632aec4

UUID-41cada18-d075-f5dd-7f0a-ebbe6632aec4

Select **Save**. Apply rule boxes to segments [#apply-rule-boxes-to-segments] If you need to edit only a part of your products, you can combine these products into a segment and apply rule boxes to the whole segment without affecting other products. Before applying rule boxes to specific product segments, you must first create a segment. To learn how to create segments, see [Use segments to apply rule boxes to specific product groups](/docs/help-center/map-and-optimize-your-data/data-view/use-segments-to-apply-rule-boxes-to-specific-product-groups#section-idm23222108490782). To apply rule boxes to segments: Go to **Data View** from your site's main menu. Choose the needed export or the intermediate stage in the dropdown on the left. Select **Edit** in the attribute column where you want to apply a rule box to a product segment. If you have already added the needed rule box, proceed to the next step. If not, choose **Select an Option**, select the needed rule box, and set it up. Select the wrench icon 🔧 in the top-right corner of the rule box. Select the label icon 🏷 at the top of the rule box and go to the *Available Segments* window to select the plus icon **+** next to the needed product segment. UUID-fc6c55f1-fa16-5ca0-87db-c0ffd60e038a

UUID-fc6c55f1-fa16-5ca0-87db-c0ffd60e038a

You can select several segments in one rule box. In this case, the platform applies the rule box to all products matching all selected segments. Select **Save**.The rule box affects the products of the selected segment only. The rest of the products remain unchanged. If you need to apply rule boxes to products based on the contents of multiple attributes, you can use the Rule box conditions feature available in Dataflow. See [Apply rule boxes based on conditions](/docs/help-center/add-a-rule-box/apply-rule-boxes-based-on-conditions). Schedule rule boxes to run at a specific time [#schedule-rule-boxes-to-run-at-a-specific-time] You can schedule rule boxes to run at a specific time. For example, if you want to offer discounts on products on weekends. The timezone of the rule boxes is the same as the site's timezone. You can't change it by yourself. If you need to change the timezone, contact [support@productsup.com](mailto:support@productsup.com). In your request, indicate the following: * needed timezone * the site IDs where you want to apply the timezone. Schedule a rule box for a specific day [#schedule-a-rule-box-for-a-specific-day] To schedule a rule box for a specific day of the week and time interval: Go to **Data View** from the site's main menu. Choose the needed export or the intermediate stage in the dropdown on the left. Select **Edit** in the attribute's column where you have a rule box. Select the wrench icon 🔧 in the top right-hand corner of the rule box. In the Box Scheduling section, select **Execute on specific days**. UUID-b80e0ee7-39a2-b59d-68ef-830699a817e3

UUID-b80e0ee7-39a2-b59d-68ef-830699a817e3

Select **Add Date**. Pick a day of the week from the dropdown. Select the **Begin** and **End** times. Select **Save** at the top of the toolbar. You can schedule as many timeframes as desired by repeating the previous actions. After you add a schedule, a little clock icon appears next to the scheduled rule box. UUID-63f8440b-3a18-ce51-2d1b-e87c07de345c

UUID-63f8440b-3a18-ce51-2d1b-e87c07de345c

Schedule a rule box between two dates [#schedule-a-rule-box-between-two-dates] Go to **Data View** from the site's main menu. Choose the needed export or the intermediate stage in the dropdown on the left. Select **Edit** in the attribute's column where you have a rule box. Select the wrench icon 🔧 in the top right-hand corner of the rule box. In the Box Scheduling section, select **Execute between two dates**. UUID-39af6b94-4907-f50d-5e79-351a16de045c

UUID-39af6b94-4907-f50d-5e79-351a16de045c

Define both **Start** and **End** dates or just one of them. Select **Save** at the top of the toolbar. If you define only a Start date, the rule box works for all runs starting this date. If you define only an End date, the rule box works for all runs before the end date. If you define the Start and End dates, the rule box works for all runs between and on those dates. Apply rule boxes in bulk across multiple sites [#apply-rule-boxes-in-bulk-across-multiple-sites] If you need to add the same rule boxes to multiple sites, use the Bulk Option functionality to save time. Your sites must have the same attribute names to apply rule boxes in bulk. Set up the rule boxes in one site. Go to the organization or project level. Select **Bulk Option** in the upper ribbon. A new page opens. UUID-0825a97e-b71c-6bbe-e850-9210a13f9c13

UUID-0825a97e-b71c-6bbe-e850-9210a13f9c13

In the *Choose Sites* step, choose the site where you created the rule boxes and select **Next Step**. In the *Choose Operation* step, select **Add Dataflow Boxes** and confirm your choice by selecting **Next Step**. In the *Operation Details* step, choose the stages that contain the rule boxes in the **Dataflow** dropdown. If you choose *Intermediate - Export*, select the export containing your rule boxes from the **Export** dropdown. All sites where you want to apply the rule boxes must have the selected export. In the *Connections* section, select the connections that contain the rule boxes you want to copy and apply in bulk.You can see the rule boxes applied to each connection. UUID-bcba70fe-9a8e-a453-7589-5a761944c795

UUID-bcba70fe-9a8e-a453-7589-5a761944c795

To let the platform display the sites where you want to copy the rule boxes, select the projects they belong to in the *Target Projects* section. Search for your desired sites in the **Target Sites** search field. If you are adding rule boxes between the intermediate and export stages, find the *Channels* column and select the exports where you want to apply the copied rule boxes. Select **Execute**. In the *Confirmation* step, check the results of the applied changes.You can leave this screen by selecting **Return to organization page**. You can also go to one of the sites where you performed the changes by selecting the name of the needed site. # Twig-based rule box capabilities to enhance your product data import { Callout } from "fumadocs-ui/components/callout"; import { Step, Steps } from "fumadocs-ui/components/steps"; Introduction [#introduction] Twig is a template engine based on PHP that lets you add dynamic content to the template. You can transform your data with the help of Twig in the rule boxes such as *Text Template*, *Text Template with Lists*, and *Math Template* in Data View or Dataflow. Twig lets you make text transformations, do math calculations, dynamically update URLs, and apply simple conditional logic. This document shows some examples of using Twig to optimize your product data. Use rule boxes with Twig to edit the text and do calculations [#use-rule-boxes-with-twig-to-edit-the-text-and-do-calculations] You can enhance your data with the help of rule boxes that can use Twig to dynamically change the content of the attributes in Data View or Dataflow. To add a rule box, take the following steps: Go to **Data View** from the site's main menu. Choose the needed export or the intermediate stage in the drop-down menu on the left. Select **Edit** in the attribute column where you want to apply the rule box: * To create or edit text in the attributes, use the rule boxes *Text Template* or *Text Template with Lists*. See [Create text template using data from other attributes](/docs/help-center/add-a-rule-box/find-the-needed-rule-box-category/replace-values#section-idm353458339224944) to learn how to set up these rule boxes. * To make math calculations in the attributes, use the *Math Template* rule box. See [Work with prices & math](/docs/help-center/add-a-rule-box/find-the-needed-rule-box-category/work-with-prices-math) to learn how to set up the rule box. Enter your text with Twig to integrate attributes' values in your text. See [Add Twig in the rule boxes](#section-idm4625748940313634263541042005). Select **Save**. Add Twig in the rule boxes [#add-twig-in-the-rule-boxes] To get the needed result with Twig, create the Twig code according to the rules: . The Twig should begin and end with curly brackets and spaces such as `{{ text }}`. . The contents of Twig are case-sensitive meaning that if you refer to an attribute with a Twig, you need to enter the attribute's name exactly as it is in the feed. For example, `{{ Long_description }}` or `{{ long_description }}`. . To get values from certain attributes and insert them into the template of the rule box with Twig, use the necessary Twig syntax: * If the attribute name consists only of alphanumeric characters and underscores, you can refer to it using this syntax: `{{ attribute_name }}`. * If the attribute name contains spaces, dots, commas, or other special characters, you can refer to it using this syntax: `{{ fromField('attribute name')|raw }}`. Alternatively, you can rename such an attribute using only alphanumeric characters and underscores. Then, you can refer to the renamed attribute in a Twig using the standard syntax `{{ attribute_name }}`.If renaming an attribute isn't an option, you can copy it, rename the copy, and use the copy in a Twig. . To edit the attribute's current value, use `currentValue`: * If the value consists only of alphanumeric characters and underscores, you can refer to it using this syntax: `{{ currentValue }}`. * If the value contains spaces, dots, commas, or other special characters, you can refer to it using this syntax: `{{ fromField('currentValue')|raw }}`. Use AI-generator for Twig suggestions [#use-ai-generator-for-twig-suggestions] If you need a suggestion for a possible Twig, use our AI-based Twig generator. Select the **>\_** icon in a rule box. UUID-33f340e1-450f-53c9-3747-61208fae6f96

UUID-33f340e1-450f-53c9-3747-61208fae6f96

Describe the aim and result you want to achieve in the Twig generator window and select **Generate**. UUID-98f3cf17-c3cf-7963-59a3-9cad44e95011

Select **Copy** below the **Answer** field. Paste the copied answer into the Twig field of the rule box. To create the most accurate prompts, see our best practices in [Create the right prompt for the AI Twig generator](/docs/help-center/best-practices/create-the-right-prompt-for-the-ai-twig-generator). Refer to a site with Twig [#refer-to-a-site-with-twig] Some sites use shared elements. To distinguish data among the sites, it is possible to add a site tag or site ID in the data feed. See [Edit site settings](/docs/help-center/get-started/manage-your-organization-projects-and-sites/edit-site-settings) to learn how to add a tag to a site. If you need to refer to a site in your data feed, you can use Twig for site ID such as `{{Tag.SiteID}}` or a site tag such as `{{Site.Tags.XXX}}`, where XXX is the tag key that you can set in the site settings. UUID-2cd41b45-159c-d84a-a470-659de0832a0e

UUID-2cd41b45-159c-d84a-a470-659de0832a0e

Leave a comment for Twig [#leave-a-comment-for-twig] It is helpful to add a comment to your Twig in the rule boxes to keep a reminder for your colleagues and yourself of the purpose or logic of the change. To leave a comment for a Twig, use the format `{# … #}` and enter the necessary text inside the brackets. For example, `{# it's a comment to remind you what this Twig edits #}`. The comments are invisible in the data feed and you can only see them when you open the rule box. Use cases for data editing with Twig [#use-cases-for-data-editing-with-twig] Here are some use cases where you can use Twig: | Use case | Attribute value | Text Template with Twig | Result | | --------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------- | --------------------------------------------------------------------------------- | --------------------------------------------- | | **Create a text**: Create simple product descriptions in the description attribute using values from *product\_type* and *brand*. | product\_type: `T-shirt`brand: `Nike` | `This is a {{ product_type }} from {{ brand }}.` | `This is a T-shirt from Nike.` | | **Create a URL**: In the link attribute, create a URL that includes *brand*, and *category*. | brand: `Nike`category: `T-shirts` | `https://www.store-example.com/{{ brand }}/{{ category }}` | `https://www.store-example.com/Nike/T-shirts` | | **Set value if empty**: Change the current value to `brand new` if it is empty. | The current attribute is empty | `{% if currentValue == '' %}{{'brand new'}}{% else %}{{currentValue}}{% endif %}` | `brand new` | | **Prepend the text**: Prepend the text `'cheap'` if the price is lower than 130. | The current attribute: `red jacket` | `{% if price < 130 %}Cheap {{currentValue}}{% else %}{{currentValue}}{% endif %}` | `Cheap red jacket` | # Manage an FTP server hosted by Productsup import { Callout } from "fumadocs-ui/components/callout"; import { Step, Steps } from "fumadocs-ui/components/steps"; Once you create your FTP server, you can manage it directly in Productsup. Reset the FTP server password [#reset-the-ftp-server-password] Go to the organization level and select **FTP Accounts**. Select the arrow to expand the drop-down menu. Select **Reset Password**. UUID-bd1c0d49-52af-f119-b532-d20d86a405d2

UUID-bd1c0d49-52af-f119-b532-d20d86a405d2

Enter and then repeat the new password. Delete an FTP server [#delete-an-ftp-server] When you delete an FTP server you created, be aware that you should first back up all hosted files. Additionally, any data feed that you export to the FTP will fail once you delete the FTP server. Ensure that you change the export destination for your data feeds. Go to the organization level and select **FTP Accounts**. Select the arrow to expand the drop-down menu. Select **Remove**. UUID-ef6c5921-4fa9-3cb6-54b1-655b4ce8f9e7

UUID-ef6c5921-4fa9-3cb6-54b1-655b4ce8f9e7

# Create and manage an FTP server import { Callout } from "fumadocs-ui/components/callout"; If you need an FTP server to import or export data, you can use an FTP server hosted by Productsup. Creating and managing FTP servers through Productsup is only possible for admin users. # Create an FTP server hosted by Productsup import { Callout } from "fumadocs-ui/components/callout"; import { Step, Steps } from "fumadocs-ui/components/steps"; FTP (File Transfer Protocol) servers are the software used for transferring files across the Internet and facilitating remote data sharing between computers. FTP server lets you organize your files and provide access to other users to download them remotely. The FTP server gives you storage protected with a username and password. Productsup lets you create an account at an FTP server to transfer and store your files. Create an FTP account [#create-an-ftp-account] Go to the organization level and select **FTP Accounts**. UUID-20ab6434-d7eb-372e-f91a-8578492c910f

UUID-20ab6434-d7eb-372e-f91a-8578492c910f

Select **ADD FTP ACCOUNT**. Create a username for your FTP server and enter it in the **Username** field. Enter and repeat your password. Select **Save**. Get credentials for your FTP server [#get-credentials-for-your-ftp-server] After creating an account, you get the link to the FTP server where you can store your files. This link never changes. You need the credentials, for example, to access an FTP client to transfer files between your computer and the server. See [Upload files to or download them from an FTP server](#section-idm4525956711566433418746304707). | **Host name** | [ftp://ftp.productsup.com/](http://) | | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **Username** | Defined upon creation | | **Password** | Defined upon creation | | **Port number** | For FTP servers, the global port number is `21`.For SFTP servers, the global port number is `22`. These are default port numbers. If arranged with the administration, your specific port number can differ. Contact [support@productsup.com](mailto:support@productsup.com) if you experience issues with your connection. | See [Reset the FTP server password](/docs/help-center/get-started/create-and-manage-an-ftp-server/manage-an-ftp-server-hosted-by-productsup#section-idm232209163571939). Upload files to or download them from an FTP server [#upload-files-to-or-download-them-from-an-ftp-server] You can transfer files between the FTP server and your computer. You need to install a program on your computer, such as [Cyberduck](https://cyberduck.io/) or [FileZilla](https://filezilla-project.org/), to transfer files between the FTP server and your computer. Use your FTP server's credentials to access it and upload or download files. Import files from the FTP server to Productsup [#import-files-from-the-ftp-server-to-productsup] You can use files from the FTP server as a data source to import them into the Productsup platform: Create an FTP account and get the credentials. See [Create an FTP account](#section-idm4525956770785633418778107327). Go to **Data Sources** from your site's main menu and select **ADD DATA SOURCE**. Search for *Feed URL* and select **Add**. Give it a custom name as desired and select **Continue**. In **Source URL**, add a link to your file stored on the FTP server. In **Description (optional)**, edit the name of the data source as needed. As you can store multiple files on the FTP server, you need to enter the URL with the complete path to your file within the server in **Source URL** — for example, `ftp://ftp.productsup.com/yourfile.csv`. Enter a username and password for your FTP account. Select **Save**. Export files to the FTP server from Productsup [#export-files-to-the-ftp-server-from-productsup] You can export your feed from a site in Productsup to the FTP server hosted by Productsup. See [Add an FTP, SFTP, or FTPS destination](/docs/help-center/export-data-feeds/set-up-an-export-destination/add-an-ftp-sftp-or-ftps-destination) for setup instructions. # Transport Server Data Retention Policy According to the *Productsup Platform Description – Version Q2-2023-V1, updated May 29, 2023*, the retention policy for the files stored on the Productsup Transport Server is as follows: * Removal of Files stored on Transport Server: * Productsup removes files older than 12 months stored on the Transport Server. To prolong their lifetime, you can export the same files again to reset the 12-month Time-To-Live (TTL). * Files with dynamic filenames: * Files with filenames containing a dynamic template fragment ( `{{ ... }}` ) have a 30-day TTL. Productsup removes files if you haven't updated them. See [Legal](https://www.productsup.com/legal/) for more information. # Billing section import { Callout } from "fumadocs-ui/components/callout"; import { Step, Steps } from "fumadocs-ui/components/steps"; The Billing section lets administrators add and modify their billing information. To access Billing, select your profile icon in the top-right corner and choose **Billing**. UUID-213f6466-dbd4-af4f-3d98-481589a2dcd8

UUID-213f6466-dbd4-af4f-3d98-481589a2dcd8

You can only see the *Workspaces* link leading to the [Retail platform](https://retail.productsup.com/dashboard/insights) if you have a Retail platform account. Prerequisites [#prerequisites] You must be an administrator of your Productsup organization to access the **Billing** section. Payment Settings tab [#payment-settings-tab] The Payment Settings view lets you set up an automatic payment method on your organization. You can choose to pay your invoices by direct debit or credit card if the Productsup Finance team has set up [Zuora](https://www.zuora.com/products/billing-software/) on your organization. Productsup supports the following credit cards: Mastercard, Visa, and American Express. You can also select a default payment method or remove payment methods. Productsup only offers the direct debit payment option in the European, United Kingdom, and Australian regions. Contact [support@productsup.com](mailto:support@productsup.com) if you have any questions. Productsup does not store any credit card data. Payment provider [Zuora](https://www.zuora.com/products/billing/) stores all credit card payment data. Add direct debit or credit card [#add-direct-debit-or-credit-card] To add a direct debit or credit card payment method, select the **Payment Settings** tab in the Billing section and **Add payment method**. UUID-a3c3e853-9e51-4281-7b38-aafb3380afe7

UUID-a3c3e853-9e51-4281-7b38-aafb3380afe7

Select **Direct debit** or **Credit card** and choose **Continue** at the bottom of the window. UUID-1fc88c51-0a8f-9aad-079f-76233a0c85e8

Enter your payment details in all fields and select **Add**. This process directs you to the region-specific direct debit modal based on the account setup in Zuora. For example, if your billing address is in France, your country's banking details are pre-populated by the EU (SEPA) direct debit modal. Once you return to the Payment Settings view, choose a payment method and select **Set as default payment method**. To remove a payment method, select the delete icon. You can't delete the default payment method. You must select another payment method as default before being allowed to delete an active default method. UUID-e0d3f289-7b8c-05a3-1f9e-63d51b950c35

UUID-e0d3f289-7b8c-05a3-1f9e-63d51b950c35

# Set up User Management import { Callout } from "fumadocs-ui/components/callout"; import { Step, Steps } from "fumadocs-ui/components/steps"; Learn how to set up User Management, add new users, remove users, and change user access to sites and projects. To learn more about multiple user types, see [User types and permissions](/docs/help-center/get-started/user-management/user-types-and-access-rights). To access User Management, you must be a user admin in your organization. All changes, such as adding new users, removing existing ones, and changing access permissions, must be performed by the organization admin(s). The Productsup Support Team cannot make those changes. Access User Management [#access-user-management] To access User Management: Go to **User Management** from your [organization's](/docs/help-center/get-started/manage-your-organization-projects-and-sites/your-productsup-organization) main menu. UUID-bb13f71d-b1bb-76cf-3e38-fd7b0d95a683

UUID-bb13f71d-b1bb-76cf-3e38-fd7b0d95a683

Here's an overview of all users associated with your organization. UUID-09d2943b-a6e7-7513-f502-29880d69eaf9

Add new users [#add-new-users] Go to **User Management** from your organization's main menu. Select **INVITE USERS** in the top right-hand corner of the *User Management* page. Add the email address(es) of those you wish to invite. 1. You can add one email address per line to invite multiple users at once. Select if your user should have **Admin** or **User** access. 1. After making a selection, you can give them access to the appropriate sites or projects. 2. When adding sites or projects, you should define whether access should be Read-Write or Read-Only. Select **Save**. UUID-4569ba0e-e73e-8bf5-5445-a267458900bd

UUID-4569ba0e-e73e-8bf5-5445-a267458900bd

* The users you invited now receive an email prompting them to accept an invitation to join your organization. * The email prompts your invited users to accept this invitation. * Upon accepting it, they will be prompted to configure their account by setting their name, password, email address, the country they are in, and the language they want to use in the platform. * After accepting the invitation, your new users will have access to Productsup. Any invites sent to new users will be valid for 30 days. After this, the link expires. The address will then disappear from the list of invited users in your User Management. Remove users [#remove-users] Go to **User Management** from the main menu at the organization level. Select the arrow to expand the **Edit** drop-down menu for the user you want to delete. UUID-fd032f35-b623-7645-c508-65405451c28b

UUID-fd032f35-b623-7645-c508-65405451c28b

Select **Delete**. To delete admin users, you should first change their role from *Admin* to *User*. See [Change user/admin role](#section-idm232207392753555). Without changing the user role, you can't delete admin users. UUID-35e75c08-60ca-da20-7c09-668ab9030a53

UUID-35e75c08-60ca-da20-7c09-668ab9030a53

Give users access to sites/projects [#give-users-access-to-sitesprojects] To give access to users, either Read-Write or Read-Only, to sites or projects: Go to **User Management** from your organization's main menu. Select the button showing the number of sites the user has access to. UUID-3b5fe4b0-c091-9193-ce10-085ab79954d4

UUID-3b5fe4b0-c091-9193-ce10-085ab79954d4

**Add**, **change**, or **delete** access to sites and projects. Change user/admin role [#change-useradmin-role] You can elevate users to administrators as well as demote administrators to users. Go to **User Management** from your organization's main menu. To demote a person from an admin profile, select **Edit** from their user profile in User Management: 1. In **Role**, change their role from *Admin* to *User*. UUID-1295ec2f-3da4-10bc-a2a2-6ed97e413765

UUID-1295ec2f-3da4-10bc-a2a2-6ed97e413765

2. Select **Save**. 3. Add any sites/projects you wish the user to have access to. To elevate a user with read-only or read-write access: 1. Select edit on their user profile in **User Management**. 2. Under settings, change the role to **Admin**. 3. Select **Save**. # Two-factor authentication (2FA) feature import { Callout } from "fumadocs-ui/components/callout"; import { Step, Steps } from "fumadocs-ui/components/steps"; Two-factor authentication (2FA) requires you to prove your identity using a device you own besides your standard login credentials. An authenticator sends a code to an app on your mobile phone to confirm your identity. You can use a third-party authenticator app, such as Google Authenticator, which you can install to your phone in [App Store](https://apps.apple.com/us/app/google-authenticator/id388497605) and [Play Market](https://play.google.com/store/apps/details?id=com.google.android.apps.authenticator2\&hl=en\&gl=US). There are two ways to activate 2FA: * You can activate 2FA for your user in user profile settings. See [Set up user profile](/docs/help-center/get-started/user-management/set-up-user-profile#section-idm232205856133962) for step-by-step instructions. * You can activate 2FA for all users within your Productsup organization if you are an admin of that organization. See [Activate 2FA for all users within the organization](#section-idm23220705515061) for step-by-step instructions. If you change your mobile device, you can turn two-factor authentication off to disconnect the old device and save the settings. Then, reactivate 2FA and connect the new device. See [Set up user profile](/docs/help-center/get-started/user-management/set-up-user-profile) for step-by-step instructions. If you don't have access to your 2FA device anymore, contact [support@productsup.com](mailto:support@productsup.com). Activate 2FA for all users within the organization [#activate-2fa-for-all-users-within-the-organization] Select the cogwheel icon UUID-ce09c8b4-4286-bcd4-de46-a409fac3e748

UUID-ce09c8b4-4286-bcd4-de46-a409fac3e748

at the bottom of your organization's main menu. UUID-36341eec-8c91-f393-9f7b-76e31f456174

The **Organization settings** page opens in a new tab. Toggle **Force two-factor authentication for the entire organization** to activate the feature. UUID-42654ca8-d487-65d1-b324-ff1269b7ad24

UUID-42654ca8-d487-65d1-b324-ff1269b7ad24

Select **Save**. If you activate 2FA for all users, ensure every user in your organization recognizes this change. 2FA forces all users to authenticate during their next login, so they won't be able to access your Productsup organization without first setting up 2FA. # Usage data dashboard and overage calculations import { Callout } from "fumadocs-ui/components/callout"; import { Step, Steps } from "fumadocs-ui/components/steps"; According to the Productsup License Agreement, you get access to the platform based on your contract entitlement. If you exceed your entitlement and overuse the platform, you face additional charges for overages. The platform automatically calculates overages based on particular metrics. This document explains the formulas used to calculate excessive use of the Productsup platform. The Usage data dashboard overviews your platform usage and helps you understand charges and overages. The Usage data dashboard shows the essential metrics affecting invoices, such as items, exports, sites, users, and syndication frequency overages. The dashboard is available in the Billing section of the platform, and only organization admins can access it. You can also download the detailed usage reports in CSV format. To access the Usage data dashboard: Select your admin profile icon in the top-right corner and choose **Billing**. Select the *Usage* tab. You can find metrics' meanings under the info icon UUID-fbc49e13-5768-77ad-f36e-7a4b052faa9f

UUID-fbc49e13-5768-77ad-f36e-7a4b052faa9f

next to each metric name. UUID-418591ab-d0e4-ed44-3d27-4dda2c6993ed

Overage calculation metrics [#overage-calculation-metrics] The platform calculates overages for the following metrics: * [Max items](#section-idm4520563288896033230246059519) * [Exports](#section-idm4634253574464033230248710409) * [Users](#section-idm4561994551683233230348428299) * [Sites](#section-idm4566155644926433230350696624) * [Syndication frequency overages](#section-idm4631468298771233551804415214). Overage calculations exclude the sandbox project usage. See [Use your sandbox project for testing purposes](/docs/help-center/best-practices/use-your-sandbox-project-for-testing-purposes). Max items [#max-items] The platform identifies the maximum items imported or exported daily for each non-manual site run for every organization or edition and calculates the monthly overage. Non-manual runs are the ones that use the site scheduling, a trigger of another site, or an API triggers the site. The formula for overage calculation is: `Overage = [the highest number of items per day within a month] - [your service entitlement]` For example, if the item entitlement is `5000`, the overage calculation looks as follows: UUID-f705938d-245e-42ff-091a-ca8feee102c2

UUID-f705938d-245e-42ff-091a-ca8feee102c2

The overage for January 2021 is 5000, calculated as `10000 actual items - 5000 items from the entitlement`. There are no overages in February 2021, as the platform imported or exported exactly 5000 items. Exports [#exports] The platform takes daily snapshots of the number of your configured main and standard exports for every organization or edition and calculates the monthly overage. The overage calculations for the exports metric takes into account export clustering. See [Export clustering](#section-idm4561994500652833230356936418) to learn how it works. The formula for overage calculation is: `Overage = [the total number of clustered exports within a month] - [your service entitlement]` The platform doesn’t count the sandbox project’s exports. See [Use your sandbox project for testing purposes](/docs/help-center/best-practices/use-your-sandbox-project-for-testing-purposes). For example, if the exports entitlement is `60`, the overage calculation looks as follows: UUID-84720fcf-cfc6-7883-ee75-59afc5f4baec

UUID-84720fcf-cfc6-7883-ee75-59afc5f4baec

The overage for January 2021 is 40, calculated as `100 added exports - 60 exports from the entitlement`. There are no overages in February 2021, as the customer added only 50 exports. Export clustering [#export-clustering] The Productsup platform uses export clustering to calculate overages for exports. Productsup has three (3) types of exports: * Standard export: highlighted in *green* in the following example tables. * Main export: highlighted in *yellow* in the following example tables. * Sub-export: highlighted in *red* in the following example tables. Standard exports [#standard-exports] A standard export is the default export that doesn't have any classifications or sub-exports. For example, *Google Merchant Center*. To count standard exports on the site level, use the following formula: `[The same standard export added N times] = N` For example: UUID-e837cea8-12a8-223c-34e0-150ca0e4a958

UUID-e837cea8-12a8-223c-34e0-150ca0e4a958

The platform counts the standard export A every time you add it, which makes up three (3) exports. Main exports [#main-exports] The main export is a standard export that can have one or more sub-exports associated with it. For example, *Upljft - Basic catalog* is the main export for sub-exports *Upljft - Country feed* and *Upljft - Language feed*. This system helps to avoid overages by clustering multiple similar sub-exports that send data to the same channel but for different countries, languages, etc. To count main exports on the site level, use the following formulas: * `[The same main export added N times] = 1`For example: UUID-5a98236a-470d-8d22-6aa7-ca6c4932f19c

UUID-5a98236a-470d-8d22-6aa7-ca6c4932f19c

The platform counts the standard export A every time you add it, which makes up two (2) exports, while it counts the main export B as one (1) export although added twice. In total: three (3) exports. * `[N different main exports added] = N`For example: UUID-b0cf8ea0-28f6-18d7-cc19-a0df1ed0d7a0

UUID-b0cf8ea0-28f6-18d7-cc19-a0df1ed0d7a0

The platform counts the standard export A every time you add it, which makes up two (2) exports, while it counts the main export B as one (1) export although added twice. The platform counts main export C added once as one (1) export. In total: four (4) exports. Sub-exports [#sub-exports] A sub-export is an export that belongs to the main export and helps cluster multiple similar exports that send data to the same channel but for different countries, languages, etc. However, there might be cases where a sub-export doesn’t belong to the main export because there is no need of the main export for certain setups. In this case, the platform creates a non-global placeholder as the main export and associates sub-exports with it. For example, FabDis exports, such as *Fabdis 3.0 - C01\_Extension*, are sub-exports that belong to the non-global placeholder main export *FabDis 3.0 - Master Channel Shell*. To count sub-exports on the site level, use the following formulas: * `[The same sub-export added N times] = 1`For example: UUID-dad97a80-eec3-c65e-7f69-a53f5da33272

UUID-dad97a80-eec3-c65e-7f69-a53f5da33272

The platform counts the standard export A and the main export B as two (2) exports, while it counts the sub-export C belonging to the main export D as one (1) export although it is added twice. In total: three (3) exports. * `[N different sub-exports belonging to the same main export] = 1`For example: UUID-6b0b2d3f-9a3d-eace-63ba-06d6e3a052e6

UUID-6b0b2d3f-9a3d-eace-63ba-06d6e3a052e6

The platform counts the standard export A and main export B as two (2) exports, and it counts all sub-exports belonging to the same main export D as one (1) export, although they are added three times (twice for C and once for F). In total: three (3) exports. * `[Sub-exports from N different main exports] = N`For example: UUID-914331ca-4886-7a76-9490-6abfdcc0ab09

UUID-914331ca-4886-7a76-9490-6abfdcc0ab09

The platform makes the following calculations: 1. Counts every time you add each standard export A and H per site, which makes five (5) exports. 2. Counts the main exports B and E only once for each export type per site, regardless of how many times you added them. This makes four (4) exports. 3. Counts two (2) sub-exports C belonging to the main export D, and one (1) sub-export F belonging to the main export G, only once for each main export per site. This makes three (3) exports. 4. In total: 12 exports. Users [#users] The platform makes a daily snapshot of the number of users in each organization or edition and calculates the monthly overage. The formula for overage calculation is: `Overage = [the highest number of users daily within a month] - [your service entitlement]` For example, if the users entitlement is `10`, the overage calculation looks as follows: UUID-116bb9b6-46a0-daf8-ec77-b3e3e1077255

UUID-116bb9b6-46a0-daf8-ec77-b3e3e1077255

The overage for January 2021 is `10-10=0`. For February and March 2021, it is `15-10=5`. Sites [#sites] The platform makes a daily snapshot of the number of sites or catalogs in every Seller/Vendor Onboarding Module in each organization and calculates monthly overage. The formula for overage calculation is: `Overage = [the highest number of sites within a month] - [your service entitlement]` For example, if the sites entitlement is 10, the overage calculation looks as follows: UUID-fc5708c3-9f27-c449-416d-e95530115812

UUID-fc5708c3-9f27-c449-416d-e95530115812

The overage for January 2021 is `30-10=20`. For February and March 2021, it is `10-10=0` and `5-10=-5,` and both result in zero (0) overages. Syndication frequency overages [#syndication-frequency-overages] The platform makes a daily snapshot of the number of syndications per export in each organization and calculates the monthly overage. Syndication is the sum of exports runs per site per day. The platform doesn't count manual site runs triggered when you select the **Export** or **Run** buttons. However, if the manual site run triggers another site run, the triggered site run counts as syndication and increases the total syndication frequency count by one (1). To prevent overages in this case, check the triggering settings of your sites in **Scheduling**. See [Set up scheduling and triggering processes in Scheduling](/docs/help-center/dashboard-and-monitor/set-up-scheduling-and-triggering-processes-in-scheduling) for more information. Suppose the organization has three (3) active exports: A and B in site 1, and C in site 2. The syndication frequency entitlement per export is 1. The following syndication frequency happened during January 2021: * 01.01.2021: Three (3) syndications for export A, one (1) for export B, and one (1) for export C. * 02.01.2021: Two (2) syndications for export A, one (1) for export B, and two (2) for export C. * 03.01.2021: One (1) syndications for each export. UUID-2c13abde-f1af-5add-2183-b16fd11ef35a

UUID-2c13abde-f1af-5add-2183-b16fd11ef35a

The platform doesn’t count the number of syndications but only the fact of exceeding the entitlement per export per day, and sums up these daily cases for a month. In this example, the number of daily syndications with overages on 01.01.2021 is only one (1) because only export A exceeds the entitlement. On 02.01.2021, it is two (2) as two (2) exports exceed the entitlement. And on 03.01.2021, there were no overages. See the following table: UUID-faa94dbf-83a1-a090-2321-b90fe8c4da95

UUID-faa94dbf-83a1-a090-2321-b90fe8c4da95

January overages equal the sum of one (1) exceeding syndication case on 01.01.2021 and two (2) cases on 02.01.2021, which makes three (3) in total for January. See the following table: UUID-a20be908-ae31-d30d-8779-efb18edc3bf2

UUID-a20be908-ae31-d30d-8779-efb18edc3bf2

Syndication frequency overages details [#syndication-frequency-overages-details] You can view details of syndication frequency overages per day: Select a necessary month bar on the *Syndication frequency overages* graph. UUID-598aa538-36da-0763-8e66-181fcd66b4d2

UUID-598aa538-36da-0763-8e66-181fcd66b4d2

Select a necessary day bar on the *Syndication frequency overages* graph. UUID-4199a2cb-97c2-0230-ecad-3ce33e72e782

The *Syndication Frequency Overages Details* table shows all sites that lead to overages. You can check the following metrics for each site in your organization for a selected day: * **Overage** * **Exports** * **Entitlement** * **Syndications** UUID-f568a1d9-6b70-68d7-431f-f568e530e9d7

UUID-f568a1d9-6b70-68d7-431f-f568e530e9d7

You can take the following actions: . Select another day. Open the day picker dropdown. The red dots in the top-right corner of a day indicate the days with overages. UUID-90331f7a-5ec1-9bf6-7149-006f8a33c47d

UUID-90331f7a-5ec1-9bf6-7149-006f8a33c47d

Select a necessary day. . View the list of exports for each site and deactivate unnecessary exports to reduce overages: Select a number next to the necessary site in the *Exports* column to go to the *Overview* tab of the Exports page of the site. Check the active exports and deactivate unimportant exports. . View the scheduling of each site: Hover over a necessary site line and select **View Scheduling** to get to the *Site Scheduling* tab in Scheduling. Adjust your schedule to match your entitlement. See [Schedule your site runs in Site Scheduling](/docs/help-center/dashboard-and-monitor/set-up-scheduling-and-triggering-processes-in-scheduling#section-idm4498060092667233567717425562). Download the usage reports [#download-the-usage-reports] You can download the detailed usage reports in CSV format. The reports contain information for one (1) selected month with daily data. You get a *.zip* folder named `usage-report-YYYY-MM` that consists of the following CSV files: * Excluded sites with names * Exports with names * Max items with names * Sites with names * Syndication frequency with names * Users with names You can download the reports only for the months starting from November 2022. To download the reports, do the following: Go to the *Usage* tab. Select the download icon UUID-3f97ce99-598d-6cdf-a31a-799d8f58dade

UUID-3f97ce99-598d-6cdf-a31a-799d8f58dade

UUID-d48a8b54-d8c8-08ba-e2af-f091b147e454

Select the year and month for the report. UUID-93932d16-108a-29d1-74ef-dba766720dfc

Select **Download**. Format the downloaded usage report [#format-the-downloaded-usage-report] If the CSV files show all data in a single cell instead of separate rows and columns, you may need to set a delimiter in the Table settings of your tool: For *Numbers* on macOS, do as follows: Select the **Table** button. Select the **Adjust Import Settings…** button. Select a comma (**,**) in **Separate Value Using**. Select **Update Table**. For *Microsoft Excel*, do as follows: Go to the **Data** tab. In **Get & Transform Data**, select **From Text/CSV**. In **Import Data**, find and select your CSV file. In **Text Import Wizard**, select **Delimited** and select **Next**. Choose a comma (**,**) or a semicolon (**;**) as a delimiter and select **Next**. Check if the preview shows all the necessary columns highlighted and select **Next**. Choose the appropriate data format for each column, such as *General*, *Text*, or *Date*, and select **Finish**. The Productsup Help Center disclaims all responsibility and accountability for the accuracy and relevance of the processes, features, UI elements, and other information mentioned in these instructions about third-party tools. The instructions aim to help you perform activities outside the Productsup platform. # Set up user profile time zone import { Callout } from "fumadocs-ui/components/callout"; Your import and export times use the time zone that you set in your user profile. Any time zone you set only affects your Productsup profile. This means you can select one time zone and see all site run times in this time zone, whilst your colleague with another time zone will see different run times for the same site. A new user sees the default European time zone set for Berlin (GMT+1). UUID-97adbd75-091b-5e0b-427b-7fc9f9151f7d

UUID-97adbd75-091b-5e0b-427b-7fc9f9151f7d

Change the time zone for your user profile [#change-the-time-zone-for-your-user-profile] To choose a time zone for your user profile, select the profile icon in the top-right corner of the page from the organization, project, or site level: UUID-f17228ce-ef8a-6dda-7e5b-09bed1757e2a

UUID-f17228ce-ef8a-6dda-7e5b-09bed1757e2a

UUID-c44d2633-5197-2910-cd12-90d51272cf9a

Schedule a site for a specific time zone [#schedule-a-site-for-a-specific-time-zone] The default time zone for Scheduling is the time zone you have set in your user profile. But you can also select a different time zone in Scheduling. UUID-5d30e801-b3cd-68dc-ad13-e8419e67b215

UUID-5d30e801-b3cd-68dc-ad13-e8419e67b215

See [Set up scheduling and triggering processes in Scheduling](/docs/help-center/dashboard-and-monitor/set-up-scheduling-and-triggering-processes-in-scheduling#section-idm4615619487793633569328756071) for more details about scheduling. Reporting is always in UTC [#reporting-is-always-in-utc] If you compare the reporting data with another tracking system, such as Amazon or Google Analytics, you need to use UTC. Otherwise, you are not comparing the same time ranges. The time zone for Reporting is always UTC. You can't change this. See \[component:17350]. # User types and access rights import { Callout } from "fumadocs-ui/components/callout"; import { Step, Steps } from "fumadocs-ui/components/steps"; Introduction [#introduction] There are two user types in Productsup: . Admin . User Users may have Read-Write or Read-Only access rights depending on the project or site they get access to. UUID-48fe2096-3cba-beed-357a-fa607f861db4

UUID-48fe2096-3cba-beed-357a-fa607f861db4

Admins [#admins] Admins have the right to perform all actions within an organization. This includes: * Accessing all projects and sites * Creating, changing, and deleting all projects and sites * Inviting and deleting users * Providing users with access to sites or projects * Specifying Read-Write or Read-Only access rights for users in each site or project * Changing the rights of other administrators in the organization or demoting administrators to users. Follow these steps to add new users if you are an administrator: Go to **User Management** from your organization's main menu. Select **INVITE USERS** in the top right-hand corner of the *User Management* page. Add the email address(es) of those you wish to invite. 1. You can add one email address per line to invite multiple users at once. Select if your user should have **Admin** or **User** access. 1. After making a selection, you can give them access to the appropriate sites or projects. 2. When adding sites or projects, you should define whether access should be Read-Write or Read-Only. Select **Save**. UUID-4569ba0e-e73e-8bf5-5445-a267458900bd

To learn how to delete users or change user access rights, see [Set up User Management](/docs/help-center/get-started/user-management/set-up-user-management). Read-Write users [#read-write-users] A *Read-Write user* has access to the projects or sites that an administrator has made available to them only. Such users have the right to change those projects or sites as needed: * Edit site data * View and use all features on the site level * Create new sites Read-Write users don't have the right to: * Invite new users * See the list of all users in an organization * Assign additional access rights to themselves The administrator grants the required access if a user needs access to additional sites or projects. At the site level, a Read-Write user has access to these features: * **Dashboard** * **Data Map** * **Authentication** * **Data Sources** * **Data Services** * **Exports** * **Designer** * **Scheduling** * **Dataflow** * **Data View** * **Lists** * **ROI Strategy** * **Reporting** * **Error Log** * **Monitor** * **Activity** * **Tracking** * **Settings** At the project level, Read-Write users have access to: * **Overview** * **Authentication** * **Reporting** * **Reporting** * **Settings** At the organization level, Read-Write users can access only **Overview** and **Authentication**. Read-Only users [#read-only-users] A *Read-Only user* has the right to view only the sites or projects that an administrator has made available to them and can't edit anything in the platform. The administrator grants the required access if a user needs access to additional sites or projects. Read-Only users have access to a restricted list of Productsup features. At the site level, Read-Only users can access these features: * **Dashboard** * **Data Map** * **Data Services** * **Exports** * **Data View** * **Reporting** At the project level, Read-Only users have access to: * **Authentication** * **Reporting** At the organization level, Read-Only users can access only **Overview** and **Authentication**. # Set up single sign-on (SSO) import { Callout } from "fumadocs-ui/components/callout"; import { Step, Steps } from "fumadocs-ui/components/steps"; As an admin user, you can configure single sign-on (SSO) to let the users within your organization log in to all related applications with one set of login credentials. There are three variants of login for users in Productsup: . *Regular login* lets users log in with their Productsup credentials. This option is available to all users before you configure SSO. UUID-93d15b36-aeb2-40b9-e033-069b3a3cdd2b

UUID-93d15b36-aeb2-40b9-e033-069b3a3cdd2b

. *Enabled SSO* lets users log in with either Productsup or SSO credentials. This option is available when you have already enabled SSO but haven't finalized the configuration yet. You can stop the SSO configuration process on this step if you want to enable SSO in parallel with regular login. This step also lets you test your SSO before proceeding to enforced SSO. . *Enforced SSO* lets users only log in using SSO credentials. This option is available as soon as you finalized the SSO configuration process and enforced single sign-on. Once you set up enforced SSO, you can't remove it and roll back to the previous step. Contact [support@productsup.com](mailto:support@productsup.com) if you need to remove the enforced SSO settings. To log in with enforced SSO, users have two options: 1. Go to `subdomain.productsup.com` created for your organization after enabling SSO. The link redirects you to the Productsup login page with the SSO login button. Select the button to land on the Identity Provider (IdP) login page where you must provide your IdP credentials, such as Google account login and password. 2. Go to `platform.productsup.com` and enter the email associated with the Productsup account. If their account has enforced SSO, the platform redirects you to the Productsup login page with the SSO login button as described in [Option a](#N1717772494218). UUID-6cf4cc1e-a828-834b-1b00-0b831696ef65

UUID-6cf4cc1e-a828-834b-1b00-0b831696ef65

Prerequisites [#prerequisites] To set up SSO, you need: . An account with an Identity Provider (IdP), such as Google, Microsoft, AWS, etc. . The admin access rights to your IdP account interface to set up SSO for users in your organization. . The Identity Provider (IdP) metadata file. See [Prepare the IdP metadata file](#section-idm4519154337857632442011241752). . The admin access rights in Productsup. Prepare the IdP metadata file [#prepare-the-idp-metadata-file] Identity Provider (IdP) is a service that stores and verifies user identity. To use the SSO feature in Productsup, you must upload your IdP metadata file to the platform. The Productsup platform then creates metadata information for you to share with your IdP. When the configuration is ready, Productsup, as an SSO provider, checks user identity with the IdP when users log in. For example, to learn how to get the IdP file from Microsoft Entra ID, see [Configure Microsoft Entra SSO](https://docs.microsoft.com/en-us/azure/active-directory/saas-apps/samlssoconfluence-tutorial#configure-azure-ad-sso). The IdP metadata XML file that you receive from your IdP should contain the following: * IdP or Entity ID. * Certificate. * SSO URL. * Redirect URL. The service provider metadata XML file contains: * Entity ID * Redirect URL * Logout URL * SSO Assertion Consumer Service URL Set up SSO [#set-up-sso] To set up SSO in Productsup for your organization: Select the cogwheel icon UUID-ce09c8b4-4286-bcd4-de46-a409fac3e748

at the bottom of your organization's main menu. UUID-36341eec-8c91-f393-9f7b-76e31f456174

The **Organization settings** page opens in a new tab. Select the **Single Sign-On (SSO)** tab on the left-hand side. UUID-486cbe03-77da-e31b-4c62-62c013154d81

UUID-486cbe03-77da-e31b-4c62-62c013154d81

Take the following steps: 1. [Configure single sign-on](#section-idm4631883022056034293075463896). 2. [Enable single sign-on](#section-idm4519154055641632442014087608). 3. [Test the setup](#section-idm4559435165608034293217215196). 4. [Enforce single sign-on](#section-idm4519153987779232442025574732) (optional). Configure single sign-on [#configure-single-sign-on] In this step, you need to provide you organization subdomain information: In the **Configure single sign-on** section, select **Configure**. UUID-4078a8bb-aa45-4d6e-0aa0-57f7a7b1b07d

UUID-4078a8bb-aa45-4d6e-0aa0-57f7a7b1b07d

Enter your organization's subdomain name, for example, `yourcompany.productsup.com`, and select **Continue**. UUID-8bbc4ed6-0120-4a7c-154e-150d9bd20b6d

UUID-8bbc4ed6-0120-4a7c-154e-150d9bd20b6d

Copy the **Entity ID** and **Sign on URL and Reply URL (ACS URL)** using the **Copy** buttons and paste them into your IdP's admin console. Select **Continue**. UUID-cf65b1c3-31fa-25ff-fc1a-fcdba186ba8e

UUID-cf65b1c3-31fa-25ff-fc1a-fcdba186ba8e

Drag and drop your IdP's metadata XML file or select **BROWSE** to add the file from your computer. Select **Finish**. UUID-10a450fe-effe-9e82-5e56-2641b91156cb

UUID-10a450fe-effe-9e82-5e56-2641b91156cb

The platform fills out the **Entity ID/Issuer** and **SSO URL** fields automatically, but your IdP's XML file must contain the Productsup *Entity ID* and *SSO URL*. You have now configured SSO. Continue with [Enable single sign-on](#section-idm4519154055641632442014087608). Enable single sign-on [#enable-single-sign-on] In this step, you can enable SSO and test it to ensure everything works correctly and all users in your organization can access the platform via SSO. In the *Enable single sing-on* section, select **Enable**. UUID-30642cd1-49f5-f3ad-9dc7-e3958c6d6881

UUID-30642cd1-49f5-f3ad-9dc7-e3958c6d6881

A pop-up window appears with the following message:\*By enabling SSO, you can start testing for your organization. Testing SSO allows users in your organization to confirm if they can log in via Single Sign-on without issue.\**Note: Once you enable testing, we will use Just-In-Time (JIT) provisioning if a user attempts to log in to your Productsup organization via SSO using an email address not associated with a Productsup user. This automates user account creation with basic permissions.* UUID-6b18c80b-1850-5476-9993-7bbeaee7eccf

UUID-6b18c80b-1850-5476-9993-7bbeaee7eccf

*Just-In-Time (JIT)* is an authentication method that automates user account creation using the information from the IdP.Basic permissions are access rights given to the users who logged in with SSO. Newly-created SSO users don't have access to projects or sites until the admin provides it to them in the organization's User Management. Select **Enable** in the pop-up to turn on SSO. You have enabled SSO. Take the following steps to test it. Test the setup [#test-the-setup] Select **Copy URL** in the bottom of the *Test the setup* section. UUID-5000aeb8-7a27-7e98-fada-82e928416003

UUID-5000aeb8-7a27-7e98-fada-82e928416003

Log in using SSO. Before testing, log out of the account, use the incognito mode or another browser. If you don't want to enforce SSO for your users, you can stop here and share the copied subdomain URL with your users to let them log in via the URL. Or they can still log in using their Productsup credentials. Enforce single sign-on [#enforce-single-sign-on] Enforcing SSO enables your users to log in only via SSO, not with the Productsup credentials. Ensure the user accounts are compatible with your SSO Identity Provider. For example, their registered platform emails must match the SSO IdP, such as an Outlook email address matches the Outlook IdP. If you invite users to an additional organization that isn't SSO enforced, they may still log in via an email and a password. Once you enforce SSO, you can't remove the enforced SSO configuration. Contact [support@productsup.com](mailto:support@productsup.com) if you need to remove the enforced SSO settings. Now you can only enforce SSO for the emails with specific domain names: In **Domain name**, enter one or multiple domain names separating them with `##`. UUID-f8edaf96-34fb-e782-352d-d17cfa93b0dd

UUID-f8edaf96-34fb-e782-352d-d17cfa93b0dd

Select **I have tested the SSO, and I'm ready to enforce it now**. This checkbox activates the **Enforce** button. Select **Enforce** in the top right corner. In the pop-up, enter the same organization's subdomain name that you entered in the step [Test the setup](#section-idm4559435165608034293217215196). Select **Enforce** to confirm the SSO enforcement. UUID-113fc464-1307-73d6-882b-e5dce05a2e41

UUID-113fc464-1307-73d6-882b-e5dce05a2e41

You have now turned on SSO for users in your organization. # Set up user profile import { Callout } from "fumadocs-ui/components/callout"; import { Step, Steps } from "fumadocs-ui/components/steps"; Introduction [#introduction] Personalize your Productsup user profile settings, such as your name, email, password, job title, country, timezone, and language. In profile settings, you can also enable two-factor authentication (2FA). Access your user profile settings [#access-your-user-profile-settings] To access user profile settings, select the profile icon in the top-right corner of the page from the organization, project, or site level. Alternatively, go directly to [user profile settings](https://platform.productsup.com/profile). UUID-f17228ce-ef8a-6dda-7e5b-09bed1757e2a

You can only see the *Workspaces* link leading to the [Retail platform](https://retail.productsup.com/dashboard/insights) if you have a Retail platform account. *Billing* is only available to admin users. See [Usage Data Dashboard and overage calculations](/docs/help-center/get-started/user-management/usage-data-dashboard-and-overage-calculations). Change your profile name and email [#change-your-profile-name-and-email] You can change your profile name and email in profile settings. However, if your email is the main email registered for your organization, you can't change it in your profile settings. Contact [support@productsup.com](mailto:support@productsup.com) to change the main email registered in Productsup for your organization. To change your name and email: Go to *Profile settings* from your user profile icon in the top-right corner of the page. Enter your name and email in **Full Name** and **Your email**. UUID-055d6151-e776-a8b7-d1bf-573234992d4a

UUID-055d6151-e776-a8b7-d1bf-573234992d4a

Select **Save**. If you have updated your email, go to your inbox to confirm the new email address. Change your password [#change-your-password] You can change your password in the user profile settings. Go to *Profile settings* from your user profile icon in the top-right corner of the page. Select **Change** near the **Current password** field to open the *CHANGE PASSWORD* window. Enter your existing password in **Current password**. UUID-d247843e-91e8-d740-6de0-a9ac33c9ee22

UUID-d247843e-91e8-d740-6de0-a9ac33c9ee22

Add a new password that meets platform requirements in **New password** and repeat it in **Confirm new password**. Your password must contain at least 12 characters, 1 number, both lower- and uppercase letters, and 1 special character, such as `#`, `?`, `!` and so on. Select **Save**. Enter job title, location, and timezone [#enter-job-title-location-and-timezone] Enter your job title, location, and timezone to better identify your professional role and place within your organization. Go to *Profile settings* from your user profile icon in the top-right corner of the page and enter your position in **Job title**. UUID-6a573734-75df-3553-ea91-2d7ffa632cb9

UUID-6a573734-75df-3553-ea91-2d7ffa632cb9

Select your location in **Country** and choose a suitable option in **Timezone**. Select **Save**. See [Set up user profile time zone](/docs/help-center/get-started/user-management/set-up-user-profile-time-zone) for more information. Change the platform language [#change-the-platform-language] You can use the Productsup platform in English, German, or French. To choose the needed language option, do the following: Go to *Profile settings* from your user profile icon in the top-right corner of the page. In **Language**, select the desired language. UUID-0eb105e6-1517-8430-6521-d18e241b5fe2

UUID-0eb105e6-1517-8430-6521-d18e241b5fe2

Select **Save**. Use two-factor authentication (2FA) [#use-two-factor-authentication-2fa] You can set two-factor authentication (2FA) as a login standard for your organization. Go to *Profile settings* from your user profile icon in the top-right corner of the page. Use the toggle **Enable two factor authentication** to start the setup and select **Save**. UUID-087c4a64-3985-8816-394e-4dea3e95bea0

UUID-087c4a64-3985-8816-394e-4dea3e95bea0

When the platform saves your new settings, you see the following pop-up window. Select **Continue** to proceed. UUID-90954c66-4913-7308-8293-558aa8f87d8c

UUID-90954c66-4913-7308-8293-558aa8f87d8c

On the login page, enter your email and password to see 2FA instructions.Follow the instructions on the page *Mobile Authenticator Setup* to install an authenticator app and add a device. You can use the following apps: * Google Authenticator * FreeOTP * Microsoft Authenticator UUID-6474abfd-97ce-4ca7-6eec-b62a7d15becf

UUID-6474abfd-97ce-4ca7-6eec-b62a7d15becf

Enter a code from your authenticator app in **One-time code**. You will need to enter authentication codes in this field every time when logging in. When logging in, use the last added code in your authenticator app called `Productsup: {your-address@email.com}`. If you have used 2FA with Productsup previously, you may have multiple codes with this name in the app. All previously added codes are no longer relevant. If desired, provide a name for your authentication device in **Device Name**. Select **Submit**. Changed phones? [#changed-phones] If you change your mobile device, you can turn two-factor authentication off to disconnect the old device and save the settings. Then, reactivate 2FA and connect your new device by following the previously mentioned steps. Lost your phone? [#lost-your-phone] If you don't have access to your 2FA device anymore, contact [support@productsup.com](mailto:support@productsup.com). # Remove duplicate products with the Unique Rows Filter service import { Callout } from "fumadocs-ui/components/callout"; import { Step, Steps } from "fumadocs-ui/components/steps"; Introduction [#introduction] If you need to remove duplicate rows from the Productsup Platform, you can use the unique rows filter service. You can define which attribute to check for uniqueness. You may also consider skipping unique values directly in an export feed. Ensure you have set a [unique item identifier](/docs/help-center/import-data-feeds/import-your-data-into-productsup/set-a-unique-item-identifier) to use this service. Add the Unique Rows Filter service [#add-the-unique-rows-filter-service] To add the Unique Rows Filter service: Go to **Data Services** from your site's main menu and select **ADD SERVICE**. Then choose *Unique Rows Filter*, and select **Add**. UUID-279518ad-84d1-39f6-48f6-5d4372845774

UUID-279518ad-84d1-39f6-48f6-5d4372845774

(Optional) In **Name**, give the new service a custom name. (Optional) Define a custom column prefix in **Column prefix**. The platform uses a column prefix when a service generates multiple columns from one service and needs a common prefix for all new columns. The *Unique Rows Filter* service is only available on the import level for the **Service Data Level** function. Select **Add**. In **Uniqueness Column**, select the column you wish to filter for uniqueness in the drop-down list. In **Occurrence**, choose **first** or **last** value occurrences from the selected *Uniqueness Column* you want to keep in your import feed. The platform removes other occurrences during the import process. Select **Save**. UUID-fb04bd0f-1708-dc84-870b-a34d95d5f8a5

UUID-fb04bd0f-1708-dc84-870b-a34d95d5f8a5

For example, you can use the Unique Rows Filter service for the following scenario. This scenario imports the first occurrence of every ID and removes all duplicates. | id | title | stock | | --- | ---------------------------- | ----- | | `1` | `Amazing Shoes` | `4` | | `1` | `Amazing Shoes in blue` | `4` | | `2` | `Great Jeans` | `1` | | `3` | `Wonderful T-Shirt` | `5` | | `3` | `Wonderful T-Shirt in green` | `4` | In the previous configuration, the uniqueness column is `title`, and the selected occurrence is *first*. Here are the results: | id | title | stock | | --- | ------------------- | ----- | | `1` | `Amazing Shoes` | `4` | | `2` | `Great Jeans` | `1` | | `3` | `Wonderful T-Shirt` | `5` | Edit an existing Unique Rows Filter service [#edit-an-existing-unique-rows-filter-service] To edit settings for your Unique Rows Filter service: Go to **Data Services** from your site's main menu. Choose the *Unique Rows Filter* data service and select the settings cogwheel icon (**⚙**). Delete an existing Unique Rows Filter service [#delete-an-existing-unique-rows-filter-service] To delete your Unique Rows Filter service: Go to **Data Services** from your site's main menu. Choose the *Unique Rows Filter* data service and select the settings cogwheel icon (**⚙**). Scroll to the bottom of the page and select **Remove this service**. # Split one column into multiple columns with the Explode Columns service import { Callout } from "fumadocs-ui/components/callout"; import { Step, Steps } from "fumadocs-ui/components/steps"; Introduction [#introduction] If your data feed contains a column with a list of values, you can split the column into multiple columns using the Explode Columns data service. For example, you have the following data at the import stage and wish to split the `color` column: | id | color | | -- | ----------------------- | | 1 | `red`, `green`, `blue` | | 2 | `gray`, `black`, `blue` | After applying the Explode Columns data service, your output may look similar to the following: | id | color\_1 | color\_2 | color\_3 | | -- | -------- | -------- | -------- | | 1 | `red` | `green` | `blue` | | 2 | `gray` | `black` | `blue` | The Explode Columns data service is available for the import and intermediate stages. Prerequisites [#prerequisites] To set up the Explode Columns data service, you need: . A unique item identifier. See [Set a unique item identifier](/docs/help-center/import-data-feeds/import-your-data-into-productsup/set-a-unique-item-identifier) for more information. . A column in your feed that contains a list of values separated by a delimiter. Add the Explode Columns data service [#add-the-explode-columns-data-service] Go to **Data Services** from your site's main menu and select **ADD SERVICE**. Search for *Explode Columns*, select **Add**, and give it a desired name and column prefix.By default, `___exploded` is the column prefix. UUID-649638ef-a14e-0b2f-d793-4adf95bdac9e

UUID-649638ef-a14e-0b2f-d793-4adf95bdac9e

Choose the stage containing the columns you want to split in **Service Data Level** and select **Add**. Select the column you want to split from the drop-down list **Column that will be split into multiple columns**. If you choose **Import** in **Service Data Level** in [see the relevant section](#N1676387000216), the drop-down list **Columns that will be split into multiple columns** displays the columns of your import stage. If you choose **Intermediate**, the drop-down list contains your intermediate-stage columns. In **Delimiter**, select the delimiter that separates the values in the column you want to split. Select **Save**. UUID-223f0513-6110-0eda-7dab-03eff9f1da18

UUID-223f0513-6110-0eda-7dab-03eff9f1da18

Repeat steps starting with [see the relevant section](#N1676387043550) if you want to split more columns with the Explode Columns data service. The platform shows all exploded columns in a table at the bottom of the data service setup page. UUID-7cb74901-8654-d2be-d6b7-e48625c45636

UUID-7cb74901-8654-d2be-d6b7-e48625c45636

For the platform to process a new data service, select **Run** in the top-right corner of your site's view. Edit the Explode Columns service [#edit-the-explode-columns-service] Go to **Data Services** from your site's main menu. Search for your data service. Select the cogwheel icon (**⚙**) next to the desired data service to edit settings. Select **Save**. Delete the Explode Columns service [#delete-the-explode-columns-service] Go to **Data Services** from your site's main menu. Select the cogwheel icon UUID-e19d1a4d-9ea0-6607-b841-3cd22c1101e2

UUID-e19d1a4d-9ea0-6607-b841-3cd22c1101e2

next to the desired data service. In the **Danger Area** panel, select **Remove this service**. Select **Yes**. # Restructure your import data with the Pivot Layout data service import { Callout } from "fumadocs-ui/components/callout"; import { Step, Steps } from "fumadocs-ui/components/steps"; Introduction [#introduction] If your data feed has multiple rows representing attributes for the same product, you may need to reorganize your product attributes into columns to do attribute mapping in Dataflow properly. The Pivot Layout data service is available for the import stage only. The Pivot Layout data service scans the column containing your attribute names, creates a new column for each attribute, and sets the value in that column as stated in your value column. As a result, each product in your feed appears only once as a single row: UUID-24c37b2d-57bd-2d70-a767-60748514c309

UUID-24c37b2d-57bd-2d70-a767-60748514c309

In the example above, only one column identifies each product, *id*. The Pivot Layout data service can also work with multiple columns that uniquely identify products. The benefits of using the Pivot Layout data service are as follows: * The new attribute columns are instantly available in Dataflow, and you can map them to your intermediate and export stages. * You don't need to transform your import files manually to represent data in the format required by your export channels. * You can apply lists on the data service setup page to let the platform change the attribute names and values in bulk according to a necessary taxonomy. Prerequisites [#prerequisites] To use the Pivot Layout data service, you need to: . Import your data into a Productsup site. . Make sure your imported data has product-identifying columns, a column containing attribute names, and a column containing values corresponding to those attributes. Add the Pivot Layout data service [#add-the-pivot-layout-data-service] Go to **Data Services** from your site's main menu and select **ADD SERVICE**. Search for *Pivot Layout*, select **Add**, and give it a desired name. UUID-2ba9757a-b898-d858-f814-e2005c4e942a

UUID-2ba9757a-b898-d858-f814-e2005c4e942a

Choose *Import* in **Service Data Level** and select **Add**. In **Rows**, choose the columns that uniquely identify your products. You can select multiple columns. The order of the selected columns influences the order of rows in your feed. In **Attribute name column**, choose the column that contains the names of your product attributes. The platform scans this column to create a new column for each attribute name. Optionally, use the drop-down menu **Attribute name mapping list (optional)** to choose a list created in *Lists* if you need to change your current attribute names in bulk.See [Lists](/docs/help-center/map-and-optimize-your-data/lists) to create and set up a taxonomy mapping or replacement list. In **Attribute values column**, choose the column that contains the values of your product attributes. The platform scans this column to fill the cells of the new attribute columns with their corresponding values for each unique product. Optionally, use the drop-down menu **Attribute values mapping list (optional)** to choose a list created in *Lists* if you need to change your current attribute values in bulk.See [Lists](/docs/help-center/map-and-optimize-your-data/lists) to create and set up a taxonomy mapping or replacement list. Select **Save**. For the platform to process a new data service, select **Import** or **Run** in the top-right corner of your site's view\.As soon as the site finishes processing your data, you can see the new structure of your data at the import stage in Data View and Dataflow. If you can't see the columns the Pivot Layout data service added to your feed in Data View, ensure the platform hasn't hidden them: Go to **Data View** from your site's main menu and choose *Import* in the drop-down list on your left. Select the menu icon on the right and then select the eye icon. Find the hidden attributes in the list and select the eye icon next to each attribute you want Data View to display. Close the pop-up menu. If your data feed has more columns than you defined in the data service setup fields **Rows**, **Attribute name column**, and **Attribute values column**, the platform removes these columns from your restructured feed. To see warnings about column deletion, you can open the Run log panel by selecting its icon in the top-right corner of your view while the site is running. UUID-561c2268-3fb6-38ad-f690-b69e67011557

UUID-561c2268-3fb6-38ad-f690-b69e67011557

Edit the Pivot Layout data service [#edit-the-pivot-layout-data-service] After saving the setup of the Pivot Layout data service, you can only edit the lists used for replacing your attribute names and values. If your newly selected list has a different set of attributes, the platform adds new columns for new attributes and deletes the columns of the attributes that aren't on the list anymore. Any changes in the lists affect the columns after each site run. The fields **Rows**, **Attribute name column**, and **Attribute values column** are non-editable. If you need to edit these fields in a data service you already saved, you should delete the current data service, run the platform to reset the imported data, and create a new data service. See [Delete the Pivot Layout data service](#section-idm243319908032630). To edit the Pivot Layout data service: Go to **Data Services** from your site's main menu. Search for your data service. Select the cogwheel icon (**⚙**) next to the desired data service and choose the needed lists. Select **Save**. For the platform to process an edited data service, select **Import** or **Run** in the top-right corner of your site's view. Delete the Pivot Layout data service [#delete-the-pivot-layout-data-service] Go to **Data Services** from your site's main menu. To stop a data service from restructuring your feed without deleting the data service itself, you can choose the pause icon next to the desired data service. Select the cogwheel icon UUID-e19d1a4d-9ea0-6607-b841-3cd22c1101e2

next to the desired data service. In the **Danger Area** panel, select **Remove this service**. Select **Yes**. # Split parent items to create product variants with the Split Variants data service import { Callout } from "fumadocs-ui/components/callout"; import { Step, Steps } from "fumadocs-ui/components/steps"; Introduction [#introduction] If a product attribute in your feed contains all product variants, such as sizes or colors, in one (1) row, you can split these product variants into separate rows using the Split Variants data service. The Split Variants data service is only available for the import stage. For example, the following feed contains the *size* attribute that stores all sizes of each product in the same row, separated by a comma: | parent\_id | size | title | | ---------- | ------ | ---------- | | 1 | XS,S,L | t-shirt | | 2 | XS,M | polo shirt | After applying the Split Variants data source with the **Mutliply Variants** mode, each size takes a separate row, and the feed looks as follows: | parent\_id | size | title | | ---------- | ---- | ---------- | | 1 | XS | t-shirt | | 1 | S | t-shirt | | 1 | L | t-shirt | | 2 | XS | polo shirt | | 2 | M | polo shirt | The Split Variants data service creates more rows in your feed, increasing the number of imported and maintained products. This service is the opposite of the Merge Variants data service. See [Combine product variants into one parent item with the Merge Variants data service](/docs/help-center/map-and-optimize-your-data/data-services/combine-product-variants-into-one-parent-item-with-the-merge). Prerequisites [#prerequisites] To set up the Split Variants data service, you need: . A unique item identifier. See [Set a unique item identifier](/docs/help-center/import-data-feeds/import-your-data-into-productsup/set-a-unique-item-identifier). . Products in your feed that contain variants in one of their attributes. Add the Split Variants data service [#add-the-split-variants-data-service] Go to **Data Services** from your site's main menu and select **ADD SERVICE**. Search for *Split Variants* and select **Add**. UUID-5bdc9edf-6007-a034-8ed3-522d0e2feb66

UUID-5bdc9edf-6007-a034-8ed3-522d0e2feb66

Give the service a desired name and column prefix, and select **Add**. By default, `___service_split` is the column prefix. Select **Add Split Column**. Select the column that you want to split in **Source Columns**. The source column is typically the *parent\_id* or the *item\_group\_id* attribute. In **Delimiter**, enter the character that currently separates the values in the source column. In **Split mode**, select from one of the options. See [Set up split modes](#section-idm4589942687297633671130114533) for more information. Select **Save**. UUID-eeb1a757-140b-3ac9-08f9-defabf5dc8a0

UUID-eeb1a757-140b-3ac9-08f9-defabf5dc8a0

To run the data service, select **Import** in the top-right corner of your site's view. Set up split modes [#set-up-split-modes] You can select from three (3) different modes to split your product variants: * **Multiply Variants** mode creates separate rows for each product variant. * **Aggregate Variants** mode creates separate rows for each product variant combining values from different columns according to their position in a row. * **Static Variants** appends and/or prepends static strings to the attribute values creating a new row for each added variant. Multiply Variants split mode [#multiply-variants-split-mode] The Multiply Variants split mode lets you select one (1) or more source attributes to split them into new rows with all possible combinations of product variants. For example, you have the following feed: | id | size | color | | --- | ----- | -------- | | 123 | S,M,L | blue,red | To split product variants of products by sizes and colors into separate rows, use the following setup: . Select **Add Split Column**. . Select `size` and `color` in **Source Columns** and enter a comma (`,`) in **Delimiter**. Using Multiple Variants, you must add one (1) or several columns in **Source Columns**. . Select **Multiply Variants** in **Split mode**. UUID-dfc2c564-d52f-4835-25cf-0f7186871c2a

UUID-dfc2c564-d52f-4835-25cf-0f7186871c2a

. Select **Import** in the top-right corner of your site's view to let the platform split the product variants into separate rows as follows: | id | size | color | | --- | ---- | ----- | | 123 | S | red | | 123 | M | red | | 123 | L | red | | 123 | S | blue | | 123 | M | blue | | 123 | L | blue | Aggregate Variants split mode [#aggregate-variants-split-mode] The Aggregate Variants split mode lets you split two (2) or more columns into separate product variant rows combining values by their position in the source columns. For example, you have the following feed: | id | country | food | | --- | ----------------------------- | ---------------------- | | 123 | France,Germany,United Kingdom | cheese,sausage,pudding | To split variants of products into separate rows where each row contains a country and its corresponding food, use the following setup: . Select **Add Split Column**. . Select `country` and `food` in **Source Columns** and enter a comma (`,`) in **Delimiter**. Using Aggregate Variants, you must add at least two (2) columns in **Source Columns**. . Select **Aggregate Variants** in **Split mode**. UUID-d9c83afc-5af5-bd60-b91c-49f27c8563de

UUID-d9c83afc-5af5-bd60-b91c-49f27c8563de

. Select **Import** in the top-right corner of your site's view to let the platform split the product variants into separate rows as follows: | id | size | color | | --- | -------------- | ------- | | 123 | France | cheese | | 123 | Germany | sausage | | 123 | United Kingdom | pudding | Static Variants split mode [#static-variants-split-mode] The Static Variants split mode lets you append and/or prepend static variants to the attribute values creating a new row for each variant. For example, you have the following feed: | id | title | | --- | ---------------------- | | 123 | My product is the best | To append the static variants `Alpha`, `Bravo`, and `Charlie` to the *title* attribute, use the following setup: . Select **Add Split Column**. . Select `title` in **Source Columns**. The Static Variants split mode is only available if you select one (1) column in **Source Columns**. . Select **Static Variants** in **Split mode**. UUID-d9c83afc-5af5-bd60-b91c-49f27c8563de

. Enter variants separated by a comma in **Comma separated list of variants**. . In **Variant Format**, enter how you want the data service to add your variants to the attribute. By default, the value is `{{ value }} {{ variant }}`, which means that your variant appears after the title value. . Select **Save**. UUID-bf4da1b1-b85b-e4b7-757f-d24a700fa562

UUID-bf4da1b1-b85b-e4b7-757f-d24a700fa562

. Select **Import** in the top-right corner of your site's view to let the platform split the product variants into separate rows as follows: | id | title | | --- | ------------------------------ | | 123 | My product is the best Alpha | | 123 | My product is the best Bravo | | 123 | My product is the best Charlie | Edit the Split Variants data service [#edit-the-split-variants-data-service] Go to **Data Services** from your site's main menu. Search for your data service. Select the cogwheel icon (**⚙**) next to the desired data service to edit settings. Select **Save**. Delete the Split Variants data service [#delete-the-split-variants-data-service] Go to **Data Services** from your site's main menu. Select the cogwheel icon UUID-e19d1a4d-9ea0-6607-b841-3cd22c1101e2

next to the desired data service. In the **Danger Area** panel, select **Remove this service**. Select **Yes**. # Data Services import { Callout } from "fumadocs-ui/components/callout"; Introduction [#introduction] A Productsup data service is a tool that lets you enhance and restructure your product feed using the Data Services feature. This section covers the data services that let you restructure and optimize your product data. See [Enhance your import data through Data Services](/docs/help-center/import-data-feeds/enhance-your-import-data-through-data-services) for more information on the data services that help to enhance your product feed with additional data. Some data services are available at an additional cost in all platform editions. If you are unsure whether the desired data service is free, reach out to your Customer Success Manager or contact [support@productsup.com](mailto:support@productsup.com). All Productsup data services fall into one of the following categories: * *ID Generators* - Enhance your products with columns containing unique product or category IDs. * *Crawlers* - Let you crawl your product or image links to extract additional product data or image properties and add them to your site. * *Merge/Split Feed* - Let you manage product variants by splitting a product into multiple product variants or merging multiple product variants into one product. * *Implode/Explode/Group Columns* - Let you manage your columns by merging and splitting them. They also help you manipulate your column values to enhance the feed with more data. * *Exclude Rows from Import* - Remove duplicate products from your feed based on product IDs. * *Travel Services* - Enrich your feed with geographical data and information related to weather and travel. * *Pricing* - Let you add price comparison data to your feed. * *AI Services* - Use machine learning to transform or enrich your data by, for example, removing image backgrounds or detecting image colors. Prerequisites [#prerequisites] All data services require you to: * Add a unique item identifier in your site. See [Set a unique item identifier](/docs/help-center/import-data-feeds/import-your-data-into-productsup/set-a-unique-item-identifier) for more information. The rest of the prerequisites are individual to each data service. You can see the relevant prerequisites in a document dedicated to the data service of your interest. See [Arrange the processing order of your data services](/docs/help-center/import-data-feeds/enhance-your-import-data-through-data-services#section-idm4653092417062433346529892231) to set up the order according to which Productsup should execute your data services. # Group data across multiple rows with the Group Attributes data service import { Callout } from "fumadocs-ui/components/callout"; import { Step, Steps } from "fumadocs-ui/components/steps"; The *Group Attributes* data service lets you create a new attribute in your site to group values from a chosen attribute for all products that have the same value in a grouping attribute. For example, for all products in your site that have the same value in the grouping attribute **id**, you can create a new attribute **\_\_\_grouped** and populate it in the following ways: * Add all values of a chosen attribute. See [Concat method](#N1684769874080). * Count values of a chosen attribute and output the result. See [Count method](#N1684769892570). * Identify and save the highest or lowest value in a chosen attribute. See [Max and Min methods](#N1684769951508). * Produce a sum of all values of a chosen attribute. See [Sum method](#N1684769929250). The service works based on the SQL function `GROUP BY`. See [SQL Tutorial](http://www.sql-tutorial.net/sql-group-by.asp) for more information. The *Group Attributes* data service is available for the import and intermediate stages. Prerequisites [#prerequisites] To set up the *Group Attributes* data service, you need: . A unique item identifier. See [Set a unique item identifier](/docs/help-center/import-data-feeds/import-your-data-into-productsup/set-a-unique-item-identifier) for more information. Add the Group Attributes data service [#add-the-group-attributes-data-service] Go to **Data Services** from your site's main menu and select **Add Service**. Search for *Group Attributes*, select **Add**, and rename the data service as desired. UUID-0a06923f-3904-fb5d-bf2c-e5dc5ec70103

UUID-0a06923f-3904-fb5d-bf2c-e5dc5ec70103

Choose the stage containing the attributes you want to group in **Service Data Level** and select **Add**. This takes you to the data service setup: UUID-ec7d6652-352c-2151-3020-7c274ba14c15

UUID-ec7d6652-352c-2151-3020-7c274ba14c15

Select the attribute containing the values you wish to group from the drop-down menu **Attribute containing the values**. If you choose **Import** in **Service Data Level** in [see the relevant section](#step-idm351683120570619), the drop-down menu **Attribute containing the values** displays the attributes of your import stage. If you choose **Intermediate**, the drop-down menu shows your intermediate-stage attributes. In the drop-down menu **Import attribute you want to group by**, select the import-stage attribute which should determine your value-grouping range. If multiple products have the same value in this grouping attribute, the data service analyzes the values of these products in the attribute chosen in [see the relevant section](#step-idm353366241141236) and groups the values of these products in a newly-created attribute named in [see the relevant section](#N1739875634135) by performing the action chosen in [see the relevant section](#N1739875407524)To choose several grouping attributes, hold the *CTRL* (or *CMD*) key while selecting.In **Import attribute you want to group by**, you can't choose an attribute that contains only empty values. If you do so and try to save the data service setup, the platform shows an error and prompts you to change your attribute selection: UUID-8ff2eacb-577c-86a4-c872-52d1d4e6687a

UUID-8ff2eacb-577c-86a4-c872-52d1d4e6687a

Enter the desired name of the new attribute in **Result attribute**.The system creates a new attribute to store the grouped data without overwriting your existing attributes. The platform prepends the attribute name specified in this field with the prefix you set in [see the relevant section](#N1683194128497). Select the grouping method from the **Method** drop-down menu. For the Concat method only: In **Delimeter**, select the delimiter that separates the grouped values in the new attribute. Activate **Concat unique** if you don't want to display duplicate values. Select **Save**. For the platform to process a new data service, select **Run** in the top-right corner of your site's view. Output examples of different grouping methods [#output-examples-of-different-grouping-methods] While setting up the data service, you can select from five different data-grouping methods in the **Method** drop-down menu: * *Concat* * *Count* * *Max* * *Min* * *Sum* Here is a sample feed we can use to show how each grouping method works: | id | item\_group\_id | stock | size | color | discount\_in\_percent | | -- | --------------- | ----- | ---- | ----- | --------------------- | | 1 | 123 | 4 | S | red | 10 | | 2 | 123 | 2 | S | blue | 15 | | 3 | 123 | 1 | L | blue | 25 | | 4 | 456 | 5 | 38 | black | 7 | | 5 | 456 | 4 | 38 | blue | 15 | | 6 | 456 | 7 | 38 | green | 5 | | 7 | 456 | 2 | 40 | green | 10 | Concat method [#concat-method] Use the **Concat** method to combine all values from different products in one attribute. Example: To concat sizes for products with the same **item\_group\_id**, use the following setup: * **Attribute containing the values**: `size` * **Import attribute you want to group by**: `item_group_id` * **Result attribute**: `concat_sizes` * **Method**: *Concat* * **Delimiter**: *,COMMA* * **Concat unique**: off Using this setup, the system groups all sizes of the products with the same **item\_group\_id** in a newly created **\_\_\_concat\_sizes** attribute: | id | item\_group\_id | stock | size | color | discount\_in\_percent | \_\_\_concat\_sizes | | -- | --------------- | ----- | ---- | ----- | --------------------- | ------------------- | | 1 | 123 | 4 | S | red | 10 | S,S,L | | 2 | 123 | 2 | S | blue | 15 | S,S,L | | 3 | 123 | 1 | L | blue | 25 | S,S,L | | 4 | 456 | 5 | 38 | black | 7 | 38,38,38,40 | | 5 | 456 | 4 | 38 | blue | 15 | 38,38,38,40 | | 6 | 456 | 7 | 38 | green | 5 | 38,38,38,40 | | 7 | 456 | 2 | 40 | green | 10 | 38,38,38,40 | The system combines the data without any spaces between characters. Count method [#count-method] Use the **Count** method to count the number of product variations. Example: To count the number of product variations with the same **item\_group\_id**, use the following setup: * **Attribute containing the values**: `item_group_id` * **Import attribute you want to group by**: `item_group_id` * **Result attribute**: `count_variations` * **Method**: *Count* Using this setup, the system counts all product variations with the same **item\_group\_id** and records the result in a newly created **\_\_\_count\_variations** attribute: | id | item\_group\_id | stock | size | color | discount\_in\_percent | \_\_\_count\_variations | | -- | --------------- | ----- | ---- | ----- | --------------------- | ----------------------- | | 1 | 123 | 4 | S | red | 10 | 3 | | 2 | 123 | 2 | S | blue | 15 | 3 | | 3 | 123 | 1 | L | blue | 25 | 3 | | 4 | 456 | 5 | 38 | black | 7 | 4 | | 5 | 456 | 4 | 38 | blue | 15 | 4 | | 6 | 456 | 7 | 38 | green | 5 | 4 | | 7 | 456 | 2 | 40 | green | 10 | 4 | Max and Min methods [#max-and-min-methods] Use the **Max** or **Min** methods to find and display the highest or lowest value. Example: To return the highest discount among all products with the same **item\_group\_id**, use the following setup: * **Attribute containing the values**: `discount_in_percent` * **Import attribute you want to group by**: `item_group_id` * **Result attribute**: `max_discount` * **Method**: *Max* Using this setup, the system compares discounts of all products with the same **item\_group\_id** and records the highest value in a newly created **\_\_\_max\_discount** attribute: | id | item\_group\_id | stock | size | color | discount\_in\_percent | \_\_\_max\_discount | | -- | --------------- | ----- | ---- | ----- | --------------------- | ------------------- | | 1 | 123 | 4 | S | red | 10 | 25 | | 2 | 123 | 2 | S | blue | 15 | 25 | | 3 | 123 | 1 | L | blue | 25 | 25 | | 4 | 456 | 5 | 38 | black | 7 | 15 | | 5 | 456 | 4 | 38 | blue | 15 | 15 | | 6 | 456 | 7 | 38 | green | 5 | 15 | | 7 | 456 | 2 | 40 | green | 10 | 15 | Sum method [#sum-method] Use the **Sum** method to return the numerical sum of products matching the selected conditions. Example: To sum the stock for products with the same **item\_group\_id** and **color**, use the following setup: * **Attribute containing the values**: `stock` * **Import attribute you want to group by**: `item_group_id` and `color` * **Result attribute**: `stock_sum` * **Method**: *Sum* Using this setup, the system sums the values of all products with the same **item\_group\_id** and **color** and records the numbers in a newly created **\_\_\_stock\_sum** attribute: | id | item\_group\_id | stock | size | color | discount\_in\_percent | \_\_\_stock\_sum | | -- | --------------- | ----- | ---- | ----- | --------------------- | ---------------- | | 1 | 123 | 4 | S | red | 10 | 4 | | 2 | 123 | 2 | S | blue | 15 | 3 | | 3 | 123 | 1 | L | blue | 25 | 3 | | 4 | 456 | 5 | 38 | black | 7 | 5 | | 5 | 456 | 4 | 38 | blue | 15 | 4 | | 6 | 456 | 7 | 38 | green | 5 | 9 | | 7 | 456 | 2 | 40 | green | 10 | 9 | Edit the Group Attributes data service [#edit-the-group-attributes-data-service] Go to **Data Services** from your site's main menu. Change the settings of the needed data service: 1. To deactivate a data service, choose the pause icon next to the desired data service. 2. Select the cogwheel icon (**⚙**) next to the desired data service to edit other settings and select **Save**. Delete the Group Attributes data service [#delete-the-group-attributes-data-service] Go to **Data Services** from your site's main menu. To stop a data service from affecting your feed without deleting the data service itself, you can choose the pause icon next to the desired data service. Select the cogwheel icon UUID-e19d1a4d-9ea0-6607-b841-3cd22c1101e2

next to the desired data service. In the **Danger Area** panel, select **Remove this service**. Select **Yes**. # Merge multiple columns with the Implode Columns service import { Callout } from "fumadocs-ui/components/callout"; import { Step, Steps } from "fumadocs-ui/components/steps"; Introduction [#introduction] If you wish to unite multiple columns with corresponding values into one column, you can merge these columns using the Implode Columns data service. For example, you can merge the varying color columns in the following data source: | id | color\_1 | color\_2 | color\_3 | | --- | -------- | -------- | -------- | | `1` | `red` | `green` | `blue` | | `2` | `gray` | `black` | `blue` | After applying the Implode Columns data service, your data may look similar to the following: | id | color\_1 | color\_2 | color\_3 | \_\_\_imploded\_all\_colors | | --- | -------- | -------- | -------- | --------------------------- | | `1` | `red` | `green` | `blue` | `red,green,blue` | | `2` | `gray` | `black` | `blue` | `gray,black,blue` | The Implode Columns data service is available for the import and intermediate stages. Prerequisites [#prerequisites] To set up the Implode Columns data service, you need: . A unique item identifier. See [Set a unique item identifier](/docs/help-center/import-data-feeds/import-your-data-into-productsup/set-a-unique-item-identifier) for more information. . A number of relevant columns in your feed that you want to merge. Add the Implode Columns data service [#add-the-implode-columns-data-service] Go to **Data Services** from your site's main menu, and select **Add data service**. Search for *Implode Columns*, select **Add**, and give it a desired name and column prefix.By default, `___imploded` is the column prefix. UUID-0532cd10-bc89-b805-620f-963255af84af

UUID-0532cd10-bc89-b805-620f-963255af84af

Choose the stage containing the columns you want to merge in **Service Data Level** and select **Add**. Select the columns you want to implode from the **Columns that you want to use as input** drop-down list or write the column names directly into the input text field.If you chose **Import** in [see the relevant section](#step-idm243349476307592), the drop-down list **Columns that you want to use as input** displays the columns of your import stage. If you chose **Intermediate** in that field, the drop-down list contains your intermediate-stage columns. * Alternatively, you can check the **Use regex** box and enter a valid PHP regex into the input text field. See [Rule box category Use regular expressions](/docs/help-center/add-a-rule-box/find-the-needed-rule-box-category/rule-box-category-use-regular-expressions) and [Pattern Syntax](https://www.php.net/manual/en/reference.pcre.pattern.syntax.php) for more information. In the field **Column that will be created and populated with the selected columns above**, enter a name for your merged output column. The platform uses the column prefix and the name you specify in this step to produce the full name of the new column. For example, if you use the default column prefix `___imploded` and the output column name is `all_colors`, the full name of the new imploded column is `___imploded_all_colors`. In **Delimiter**, select the delimiter that separates the values of different columns once you merge them.You can choose from a list of popular delimiters or enter a custom delimiter in the input text field that appears after selecting **Custom**. Select **Save**. For the platform to process a new data service, select **Import** or **Run** in the top-right corner of your site's view. If you can't see the columns that the Implode Columns data service added to your feed in Data View, ensure the platform hasn't hidden them: Go to **Data View** from your site's main menu and choose the relevant stage or export in the drop-down list on your left. Select the menu icon on the right and then select the eye icon. Find the attributes in the list that use the custom prefix `___imploded` and select the eye icon next to each attribute you want Data View to display. Close the pop-up menu. The naming of the attributes created by the Implode Columns data service depends on the column prefix you chose in [see the relevant section](#step-idm243349476184336). The attribute names the data service generates always start with three underscores (`___`), which means the platform doesn't send those attributes to your export channels. You can add multiple instances of this data service by repeating these steps. The platform shows all imploded columns and their source columns in a table at the bottom of the data service setup page. UUID-7504ff24-18d3-ffdd-8305-98246c6271ba

UUID-7504ff24-18d3-ffdd-8305-98246c6271ba

Edit the Implode Columns data service [#edit-the-implode-columns-data-service] Go to **Data Services** from your site's main menu. Search for your data service. Select the cogwheel icon (**⚙**) next to the desired data service to edit settings. Select **Save**. Delete the Implode Columns data service [#delete-the-implode-columns-data-service] Go to **Data Services** from your site's main menu. Select the cogwheel icon UUID-e19d1a4d-9ea0-6607-b841-3cd22c1101e2

next to the desired data service. In the **Danger Area** panel, select **Remove this service**. Select **Yes**. # Combine product variants into one parent item with the Merge Variants data service import { Callout } from "fumadocs-ui/components/callout"; import { Step, Steps } from "fumadocs-ui/components/steps"; The *Merge Variants* data service lets you combine all attribute values of all product variants with the same ID into one item. Alternatively, you can use any attribute other than an ID as a basis to merge your product variants. The *Merge Variants* data service is available for the import stage only. For example, if you have product variants in your data feed, it may look similar to this: | **product\_id** | **variant\_id** | **size** | **color** | **discount\_code** | | --------------- | --------------- | -------- | --------- | ------------------ | | *1* | *1-1* | *XS* | *green* | | | *1* | *1-2* | *S* | *green* | *SALE20* | | *1* | *1-3* | *L* | *blue* | | | *2* | *2-1* | *XS* | *red* | | | *2* | *2-2* | *M* | *yellow* | | You can merge all product variants with the same value in the **product\_id** attribute. This means that, instead of several product variants with the same product ID, you create one item in your feed and combine attribute values for all relevant product variants. After applying the *Merge Variants* data service, your feed can look as follows: | **product\_id** | **variant\_id** | **size** | **color** | **discount\_code** | | --------------- | --------------- | -------- | ------------ | ------------------ | | *1* | `1-1,1-2,1-3` | `XS,S,L` | `green,blue` | `,SALE20,` | | *2* | `2-1,2-2` | `XS,M` | `red,yellow` | `,` | This example illustrates removing duplicate values for each merged attribute. You can also keep them in your merged values. Prerequisites [#prerequisites] To set up the *Merge Variants* data service, you need: . A unique item identifier. See [Set a unique item identifier](/docs/help-center/import-data-feeds/import-your-data-into-productsup/set-a-unique-item-identifier) for more information. Add the Merge Variants data service [#add-the-merge-variants-data-service] Go to **Data Services** from your site's main menu and select **Add Service**. Search for *Merge Variants*, select **Add**, and rename the data service as desired. UUID-4d830efd-513c-d31f-8ec2-960bf87ab9c3

UUID-4d830efd-513c-d31f-8ec2-960bf87ab9c3

Select **Add** to go to the data service setup page: UUID-d6888636-28b1-e7eb-f986-564f6a182b9b

Select **Add Merge Column** to open a pop-up window. In the drop-down menu **Source Columns**, select the import-stage attribute that should be the basis for merging your product variants.In **Source Columns**, you can't choose an attribute if 100% of its values are empty. If you do so and try to save the data service setup, the platform shows an error and prompts you to change your attribute selection: UUID-a0dbc398-9ac4-548a-1fe3-d099f057fa03

UUID-a0dbc398-9ac4-548a-1fe3-d099f057fa03

In **Delimeter**, select the delimiter that should separate your combined values in the merged attributes. If you don't select a delimiter, the platform merges values without separating them with any characters. Select **Add** to close the pop-up window and return to the data service setup page. If you don't want to display duplicate values in the merged attributes, leave **Concat unique** checked. Uncheck this box to keep duplicates in the merged attributes. For the platform to process the new data service, select **Import** in the top-right corner of your site's view. Edit the Merge Variants data service [#edit-the-merge-variants-data-service] Go to **Data Services** from your site's main menu. Change the settings of the needed data service: 1. To deactivate a data service, choose the pause icon next to the desired data service. 2. Select the cogwheel icon (**⚙**) next to the desired data service to edit other settings. Delete the Merge Variants data service [#delete-the-merge-variants-data-service] Go to **Data Services** from your site's main menu. To stop a data service from affecting your feed without deleting the data service itself, you can choose the pause icon next to the desired data service. Select the cogwheel icon UUID-e19d1a4d-9ea0-6607-b841-3cd22c1101e2

next to the desired data service. In the **Danger Area** panel, select **Remove this service**. Select **Yes**. # Information security and data protection import { Callout } from "fumadocs-ui/components/callout"; At Productsup, customer data confidentiality and the service's reliability are essential. Productsup is committed to a comprehensive company-wide information security program and continues to participate in independent external security validations, such as being certified according to ISO/IEC 27001. Authentication [#authentication] With SAML 2.0-based single sign-on (SSO), we allow our customers to access our service through an identity provider (IDP) of their choice. Our platform has strict requirements for password complexity and uses two-factor authentication (2FA) to provide an extra layer of security. Data Centers [#data-centers] Our servers are hosted at state-of-the-art data center parks that provide excellent and environmentally friendly infrastructure. These data centers meet strict safety requirements and hold certifications such as ISO/IEC 27001. Our cloud hosting provider is also certified for various security and privacy standards, including ISO 27001, ISO 27017, ISO 27018, SOC1, SOC2, and SOC3. DDoS Protection [#ddos-protection] Our hosting provider's automated DDoS protection system recognizes almost all attack patterns in advance, allowing it to block attacks and thwart most of them effectively. It uses the latest hardware appliances and sophisticated perimeter security technologies, providing first-rate protection against large-scale DDoS attacks. Incident Response [#incident-response] We have established policies and procedures for responding to potential security incidents. Our dedicated incident response team manages all security incidents. In the event of an incident, affected customers will be informed and quickly updated by our support team while our teams fix the issue. In addition, the operational status of our platform components is always available for our customers under [https://status.productsup.io/](https://status.productsup.io/). Privacy [#privacy] Fulfilling our data privacy and security commitments is essential to us. Therefore, we have ensured that our processes, data processing agreements (DPAs), and other protections in place comply with GDPR requirements. Our compliance with GDPR requirements is regularly audited through our external DPO Nils Möllers (Keyed GmbH). Reliability [#reliability] To ensure the safety of our customers' data, we perform incremental backups every hour and full backups every day, storing them both on- and off-site. We test our data restoration procedure regularly. If needed, we can smoothly switch to another infrastructure region, as core components are redundantly deployed across two geographically separated hosting locations. Secure Development [#secure-development] At Productsup, security is managed throughout every stage of our software development lifecycle (SDLC). This involves the application of development procedures and secure coding principles, consideration of OWASP Top 10 vulnerabilities, and fully automated code reviews with strict quality gates, among others. Vulnerability Scanning [#vulnerability-scanning] Productsup uses advanced network and web application vulnerability scanners to identify vulnerabilities and potential security threats. Identified vulnerabilities are assessed by our development and infrastructure operations team and remediated subsequently. In addition, we regularly undergo external security assessments through independent third parties. Encryption [#encryption] Our service uses HTTPS with modern TLS (1.2) implementations only and strong ciphers to encrypt all data while in transit. For sensitive data at rest, column-level encryption is applied (AES256), and user credentials are salted and hashed. Exporting data to third parties A necessary aspect of feed management is sending product feeds to data to external channels such as Google, Facebook, Amazon, and hundreds more. The method of integration with these channels depends on the use case. Each external channel will receive the data over a destination. For example, this could be an FTP Server or an API connection. The encryption varies, depending on the destination. You are advised to make yourself aware of the type of encryption of these destinations before using them. Encryption types of the most popular Productsup destinations Here is a brief list of some of the most popular Productsup destinations and appropriate encryption methods and security information: | Destination | Encryption method | Security protocol | | -------------------------- | ------------------------------------------------- | ----------------- | | Productsup Server | TLS1.2 | HTTPS | | Productsup Platform API | TLS, SSLv3 | HTTPS | | Google Merchant Center API | TLS, SSLv3 | HTTPS | | Facebook Marketing API | TLS, SSLv3 | HTTPS | | SFTP Server | AES, 3DES, or other, depending on the target host | SSH | | Productsup SFTP Server | aes256-ctr, aes192-ctr,aes128-ctr | SSH | | FTP Server | None | FTP | | SAP Product Content Hub | TLS, SSLv3 | HTTPS | SAP Product Content Hub data is sent through the Productsup Platform API. # Supported browsers The Productsup platform and the Content Portal run best on the latest versions of Chrome, Firefox, Safari, and Edge (Chromium-based). See the following links for the latest browser versions: * [Firefox](https://www.mozilla.org/en-US/firefox/) * [Chrome](https://www.google.com/chrome/) * [Safari](https://www.apple.com/safari) * [Edge (Chromium)](https://www.microsoft.com/en-us/edge) If you experience any issues displaying the platform properly, contact the Support Team at [support@productsup.com](mailto:support@productsup.com). Include a screenshot of the issue and list your browser version. See [Report a platform-related issue to Support](/docs/help-center/best-practices/report-a-platform-related-issue-to-support). # Product feed management and automation benefits Introduction [#introduction] Automating product feed allows you to keep product data up-to-date across multiple channels automatically. Product feed, also known as a product data feed or data feed, refers to product information files. These feed files vary; see the following list for some commonly-used formats: * CSV - Comma-separated value * JSON - JavaScript Object Notation * TXT - Text files * XLS - Excel file spreadsheet * XML - Extensible Markup Language Marketers, for instance, use product feed across sales and marketing channels to communicate product data from one end to another. This product data can contain product size information, colors, availability, product images, etc. Online merchants use this data to display product listings to customers in the E-commerce space accurately. Depending on the marketplace, the formatting and structure of the product feed typically follow guidelines set by any specific channel. Automate the display of product feed across several channels to reduce the amount of time needed to optimize data feeds across all channels. Productsup [#productsup] Productsup is a SaaS feed management software solution for data feed integration, optimization, and distribution. Productsup lets you manage product feed by automating the import, optimization, and export of product data feed. You can import product data feed from multiple sources, including API integrations. From spreadsheets to product information management (PIM) solutions, integrate product data feed in several formats and sizes. Automation use and benefits [#automation-use-and-benefits] Productsup offers you a range of solutions to efficiently manage product feed, integrate marketplaces, onboard vendors, suppliers, third-party data providers, and use with product content syndication or PIM platforms. Managing product feed with Productsup helps marketplaces and brands structure and enhance their product content across thousands of retail and digital channels. Automating pricing updates and inventory, along with data mapping, defining product categories, scheduling imports, and even excluding products for export, is where automation becomes most beneficial. And the importation and exportation of product feed is the most efficient way to communicate this data seamlessly throughout multiple channels. High-quality product feed [#high-quality-product-feed] Channels rely on product feeds to display product listings to shoppers reliably. The higher the quality of your product feed means the more accessible your products are to vendors and clients by matching merchant-set algorithms. Accuracy [#accuracy] Product feed must be accurate, as marketplaces and channels rely on accurate data to display your products. Marketplaces can be a highly competitive space, where inaccuracies in your data feed may cause a loss of clients. Save time and money [#save-time-and-money] Save time by automating updates and the processing of your data feeds. You’ll also save money by managing your product feed data from one platform. Productsup lets your marketing campaigns reach their maximum potential, reducing waste on ad spend, costs-per-clicks, lost conversions, etc. Get started [#get-started] See [Set up User Management](/docs/help-center/get-started/user-management/set-up-user-management) for getting started in the Productsup platform. # Network information import { Callout } from "fumadocs-ui/components/callout"; All requests originate from the IP ranges listed below. **These ranges belong exclusively to Productsup** — no other organization sends traffic from them — so there is no need to configure a proxy in the platform. You must allowlist the **entire range**, not a single IP address. Productsup might use any address in these blocks, and the specific source IP for any given request is not stable. Productsup IP ranges [#productsup-ip-ranges] * IPv4: `185.252.140.0/22` * IPv6: `2a13:7840::/29` For more information about the Productsup network, see [AS200249](https://www.peeringdb.com/net/31954) on PeeringDB. CIDR and netmask notation [#cidr-and-netmask-notation] The `/22` and `/29` suffixes are CIDR notation — a compact way of writing a whole range of IP addresses in one line. Instead of listing every individual address, the suffix tells your firewall how large the range is. For example, `185.252.140.0/22` means "this address and the 1,023 addresses that follow it." Most modern firewalls, load balancers, and server tools accept this CIDR format directly — paste the range as written and you are done. Some older or simpler IPv4 tools split the range into two separate fields: a starting IP address and a *netmask* (sometimes called a *subnet mask*). The netmask is just a different way of describing the same range size. If your tool asks for both, use the values below. | CIDR | Starting IP | Netmask | | ------------------ | --------------- | --------------- | | `185.252.140.0/22` | `185.252.140.0` | `255.255.252.0` | IPv6 has no netmask equivalent — the protocol only uses CIDR notation (the `/29` prefix length). Enter `2a13:7840::/29` directly wherever your tool accepts an IPv6 range. # Error log codes and troubleshooting overview import { Callout } from "fumadocs-ui/components/callout"; Introduction [#introduction] Error log is the platform's feature that shows all the records of the errors and warnings that occurred during the import, export, or run. When you open a list of projects, you can see the number of errors and warnings per site. To see more details on them, open the error log. UUID-089ac0b7-88d7-be94-d0e6-832c3896a151

UUID-089ac0b7-88d7-be94-d0e6-832c3896a151

Locate Error Log [#locate-error-log] To access the error log: . Go to **Error Log** from your site's main menu. . Alternatively, in the site's **Dashboard**, select the **View error log** link in the Warnings and Errors section. The section displays the number of warnings and errors from the last run of the site and the severity level of the errors: *Medium*, *High*, or *Low*. UUID-1297c324-e395-010e-8772-3e9be79184c3

UUID-1297c324-e395-010e-8772-3e9be79184c3

Error log [#error-log] Error log displays all warnings and errors represented in a table view: UUID-5bdc83f3-a97e-f25d-7a34-1171b78e0955

* **Result** - indicates whether the process failed or generated warnings. * **Datetime** - shows the date and time when the process took place. * **Process ID** - shows a unique ID of every process such as import, export, or run. * **# Errors** - shows the number of times errors occurred. * **# Warnings** - shows the number of times warnings occurred. * **Purge** - lets you remove the entry from the list. You can open each record to see the details of every process, namely: UUID-350e8451-92d4-302e-ffa8-acd30c47a87a

UUID-350e8451-92d4-302e-ffa8-acd30c47a87a

* The orange labels for warnings and red labels for different severity levels for errors. * **Process** with its ID. You can select the arrow (**>**) icon for each entry to expand more details. * **Score** - the entry's rank, with 0 for the lowest and 1000 for the highest score. * **Code** - the error code by which you can search for the meaning of the error and find possible solutions in our Help Center. See [Error codes and possible solutions](#section-idm4558182659704032694736461777). * The **Snooze/Blacklist** drop-down menu with the following actions: * **Add to Blacklist** - an entry will not appear in your error history until you remove it from the blacklist. * **Snooze for 24 hours** - an entry won't appear in your error history for 24 hours. * **Snooze for 7 days** - an entry won't appear in your error history for 7 days. * **Snooze for 14 days** - an entry won't appear in your error history for 14 days. * **Snooze for 30 days** - an entry won't appear in your error history for 30 days. Beneath the error history, a table shows all snoozed or blacklisted errors, where you can unsnooze or remove from Blacklist the needed errors. UUID-07e8f524-091e-25c5-3e76-2bf1957e6605

UUID-07e8f524-091e-25c5-3e76-2bf1957e6605

Error codes and possible solutions [#error-codes-and-possible-solutions] If you run into an issue in the platform and see an error code or message in your error log, here's a summary of what they mean and some possible solutions to help you resolve the issue. | Error code | Description of error | Possible cause for error | Possible solution | | ---------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `10000` | `Download Failed or File is empty` | Downloading the feed from the source was unsuccessful or the file did not contain any data. This could indicate an invalid URL or error when during the file creation process. | - Make sure the Source URL, and if applicable, the username and password are all correct. - Make sure the Productsup Platform has permission to access this file. You may need to make sure the file has read permissions, and if the source server blocks outbound traffic, allowlist Productsup's IP ranges (see [Network information](/docs/help-center/get-started/productsup-fundamentals/network-information)). - Confirm the file is not empty, the file path and filename exist, and there are no typographical errors. | | `10008` | `Export not enabled for this site` | You have not mapped any Dataflow connections to the intermediate and or export stages yet. | Map your product data from the import stage to the export stage. | | `10012` | `FTP Transfer: Could not connect to host` | The FTP server has a firewall and only allows certain IP addresses to connect to it. | If the FTP server only allows certain IPs, allowlist Productsup's IP ranges (see [Network information](/docs/help-center/get-started/productsup-fundamentals/network-information)). | | `10018` | `No exports enabled yet` | You have not added export channels to the site yet.You have set **Upload** on all export channels to **Off**. | - Add an export channel. - Confirm that you set **Upload** to **On** for at least one export channel. | | `10031` | `Import File Empty or Missing CSV Header` | When you import XML files as data sources, you convert them into CSV files, which then lets you manipulate those products in the platform. Sometimes this conversion can go wrong and the generated CSV file is missing its header.This can also occur when you import a CSV, but you add XML settings in the setup and vice versa. | Contact [support@productsup.com](mailto:support@productsup.com). | | `10032` | `Failed to connect expanding CSV. Skipping.` | Your additional data source is unable to connect with the main data source correctly. Could be because the ID columns are incorrectly set. | Go to your additional data source settings and confirm that the ID columns are set correctly. To learn more about additional data sources and how to add them to your site, see [Enhance your products with additional data sources](/docs/help-center/import-data-feeds/import-your-data-into-productsup/enhance-your-products-with-additional-data-sources). All settings are case-sensitive. | | `10036` | `No files to upload to export destination since all products have been skipped. If this is not expected, please review your skipping rules` | Your skipping rule boxes have caused the platform to skip all of your products for this specific export channel. | Review your skipping rules to confirm that they are not skipping rows or products by accident. | | `10042` | `FTP Remote Folder not Found` | The platform is unable to find the folder on the FTP server to upload the exported feed file to. | In your export channel’s FTP server destination setup, confirm that both the **FTP Host** is correct and the FTP directory exists on the server. | | `10044` | `FTP Upload failed` | A generic error message, usually followed by a more detailed message, often indicating an error with the export destination. | Check the error log for more detailed information about the error message. | | `10055` | `Index column doesn't exist` | The column chosen to connect the main data source to an additional data source doesn't exist during import. It can happen possibly due to the order of operations of import, data services, and column creation. | - Go to your additional data source settings. - Confirm that the ID columns are set correctly. The column chosen as **ID Column From Your Main Feed** can't be a column created by a data service from this site. See [Enhance your products with additional data sources](/docs/help-center/import-data-feeds/import-your-data-into-productsup/enhance-your-products-with-additional-data-sources), to learn more about additional data sources and how to add them to your site. | | `10064` | This message uses the actual numbers and attribute names from your site. See an example:`50 items (100%) of column "shipping" contains an invalid shipping value` | Some of the products in the given attribute contain incorrect values. | - Check the warning message to find information about the export and attribute where your products contain incorrect values. - Go to the needed site and export, select **Analyze** in the column of the relevant attribute, and see what causes the problem with your values | | `10078` | `Unable to download Feed or Feed is empty` | - The data source was unable to download. - The data source contained no data. - The server containing the file uses a firewall and only allows specific IP addresses to connect to it. | - Confirm the source URL or host is correct, and if applicable, the username and password as well. - Confirm the Productsup platform has permission to access this file (read permissions). - Confirm the file is not empty. - If the server uses a firewall, allowlist Productsup's IP ranges (see [Network information](/docs/help-center/get-started/productsup-fundamentals/network-information)). | | `10079` | `Downloaded Additional Feed is empty` | The downloaded additional data source contains no data. | Check with your local IT team since the logic to populate this data source, before the Productsup platform pulls it, may contain a bug. | | `10080` | `Main feed doesn't contain any products` | - The main data source contains no data. - The contained data is distorted. | Check with your local IT team since the logic to populate this data source, before the Productsup platform pulls it, may contain a bug. | | `10081` | `No Data Source defined yet.` | The site has no data sources set up, so the run cannot begin since there is no available data for download. | Set up a data source. | | `10082` | `Request to URL forbidden (HTTP Status 403)` | The platform does not have permission to access the URL. | Check if the URL needs credentials. If it requires an IP allowlist, allowlist Productsup's IP ranges (see [Network information](/docs/help-center/get-started/productsup-fundamentals/network-information)). | | `10083` | `File not found at URL (HTTP Status 404)` | - The hosted file is in another URL. - The URL expired. | Double-check and update the file URL in the **Data Sources** > **Settings** tab. | | `10097` | `FTP Transfer: Could not login at host` | - The credentials you used to access the FTP could be incorrect. - The FTP server only allows *Passive Mode*. | - Confirm you are using the correct credentials. - Activate **Passive Mode** in the **Data Sources** > **Settings** tab. | | `10104` | `IO Service \{{ UserInfo.Metadata. service_name }}\" failed"` | The activated IO service may not be compatible with your data. | Check the settings of the IO service. If they look correct, contact Technical Support at [support@productsup.com](mailto:support@productsup.com). | | `10115` | `Feed upload failed` | A generic error indicates that either the destination settings are not correct or the platform cannot access the destination. | - Check the destination settings for possible typographical errors or incorrect credentials. - If the destination requires an IP allowlist, allowlist Productsup's IP ranges (see [Network information](/docs/help-center/get-started/productsup-fundamentals/network-information)). - If everything looks correct, contact Technical Support at [support@productsup.com](mailto:support@productsup.com). | | `10117` | `Conditionally mandatory attribute is empty` | A [conditionally mandatory attribute](/docs/export-template-management/attributes/conditionally-mandatory-attributes) has no value for products where one of its conditions is met. The attribute becomes mandatory when one of its configured conditions is met; for example, when `batteries_required` equals `true` or when the trigger attribute contains any non-empty value. | - Provide a value for the attribute on the affected products, or review the attribute's conditions in the Developer Portal. - Go to the site and export, and select **Analyze** in the attribute's column to see which products are affected. | | `10118` | `Conditionally mandatory attribute failed validation` | A [conditionally mandatory attribute](/docs/export-template-management/attributes/conditionally-mandatory-attributes) has a value that fails one of its Analyzer Tests (for example, length, format, numeric range, or allowed values) for products where one of its conditions is met. | - Correct the values so they pass the attribute's Analyzer Test, or review the test configuration in the Developer Portal. - Go to the site and export, and select **Analyze** in the attribute's column to see which products and values are affected. | | `10200` | `Unable to download file from FTP/SFTP/FTPS/FTPES` | The server may use a firewall or require different credentials. | Check if the platform needs credentials. If the server requires an IP allowlist, allowlist Productsup's IP ranges (see [Network information](/docs/help-center/get-started/productsup-fundamentals/network-information)). | | `10202` | `Columns for Id Service were missing` | The platform did not set up the **ID Column** in **Data Sources** > **Settings**, or it disappeared. | Go to **Data Sources** > *Settings* tab, find the section *Unique item identifier*, and define one or more attributes that uniquely identify items in your feed. | | `10211` | `Aborted due to Error Monitoring Configuration` | Monitor event conditions were met, so the platform aborted the current run. | Go to the error log to see which Monitor event was met. If it appears as expected, you can snooze the Monitor event for a specific period. | | `10212` | `File decompression of download source {{ UserInfo.Datasource }} failed` | File decompression of download source `{{ UserInfo.Datasource }}` failed. | - Check with your IT team to see how they have compressed the file. - Check the file, as an uncompressed file might contain the wrong extension. For example, containing a .zip or .gz extension. | | `10222` | `Could not upload {{ UserInfo. Metadata.cnt }} products. Mandatory attributes were missing` | The export is missing mandatory attributes that the target channel sets. | Confirm all mandatory attributes in the export channel have mapped connections to them. Mandatory attributes appear blue in **Dataflow**. | | `10224` | `Channel not enabled for this site` | The platform is refreshing **Data View** for a channel that is currently inactive. | Check if it’s expected that the channel is inactive. If so, you can ignore this error message. | | `10250` | `List {{ UserInfo.Id }} download failed. Read access is required?` | The platform may have restrictions for accessing or downloading the file. | - Confirm that everyone with the list URL has at least read access and rights to download the file. - If importing from Google Sheets, check that the URL ends with `/export? format=csv`. | | `10313` | `Column '{{ UserInfo.Column }}' disappeared from source feed` | A previously imported column in Productsup no longer exists in the platform. This could be the case if you removed it from the data source or because the data source has failed to import. | Verify if the imported column should not exist. If it should, check with your IT team and confirm the data source that contained the column was set up correctly and did not fail to import. If it failed, review the corresponding error message. | | `10314` | `Column '{{ UserInfo.Column }}' appeared as new column in the source feed` | A warning message letting you know that the site imported a new attribute from your data sources. The warning message mentions the name of the new attribute instead of the curly brackets shown in this example. | There must have been a change in your data sources, which resulted in the site importing a new attribute. No specific actions required. You can use the new attribute in your site if needed. | | `10322` | `Destination Failed` | Generic error message for a failed upload to an export destination. May occur because of incorrect credentials, a server outage, or other technical reasons. | Check the error log for further information or contact [support@productsup.com](mailto:support@productsup.com) to investigate. | | `10323` | `Product Count Changed from Import to Intermediate` | This error message indicates an inconsistency in the database regarding the number of products in the import and intermediate stage. | Contact [support@productsup.com](mailto:support@productsup.com) to investigate. | | `10330` | `Product Count Changed from Intermediate to {{ UserInfo.Metadata. currentStage }}` | This error message indicates an inconsistency in the database regarding the number of products in the intermediate column and the listed export channel. | Contact [support@productsup.com](mailto:support@productsup.com) to investigate. | | `10343` | `Could not upload {{ UserInfo. Metadata.cnt }} of {{ UserInfo. Metadata.total }} products {{ UserInfo. Metadata.rate }}% to Bing Content API` | The platform could not upload a percentage of products via the Bing Content API. | Check that all mandatory attributes are present. Mandatory attributes appear in blue in **Dataflow**. | | `10344` | `Failed to connect expanding SQLite. Skipping.` | This error indicates that the database was not able to expand with additional data. | Check that you have the correct column names in the **Additional Data Source** settings. Check for possible typos, the correct case, for example, `ID` vs `id`, or if the column exists in **Data Sources** > **Additional Data Sources** > the **Content Mode** section. | | `10345` | `Maximum Product Count Exceeded. Please Contact Productsup Support: support@productsup.com` | This error comes from a predefined value of the maximum number of products the platform allows for import and acts as a safeguard to prevent performance limitations or accidental overages. | Confirm you did not accidentally try to import too many products. If you need to increase the limit, contact [support@productsup.com](mailto:support@productsup.com), as they can adjust this limit according to your needs. | | `10352` | `Maximum processing time exceeded` | This error refers to the threshold set in the Monitor event **Site run exceeds given number of hours**. For example, this could occur because of new rules applied in the Dataflow or Data View, or slow down and upload speeds. The number correlates to previous durations. | Review your Monitor settings. If the run time seems unusually high, contact [support@productsup.com](mailto:support@productsup.com) to investigate. | | `10354` | `Unable to parse XML file` | A generic error message, usually followed by a more detailed message, could indicate a corrupted file. | Check the error log for more information. | | `10370` | `XSL Transformation Failed (Export {{ UserInfo.Metadata.export_id }}: {{ UserInfo.Metadata.name\|raw }})` | An error occurred while attempting to transform the export XML file using an XSL Template. This may occur because the XML structure changed or the XSLT is invalid. | If you set up the XSLT, go to the settings of the specified export and check if you can find any inconsistencies between the XSL Template under XSL Template for XML Export and the original XML. Otherwise, contact Technical Support at [support@productsup.com](mailto:support@productsup.com) to investigate. | | `10380` | `Invalid Dynamic Filename` | This occurs when an export uses a dynamic filename or URL, and the used Twig that generates the filename or URL is invalid. | Confirm that the used Twig that builds the filename or URL is valid. See [Import dynamic URLs](/docs/help-center/import-data-feeds/import-your-data-into-productsup-advanced-settings/import-dynamic-urls) for both imports and exports. | | `10513` | `Processing Error` | A generic error message indicating an issue with the data processing in the database. | Contact [support@productsup.com](mailto:support@productsup.com) to investigate. | | `10514` | `Service Failed` | A generic error message indicating a failed data service. | - Go to **Data Sources** > *Settings* tab, find the section *Unique item identifier*, and define one or more attributes that uniquely identify items in your feed. - If the setup looks correct, contact [support@productsup.com](mailto:support@productsup.com) to investigate. | | `10515` | `Too many input columns provided` | The hard limit of columns in the import is 2.000 | - Check if there are any unnecessary columns and remove them from your import source. - Services may create additional columns, such as *Explode Columns*. - If the import file is an XML or JSON file, it might help to reduce the threshold for **Bundle repeating nodes** found in **Data Source** options > **Content Options** > **XML Settings**. | | `10517` | `Destination upload failed because of missing required file configuration` | The failed export doesn't have a file to send data to | Go to the settings of the failed export and check if there is a file added in the *Files* panel at the bottom of the export setup page. If not, select **Add File**, define a desired filename and extension in **Filename**, and select **Save**. | # Edit or delete a project import { Callout } from "fumadocs-ui/components/callout"; import { Step, Steps } from "fumadocs-ui/components/steps"; Once a project is set up, you can edit its name or delete it entirely. You can use projects to organize your sites as you wish. This could be per country, per brand, per branch, or in any other way that suits your organization and use case. Navigate to a project [#navigate-to-a-project] Go to the organization level. Select the project name. Edit a project name [#edit-a-project-name] Go to the project level. Go to **Settings** from the project's main menu. project_level_settings

Enter a new name in the **Project name** field. rename_project

Select **Save**. Delete a project [#delete-a-project] To delete a project, it must not have any sites in it. You must first delete the sites. This is built-in as a safeguard to ensure that your feeds cannot easily be removed. Go to the project level. Go to **Settings** from the project's main menu. Go to the **advanced settings**. delete_project_advanced_settings

Select **Delete Project**. # Add a project import { Callout } from "fumadocs-ui/components/callout"; import { Step, Steps } from "fumadocs-ui/components/steps"; Introduction [#introduction] According to the Productsup data structure, each site should exist in a project. The project is a container for sites, and you need to add a project to your Productsup organization before creating sites. It is up to you to define the names and hierarchy of your projects and sites within Productsup. Add a project to your organization [#add-a-project-to-your-organization] You may have access to several organizations, each of which has its projects, sites, and settings. If you have only one organization, you can go to the organization level one of the following ways: 1. Select your organization name at the top of the main menu (highlighted in red). 2. Select your organization name in the breadcrumbs (highlighted in blue). 3. Go directly to the link ending with your organization ID, for example, `https://platform.productsup.com/overview/account/123456`. UUID-ee0b693c-ee98-f447-42eb-5c6b76119d5c

UUID-ee0b693c-ee98-f447-42eb-5c6b76119d5c

Select **Add Project**. Enter a name for your project. Select **Save**. This action creates a project and redirects you to the project level in Productsup, where you can see an overview of the selected project and all its sites. UUID-de299425-ffc4-22a3-adec-8e1d317858a2

UUID-de299425-ffc4-22a3-adec-8e1d317858a2

To see an overview of all projects within your organization, go to the organization level described in [Step 1](#N1650895275458). Project's main menu [#projects-main-menu] You can open the project-level menu by selecting it in breadcrumbs. UUID-c1881d68-eb23-6a0f-2248-5a65069e6e75

UUID-c1881d68-eb23-6a0f-2248-5a65069e6e75

The project's main menu features include: * **Overview**: an overview of all sites within the selected project available for you according to your access rights. * **Dashboard**: an overview of errors and warnings occurring in the sites belonging to the project. * **Authentication**: a feature that lets you add and view your authentications with external systems. See [Add OAuth authentication to external systems](/docs/help-center/import-data-feeds/import-your-data-into-productsup/add-oauth-authentication-to-external-systems) for more information. * **Monitor**: a feature that lets you set up email alerts for error events and process breaks. See [Monitor events overview](/docs/help-center/dashboard-and-monitor/ensure-data-quality-in-monitoring/monitor-events-overview) for more information. * **Activity**: a summary of maintained and exported products by a selected month. * **Reporting**: settings to generate and download performance reports for clicks and orders of the selected exports. * **Settings**: a page where you can rename, delete, or move a site to another project. The list of available features depends on your user access rights. See [User types and access rights](/docs/help-center/get-started/user-management/user-types-and-access-rights) for more information. Use the navigation bar of the project level [#use-the-navigation-bar-of-the-project-level] Once you've created a project, you can use the upper ribbon to apply various actions to the sites within the chosen project. UUID-038859c0-4c43-77fa-6e92-f792c19ae326

UUID-038859c0-4c43-77fa-6e92-f792c19ae326

* Use the **Search** field to find a site by its name. * Use the **Filter**, **Recent**, **Exports**, and **Tags** drop-down menus to filter sites within the selected project based on their states, time of creation, available exports, and tags. You can add tags in the project level: Select the **Tag** drop-down menu in the needed project line. Select **Add new tag** or select a tag from the list of existing tags. UUID-3caef1e5-c65d-3994-a314-57d9b4b676ea

UUID-3caef1e5-c65d-3994-a314-57d9b4b676ea

Add key and value and select **Save**. In the project level, you can only add new tags or select from the existing tags. To edit or delete tags, go to the **Setting** in the site level. See [Edit site settings](/docs/help-center/get-started/manage-your-organization-projects-and-sites/edit-site-settings#section-idm234666106254992). * To search for errors, select **Errors** and start typing the error name. Select the necessary error from the drop-down list and choose **Search** to see the sites with the error.To get the meaning of the errors, see [Error log codes and troubleshooting overview](/docs/help-center/get-started/manage-your-organization-projects-and-sites/error-log-codes-and-troubleshooting-overview). Alternatively, you can view the error history in **Error Log** in the main menu. UUID-dc2baded-a3a9-1a65-8d90-7259c220218e

UUID-dc2baded-a3a9-1a65-8d90-7259c220218e

Use **Clear Filters** in the upper ribbon to restore the page view before the error searching. * Select the graph icon to change the project view and have different columns describing your sites. By default, the warning view is active. * The graph view provides such columns as *ID*, *Title*, *State*, *Imported*, *Changed*, *Export(ed)*, *Tags*, *Last Duration*, and *Last/Next Run*. UUID-11e9bfe0-64c3-8f84-5dc2-8711d27c865b

UUID-11e9bfe0-64c3-8f84-5dc2-8711d27c865b

* The warning view provides such columns as *ID*, *Title*, *State*, *Errors/Warnings*, *Imported*, *Last Duration*, and *Last/Next Run*. UUID-6ba1f861-8784-84f3-1b1b-683e077f57a2

UUID-6ba1f861-8784-84f3-1b1b-683e077f57a2

The *Errors/Warnings* column shows the number of errors and warnings during the last run. To see the list of errors, hover over the red cross icon. To see the list of warnings, hover over the orange exclamation mark icon. UUID-d898163d-fcf7-474a-100c-c9d4b75d8b45

UUID-d898163d-fcf7-474a-100c-c9d4b75d8b45

* Perform a bulk action on multiple projects and sites simultaneously by selecting **Bulk Option**. See [Use bulk options to perform actions across multiple sites](/docs/help-center/get-started/manage-your-organization-projects-and-sites/use-bulk-options-to-perform-actions-across-multiple-sites) for more information. * Select **Download** to download a list of all sites within the selected project as a CSV file. * Select **Clear Filters**, to restore the default state of the page before using any filters. * Sort through sites by any column selecting the column title and using the up and down arrows. # Manage your organization, projects, and sites Learn how to manage your Productsup organization, projects, and sites. Also, learn how to use them. There are two main levels in a Productsup organization: * **Projects:** A portfolio or folder that groups and organizes sites, for example, by region, country, or branch. * **Sites:** Productsup processes and maintains feeds within sites. You can create several exports in a site. # Edit site settings import { Callout } from "fumadocs-ui/components/callout"; import { Step, Steps } from "fumadocs-ui/components/steps"; Introduction [#introduction] To structure and organize your Productsup organization, you can use various site settings. This document gives you an overview of the high-level site settings. Change the name of a site [#change-the-name-of-a-site] Go to **Settings** from the site's main menu. Enter the new name in **Title**. UUID-af2dce2b-9dd1-4a41-e55c-524e1bdf2d15

UUID-af2dce2b-9dd1-4a41-e55c-524e1bdf2d15

Select **Save**. Add a logo to a site [#add-a-logo-to-a-site] You can see a site's logo between the **Title** and **State** columns of the site's row on the project and organization overview pages. In the following screenshot, the globe image is an example of a logo added to a site. UUID-6952e04e-09f2-d895-0a85-b8d01e0a1990

UUID-6952e04e-09f2-d895-0a85-b8d01e0a1990

Go to **Settings** from the site's main menu. Add a link to your logo in **Logo URL**. Select **Save**. Add a comment to a site [#add-a-comment-to-a-site] You can add comments to sites to keep things organized and help other users of the platform understand the purpose of each site better. Go to either the organization or the project level. Select the comment bubble at the end of the chosen site's row. Enter your comment and select **Save**. To see your comment, hover over the comment bubble or select it. Sites with comments have a black comment bubble, while sites with no comments have a white comment bubble. UUID-b6670fda-a90b-871f-1111-ac543ec31225

UUID-b6670fda-a90b-871f-1111-ac543ec31225

Site's tags [#sites-tags] Tags let you do the following actions: * Filter sites by tags on the project level in the Overview. See [Add a project](/docs/help-center/get-started/manage-your-organization-projects-and-sites/add-a-project#section-idm4519495076728033017925908111). UUID-5088c6e4-0e3b-3c00-4f60-ff36a3f07712

UUID-5088c6e4-0e3b-3c00-4f60-ff36a3f07712

* Refer to the necessary sites when using some rule boxes. See [Replace values](/docs/help-center/add-a-rule-box/find-the-needed-rule-box-category/replace-values#section-idm353458339224944) and [Other](/docs/help-center/add-a-rule-box/find-the-needed-rule-box-category/other#section-idm234573119882414). * Simplify the site references when making some operations via Platform API. You can use a textual representation of a site instead of storing the site ID. In this case, the site tags must be unique within an organization. Add tags to a site [#add-tags-to-a-site] Go to **Settings** from the site's main menu. Choose the **Tags** tab. UUID-ec0fdd1c-877c-b0c6-4dbc-f08386db26ff

UUID-ec0fdd1c-877c-b0c6-4dbc-f08386db26ff

Add key and value in the **Add new tag** section and select **Add Tag**. Edit or delete tags [#edit-or-delete-tags] UUID-f8e89bfb-9808-439a-55c9-57792430d9de

Go to **Settings** from the site's main menu. Choose the **Tags** tab. Next to the needed tag, select **Edit** to change the tag or select **Remove** to delete the tag. You can't edit the platform-generated tags. Move a site to a different project [#move-a-site-to-a-different-project] Go to **Settings** from the site's main menu. From the **Project** drop-down menu, select the project where you want to move the site. UUID-ab50b11f-da02-0b30-0321-f6e3a80f2112

UUID-ab50b11f-da02-0b30-0321-f6e3a80f2112

Select **Save**. Move multiple sites to a different project in bulk [#move-multiple-sites-to-a-different-project-in-bulk] You can move multiple sites into a different project at once: Go to either the organization or the project level. Select **Bulk Option** in the upper ribbon. Tick the boxes next to the sites you want to move and select **Next Step**. Select **Move into Project** and choose **Next Step**. From the **Project** drop-down menu, select the project where you want to move the sites. If one of the sites you are moving has lists shared on the project level, this project loses access to the lists as the lists' source site moves to a different project. The lists become available to the target project chosen in the **Project** drop-down menu. Select **Execute**. Reset data in a site [#reset-data-in-a-site] You can delete all product data from a site but preserve all site configurations, such as data sources, mapping, rule boxes, and exports. To reset the data: Go to **Settings** from the site's main menu. Choose the **Advanced Settings** tab. Select **Reset** in the **Reset Data** panel. UUID-521fa8ad-1a08-dadb-615f-b499a322976e

UUID-521fa8ad-1a08-dadb-615f-b499a322976e

Select **Yes**. Reset data for multiple sites in bulk [#reset-data-for-multiple-sites-in-bulk] You can reset data for multiple sites at once: Go to either the organization or the project level. Select **Bulk Option** in the upper ribbon. Tick the boxes next to the sites where you want to reset data and select **Next Step**. Select **Reset Sites** and choose **Next Step**. Select **Execute**. Disable or pause a site [#disable-or-pause-a-site] By default, sites are always active in the platform. They import data from your data sources, process it by applying rule boxes and mapping attributes, and export it to the selected channels. If you want to deactivate a site, there are two (2) options: . Pause a site's export. In this case, the site still imports data from your data sources and processes it without exporting it to any channels. . Disable a site. In this case, the site no longer imports, processes, or exports any data. Even if the site uses scheduling or triggering settings, no run occurs. To pause or disable a site, use one of the following procedures. From the site level [#from-the-site-level] Go to **Dashboard** from the site's main menu. In the top-right corner, select the **Active** drop-down menu. To pause the export of this site, select **Paused**. To disable this site, select **Disabled**. From the organization or the project level [#from-the-organization-or-the-project-level] Go to either the organization or the project level. Select the green play icon (**▶︎**) in the **State** column of the desired site. To pause the export of this site, select **Paused Upload**. To disable this site, select **Disabled**. To change the state of multiple sites in bulk, use the Bulk Option feature: Go to the organization or the project level and select **Bulk Option**. Tick the boxes next to the desired sites and select **Next Step**. Select **Activate/Deactivate Sites** and choose **Next Step**. Choose the desired state and select **Execute**. Delete a site [#delete-a-site] Go to **Settings** from the site's main menu. Choose the **Advanced Settings** tab. In the **Delete this Site** panel, select **Yes, delete this Site**. UUID-c53bf7e6-3d7d-184f-9d9e-b9584b239b9c

UUID-c53bf7e6-3d7d-184f-9d9e-b9584b239b9c

Select **Yes**. Delete multiple sites in bulk [#delete-multiple-sites-in-bulk] Go to either the organization or the project level. Select **Bulk Option** in the upper ribbon. Tick the boxes next to the sites you want to delete and select **Next Step**. Select **Delete Sites** and choose **Next Step**. Select **Execute**. # View your Activity Log and Summary import { Callout } from "fumadocs-ui/components/callout"; import { Step, Steps } from "fumadocs-ui/components/steps"; With the Activity feature, you can keep track of the following: * All your applied, edited, scheduled, and deleted rule boxes. * All rule box conditions added to, moved within, or deleted from attributes. * All added and deleted connections in Dataflow. * All added, edited, and deleted user-generated attributes. * The number of monthly maintained and exported items. UUID-e3c65727-49c9-6e43-ed46-b5ea3199e264

UUID-e3c65727-49c9-6e43-ed46-b5ea3199e264

Locate the Activity page [#locate-the-activity-page] To access the Activity page, go to **Activity** from your organization's, project's, or site's main menu. * If you access the Activity page from the organization or site level, you can see two tabs: * The *Activity Log* tab displays all activities related to rule boxes, connections, rule box conditions, and user-generated attributes. * The *Activity Summary* tab shows the number of monthly maintained and exported items for the organization. * If you access the Activity page from the project level, you can see only the *Activity Summary* tab with the number of monthly maintained and exported items for each site in a project. Activity Log [#activity-log] Activity Log displays your users' activities in Dataflow and Data View: * Adding, editing, pausing, scheduling, or deleting rule boxes. * Applying rule box conditions to attributes, moving them within attributes, or removing them from attributes. * Adding or deleting connections in Dataflow. * Adding, editing, and deleting user-generated attributes. Your Activity Log displays a table containing the following information: * **Activity** shows the name of the logged activity. * **Type** displays the type of performed activity, such as *Add*, *Edit*, *Order change*, and *Delete*. The current version doesn't show the scheduling of rule boxes and changes of Dataflow versions. * **Location** shows the project and site of the activity. * **Timestamp** displays the time when the activity occurred based on the time zone selected in your profile. See [Set up user profile time zone](/docs/help-center/get-started/user-management/set-up-user-profile-time-zone). * **User** records the name and email of the user who performed the activity. UUID-a47c9249-a2e5-3c9d-a7ee-72b0b3cf0bb8

UUID-a47c9249-a2e5-3c9d-a7ee-72b0b3cf0bb8

Search for the needed user activities in the top toolbar [#search-for-the-needed-user-activities-in-the-top-toolbar] You can search for the needed user activities using the search bar or the filters displayed next to it: UUID-03b6d34d-1501-c134-7a43-802056888e82

UUID-03b6d34d-1501-c134-7a43-802056888e82

. In **Activity**, choose the entity that the needed activity relates to and select **Apply**: * *Dataflow connection* shows an added or deleted connection between attributes in Dataflow. * *Dataflow rule box* shows a rule box added, edited, moved, or deleted in Data View or Dataflow. * *Rule box condition* shows an applied, moved, or deleted rule box condition in Data View or Dataflow. * *User-generated attribute* shows an added, edited, or deleted attribute in the intermediate or export stage in Dataflow. UUID-1c51dc6e-b3c2-a4bf-167b-9b5c38e0e12c

UUID-1c51dc6e-b3c2-a4bf-167b-9b5c38e0e12c

. In **Type**, choose the needed type of activity and select **Apply**: * *Add* shows activities where a user added a rule box, a connection, a rule box condition, or a user-generated attribute. * *Edit* shows activities where a user changed a rule box setup or renamed a user-generated attribute. * *Order change* shows activities where a user changed the order of rule boxes and rule box conditions in an attribute. * *Delete* shows activities where a user deleted a rule box, a connection, a rule box condition, or a user-generated attribute. UUID-b94a49a6-7ecc-27fa-5592-26b7583c0fa8

UUID-b94a49a6-7ecc-27fa-5592-26b7583c0fa8

See the activity details [#see-the-activity-details] Select any activity in Activity Log to view its details: . The rule box activity details page shows the following information: UUID-6729f654-153c-9aa1-aaf5-7c35226cfe9c

UUID-6729f654-153c-9aa1-aaf5-7c35226cfe9c

* *Add*, *Edit*, *Order change*, and *Delete* identify the type of action related to the rule box. * *User* shows the user who performed the change. * *Location* displays the organization, project, and site where the change happened. * *Timestamp* logs the time of the change. * *Rule box name* shows which rule box relates to the change. * The *Before* and *After* panels display: * The settings of the rule box before and after the change. This is only visible for *Edit* activities. * In **Attribute Name**, the attribute where a user applied the rule box. * In **Rule Box Order**, the number indicating the order in which a user applied the rule box to the attribute. See [Rule box order](/docs/help-center/add-a-rule-box#note-idm243488719234062). * In **Stage**, the stage or export where a user applied the rule box. . The activity details page of a Dataflow connection shows the following information: UUID-38045b63-a1fa-7352-4e0c-5d07084f9d0e

UUID-38045b63-a1fa-7352-4e0c-5d07084f9d0e

* *Add* and *Delete* identify the type of activity related to the connection in Dataflow. * *User* shows the user who performed the change. * *Location* displays the organization, project, and site where the change happened. * *Timestamp* logs the time of the change. * *Connection* shows the stages where the connection changed. If the connection changed between the intermediate and export stages, you can also see the name of the specific export related to the change. * The names of the attributes between which a user changed the connection. . The activity details page of a rule box condition shows the following information: UUID-f0a05324-b5ae-ac4a-b2a4-37c196f6447e

UUID-f0a05324-b5ae-ac4a-b2a4-37c196f6447e

* *Add*, *Order change*, and *Delete* identify the type of activity related to the rule box condition. * *User* shows the user who performed the change. * *Location* displays the organization, project, and site where the change happened. * *Timestamp* logs the time of the change. * The *Before* and *After* panels display: * In **Attribute Name**, the attribute where a user applied the rule box condition. * In **Rule Box Order**, the number indicating the order in which a user applied the rule box condition to the attribute. See [Rule box order](/docs/help-center/add-a-rule-box#note-idm243488719234062). * In **Stage**, the stage or export where a user applied the rule box condition. . The activity details page of a user-generated attribute shows the following information: UUID-5aa8bbe5-63f7-d7c8-8dda-827e657950fc

UUID-5aa8bbe5-63f7-d7c8-8dda-827e657950fc

* *Add*, *Edit*, and *Delete* identify the type of activity related to the user-generated attribute. * *User* shows the user who performed the change. * *Location* displays the organization, project, and site where the change happened. * *Timestamp* logs the time of the change. * The *Before* and *After* panels display: * In **Attribute Name**, the name of the affected attribute. * In **Stage**, the stage or export where a user added, edited, or deleted the attribute. Activity Summary [#activity-summary] Your Activity Summary displays two KPIs: * **Maintained items** (previously *Maintained Products*) show the average monthly number of imported items per site, project, or organization available in Activity. The platform calculates the average number of items in the import and intermediate stages and displays the higher of the two numbers. See a calculation example in the following table. * **Exported items** (previously *Exported Products*) show the total monthly number of exported items per site, project, or organization available in Activity. The platform keeps your data for one (1) year only. The Activity Summary tab shows you the maintained and exported items for a selected month per project when you are at the organization level. But if you access the Activity Summary tab from the project level, you can see the maintained and exported items per each site within this project. And if you access it from the site level, the Activity Summary tab displays the maintained and exported items only for the current site. UUID-97e4a281-54c4-157d-ade8-219166cd9bf6

UUID-97e4a281-54c4-157d-ade8-219166cd9bf6

To view your import and export activities for a certain month, choose the month from the dropdown in the top right corner. UUID-a51221eb-ee82-08e0-2d5d-7979987459b5

UUID-a51221eb-ee82-08e0-2d5d-7979987459b5

Example of maintained items calculation: In the following table, you can see that the platform triggered a run four times during the month and imported 7,525 items on average (30,100 divided by 4). At the same time, the platform passed 10,000 items on average to the Intermediate stage (20,000 divided by 2). Since the Intermediate average is higher than the Import average, the Activity Summary displays `10,000` as the number of Maintained items for that month. | Event | Item count on Import | Item count on Intermediate | Description | | ------ | -------------------- | -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Run #1 | `100` | `0` | The platform triggered an import, but the file was faulty and only imported 100 out of 10,000 items. The platform passed nothing to the intermediate and export stages. | | Run #2 | `10,000` | `0` | The platform triggered an import again and imported all items successfully. The platform passed nothing to the intermediate and export stages. | | Run #3 | `10,000` | `10,000` | The platform triggered an import and export for all items and passed them to the intermediate stage and then to the export stage. | | Run #4 | `10,000` | `10,000` | Scheduling triggered another data import and export, successfully passing all imported items. | | | `7,525` | `10,000` | Average maintained items. | The Activity Summary data might differ from your invoice if you moved a site from your testing or sandbox project to a live project. For example, in January, the sandbox site had 1,000 maintained items. You moved this project to live in February. Now, if you select January to review Activity Summary for January, you see 1,000 maintained items under the live project, even though in that month, they belonged to a sandbox project. Download Activity Summary [#download-activity-summary] You can download the Activity Summary data as a CSV file for one of the past 12 months as follows: In the *Activity Summary* tab, select a month from the dropdown on the right. Select **Export CSV**. UUID-de13c39a-3cc6-5b0e-fa44-f531eb700839

UUID-de13c39a-3cc6-5b0e-fa44-f531eb700839

# Create or copy a site import { Callout } from "fumadocs-ui/components/callout"; import { Step, Steps } from "fumadocs-ui/components/steps"; A site is the smallest structural entity in the platform. Your Productsup organization can have multiple projects where you can add multiple sites. A site contains your imported data, the optimizations you apply to it, and the exports where you can send your data. Sites are usually your main workspace in the Productsup platform. Similar to projects, you can organize your sites per country, brand, language, export, etc. Dashboard is the homepage of every site. Here, you can see the site's stats and get quick access to troubleshooting features. UUID-09173611-2b26-e4f2-47fd-aef6f1db8568

UUID-09173611-2b26-e4f2-47fd-aef6f1db8568

When creating a site, you have two options: . Creating a new site and manually setting it up from scratch. . Copying an existing site and reusing its settings. Create a site [#create-a-site] You have created a new site. The platform opens it in your current browser tab, leading you directly to Data Sources to let you start setting up your new site. See [Import your data into Productsup](/docs/help-center/import-data-feeds/import-your-data-into-productsup) for next steps. UUID-107562d2-1877-e622-dd68-c69f742d3a58

UUID-107562d2-1877-e622-dd68-c69f742d3a58

Go to a project where you want to add a site. UUID-a39fc03d-631f-932c-2101-edc932cd8a80

Select **Add Site**. Enter a name for your site in **Title**. Leave the option *Create a new Site* in the **Create or Copy** dropdown. Select **Add**. Copy a site [#copy-a-site] Copying a site saves time and reduces the probability of errors caused by configuring sites manually.

Productsup copies the following entities from the source site:	Additionally, you can choose to copy:	Productsup doesn't copy:
Data sources and unique item identifier settings. Exports. Dataflow connections and rule boxes. Segments from Data View. Data service settings. Tracking settings. All lists shared on the site level. ROI rules from ROI Strategy. Site tags from Settings.	Export destinations. Site scheduling and triggering settings.	Tracking data: the platform copies tracking settings into the new site, but all tracking data is only available in the source site. ROI rules based on tracking KPIs, such as clicks and orders, don't work in the new site. Organization- and project-level lists: the availability of lists shared on the project and organization level depends on where your new site exists. If the new site exists in the same project or organization as the source site, your new site automatically uses all lists shared within that project or organization. If you delete a list shared on the project or organization level from the source site where it was originally created, all sites in the same project or organization lose access to it.

You can use bulk actions to copy multiple sites at once. See [Use bulk options to perform actions across multiple sites](/docs/help-center/get-started/manage-your-organization-projects-and-sites/use-bulk-options-to-perform-actions-across-multiple-sites). To copy a site, take these steps: Go to the organization level in Productsup by performing one of the following actions: 1. Select your organization name at the top of the main menu (highlighted in red). 2. Select your organization name in the breadcrumbs (highlighted in blue). 3. Go directly to the link ending with your organization ID, for example, `https://platform.productsup.com/overview/account/123456`. UUID-ee0b693c-ee98-f447-42eb-5c6b76119d5c

Select the name of the project where you wish to add a site. Select **Add Site**. Enter a name for your site in **Title**. Select *Create a copy of an existing Site* from the **Create or Copy** dropdown. In the *Select a Site* pop-up, choose the site you want to copy in **Select a Site to copy**. Choose **Select**. This action closes the pop-up and shows you further site settings. UUID-54382da2-2d9d-e5bb-e071-ed504fe8f026

UUID-54382da2-2d9d-e5bb-e071-ed504fe8f026

If you want to copy all export destinations from the source site, select **Copy with Export Destinations**. If you copy a site with its export destinations, the destinations of both the source and the new site have the same settings, such as file names, folders, buckets, etc.The *Productsup Server* destination is the only one that remains unique and gets a new link and file name when you copy it. To copy all scheduling and triggering settings from the source site, select **Copy with Scheduling & Triggering**. To copy all shared dataflow settings from the source site to the new one, select **Copy with Shared elements**. This option lets you copy only the sites that already have a shared dataflow\.It is impossible to copy a site with this option if the selected source site is also the source site for the shared dataflow settings. If you still need to copy this type of site, do it without the **Copy with Shared elements** option and then manually set up the shared dataflow in **Shared Dataflow** at the organization level. See [Share dataflow with other sites](/docs/help-center/map-and-optimize-your-data/dataflow/share-dataflow-with-other-sites) to learn more. Select **Copy Selected Site**. Site statuses [#site-statuses] Using site statuses, you can manage which sites run or export data and which ones don't. There are three site statuses in Productsup: * **Active**: In an active site, the platform uses the existing triggers and schedules to run the site automatically. It imports, processes, and exports data as expected. This is the default site status. * **Paused**: In a paused site, the platform uses the existing triggers and schedules to partially run the site. It imports and processes your data, but it doesn't send any data to any of the added export destinations. Even if you manually run a paused site, the platform doesn't export the data. Using paused sites is a good way to test data optimization strategies without exporting any data to your target channels before it's ready. The platform considers items in paused sites as maintained items. * **Disabled**: In a disabled site, the platform doesn't apply any existing triggers or schedules to import, process, or export data. Disabled sites don't run.The platform doesn't consider items in disabled sites as maintained items. UUID-63ecf511-2975-c0b2-ba6c-d2ad7a665c05

UUID-63ecf511-2975-c0b2-ba6c-d2ad7a665c05

Besides the site level, you can also change a site's status at the project and organization level in Overview using the dropdown in the *State* column. Site's main menu [#sites-main-menu] You can open and collapse the site-level menu using the arrow at the bottom of the menu. UUID-b62ca6a9-80fc-6618-c118-3cab043ee5dd

UUID-b62ca6a9-80fc-6618-c118-3cab043ee5dd

The features available in the site's main menu are: UUID-96c9099d-47a0-1335-c36e-e5633e25d4de

* **Dashboard**. You can see an overview of a site, including the number of imported and exported items, errors and warnings, import history overview, core readiness score, and site run times. See [Dashboard at the organization, project, and site level](/docs/help-center/dashboard-and-monitor/dashboard-at-the-organization-project-and-site-level). * **Data Map**. You can get a visual overview of where your data is coming from, what happens to it, and what exports it goes to. See [View your site's flowchart in Data Map](/docs/help-center/dashboard-and-monitor/view-your-sites-flowchart-in-data-map). * **Authentication**. You can add and view your authentications with external systems. See [Add OAuth authentication to external systems](/docs/help-center/import-data-feeds/import-your-data-into-productsup/add-oauth-authentication-to-external-systems). * **Data Sources**. You can add new data sources and select a unique item identifier. See [Add a main data source to import your products](/docs/help-center/import-data-feeds/import-your-data-into-productsup/add-a-main-data-source-to-import-your-products). * **Data Services**. You can add and view data services that can enhance and restructure your data feed. See [Enhance your import data through Data Services](/docs/help-center/import-data-feeds/enhance-your-import-data-through-data-services) and [Restructure your data in Data Services](/docs/help-center/map-and-optimize-your-data/data-services). * **Exports**. You can add and set up exports and view the export history. See [Export data feeds](/docs/help-center/export-data-feeds). * **Designer**. You can edit images in your data feed. See [Image Designer](/docs/help-center/map-and-optimize-your-data/image-designer). * **Scheduling**. You can create schedules and trigger events so that your sites run automatically. See [Set up scheduling and triggering processes in Scheduling](/docs/help-center/dashboard-and-monitor/set-up-scheduling-and-triggering-processes-in-scheduling). * **Dataflow**. You can get an overview of attribute mapping from import to export. See [Map your data from import to export in Dataflow](/docs/help-center/map-and-optimize-your-data/dataflow). * **Data View**. You can view your data and use rule boxes to optimize it. See [Data View](/docs/help-center/map-and-optimize-your-data/data-view). * **Lists**. You can include, exclude, replace, or map values in your data feed. See [Lists](/docs/help-center/map-and-optimize-your-data/lists). * **ROI Strategy**. You can optimize your data feed using performance tracking data and KPIs. * **Reporting**. You can generate and download performance reports for clicks and orders for selected exports. * **Error Log**. You can see all errors and warnings occurring within site runs. See [Error log codes and troubleshooting overview](/docs/help-center/get-started/manage-your-organization-projects-and-sites/error-log-codes-and-troubleshooting-overview). * **Monitoring**. You can set up email notifications or other monitoring actions for site run failures or irregularities. See [Monitor events overview](/docs/help-center/dashboard-and-monitor/ensure-data-quality-in-monitoring/monitor-events-overview). * **Activity**. You can get a summary of the maintained and exported items for a selected month or see user activity in your site. See [View your Activity Log and Summary](/docs/help-center/get-started/manage-your-organization-projects-and-sites/view-your-activity-log-and-summary). * **Tracking**. You can track and analyze performance by collecting clicks, keywords, conversions, and other statistics from your exports. * **Settings**. You can rename, delete, or move a site to another project. The list of available features depends on your user access rights. See [User types and access rights](/docs/help-center/get-started/user-management/user-types-and-access-rights) for more information. # View runtime and estimations in the header Introduction [#introduction] You can view your site’s runtimes in the header to give you a better understanding of run durations. View your estimated runtime or historical information, such as when a run occurred and how long it lasted. View inactive run header information [#view-inactive-run-header-information] On any site-level page, for inactive runs, hover your mouse over the **Run** button to view: * *The Last run (date, time)* * *Estimated duration (amount of time)* * *Last run’s duration (amount of time)* UUID-8eac86ed-23d3-1483-5dd8-9d5724177427

UUID-8eac86ed-23d3-1483-5dd8-9d5724177427

**Note:** While on a site-level page, Productsup updates the *Estimated duration once a minute*. View active run header information [#view-active-run-header-information] After selecting the **Run** button to trigger a run, hover your mouse over **Run** to view: * *Run’s estimated duration (amount of time)* * *Last run (date, time)* * *Last run’s duration (time)* UUID-b4c05139-04ba-4947-fc5e-f4c084e79cbf

UUID-b4c05139-04ba-4947-fc5e-f4c084e79cbf

View queued-run status on site-level pages [#view-queued-run-status-on-site-level-pages] View queued-runs information on any site-level page by hovering your mouse over the **Importing**, **Processing**, and **Exporting** header statuses. Read a tooltip pop-up message displaying the following information: * *There are runs on hold since (day, time)* * *The Run started (day, time)* * *Run’s estimated duration (amount of time in hours, minutes)* * *Last run’s duration (amount of time in hours, minutes)* UUID-f6f4a9eb-c8d6-ef0a-3031-8736aa314f02

UUID-f6f4a9eb-c8d6-ef0a-3031-8736aa314f02

Read more about site-level statuses in the *View queued-runs in the header document*. Have questions? Contact [support@productsup.com](mailto:support@productsup.com). # View queued runs in the header import { Callout } from "fumadocs-ui/components/callout"; Introduction [#introduction] When you schedule or trigger runs on-demand, they generally begin when they’re supposed to. For runs that don’t start when expected, they may have fallen into a queue. There are several reasons why runs can fall into a queue. One reason can be that a run produced an error, which prevented it from being processed. The other is that an earlier run took longer than expected. In the Productsup platform, you can view the status of queued runs at the site level, all from the site-level header. View queued runs pop-up warning message [#view-queued-runs-pop-up-warning-message] On every site-level page, a pop-up warning message displays, *There are runs on hold since (date, time)*, if all of the following conditions are met: . You scheduled a run, or it was manually triggered by another site or API connection . The run is ongoing . The run blocks at least one other run’s start. This typically occurs when the estimated time of completion exceeds the next run’s start UUID-db03b06e-ea59-4e0a-d5e2-ed1216e5bdf3

UUID-db03b06e-ea59-4e0a-d5e2-ed1216e5bdf3

You can close this pop-up message by selecting the **X** selector. The queued runs pop-up warning message reappears after every browser restart or when the queue clears. View queued runs header status [#view-queued-runs-header-status] Confirm if you have queued runs by checking the site-level header on any site-level page. Queued runs display one of the following header statuses: * **Importing** * **Processing** * **Exporting** The **Importing**, **Processing**, and **Exporting** site-level headers indicate: * That you scheduled a run, or it was manually triggered by another site or API connection * A run is ongoing * A run blocks at least one other run’s start, because its estimated time of completion exceeds the next run’s start View queued runs status on site-level pages [#view-queued-runs-status-on-site-level-pages] View queued runs information on any site-level page by hovering your mouse over the **Importing**, **Processing**, and **Exporting** header statuses. UUID-9286b7d0-1a9b-b637-b88c-87e1f755b7c7

UUID-9286b7d0-1a9b-b637-b88c-87e1f755b7c7

The tooltip pop-up message displays the following information: * *There are runs on hold since (day, time)* * *The Run started (day, time)* * *Run’s estimated duration (amount of time in hours, minutes)* * *Last run’s duration (amount of time in hours, minutes)* Have questions? Contact [support@productsup.com](mailto:support@productsup.com). # Your Productsup organization import { Callout } from "fumadocs-ui/components/callout"; import { Step, Steps } from "fumadocs-ui/components/steps"; The organization level consists of all information in Productsup related to your company, such as all projects and their sites, user management, monitoring, and more. Find your organization [#find-your-organization] You may have access to several organizations, each of which has its projects, sites, and settings. If you have only one organization, you can go to the organization level one of the following ways: . Select your organization name at the top of the main menu (highlighted in red). . Select your organization name in the breadcrumbs (highlighted in blue). . Go directly to the link ending with your organization ID, for example, `https://platform.productsup.com/overview/account/123456`. UUID-ee0b693c-ee98-f447-42eb-5c6b76119d5c

If you have multiple organizations, to switch to the necessary organization level, take the following steps: Select the arrow next to your organization name at the top of the side menu. Search for or select the necessary organization from the list. UUID-435e1cfe-188b-1b18-2688-26e25380e626

UUID-435e1cfe-188b-1b18-2688-26e25380e626

Overview of your organization level [#overview-of-your-organization-level] The organization level of the platform provides you with an overview of all projects within your Productsup organization. You can select the right arrow icon (**>**) on a project to expand it and get an overview of its sites. For example, the expanded *Tracking Data* project has the site *Tracking Data for Retailer Demo*. UUID-4e297e74-4fe4-d228-c12c-ceb9542000bc

UUID-4e297e74-4fe4-d228-c12c-ceb9542000bc

In the upper ribbon of the overview of the projects in your organization, you can search for, sort, and filter your projects and sites with the help of the following options: * Use the search bar to find a project or a site by name. You can also search for the sites containing specific attributes and connections between the stages. * Use the **Projects only**, **Filter**, **Recent**, **Exports**, and **Tags** dropdowns to filter projects and sites based on their states, exports, and tags. * Select **Errors** to see the projects and sites that have the error you are looking for. * Select the graph or warning icon to change the view of your organization overview and have a different set of columns describing your projects and sites: * The graph view focuses on exports. * The warning view focuses on errors and warnings. UUID-92953b20-21f9-cd69-7e20-f89594608a2a

UUID-92953b20-21f9-cd69-7e20-f89594608a2a

UUID-f1920f79-3108-60d4-ae1f-5e7d8b00d2df

Search for sites by their attributes in the needed stage and connections between them [#search-for-sites-by-their-attributes-in-the-needed-stage-and-connections-between-them] You can search for the sites based on their attributes and connections between them in different stages. Enter an attribute name and desired connection in the search bar in the top right corner of the Projects Overview page. Use one of the following search requests, entering the needed attributes instead of AAA, BBB, and CCC: | Search request | Description | | -------------------------- | -------------------------------------------------------------------------------------------------- | | import: AAA --> | All sites with the connection between the import attribute AAA and any intermediate attribute. | | import: AAA -/-> | All sites with no connection between the import attribute AAA and any intermediate attribute. | | import: AAA --> BBB | All sites with the connection between the import attribute AAA and the intermediate attribute BBB. | | import: AAA -/-> BBB | All sites with no connection between the import attribute AAA and the intermediate attribute BBB. | | import: --> BBB | All sites with the connection between the intermediate attribute BBB and any import attribute. | | import: -/-> BBB | All sites with no connection between any import attribute and the intermediate attribute BBB. | | intermediate: BBB --> | All sites with the connection between the intermediate attribute BBB and any export attribute. | | intermediate: BBB -/-> | All sites with no connection between the intermediate attribute BBB and any export attribute. | | intermediate: BBB --> CCC | All sites with the connection between the intermediate attribute BBB and the export attribute CCC. | | intermediate: BBB -/-> CCC | All sites with no connection between the intermediate attribute BBB and the export attribute CCC. | | intermediate: --> CCC | All sites with the connection between the export attribute CCC and any intermediate attribute. | | intermediate: -/-> CCC | All sites with no connection between any intermediate attribute and the export attribute CCC. | Select the Enter key to see the sites meeting the search request. For example, enter *import: image-->image*. As a result, the platform shows all sites where the **image** attribute in the import stage connects to the **image** attribute in the intermediate stage. UUID-558c8cdf-d170-937b-0a5a-00f6a2571ac3

UUID-558c8cdf-d170-937b-0a5a-00f6a2571ac3

You can only filter sites but not the exports within them. If a site contains multiple exports, some exports may meet the search request, while others may not. Organization's main menu [#organizations-main-menu] You can open the organization-level menu by selecting your organization's name at the top of the main menu. UUID-ca5e2784-34e5-059a-876d-e5ebba47816f

UUID-ca5e2784-34e5-059a-876d-e5ebba47816f

The organization's main menu features include: * **Overview**: an overview of all projects and sites available to you according to your access rights. * **Dashboard**: an overview of the errors and warnings occurring in all projects and sites on this organization. * **Authentication**: a feature that lets you add and view your authentications with external systems. See [Add OAuth authentication to external systems](/docs/help-center/import-data-feeds/import-your-data-into-productsup/add-oauth-authentication-to-external-systems) for more information. * **User Management**: a feature that lets you add, edit, and remove users and change their access to sites and projects. See [User Management](/docs/help-center/get-started/user-management) for more information. * **Monitor**: a feature that lets you set up email alerts for error events and process breaks. See [Monitor events overview](/docs/help-center/dashboard-and-monitor/ensure-data-quality-in-monitoring/monitor-events-overview) for more information. * **FTP Accounts**: a feature that lets you add your FTP accounts in Productsup. * **Activity**: a summary of maintained and exported items by a selected month. * **Shared Dataflow**: a feature that lets you configure Dataflow once and reuse it across multiple sites. See [Share dataflow with other sites](/docs/help-center/map-and-optimize-your-data/dataflow/share-dataflow-with-other-sites). The number of available menu options depends on your user access rights. For example, the *User Management* menu option is only available to users with administrator rights. See [User types and access rights](/docs/help-center/get-started/user-management/user-types-and-access-rights) for more information. Edit Organization settings [#edit-organization-settings] Users with admin rights can access the Organization settings by selecting the cogwheel icon UUID-ce09c8b4-4286-bcd4-de46-a409fac3e748

in the lower-left corner of the main menu. UUID-36341eec-8c91-f393-9f7b-76e31f456174

The **Organization settings** page opens in a new tab. On the left-hand side, you can choose what you want to configure: Organization settings or single sign-on (SSO). In the **Organization settings**, you can do the following actions: * Change the company name. * Force the two-factor authentication (2FA) for the entire organization. UUID-9a8cd25b-049d-f851-70bf-ecdf892972b4

UUID-9a8cd25b-049d-f851-70bf-ecdf892972b4

Select **Save** when you've made all the needed changes. To set up single sign-on (SSO), see [Set up single sign-on (SSO)](/docs/help-center/get-started/user-management/set-up-single-sign-on-sso). Switch between Productsup and Retail platforms [#switch-between-productsup-and-retail-platforms] The [Productsup](https://platform.productsup.com/) and [Retail](https://retail.productsup.com/) platforms share the same login. If you use both platforms, you can switch between them using the Projects and Workspaces icons on the side panel on the left. Also, from this panel, you can go to Content Portal. See [Productsup Retail Platform Help Center](https://retail-docs.productsup.com/en/) for end-user documentation. To go to Workspaces or Content Portal: Select the **Workspaces** or **Content Portal** icon in the side panel on the left. UUID-700910a1-ede9-3043-1d21-45b1255d5e55

UUID-700910a1-ede9-3043-1d21-45b1255d5e55

# Use bulk options to perform actions across multiple sites import { Callout } from "fumadocs-ui/components/callout"; import { Step, Steps } from "fumadocs-ui/components/steps"; Introduction [#introduction] When working with your data, you may need to perform the same action across multiple sites. To save time, you can use the Bulk Option feature and perform this action once while applying the needed changes across multiple sites in bulk. You can find the Bulk Option feature in the upper ribbon at the organization and project level. If you use it at the organization level, you can apply bulk actions to all sites of your organization. If you use this feature at the project level, you can apply changes only to the sites located within one project. UUID-0825a97e-b71c-6bbe-e850-9210a13f9c13

Full list of available bulk actions [#full-list-of-available-bulk-actions] Productsup offers bulk actions to save time when optimizing your product data across sites. The following bulk actions can affect the site dataflow: * Add Dataflow Boxes * Add Dataflow Connection * Copy Exports * Map Dataflow Boxes from one dataflow * Map import column(s) to multiple exports To mitigate the risks, save a Dataflow version before making any of these bulk actions. See [Manage versions in Dataflow](https://help.productsup.com/en/29493-29497-organize-your-dataflow-columns-and-attributes.html#UUID-29d1496f-2f39-6677-788e-f7daf8528370_section-idm232216577475068). Here is the full list of available bulk actions: | Bulk action name | Description | | ------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | *Activate/Deactivate Sites* | Changes the site status by pausing the chosen sites to let them stop running or making them active again to resume site runs. | | *Add Dataflow Boxes* | Copies rule boxes from a connection in the source site into the same connection in the target sites while overwriting the existing rule boxes in this connection. To copy rule boxes from one site to another, you need to make sure your target sites have the same connection as the one you are copying rule boxes from. | | *Add Dataflow Connection* | Connects attributes between the import and intermediate or the intermediate and export stages in multiple sites. To create a connection between attributes in multiple sites, you need to make sure all the selected sites have the needed attributes in the respective stages.If you need to create a connection in one site only, go to **Dataflow** and add it there. | | *Copy Data Sources* | Copies data sources and their settings from the selected source site to the target sites. | | *Copy Exports* | Copies exports and their settings from the selected source site to the target sites. You can also choose to copy the export's destinations and dataflow. | | *Copy Segments* | Copies Data View segments from the selected source site to the target sites. | | *Delete Exports* | Deletes the chosen exports from the selected site. | | *Delete Sites* | Deletes the selected sites. Be careful while using this bulk action. It deletes the selected sites along with all their data sources, data services, exports, rule boxes, and other settings. | | *Disable Export* | Pauses the chosen export to stop it from sending data to its destinations during the following site runs. | | *Enable Export* | Adds a new export to the chosen sites in bulk. | | *Import* | Starts a partial run in the selected sites to let them import data from the active data sources. | | *Import & Export All* | Starts a full run in the selected sites to let them import, process, and send data to the active export destinations. | | *Map Dataflow Boxes from one dataflow* | Copies the rule boxes of the selected connections into the export of the same template within the same site.If you added two (2) Google Merchant Center exports to your site, you can add and set up the needed rule boxes for one of the Google Merchant Center exports and use this bulk action to copy all the configured rule boxes to the other Google Merchant Center export within this site. To copy rule boxes from one export template to the other, you need to first map all the relevant attributes in the target export template. | | *Map import column(s) to multiple exports* | Connects the selected import-stage attributes to the respective attributes of one or more exports in this site. | | *Move into Project* | Moves the selected sites to a different project. | | *Remove Service Data Source* | Removes the additional data sources created by the added data services while leaving the related data services and their settings intact. | | *Reset Sites* | Removes all product data from the selected sites while leaving all the other site settings intact. If a site has a delta export, the next site run imports all product data from the active data sources, applies the added data optimizations, and then exports all the products in the site to the destination of this delta export. | Set up the needed bulk action [#set-up-the-needed-bulk-action] In this section, you can find the general steps necessary to add a bulk action: Go to the organization or project level and select **Bulk Option** in the upper ribbon.The platform opens a page featuring the first of four (4) steps. UUID-a75fed38-3934-de63-c1a0-2872c8395556

UUID-a75fed38-3934-de63-c1a0-2872c8395556

In *Step 1*, choose the site or sites where you want to apply the changes and select **Next Step**. You see the full list of bulk actions only if you select one (1) site in *Step 1*. If you select multiple sites, the platform shows a reduced list of bulk actions in *Step 2*: | - *Activate/Deactivate Sites* - *Add Dataflow Connection* - *Delete Sites* - *Disable Export* - *Enable Export* | - *Import* - *Import & Export All* - *Move into Project* - *Remove Service Data Source* - *Reset Sites* | | --------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------- | In *Step 2*, choose the bulk action and select **Next Step**. In *Step 3*, provide more details for the desired bulk action and select **Execute**. If you use **Copy Exports** bulk action in this step, you can choose what you want to copy. Choosing the following options affects the target site's dataflow as follows: * If you choose **Copy import-intermediate**, the platform overwrites the entire import-intermediate stage of the target site's dataflow, including column names, dataflow connections, and rule boxes. * If you choose **Copy intermediate-export**, the platform overwrites the entire intermediate-export stage of the target site's dataflow, including column names, dataflow connections, and rule boxes. UUID-a1398326-170e-8a6b-844a-1893d5177df0

UUID-a1398326-170e-8a6b-844a-1893d5177df0

If you aren't sure that you want these changes, save a Dataflow version before making the **Copy Exports** bulk action to have an opportunity to revert to the original dataflow. See [Manage versions in Dataflow](https://help.productsup.com/en/29493-29497-organize-your-dataflow-columns-and-attributes.html#UUID-29d1496f-2f39-6677-788e-f7daf8528370_section-idm232216577475068). In *Step 4*, view the performed changes.You can leave this screen by selecting **Return to organization page**. You can also go to one of the sites where you performed the changes by selecting the name of the needed site. See the following documents for the specific steps to set up the needed bulk action: * [Apply rule boxes in bulk across multiple sites](/docs/help-center/add-a-rule-box/advanced-rule-box-options#section-idm232217535173292) * [Move multiple sites to a different project in bulk](/docs/help-center/get-started/manage-your-organization-projects-and-sites/edit-site-settings#section-idm232209042059852) * [Change the state of multiple sites in bulk](/docs/help-center/get-started/manage-your-organization-projects-and-sites/edit-site-settings#tip-idm243411323387524) * [Reset data for multiple sites in bulk](/docs/help-center/get-started/manage-your-organization-projects-and-sites/edit-site-settings#section-idm232209049596325) * [Delete multiple sites in bulk](/docs/help-center/get-started/manage-your-organization-projects-and-sites/edit-site-settings#section-idm232209057735875) * [Map attributes across multiple sites in bulk](/docs/help-center/map-and-optimize-your-data/dataflow/use-dataflow-to-map-your-attributes-from-import-to-export#section-idm4605326145878432706744933005) * [Manually importing multiple sites in bulk](/docs/help-center/import-data-feeds/import-your-data-into-productsup/add-a-main-data-source-to-import-your-products#section-idm243410997409660) # Set up the Walmart Marketplace Product Creation export import { Callout } from "fumadocs-ui/components/callout"; import { Step, Steps } from "fumadocs-ui/components/steps"; The Walmart Marketplace Product Creation export lets you create new product listings on Walmart Marketplace and update existing ones directly from Productsup. It connects via the Walmart Marketplace REST API and currently supports the US marketplace. Prerequisites [#prerequisites] Before setting up the Walmart Marketplace Product Creation export, confirm the following: * You have an approved Walmart Marketplace seller account (US) with access to Seller Center. * You are ready to authorize Productsup to access your Walmart account. You do this as part of [Configure the destination](#configure-the-destination) below. Add the export [#add-the-export] Go to **Exports** from your site's main menu and select **ADD EXPORT**. Search for **Walmart Marketplace - US - Product Creation** and select **Add**. Select the export's name link. Configure the destination [#configure-the-destination] Select **Add Destination** and choose *Walmart Marketplace Products* from the dropdown. Give it a name as desired and select **Save**. In **Authentication**, choose an existing authentication or select **Add New Authentication**. Selecting **Add New Authentication** redirects you to Walmart's authorization page. After you approve access, Walmart redirects you back to Productsup automatically. Toggle **Active** to **On** to activate the destination. Select **Save**. Set up category mapping [#set-up-category-mapping] Walmart has more than 6,700 product types, each with its own required and optional category-specific attributes. Map your product categories to Walmart's categories using a Classification Mapping list so Productsup knows which attributes to make available to you. Not every Walmart category is available in Productsup today. If a category you need doesn't appear when you set up the Classification Mapping list below, contact [support@productsup.com](mailto:support@productsup.com) to request it. Automotive product types that require fitment data (vehicle compatibility submitted as ACES/PIES files) aren't supported. If you sell automotive parts that require fitment, contact your Customer Success Manager before setting up this export. Go to **Lists** from your site's main menu and select **ADD LIST**. Choose **Classification Mapping** and select **Continue**. In **Name**, give your list a desired name. In **Classification**, choose **Walmart Marketplace - US - Product Creation**. In **Stage**, select **Import** to replace your imported categories with the categories accepted by Walmart. In **Attribute**, choose your category attribute from your imported attributes. Select **Add**. Map your categories, pre-populated in the right-hand column, to the corresponding Walmart product categories in the **Replace term** column. Create a new Classification Mapping list every time you change the category attribute in your data source or import new category values into your site. Map attributes in Dataflow [#map-attributes-in-dataflow] Go to **Dataflow** from your site's main menu and select **Walmart Marketplace - US - Product Creation** in the dropdown on the left. Map your category attribute in the import stage to `__category_path` in the intermediate stage. Select `__category_path` in the intermediate stage to add the Classification Mapping rule box. Choose the list you created in [Set up category mapping](#set-up-category-mapping) from the **List** dropdown, and configure **Case Sensitivity** and **On No Match** as needed. Select **Save**. Select **Run** or **Import** in the top-right corner to load your categories and attributes into Dataflow. This first run is expected to fail — no data is exported yet. Its only purpose is to load the Walmart categories and their attributes into Dataflow. Once the run completes, open the **Classifications** dropdown in the top toolbar of Dataflow. It now lists all your mapped Walmart product categories. Refresh the page if the dropdown doesn't appear. Select each category in the **Classifications** dropdown and map its relevant attributes from import to export. Attributes with a fork icon next to their name are specific to the selected category. Set up variants [#set-up-variants] If your products have variants, for example different sizes, colors, or counts of the same product, set up each variant as a separate row. All variants in a group share the same `variantGroupId`. Map the following attributes: | Attribute | Description | | :---------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | `variantGroupId` | The same value for every item in the variant group. | | `isPrimaryVariant` | Set to *Yes* for exactly one item in the group — typically the top-selling item or the one with the most inventory. This is the item Walmart displays by default. | | `variantAttributeNames` | Up to three attributes that vary within the group, for example *size*, *color*, or *countPerPack*. Each attribute you list here must also be mapped and visible at the export stage, or the submission fails. | For example, a curtain set available in 2 sizes and 6 colors needs 12 rows, all sharing the same `variantGroupId`. Set up swatch images [#set-up-swatch-images] For visual variants such as color, you can provide swatch images that Walmart displays on the item page. Map the following attributes: | Attribute | Description | | :----------------------- | :----------------------------------------------------------------------------------------------------------- | | `swatchVariantAttribute` | The attribute the swatch represents, for example *color*. | | `swatchImageUrl` | The URL of the swatch image for each variant. Walmart recommends a resolution of 100 x 100 pixels at 72 ppi. | Include swatch image URLs on every row when you resubmit variants. Leaving them out can remove existing swatch images from the live listing. Common pitfalls [#common-pitfalls] | Pitfall | What to do | | :----------------------------------------------------------- | :--------------------------------------------------------------------------------------------------------------------------------------------------- | | The first export run fails | This is expected. The first run only loads Walmart's categories and attributes into Dataflow. Map the remaining mandatory attributes and run again. | | The Classifications dropdown doesn't show your categories | Refresh the page after the first run. If categories still don't appear, check that your category attribute is correctly mapped to `__category_path`. | | A category you need isn't in the Classification Mapping list | Contact [support@productsup.com](mailto:support@productsup.com) to request it. | | Variant submissions are rejected | Confirm that every attribute listed in `variantAttributeNames` is also mapped and visible at the export stage. | # Add CJ Affiliate Products Delta API export import { Callout } from "fumadocs-ui/components/callout"; import { Step, Steps } from "fumadocs-ui/components/steps"; CJ Affiliate is one of the biggest online advertising companies operating worldwide in the affiliate marketing industry. You can use the *CJ Affiliate Products Delta API* export template in Productsup to send your new or updated product data to CJ Affiliate via API. The export uses delta logic, meaning it sends only updated product data instead of the entire catalog. Prerequisites [#prerequisites] To send your products to CJ Affiliate, you need: . An account in CJ Affiliate. Set up CJ Affiliate Products Delta API export [#set-up-cj-affiliate-products-delta-api-export] Go to **Exports** from your site's main menu and select **ADD EXPORT**. Search for *CJ Affiliate Products Delta API*, hover over it, and select **Add**. UUID-9e2f0c31-a0f4-351b-eafb-ba936d758643

UUID-9e2f0c31-a0f4-351b-eafb-ba936d758643

Go to **Exports** and select *CJ Affiliate Products Delta API*. Select **Add Destination**. Select *Commission Junction* from the **Destination** dropdown, and choose **Save**. In **Company Id**, enter your CJ Company Id. In **Access Token**, enter your Cj Access Token. Leave the **Feedback Import** toggle **On** to let the platform receive feedback files from CJ Affiliate in case of export errors to troubleshoot the setup. Toggle **Active** to **On** to activate the destination. Select **Save**. UUID-ffbebac1-51be-d9e1-626c-90fbfefc34d3

UUID-ffbebac1-51be-d9e1-626c-90fbfefc34d3

Go to **Dataflow** from the site's main menu and choose the added export from the dropdown in the top ribbon on the left. Map the attributes from import to export. See [Use Dataflow to map your attributes from import to export](/docs/help-center/map-and-optimize-your-data/dataflow/use-dataflow-to-map-your-attributes-from-import-to-export) for more information. Your export must have the **AdID** attribute containing the advertiser link IDs for every product from CJ Affiliate. If it is missing in the import file, add it as and additional data source. Or, if only few products are missing the AdIDs, add the attribute in the export stage of the Dataflow and add values using the *Static Value* rule box. See [Add static or dynamic values](/docs/help-center/add-a-rule-box/find-the-needed-rule-box-category/add-static-or-dynamic-values#section-idm243451095539816) to learn how to add a static value. If you want to add many additional images, you must add custom attributes like **additionalImageLink.1** and **additionalImageLink.2**, up to 20 attributes. Each attribute should only contain one image URL. See [Use Dataflow to map your attributes from import to export](/docs/help-center/map-and-optimize-your-data/dataflow/use-dataflow-to-map-your-attributes-from-import-to-export#section-idm4605326417364832706742715884) to learn how to add custom attributes. Check your export readiness. See the following section. Check your export readiness [#check-your-export-readiness] Use analyzer tests in Data View to check your data completeness and readiness for export. Go to **Data View** from your site's main menu and select *CJ Affiliate Products Delta API* from the dropdown at the top left-hand side. Select **Full View** in the top ribbon and refresh the Data View page. For each attribute, select **Analyze** to ensure your data meets the CJ Affiliate requirements. Alternatively, select the **Overview** dropdown and choose **Readiness**. See [Analyze your data in Data View](/docs/help-center/map-and-optimize-your-data/data-view/analyze-your-data-in-data-view) for more information. UUID-b12edf76-a2cf-6c9d-7f85-3f5b5a8ac6dc

UUID-b12edf76-a2cf-6c9d-7f85-3f5b5a8ac6dc

See the core readiness score and correct the data using rule boxes, if needed. UUID-288e1bec-5bb2-f770-0962-1bc383227ffe

Once your data is ready, select **Run** in the top-right corner of your view to send your products to CJ Affiliate. You can open the Run log panel UUID-747bc54c-fc18-5927-c8d7-b2c173ad5d86

UUID-747bc54c-fc18-5927-c8d7-b2c173ad5d86

to check the export progress. # Add Cdiscount Offers export import { Callout } from "fumadocs-ui/components/callout"; import { Step, Steps } from "fumadocs-ui/components/steps"; Cdiscount is one of the largest e-commerce platforms in France. It offers a various products, including electronics, household appliances, and food. The *Cdiscount Offers* export lets you send pricing and stock updates for items already listed on Cdiscount. You can't send new items with it. You can also synchronize order between Producstup and Cdiscount using the the *Cdiscount Orders* data source and the *Cdiscount Order Shipment Delta API* export. See [Set up order sync for Cdiscount](/docs/help-center/export-data-feeds/special-export-setups/set-up-order-sync-for-cdiscount). Add the Cdiscount Offers export [#add-the-cdiscount-offers-export] You can send your offer updates to the items that are already listed on Cdiscount. Go to **Exports** from your site's main menu and select **ADD EXPORT**. Search for *Cdiscount Offers*, hover over it, and select **Add**. UUID-5b331a9e-0f92-3906-4e2d-9d5c956d79d5

UUID-5b331a9e-0f92-3906-4e2d-9d5c956d79d5

In the *Exports* page, select the name of the added export to set it up. Select **Add Destination**, choose *CDiscount offers* from the dropdown, give it a name as desired, and select **Save**. Enter the seller ID in **Seller ID**. Toggle **Preprod environment** to **On** to send offers to the sandbox environment without affecting live Cdiscount data. You can use Preprod environment only if you requested Octopia to enable it for you in Productsup. Toggle **Active** to **On** to activate the destination. Select **Save**. UUID-f984e11e-683b-a008-3e45-60d991e65629

UUID-f984e11e-683b-a008-3e45-60d991e65629

Go to **Dataflow** from the site’s main menu. Choose your *Cdiscount Offers* from the dropdown on the top left. Connect the attributes from the import to export stages. Cdiscount requires the following mandatory attribute: * **Offer/ProductEan** * **Offer/Price** * **Offer/Stock** * **Offer/SellerProductId** * **Offer/EcoPart** * **Offer/ProductCondition** Ensure each of these attributes has values. The platform won't export the offers with empty attributes to Cdiscount. If your data is ready, select **Run** or **Export this export** in the upper right corner of the page. If you want to receive feedback files, contact your Customer Success Manager or [support@productsup.com](mailto:support@productsup.com) to enable this feature. # Add Magento 2.x Product Export import { Step, Steps } from "fumadocs-ui/components/steps"; Introduction [#introduction] The Magento 2.x Product Export lets you export products from the Productsup platform to a Magento 2.x instance. Use the Magento Product Export to enhance your data and provide more product information. Add and set up export [#add-and-set-up-export] To add the *Magento 2.x Product Export* in Productsup: Go to **Exports** from your site’s main menu. Select **ADD EXPORT** and search for *Magento 2.x Product Export.* UUID-507fd602-26c8-312a-5795-f50132d00cbb

UUID-507fd602-26c8-312a-5795-f50132d00cbb

Select **Add** and confirm adding it again as an export. In the export setup, select **Add Destination** and choose *Magento 2 API Product Export* from the drop-down list. Now enter a destination **Name**. UUID-e04357ea-d1e2-ba3c-59e8-59bd811a164a

UUID-e04357ea-d1e2-ba3c-59e8-59bd811a164a

In **Authentication**, choose **Select authentication**. Then choose an available authentication from the drop-down list or select **Add New Authentication**. You can also choose to use pre-existing export tags from another platform in **Authentication**. See [Add OAuth authentication to external systems](/docs/help-center/import-data-feeds/import-your-data-into-productsup/add-oauth-authentication-to-external-systems) to set up authentication with another platform. Add your Magento store URL in **Base URL**. Switch **Feedback import** to **On** if you want an error file returned to the platform once your data export finishes. Go to step [10](#N1616685345815) if **Feedback import** is set to **Off**. Choose a column that you want to receive a feedback import file on in **Main feed connection column**. Enter the column that connects to your feedback import in **Feedback file connection column**. Select a **Magento Version** from the drop-down list. Turn on the destination by switching **Active** to **On**. Select **Save**. UUID-a668a1d2-05d5-91fa-2c60-980dc36b6d9a

UUID-a668a1d2-05d5-91fa-2c60-980dc36b6d9a

# Add Google Product Inventory Feed (LIA) export import { Callout } from "fumadocs-ui/components/callout"; import { Step, Steps } from "fumadocs-ui/components/steps"; Introduction [#introduction] Google Local Inventory Ads (LIA) are Google Shopping ads that provide your customers with up-to-date information on prices, availability, and location of your in-store items. Google Local Inventory Ads (LIA) information is an additional data feed to the Google Merchant Center (GMC) main data feed. Productsup lets you prepare the Google LIA additional data feed using one of the export templates: . The *Google Product Inventory Feed (LIA)* export sends your data to selected destination, such as an SFTP of your choice. We recommend this export for exporting feeds with over 10M items. . The *Google LIA Delta API* export sends your data directly to Google via API. This export sends only the updated items, rather than re-sending the entire catalog. The Google LIA exports are part of the *LIA Module*, available at an additional cost in all platform editions. Contact your Customer Success Manager to discuss adding it to your organization. Productsup still supports the legacy variant of the Google LIA export called *(Legacy) Google Local Product Feed (LIA)*, in case you are already using it. Prerequisites [#prerequisites] Before setting up any Google LIA exports, follow these steps: . Create a Google account and enable your local inventory ads. See Google Local inventory onboarding guide: * [Step 1: Enable local inventory ads or free local product listings](https://support.google.com/merchants/answer/3425157?hl=en\&ref_topic=7023401). * [Step 2: Add your business information](https://support.google.com/merchants/answer/7457386?hl=en\&ref_topic=7023401). * [Step 3: Link your Business Profiles and select your business group](https://support.google.com/merchants/answer/10507042?hl=en\&ref_topic=7023401). * [Step 4: Select a landing page experience for your local inventory ads](https://support.google.com/merchants/answer/10507043?hl=en\&ref_topic=7023401). * [Step 5: Upload a primary feed](https://support.google.com/merchants/answer/10947084?hl=en\&ref_topic=7023401). The Productsup Help Center doesn't bear any responsibility for the accuracy of the information provided in the [Google Local inventory onboarding guide](https://support.google.com/merchants/answer/3540291?hl=en\&visit_id=638112759963254050-2537880770\&ref_topic=7023401\&rd=1). The steps of the guide aim to help you follow the process between the Productsup platform and Google instances. . Have a separate site for GMC in Productsup and set up the *Google Merchant Center* export for your main feed. See [Add Google Merchant Center export](/docs/help-center/export-data-feeds/add-export/add-google-merchant-center-export). If you want to make a product available online only and prevent it from appearing in certain locations, use the **\[excluded\_destination]** attribute. . Set up a new site in Productsup for the Google LIA export. See [Create or copy a site](/docs/help-center/get-started/manage-your-organization-projects-and-sites/create-or-copy-a-site). The GMC feed and the LIA feed must be in different sites. The reason is that the Google LIA data feed can have the same item ID multiple times for every store where the item is available, unlike the GMC feed, which has unique IDs per item. That leads to different settings for the two sites. Add and set up the Google Product Inventory Feed (LIA) export [#add-and-set-up-the-google-product-inventory-feed-lia-export] If you want to prepare and first get your data feed in an SFTP and then manually upload the feed to the Google account, use the *Google Product Inventory Feed (LIA)* export: Go to **Exports** from your Google LIA site's main menu and select **ADD EXPORT**. Search for *Google Product Inventory Feed (LIA)*, hover over the export, and select **Add**. UUID-35c16162-e50d-a212-d37b-4f9949148707

UUID-35c16162-e50d-a212-d37b-4f9949148707

On the Exports page, select the name of the added export to set it up. Select **Add Destination**, choose a necessary destination from the dropdown, give it a name as desired, and then select **Save**. You can choose any destination matching Google's requirements. See [Upload options](https://support.google.com/merchants/answer/188477). Go to the **Settings** tab and ensure that **Product Uniqueness** is unselected to let products repeat multiple times in the data feed for different stores. UUID-16689317-dd63-f557-0784-19379ae658d1

UUID-16689317-dd63-f557-0784-19379ae658d1

Go to **Dataflow** and map all mandatory attributes for Google Product Inventory Feed (LIA) from import to export. The mandatory attributes are in blue. * **id** shows an individual SKU or item ID. SKUs may appear multiple times in the feed because numerous store locations may have the same items. Ensure that your GMC and LIA feeds use the same ID values. * **store code** shows in which stores customers can find the items. The store code values are case-sensitive and must match the store codes in your Google Business Profiles. See [Google Business Profile](https://www.google.com/business/) for more information. * **availability** shows whether an item is in or out of stock. As of June 15, 2023, the **quantity** attribute is no longer mandatory, while **availability** is required. See [2023 Merchant Center product data specification update](https://support.google.com/merchants/answer/13648265?sjid=11833305773604807122-EU%7Chttps://support.google.com/merchants/answer/13648265?sjid=11833305773604807122-EU%7Csmart-link). UUID-c7420d2d-a98c-98cc-98ff-5f21049a2200

UUID-c7420d2d-a98c-98cc-98ff-5f21049a2200

Select **Export** in the top right corner of the page to run the export. Next, finalize the setup process on the GMC side and upload your LIA feed to Google. Finalize your registration in Google and submit LIA data [#finalize-your-registration-in-google-and-submit-lia-data] To finalize the setup process and upload your LIA feed to Google, you must complete your registration in Google Merchant Center. See [Local inventory onboarding guide](https://support.google.com/merchants/answer/3061590?hl=en\&ref_topic=7023401) and follow the steps: * [Step 6b: Create a local product inventory feed - Step 3: Upload your local products inventory feed](https://support.google.com/merchants/answer/7023001?hl=en\&ref_topic=7023401) * [Step 6c: Verify your About page (Austria, Germany, and Switzerland only)](https://support.google.com/merchants/answer/3061590) * [Step 7: Request inventory verification](https://support.google.com/merchants/answer/7455784?hl=en\&ref_topic=7023401). * [Step 8: Link your Merchant Center and Google Ads accounts (local inventory ads only)](https://support.google.com/merchants/answer/7022488?hl=en\&ref_topic=7023401). * [Step 9a and 9b: Enable local products in your Shopping campaigns](https://support.google.com/merchants/answer/10506537?hl=en\&ref_topic=7023401). Add and set up the Google LIA Delta API export [#add-and-set-up-the-google-lia-delta-api-export] Alternatively, if you want to send your data directly to Google via API, use the *Google LIA Delta API* export: Go to **Exports** from your Google LIA site's main menu and select **Add export**. Search for *Google LIA Delta API*, hover over the export, and select **Add**. UUID-ccc2fb78-9fcf-b13b-9882-8b8c5ca895d2

UUID-ccc2fb78-9fcf-b13b-9882-8b8c5ca895d2

On the Exports page, select the name of the added export to set it up. Select **Add Destination**, choose *Google LIA Delta Export* from the dropdown, give it a name as desired, and then select **Save**. Enter your Google Merchant Center account ID in **Account ID**. Select **Add New Authentication** or choose a previously created authentication from the **Select authentication** dropdown. See [Add OAuth authentication to external systems](/docs/help-center/import-data-feeds/import-your-data-into-productsup/add-oauth-authentication-to-external-systems) to set up authentication with another platform. Enter your merchant ID in **Merchant ID** to send data directly to the selected Merchant Center account. If you have a multi-client Merchant Center account, enter the ID of the relevant sub-account. If you have several sub-account, you must add and set up a separate export for each of them. Leave **Feedback Import** on **On** if you want to receive a response directly from GMC in case of any export failures. Toggle **Active** to **On** to activate the destination. Select **Save**. Go to **Dataflow** and map all mandatory attributes for Google LIA from import to export. The mandatory attributes are in blue. * **productId** shows a unique item identifier. * **price.value** shows the price of an item. * **price.currency** contains the currency code for the price, following ISO currency standards such as *USD* or *EUR*. * **availability** indicates whether the item is in stock. * **storeCode** contains the code of the specific local store. * **language** shows the code of the language used to display information about an item, such as *en* for English. * **country** contains the code of the country where the store is located. * **merchantID** shows the unique identifier of the Google Merchant Center account. UUID-6b3df7cf-b172-a935-166b-2f456a8c0061

UUID-6b3df7cf-b172-a935-166b-2f456a8c0061

Select **Export** in the top right corner of the page to run the export. # Add Digitec Galaxus export import { Callout } from "fumadocs-ui/components/callout"; import { Step, Steps } from "fumadocs-ui/components/steps"; Introduction [#introduction] Digitec Galaxus is the largest online retailer in Switzerland that operates two online shops called digitec and Galaxus and runs several physical outlets across different German- and French-speaking parts of the country. The digitec store primarily focuses on selling electronics, while Galaxus offers a broader array of products spanning household, DIY, sports, office, fashion, and other categories of goods. Prerequisites [#prerequisites] . An established partnership with Digitec Galaxus. See [Join our merchant programme!](https://www.galaxus.ch/en/page/join-our-merchant-programme-12462). . An FTP server account and connection data.Digitec Galaxus supports submitting all product data to their marketplace through an FTP server. See [Data Transmission](https://confdg.atlassian.net/wiki/spaces/PI/pages/168665885047/Product+Data) for more info on establishing your FTP server access and contact Digitec Galaxus to get your FTP connection data. Digitec Galaxus exports in Productsup [#digitec-galaxus-exports-in-productsup] There are four separate Digitec Galaxus exports in the Productsup platform: Stammdaten, Verfügbarkeit und Preis, Eigenschaften, and Zubehör. Each of these exports contains different sorts of data that you can submit to the Digitec Galaxus marketplace. Stammdaten, Verfügbarkeit und Preis, and Eigenschaften are obligatory exports that you must set up to send your products to Digitec Galaxus. The Zubehör export is optional. Digitec Galaxus - Stammdaten export [#digitec-galaxus---stammdaten-export] The Stammdaten export contains all basic product data, such as product ID, GTIN, category, product description, product title, image URLs, etc. This export can contain German, French, Italian, and English product data. Language variations of attributes' names end with a corresponding language code: `_DE`, `_FR`, `_IT`, `_EN`. Digitec Galaxus - Verfügbarkeit und Preis export [#digitec-galaxus---verfügbarkeit-und-preis-export] The Verfügbarkeit und Preis export contains data on stock levels and prices for every product from the Stammdaten export. Digitec Galaxus - Eigenschaften export [#digitec-galaxus---eigenschaften-export] The Eigenschaften export enriches your product data with attributes relevant for the customer, such as product color, size, material, features, technical details, etc. This export can contain German, French, Italian, and English product data. Language variations of attributes' names end with a corresponding language code: `_DE`, `_FR`, `_IT`, `_EN`. The Eigenschaften export requires a separate row for every attribute of a product, which is why the CSV output file contains as many rows for each product as the number of German attributes that product has. Every row in the output file contains the following columns: UUID-a2be22f1-ade8-2b0d-ef45-67f3b25f186d

UUID-a2be22f1-ade8-2b0d-ef45-67f3b25f186d

* `ProviderKey` - This is the product ID. * `SpecificationKey` - This is the ID of the product attribute described in this row. * `SpecificationGroup_LanguageCode` - This is the attribute group to which the attribute described in this row belongs. For example, if a row describes the attribute height, its attribute group can be dimensions. You can specify your attribute group in multiple languages. * `SpecificationKey_LanguageCode` - This is the attribute's name. You can specify it in multiple languages. * `SpecificationValue_LanguageCode` - This is the attribute's value. You can specify it in multiple languages. Currently, Productsup doesn't support the columns `SpecificationKey` and `SpecificationGroup_LanguageCode` because they aren't mandatory for the Eigenschaften export. Productsup leaves them blank in the output file without affecting the overall success of exporting products to Digitec Galaxus. Digitec Galaxus - Zubehör export [#digitec-galaxus---zubehör-export] The Zubehör export is optional. You don't have to set it up in Productsup to send your products to the Digitec Galaxus marketplace. However, you can set it up to supplement your products from the Stammdaten feed with related items that customers can buy as accessories to those products. This export has only two attributes: `ProductKeyMainProduct` and `ProductKeyAccessoryProduct`. Add and set up the exports [#add-and-set-up-the-exports] To add the Digitec Galaxus exports to Productsup, follow these steps for each export. The Stammdaten, Verfügbarkeit und Preis, and Zubehör exports have the same setup process, while the setup of the Eigenschaften export has some differences outlined in notes throughout the steps. Go to **Exports** from your site’s main menu. Select **ADD EXPORT** and search for *Digitec Galaxus - Stammdaten*, *Digitec Galaxus -Verfügbarkeit und Preis*, *Digitec Galaxus - Eigenschaften*, or *Digitec Galaxus - Zubehör*. UUID-1e218f6c-ee8b-bf60-e888-399768068bdc

UUID-1e218f6c-ee8b-bf60-e888-399768068bdc

Select **Add** on the needed channel, give it a custom name if you desire, and again select **Add**. Select **Add Destination** and choose *SFTP/FTP/FTPS Server* from the drop-down list. Enter a custom name as desired in **Name** and select **Save**. In the destination setup, select the needed protocol in **Protocol**, enter your connection data in **Host**, **Username**, **Password**, and **Directory**, select **On** in **Active**, and then select **Save**. See [Export your data to an FTP, SFTP, or FTPS server](/docs/help-center/export-data-feeds/set-up-an-export-destination/add-an-ftp-sftp-or-ftps-destination) for more details. UUID-02f61a68-a84a-c8bd-f25c-6e7053a1a498

UUID-02f61a68-a84a-c8bd-f25c-6e7053a1a498

For export testing purposes, you can select **Add Destination** once more and choose *Productsup Server* from the drop-down list, enter a custom name as desired in **Name**, and select **Save**. Using this destination, you can look at your output files before sending them to Digitec Galaxus. For the Eigenschaften export, don't add any destination and skip Step 3 altogether. This export doesn't require any destination because of the writer class added in Step 4. This step is relevant for the Eigenschaften export only.Go to the *Labels, Tags & Sorting* tab on the channel setup page. In the **Export Tags** panel, find the **Key** field and add `custom_csv_writer_class`. In **Value**, add `ProductsUp_Csv_File_Writer_DigitecGalaxus_VollstandigeEigenschaften`. Select **Add Tag** and then select **Save**. In Dataflow, Productsup maps the mandatory attributes of the export stage with their respective attributes in the intermediate stage automatically. If you want to map non-mandatory attributes, you must do it manually.Go to **Dataflow** and select the needed export in the drop-down menu on the left. Check that your import stage has the information required for the relevant export attributes. If not, add the needed information to your data source and trigger an import by selecting **Import** in the upper-right corner of your view in **Dataflow**. The Eigenschaften export in **Dataflow** automatically creates two attributes in the export stage: `ProductKey` and `ProviderKey`. To set up your export properly, you need to add the rest of the relevant attributes to the export stage manually.The attributes you add here should be the product attributes you want to display on Digitec Galaxus, such as color, brand, size, etc. Later, the writer class you added in the channel setup restructures products and attributes in the output file featuring the `SpecificationKey_LanguageCode` and `SpecificationValue_LanguageCode` columns.To add an attribute to the export stage in Dataflow: 1. Go to **Dataflow** from your site's main menu 2. Select **Drop or Click to add new field** under the export stage 3. Give the attribute a name 4. Select **Save** UUID-ccfed459-faf9-9155-2358-d76bd817c2ce

UUID-ccfed459-faf9-9155-2358-d76bd817c2ce

Mind that Productsup follows specific attribute naming rules while processing the export. Make sure to: * Use the language codes `_FR`, `_IT`, `_EN` at the end of attribute names in French, Italian, and English, respectively. * Use either the language code `_DE` or no language code at all at the end of attribute names in German. The minimum requirement for the Eigenschaften export to work is one (1) attribute in German per row. Once you have all the needed information in the import stage and all relevant attributes in the export stage, select the node of a chosen attribute in one stage and drag a line from that node to the node of a corresponding attribute in the next stage to map the attributes. You should map all relevant attributes from import to intermediate and then from intermediate to export. # Add Amazon Inventory and Price Update SP-API export import { Callout } from "fumadocs-ui/components/callout"; import { Step, Steps } from "fumadocs-ui/components/steps"; The *Amazon Inventory and Price Update SP-API* export lets you send updates on inventory and prices for the items on Amazon. This API-based export uses delta files, sending only new, updated, and deleted items to Amazon instead of the entire catalog. See [Add Amazon Seller Central – Product Creation (US) export](/docs/help-center/export-data-feeds/add-export/add-amazon-seller-central-product-creation-us-export) to learn more about the Amazon ecosystem in Productsup. Prerequisites [#prerequisites] Before adding the *Amazon Inventory and Price Update SP-API* export in Productsup, you need to: . Create an Amazon seller account. You need to provide your account data to Productsup to connect to Amazon via the Selling Partner API. . Upload your data to Amazon. . Import your inventory and price updates to Productsup. Add and set up Amazon Inventory and Price Update SP-API export [#add-and-set-up-amazon-inventory-and-price-update-sp-api-export] Go to **Exports** from your site's main menu and select **ADD EXPORT**. Search for *Amazon Inventory and Price Update SP-API*, hover over it, and select **Add**. On the Exports page, select the name of the added export to set it up. Select **Add Destination** and choose *Amazon Price & Inventory export* from the drop-down list, give it a name as desired, and select **Save**. UUID-191b9bb5-91c5-cdb0-51ac-2f3c27d7538d

UUID-191b9bb5-91c5-cdb0-51ac-2f3c27d7538d

In **Authentication**, choose the Amazon authentication you previously set up in your organization, project, or site. If you haven't set up Amazon authentication yet, perform the following steps: 1. Select **Add New Authentication**. UUID-6c723739-f030-e9c5-8e46-70795b0e4af4

UUID-6c723739-f030-e9c5-8e46-70795b0e4af4

2. Select *Amazon Authentication (BETA version by Amazon)* in **Type**. You can optionally give your authentication a name. 3. Select **Next**. 4. If applicable, select **Region** and **Country** to choose your marketplace country and locale. 5. Select **Connect**. Before proceeding, Productsup redirects you to Amazon to finalize your authentication. After completing the authentication setup, Amazon redirects you back to Productsup. 6. Close the confirmation window to proceed. Choose the market of interest in **Marketplace ID**. Enter your merchant token from your Amazon seller account in **Seller ID**. Switch **Active** to *On* to activate the destination. Select **Save**. Next, map the attributes for the export. See the following section. Map the attributes to Amazon Inventory and Price Update SP-API export [#map-the-attributes-to-amazon-inventory-and-price-update-sp-api-export] To update price and inventory using JSON-based feeds, you must map mandatory attributes from the import to export stage in Dataflow. Go to **Dataflow** from your site's main menu and select *Amazon Inventory and Price Update SP-API* in the drop-down menu on the left. Map all mandatory attributes from import to export: * **SKU** is a unique identifier to track and manage your inventory. * **FulfillmentCenterID** is the name of the fulfillment channel. Possible values are `DEFAULT (MFN)`, `AMAZON_NA (FBA)`, `AMAZON_EU (FBA)`, and `AMAZON_JP (FBA)`. Depending on your fulfillment method, the mapping should be as follows: * MFN (Merchant Fulfilled Network) is a shipping method where you list your items on Amazon international marketplaces and choose to ship them by yourself to each customer.If MFA is your fulfillment method, unmap the **FulfillmentCenterID** attribute. The platform will automatically consider the `DEFAULT (MFN)` value for this attribute. * FBA (Fulfillment by Amazon) is a service that lets you outsource order fulfillment, including storage, packing, and shipping, to Amazon.If FBA is your fulfillment method, map the **FulfillmentCenterID** attribute containing your fulfillment method as a value. It's impossible to switch from MFN to FBA and back by changing the attribute's values. First, you need to change your fulfillment method in your Amazon account and only then adjust the feed in Productsup. See [List products for Fulfillment by Amazon](https://sellercentral.amazon.com/help/hub/reference/external/200141220?initialSessionID=144-0577865-4577356\&ld=NSGoogle\&pageName=US%3ASD%3AFBA-main) for mote information. * **Quantity** is the MFN quantity available for fulfillment. * **StandardPrice** is a standard price when you haven't scheduled any discounted price. * **StandardPrice.currency** is the currency of the **StandardPrice** attribute. Optionally, you can map the following attributes: * **RestockDate** is the date when an item will be available again. The date format should be `yyyy-mm-dd`. * **FulfillmentLatency** is the handling time for MFN fulfillment. The format is the number of days. * **Available** shows `true` or `false` for the MFN inventory instead of providing a quantity value. Map either **Available** or **Quantity**. You can't map both; otherwise, you will get an error from Amazon. * **MinimumSellerAllowedPrice** is the minimum price for automated pricing. * **MaximumSellerAllowedPrice** is the maximum price for automated pricing. * **Sale.StartDate** and **Sale.EndDate** contain the discounted price start and end dates. The date format is `yyyy-mm-dd`. * **Sale.SalePrice** is a discounted price. If your data is ready, select **Run** or **Export** in the upper right corner of the page. If you don't want to run the entire site, including all active exports set up in it, you can go to **Exports**, select the Amazon Inventory and Price Update SP-API export, and then choose **Export this export**. # Add Meta Shops Ads exports to sell your products on Meta import { Callout } from "fumadocs-ui/components/callout"; import { Step, Steps } from "fumadocs-ui/components/steps"; Introduction [#introduction] Meta Shops Ads are the new shopping format where Meta owns the checkout experience and lets social media users shop, order, and pay directly in the Meta apps. This leads to a smoother shopping experience, higher conversion rates, and more transparent ad performance, which yields a higher return on ad spend. Meta Shops Ads are currently in closed beta testing in the US. The general release of the new ads is due in mid-2023 in the US. There are currently no plans to expand Meta Shops Ads to countries other than the US. To support customers interested in selling products in the US via the new Meta Shops Ads, Productsup has built an ecosystem that sends product and order data to Meta Shops Ads: . *Meta Shops Ads Main*Meta requires receiving your full product catalog every 24 hours and your product data updates every hour. This API-based export uses the destinations *Meta Shops Ads: Data Feed* and *Meta Shops Ads: Delta Upload* to send your full product catalog or product data updates to Meta Shops Ads and meet these requirements. . *Meta Shops Ads - Price & Stock Update*Meta requires receiving your price and stock updates every 15 minutes. This API-based export sends your products' price and stock changes to Meta to meet this requirement. . *Meta Shops Ads - Order Import*This data source imports order data from Meta to let you send it to your order management system. When you import an order from Meta into Productsup, the order status on Meta changes from `CREATED` to `IN_PROGRESS`. . *Meta Shops Ads - Order Fulfilment Export*When your orders have the status `IN_PROGRESS`, you can send shipment and tracking information to Meta using this API-based export. You can notify customers of full and partial shipments. A partial shipment of the order means that not all of the ordered items are in one shipment. You receive a payment transfer from Meta when you confirm the order's shipment and send the corresponding tracking details to Meta. . *Meta Shops Ads - Order Cancellation Export*If you can't accept and ship an order, you can send cancellation information to Meta using this API-based export. You can cancel orders fully or partially. A partial cancellation means that some products in the order are still going to be shipped. Only orders with the status `IN_PROGRESS` can be canceled. . *Meta Shops Ads - Order Refund*If you need to refund an order that you have already shipped, you can send refund information to Meta using this API-based export. You can refund only orders with the status `COMPLETED` or `IN_PROGRESS`. Refunds can be full or partial. The Meta Shops Ads ecosystem in Productsup doesn't manage ads. It only helps you send the needed product and order updates to Meta. You need to manage your ads on Meta. To send your product and order data to Meta Shops Ads, you need to set up this ecosystem in the following order: *Meta Shops Ads Main*. See [Send your full product catalog and its updates to Meta](#section-idm4578928862486433696783562844). *Meta Shops Ads - Price & Stock Update*. See [Send your price and stock updates to Meta](#section-idm4635650123020833696783840529). *Meta Shops Ads - Order Import*. See [Import orders from Meta](#section-idm241684839243865). All exports dealing with order data. See [Send order data to Meta](#section-idm243369678487728). Prerequisites [#prerequisites] The entire Meta Shops Ads ecosystem in Productsup is currently available to a limited number of customers only. If you want to gain access to it, reach out to your Customer Success Manager or contact [support@productsup.com](mailto:support@productsup.com). To set up the Meta Shops Ads ecosystem in Productsup, you need: . A project in your Productsup organization where you are going to create multiple sites pushing and pulling data from Meta. In this separate project, you need to create a separate site for each Meta Shops Ads export. The data source *Meta Shops Ads - Order Import* should also have a separate dedicated site. A separate project for all Meta Shops Ads sites is a recommended option. If it doesn't fit your overall organization structure, you can ignore this advice.However, splitting all product-data exports into separate sites is mandatory to keep your setup easy to manage and let you set up the needed site-running schedules. . A Facebook account. . A commerce account ID that you can find in Commerce Manager on Meta. . A catalog ID that you can find in Commerce Manager on Meta. . A Meta Shops Ads authentication created on the project or organization level to use it across all Meta Shops Ads sites. See [Add OAuth authentication to external systems](/docs/help-center/import-data-feeds/import-your-data-into-productsup/add-oauth-authentication-to-external-systems) for more information.Add this authentication as follows: 1. Go to **Authentication** from your organization's or project's menu and select **ADD AUTHENTICATION**. 2. In **Type**, select *Meta Shops Ads Authentication*, give it a custom name as desired, and select **Next**. 3. In **CMS ID**, enter your commerce account ID. UUID-aa020694-87c8-b38e-e85d-770e952cf73f

UUID-aa020694-87c8-b38e-e85d-770e952cf73f

4. In **Business Name**, enter your business's name as displayed on Meta. 5. Select your location's timezone and currency in the respective fields. 6. Select **Connect** for Productsup to redirect you to a Meta account page where you can give Productsup access to your Meta account. Follow the instructions on Meta to connect the systems. On the *Open your shop* screen, uncheck the box **Facebook ads** to skip creating an ad account and pixel on Meta. 7. Once ready, select **Done** to let Meta redirect you back to Productsup. Close the confirmation window in Productsup to proceed. Add exports to send product data to Meta [#add-exports-to-send-product-data-to-meta] Productsup should be your source of truth for product data. Creating and managing products on Meta directly can cause errors on Meta's site when you run exports in Productsup. Send your full product catalog and its updates to Meta [#send-your-full-product-catalog-and-its-updates-to-meta] According to the Meta Shops Ads requirements, you need to send your full product catalog to Meta once every 24 hours and all product data updates (delta files) once every hour. To set up different scheduling for the full catalog and delta exports, create two (2) separate sites in your Meta Shops Ads project. Full product catalog [#full-product-catalog] One of the sites you created in your Meta Shops Ads project is going to send your full product catalog to Meta. Open this site and follow these steps: Go to **Exports** from your site's main menu and select **ADD EXPORT**. Search for *Meta Shops Ads Main*, hover over it, and select **Add**. UUID-8cd267c8-7def-c065-c1df-acbd73fb15b1

UUID-8cd267c8-7def-c065-c1df-acbd73fb15b1

On the Exports page, select the name of the added export to set it up. Select **Add Destination**, choose *Meta Shops Ads: Data Feed* from the drop-down list, give it a name as desired, and then select **Save**. UUID-ba9c77ff-95cb-4420-575c-82ea8a2c1c36

UUID-ba9c77ff-95cb-4420-575c-82ea8a2c1c36

In **Product Catalog ID**, enter the catalog ID of your relevant catalog in Commerce Manager. In **Feed Name**, enter the name that Meta should display in Commerce Manager as the name of your product catalog. Toggle the **Compression** button to *On* if you want the site to export your feed as a *.zip* file. In **Authentication**, select the Meta Shops Ads authentication you have added to your Productsup organization or project. Toggle the **Active** button to *On* to activate the destination. Select **Save**. Go to **Lists** and add two (2) lists: 1. Add a Partner Taxonomy Mapping list to map your categories to the expected Google category taxonomy by selecting **ADD LIST** and choosing **Partner Taxonomy Mapping**. Then, select **Continue**. 2. Add a Classification Mapping list to map your categories to Meta's categories by selecting **ADD LIST** and choosing **Classification Mapping**. Then, select **Continue**. Give each list a desired name, select **Google MC - US** in **Taxonomy** or **Meta Shops Ads Main** in **Classification**, and choose **Import** in **Stage**. | UUID-0c34cf6f-97d7-3e51-dc9f-f14653957142

UUID-0c34cf6f-97d7-3e51-dc9f-f14653957142

UUID-2cf0ccea-ff28-dfed-6cdb-628b1ee45a39

| | ------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------- | In both list types, select the **Attribute** field to choose the attribute in your import stage that contains your products' category data. Then, select **Add** at the bottom of the page to add the list. In both list types, go through all the values of your category column and select corresponding Google or Meta categories in the **Replace term** column. UUID-c2f3e530-53c5-c709-5844-a3ee7a04273b

UUID-c2f3e530-53c5-c709-5844-a3ee7a04273b

Go to **Dataflow** and select **Meta Shops Ads Main** from the drop-down menu on the left. Map all the needed attributes from import to export. The attributes list you see in the export stage is relevant for products of all your categories. Map your import-stage category attribute to both `category_path` and `google_product_category` in the intermediate stage to add the needed rule boxes and apply the lists. Add rule boxes to apply your created lists to the needed attributes: 1. Select `google_product_category` in the intermediate stage and open the **Select an Option** drop-down menu on the right to find and add the rule box **Taxonomy Mapping**. Choose your Partner Taxonomy list in **List** and select **Save**. 2. Select `category_path` in the intermediate stage and open the **Select an Option** drop-down menu on the right to find and add the rule box **Classification Mapping**. Choose your Classification Mapping list in **List** and select **Save**. To let the site display your category-specific attributes in Dataflow, select **Run** in the top-right corner of your view. This run will fail because you haven't yet mapped all the mandatory attributes, so no data export occurs at this stage. The aim of the run is to import the needed categories and attributes in Dataflow. Once the site run finishes, the **Classifications** drop-down menu appears in the upper ribbon in Dataflow. Select each category in this drop-down menu to let Dataflow display the relevant category-specific attributes in the export stage. Map all the needed attributes from import to export. UUID-851628c1-299a-3792-c36e-44bb28a60f66

UUID-851628c1-299a-3792-c36e-44bb28a60f66

If you can't see the **Classifications** drop-down menu when the site run finishes, try refreshing your page. Go to **Scheduling** and add a schedule to run your site every 24 hours.See [Set up scheduling and triggering processes in Scheduling](/docs/help-center/dashboard-and-monitor/set-up-scheduling-and-triggering-processes-in-scheduling) for more information. UUID-591a7d68-add3-9517-9e3d-593f31df5f14

UUID-591a7d68-add3-9517-9e3d-593f31df5f14

Once all the settings are ready, you can send your product data to Meta. Start a site run manually by selecting **Run** in the top-right corner of your view or let your added schedule perform your first site run automatically at the defined time. Delta files [#delta-files] The other site you created in your Meta Shops Ads project is going to send product data updates (delta files) to your Meta account. Open it and repeat all the steps you just took in the site that exports your full product catalog. Keep in mind the following modifications: * In [see the relevant section](#N1685026414810), choose the destination *Meta Shops Ads: Delta Upload*. UUID-fd7114eb-e739-ed4b-be13-a010953eb42e

UUID-fd7114eb-e739-ed4b-be13-a010953eb42e

* Skip [see the relevant section](#N1685027038044) and [see the relevant section](#N1685027088633). * In [see the relevant section](#N1685027672771), add a schedule to run your site every hour instead. UUID-a170a16a-e2bc-1b92-cdf7-2af70bbba12a

UUID-a170a16a-e2bc-1b92-cdf7-2af70bbba12a

Send your price and stock updates to Meta [#send-your-price-and-stock-updates-to-meta] According to the Meta Shops Ads requirements, you need to send your price and stock updates to Meta every 15 minutes. Create a separate site in your Meta Shops Ads project and follow these steps: Go to **Exports** from your site's main menu and select **ADD EXPORT**. Search for *Meta Shops Ads - Price & Stock Update*, hover over it, and select **Add**. UUID-fbcdbb91-1e34-e9ed-95b3-1df392b31d9d

UUID-fbcdbb91-1e34-e9ed-95b3-1df392b31d9d

On the Exports page, select the name of the added export to set it up. Select **Add Destination**, choose *Meta Shops Ads - Stock and Price Delta Export v1 - DEV* from the drop-down list, give it a name as desired, and then select **Save**. UUID-c501711e-5419-ff73-b794-77fc855558f8

UUID-c501711e-5419-ff73-b794-77fc855558f8

In **CMS ID**, enter your commerce account ID. In **Product Catalog ID**, enter the catalog ID of your relevant catalog in Commerce Manager. In **Authentication**, select the Meta Shops Ads authentication you have added to your Productsup organization or project previously. Toggle the **Feedback Import** button to *Off* if you don't want the platform to receive feedback files from Meta.This feature is active by default to let Productsup receive a feedback file from Meta's Graph API in case of errors. This helps to troubleshoot the export setup. Toggle the **Active** button to *On* to activate the destination. Select **Save**. Scroll down on the export setup page to find the *Delta Files* section. Select **Update Files** and then select **Save** to add delta files to your export. Go to **Dataflow** and select **Meta Shops Ads - Price & Stock Update** from the drop-down menu on the left to map all the needed attributes from import to export. Go to **Scheduling** to let your site run every 15 minutes. See [Set up scheduling and triggering processes in Scheduling](/docs/help-center/dashboard-and-monitor/set-up-scheduling-and-triggering-processes-in-scheduling) for more information. To set up a scheduling interval of 15 minutes, create four (4) schedules with the following setup in **Quick selection** and **Hour(s)**: UUID-8d8673bd-befe-b15a-355c-fcbdf3d75a12

UUID-8d8673bd-befe-b15a-355c-fcbdf3d75a12

In **Minutes**, uncheck the **Random** box and enter `00`, `15`, `30`, and `45` in the four schedules respectively. Once all the settings are ready, you can send your price and stock updates to Meta. Start a site run manually by selecting **Run** in the top-right corner of your view or let the schedules perform your first site run automatically at the defined time. Import orders into Productsup and send order data to Meta [#import-orders-into-productsup-and-send-order-data-to-meta] Import orders from Meta [#import-orders-from-meta] You can sync your Meta orders with your order management system, such as Shopify, via Productsup. Create a separate site in your Meta Shops Ads project and follow these steps: Go to **Data Sources** from your site's main menu and select **ADD DATA SOURCE**. Search for *Meta Shops Ads - Order Import*, select **Add**, give it a name as desired, and then choose **Continue**. UUID-d7a7980a-3ba1-44d5-409f-5ad53b2e016f

UUID-d7a7980a-3ba1-44d5-409f-5ad53b2e016f

In **CMS ID**, enter your commerce account ID. If you want to import orders created within a specific timeframe only, enter the desired dates in **Updated before** or **Updated after**. The expected input format is *YYYY-MM-DD*. If you want your Productsup site to import orders with specific statuses only, enter them in **Order state** and separate them with commas.The supported order statuses are: 1. `FB_PROCESSING` 2. `CREATED` 3. `IN_PROGRESS` 4. `COMPLETED` See [Commerce Platform Overview](https://developers.facebook.com/docs/commerce-platform/order-management/overview#order_state) for more information on order statuses and the order flow. To import specific types of orders only, enter them in **Order filter** and separate them with commas.The supported order types are: 1. `no_shipments` imports orders that you haven't shipped yet. 2. `has_cancellations` imports orders that contain canceled items. 3. `no_cancellations` imports orders that contain no canceled items. 4. `has_refunds` imports orders that contain refunded items. 5. `no_refunds` imports orders that contain no refunded items. In **Authentication**, select the Meta Shops Ads authentication you have added to your Productsup organization or project previously. Specify the desired name of the data source in **Description (optional)**. Select **Save**. Go to **Exports** from your site's main menu and select **ADD EXPORT**. Find your order management system, add it as an export, set it up, and map the needed attributes in Dataflow. Choose **Run** in the upper-right corner of the page to let the site import your order data and send it to your order management system. When you import an order from Meta into Productsup, the order status on Meta changes from `CREATED` to `IN_PROGRESS`. Send order data to Meta [#send-order-data-to-meta] To send shipment, cancellation, and refund data to Meta, create three (3) separate sites in your Meta Shops Ads project and follow these steps to add the needed export in each site: Go to **Exports** from your site's main menu and select **ADD EXPORT**. Search for *Meta Shops Ads - Order*, hover over one of the following exports, and select **Add**: 1. *Meta Shops Ads - Order Cancellation Export* 2. *Meta Shops Ads - Order Fulfilment Export* 3. *Meta Shops Ads - Order Refund* UUID-7daf18cc-35ea-c6be-0dc4-b1d648afd4b4

UUID-7daf18cc-35ea-c6be-0dc4-b1d648afd4b4

Select the name of the added export and choose **Add Destination** to add and set up the following export destinations: 1. For the export *Meta Shops Ads - Order Cancellation Export*, choose the destination *Meta Shops Ads - Order Cancellation Export*. 2. For the export *Meta Shops Ads - Order Fulfilment Export*, choose the destination *Meta Shops Ads - Order Fulfilment Export*. 3. For the export *Meta Shops Ads - Order Refund*, choose the destination *Meta Shops Ads - Order Refund*. Change the names of the added destinations as desired and select **Save**. On the setup page of each destination, take these steps: 1. In **CMS ID**, enter your commerce account ID. 2. In **Authentication**, select the Meta Shops Ads authentication you have added to your Productsup organization or project previously. 3. Toggle the **Feedback Import** button to *Off* if you don't want the platform to receive feedback files from Meta.This feature is active by default to let Productsup receive a feedback file from Meta's Graph API in case of errors. This helps to troubleshoot the export setup. 4. Toggle the **Active** button to *On*. 5. Select **Save**. Go to **Dataflow** from the site's main menu. Choose the added Meta Shops Ads exports in the drop-down menu on the left and map the following attributes from import to export: | Export name | Export-stage attributes | | -------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | *Meta Shops Ads - Order Cancellation Export* | The full list of export-stage attributes: - `facebook_order_id` - `quantity` - `reason_code`See [Cancel order](https://developers.facebook.com/docs/commerce-platform/order-management/cancellation-refund-api#reason_code) for a list of accepted cancellation reason codes. - `reason_description` - `restock_items` - `retailer_id` If you do a full cancellation, the order status on Meta changes to `COMPLETED`. If you cancel an order partially, the order status stays `IN_PROGRESS` until shipped. | | *Meta Shops Ads - Order Fulfilment Export* | The full list of the mandatory export attributes: - `facebook_order_id` - `item_quantity` - `item_retailer_id` - `tracking_carrier` - `tracking_number` - `fulfillment_location_id` or all of the following: The platform doesn't highlight these attributes as mandatory because they are conditional. Meta requires either `fulfillment_location_id` or the full following list. - `address1` - `address2` - `city` - `country_code` - `postal_code` - `province_code` - `state` - `zip` | | *Meta Shops Ads - Order Refund* | The platform doesn't highlight the attributes listed below as mandatory because they depend on your refund type. To refund an order in full, you need to send only two (2) attributes to Meta: - `facebook_order_id` - `reason_code`See [Refund order](https://developers.facebook.com/docs/commerce-platform/order-management/cancellation-refund-api#refund_reason_code) for a list of accepted refund reason codes. To refund an order partially, you need to send either this list of attributes: - `deduction_type` - `deduction_amount` - `shipping_refund.amount` - `shipping_refund.currency` - `retailer_id` - `item_refund_amount.amount` - `item_refund_amount.currency` Or this one: - `deduction_type` - `deduction_amount` - `item_refund_quantity` If you plan to do both full and partial order refunds, you should create two (2) separate sites for the export *Meta Shops Ads - Order Refund* and set up the full and partial refund flows separately. | If your data is ready, select **Run** in the upper-right corner of your view to send order data to Meta. In your order data sites, the feed structure is product-based, meaning that every row is a product. If an order contains multiple products, those products have the same `facebook_order_id` or `tracking_number`. Based on a unique identifier like this, the site groups all products belonging to one order during export and sends notifications to customers about the order or shipment on the whole, and not about separate items in them. # Migrate your Google Content API for Shopping export to the multi-threading destination import { Callout } from "fumadocs-ui/components/callout"; import { Step, Steps } from "fumadocs-ui/components/steps"; Introduction [#introduction] Productsup has implemented the multi-threading feature that lets you export the feed updates up to 6 times faster than before. Previously, you could only use the single-thread approach with destinations such as **Google Content API for Shopping** and **Google Content API for Shopping (single account)** and send updates to Google Merchant Center (GMC) in one bucket one by one. Therefore, for large feeds, the export could take hours. The multi-threading feature lets the platform combine the updates into multiple buckets and then send them to GMC in parallel. Benefits of multi-threading feature for you: . Faster export of product feed updates to GMC. For example, the live tests showed that, with multi-threading, the platform exported updates for 2.6 million products in 1,5 instead of 9 hours. . Possibility to schedule more frequent updates as the export takes less time. The number of updates still shouldn't exceed the defined quota limit. . The import or export schedules that depend on the completion of the export *Google Content API for Shopping* can also start earlier than before. Adjust schedule settings if needed. To let you use the multi-threading feature, we implemented a new destination **Google Content API (single account + multi-thread)**. UUID-d02ebd8b-7218-2751-4b6b-8e6c7e75b3fa

UUID-d02ebd8b-7218-2751-4b6b-8e6c7e75b3fa

The new destination with the multi-threading feature is available for you only if you upload your product feeds to Google Merchant Center via API and for that purpose currently use the export **Google Content API for Shopping** with the destinations such as **Google Content API** or **Google Content API (single account)**. The multi-threading destination isn't available to the export **Google Merchant Center** that uses destinations such as **Productsup Server**, **Google Merchant Center FTP**, and **Google Merchant Center SFTP**. Migrate your existing Google Content API for Shopping to the multi-threading destination [#migrate-your-existing-google-content-api-for-shopping-to-the-multi-threading-destination] You need to migrate your exports to the multi-threading destination by *May 1, 2024*. You can plan to do it at a time and pace comfortable for you. If you don't migrate your exports by May 1, 2024, Productsup will migrate them automatically. The destination *Google Content API for Shopping (single account)* will no longer be available in the platform. To migrate your **Google Content API for Shopping** export to the multi-threading destination: Go to **Exports** from the main menu of the site that contains your *Google Content API for Shopping* export. On the *Exports Overview* page, select your currently active export *Google Content API for Shopping*. UUID-cbed78f2-bf26-e647-8b8e-072f308860a1

UUID-cbed78f2-bf26-e647-8b8e-072f308860a1

Select **Add Destination**, choose **Google Content API (single account + multi-thread)** from the **Destination** drop-down list, leave the default name in **Name**, and then select **Save**. UUID-d02ebd8b-7218-2751-4b6b-8e6c7e75b3fa

Configure your destination: In **Merchant Center ID**, add the ID of your GMC account. This ID should be the same Merchant Center ID as in the previous destination. You can go to the export **Overview** page, select **Setup** the previous destination **Google Content API (single account)**, and copy the ID from the **Merchant Center ID**. UUID-b73fa95f-dda4-354e-4f23-2d04afa69bd2

UUID-b73fa95f-dda4-354e-4f23-2d04afa69bd2

With the new multi-threading destination, you don't need Merchant Center Parent ID anymore. In **Target Country** and **Target Language**, select the same values as in the previous destination. In **Authentication to use**, select the same authentication as in the previous destination. Switch **Enable Error Log File** to **On**. This option lets you view the details of the issues during the recent runs in *Error Log*. Switch **Active** to **On** to activate the destination. Select **Save**. You may leave all other fields with the default settings. Go back to the *Overview* tab of the export *Google Content API for Shopping* and select the **Settings** tab. UUID-fdae540f-ece7-c62c-0805-61c69bed0b7f

UUID-fdae540f-ece7-c62c-0805-61c69bed0b7f

Select **;SEMICOLON** in the **CSV Separator** drop-down menu and select **Save**. UUID-9bfb8a36-e179-17dc-086a-da4f4d816a09

Go back to the **Overview** tab and deactivate the previous destination: Select **Setup** for the previous destination. UUID-3a1475e0-f9ca-01a6-debf-647b63452b65

UUID-3a1475e0-f9ca-01a6-debf-647b63452b65

Switch **Active** to **Off**. Select **Save**. Select **Export this export** or **Run** at the top-right corner of the page to run the export with the new destination. Monitoring and troubleshooting [#monitoring-and-troubleshooting] The multi-threading feature has been successfully tested in the development and live environments. However, we recommend monitoring your exports and checking your Google Merchant Center seller center after the migration to ensure that everything is correct. In rare cases, you may encounter issues such as **daily or per min/request quota is hit** that may cause the export failure. This issue is a known response from Google Content API meaning that the defined limits are consumed, and Google stops receiving updates from the Productsup platform for the given period. This issue may happen when you send millions of updates several times a day for the same subaccount. To prevent this issue, we recommend scheduling exports less frequently or increasing the intervals between the full uploads. In case of issues or if you need assistance with the migration reach out to your Customer Success Manager or contact [support@productsup.com](mailto:support@productsup.com). # Add Ceneo export import { Callout } from "fumadocs-ui/components/callout"; import { Step, Steps } from "fumadocs-ui/components/steps"; *Ceneo.pl* is Poland's most popular comparison site, founded in 2005. Ceneo allows customers compare product offers from more than 18,000 Polish online stores. Productsup created the integration that lets you export your data feed in XML format to Ceneo. Set up Ceneo export [#set-up-ceneo-export] Go to **Exports** from your site's main menu, and select **Add export**. Search for *Ceneo*, hover over it, and select **Add**. UUID-fda63e14-73e1-4a84-a5ad-33cd26737195

UUID-fda63e14-73e1-4a84-a5ad-33cd26737195

On the Exports page, select the name of the added export to set it up. Select **Add Destination**. Select the needed destination option from the **Destination** dropdown, and select **Save**. See [Find the most suitable export destination](/docs/help-center/best-practices/find-the-most-suitable-export-destination) to choose a destination. Select **Save**. Go to **Dataflow** from the site's main menu and choose the added export from the dropdown in the toolbar. Map the attributes from import to export. See [Use Dataflow to map your attributes from import to export](/docs/help-center/map-and-optimize-your-data/dataflow/use-dataflow-to-map-your-attributes-from-import-to-export) for more information. For additional images, you must add and map the **img\_i** attribute in the export stage by selecting **Drop or Click to add new attribute**. These attributes may have multiple values separated by a comma (`,`). UUID-630a7419-b6cf-f899-909f-292f5212828f

UUID-630a7419-b6cf-f899-909f-292f5212828f

If your data is ready, select **Run** or **Export** in the upper right corner of the page. If you don't want to run the entire site, including all active exports set up in it, you can go to **Exports**, select the added *Ceneo* export, and then choose **Export this export**. # Add Attentive Product Export import { Callout } from "fumadocs-ui/components/callout"; import { Step, Steps } from "fumadocs-ui/components/steps"; Introduction [#introduction] Attentive is a US-based SMS marketing platform that lets you send personalized text messages to your customers. Productsup has built Attentive Product Export that lets you create and update your product catalog on Attentive to use the catalog products for SMS messages to your customers. Prerequisites [#prerequisites] To proceed with the Attentive Product Export setup, you need: . An active Attentive account. . The API key that you can create in your [Attentive account](https://ui.attentivemobile.com/signin?redir=%2Fintegrations). Select **Write** in **Product Catalog**. . A contact of your Customer Success Manager at Attentive. You need to contact them to check if the platform sent or updated the product catalog correctly. Add and set up the export [#add-and-set-up-the-export] To add Attentive Product Export in Productsup: Go to **Exports** from your site's main menu and select **ADD EXPORT**. Search for *Attentive Product Export*, hover over it, and select **Add**. UUID-bf471dbe-e553-f7df-f8f6-f129fa46241b

UUID-bf471dbe-e553-f7df-f8f6-f129fa46241b

On the *Exports* page, select the name of the added export to set it up. Select **Add Destination**, choose *Attentive* from the drop-down list, give it a name as desired, and then select **Save**. In **Attentive API Key**, enter the API key you got in your Attentive account to let the Productsup platform authenticate in your Attentive account. UUID-b325f0d3-07e1-9652-144d-dea724c04aff

UUID-b325f0d3-07e1-9652-144d-dea724c04aff

Switch **Sendbox Mode** to **On** if you want to test the export first. Ask your Attentive Customer Success Manager to help you check that the platform exported products correctly. Then, return the setting to **Off** to send the live feed. Switch **Active** to **On** to activate the destination. Select **Save**. Go to **Dataflow** and select your Attentive Product Export from the drop-down menu in the upper ribbon. Map all the needed attributes from import to export and run the export. Each attribute in the Dataflow columns acts as a variant of a product. The `product_id` attribute is the identifier that binds different variants into one product. Various attributes on Attentive can have multiple values and there can be up to 100 variants. These attributes are: * `product_option` * `product_attributes` * `variant_option` * `variant_attributes` * `product_images` UUID-f2570de7-4bc8-9736-46a8-1deb7452e403

UUID-f2570de7-4bc8-9736-46a8-1deb7452e403

By default, you have 3 iterations of the same attributes: * `product_option1_name`, `product_option2_name`, `product_option3_name` * `product_option1_position`, `product_option2_position`, `product_option3_position` * `product_option1_values`, `product_option2_values`, `product_option3_values` If needed, you can add more attributes with the help of the button **Drop or Click to add new attribute** and use the naming convention such as of the default attributes. For example, `product_option4_name`. UUID-85c8b45e-0e99-cc1d-c1ec-e4aa417cc565

UUID-85c8b45e-0e99-cc1d-c1ec-e4aa417cc565

Some fields accept multiple values in a single field. Use `#` as the separator between values. The following fields support multiple values: * `product_categories` — for example, `Footwear#Sportswear` * `product_tags` — for example, `sale#new-arrival` * `product_collections` — for example, `Summer#Outlet` * `product_option{N}_values` — for example, `S#M#L#XL` Verify the catalog export [#verify-the-catalog-export] The Attentive settings don't let you check if the platform sent or updated the product catalog correctly. Contact your Attentive Customer Success Manager and ask them to check it for you. Also, Attentive’s API doesn't provide feedback on the status of the product catalog. Therefore, the Productsup platform can't give you any feedback on errors that could have happened during the export. You can check the analyzer tests to ensure your data is correct. See [Analyze your data in Data View](/docs/help-center/map-and-optimize-your-data/data-view/analyze-your-data-in-data-view). # Add Joor export import { Callout } from "fumadocs-ui/components/callout"; import { Step, Steps } from "fumadocs-ui/components/steps"; Introduction [#introduction] Joor is the largest B2B e-commerce platform used by over 380,000 retailers and 14,000 brands to connect and grow sales around the world. In Productsup, you can add the export *Joor - Product Assets* to send your product images to Joor via API. This export is a delta-based export that sends only the new, changed, or deleted product assets to Joor instead of exporting the entire asset catalog during every site run. Prerequisites [#prerequisites] To send product images to Joor, you need: . A Joor account. . Authentication data for your Joor account, such as the API secret and key, as well as your account ID, username, and password. . A data structure in your site that suits the requirements of the Joor export. Every product-asset combination should be a separate row in your site: * If a product has multiple assets, this product appears in the site in as many rows as there are assets for this product. * If an asset belongs to multiple products, this asset appears in the site in as many rows as there are products with this image. Set up Joor - Product Assets export [#set-up-joor---product-assets-export] Go to **Exports** from your site's main menu, and select **Add export**. Search for *Joor - Product Assets*, hover over it, and select **Add**. UUID-ce63a398-083b-1440-6d07-2c5121003a32

UUID-ce63a398-083b-1440-6d07-2c5121003a32

Go to **Dataflow** from the site's main menu and choose the added export from the dropdown in the toolbar. Map the attributes from import to export. See [Use Dataflow to map your attributes from import to export](/docs/help-center/map-and-optimize-your-data/dataflow/use-dataflow-to-map-your-attributes-from-import-to-export) for more information.The only non-mandatory attribute is `asset_external_id` that can contain your seller-defined image IDs.The mandatory attributes are as follows: * `asset_filename` should contain a unique name of the image as you want Joor to display it. * `asset_source_url` should contain the image URL. * `asset_type` should contain the value *image*. The export doesn't support any other asset types. * `display_order` should contain a number to arrange the order in which Joor displays all images of one product. If a product has only one image, the value in this attribute should be *1*. * One of the following attribute options containing product identifiers that connect your assets to the related products. * If your site has product IDs defined by Joor, you must provide them in `product_id`. * If your site has seller-defined product IDs, you must provide them in `product_external_id` and `product_identifier`. Go to **Exports** and select *Joor - Product Assets*. Select **Add Destination**. Select *Joor Product Assets* from the **Destination** drop-down menu, and choose **Save**. UUID-f08cc3cf-28f8-c4c9-27db-02be3e4957db

UUID-f08cc3cf-28f8-c4c9-27db-02be3e4957db

Toggle **Sandbox mode?** to *On* if you want to send product images to your Joor sandbox. To send product images to your production organization, leave it *Off*. If you want to delete all assets that your products already have on Joor and substitute them with new assets, toggle **Replace existing assets?** to *On*. To keep the assets your products already have on Joor, leave it *Off*. This option only deletes assets for the products featured in your export data. The products that your export data doesn't include keep their existing assets. In **Joor Client ID** and **Joor Client Secret**, provide your Joor API authentication data. In **Account ID**, enter the ID of your Joor account. In **Joor Username** and **Joor Password**, enter your Joor account credentials. In **Batch Size**, enter the desired number of product assets that the platform should send to the Joor API per request. By default, the recommended batch size is `10`. Leave the **Feedback Import** toggle *On* to let the platform receive feedback files from the Joor API in case of export errors. This helps to troubleshoot the setup. Toggle **Active** to *On* to activate the destination. Select **Save**. If your data is ready, select **Run** or **Export this export** in the upper right corner of the page to let the platform send your product images to Joor via API. # Add export import { Callout } from "fumadocs-ui/components/callout"; import { Step, Steps } from "fumadocs-ui/components/steps"; Select from a variety of export templates to add exports or set up your custom exports using blank export templates. Choose you export template from the following categories: * Search engines * Comparison shopping * Shop systems * Marketing and advertising * Marketplaces * Social media * Retailers and distributors * PIM systems * Classification standards * Custom-built * Data pools and product databases * Order sync * Other If the export template you are looking for isn't on the list, contact your Customer Success Manager or [support@productsup.com](mailto:support@productsup.com) to request it. Add export [#add-export] To add a new export: Go to **Exports** from your site’s main menu. Select **Add export** in the top right corner. If you add your first export, select **ADD EXPORT** in the middle of the page. UUID-861419d4-433c-a3e3-0951-bed77ff4945f

UUID-861419d4-433c-a3e3-0951-bed77ff4945f

UUID-916fbad2-1edb-6f36-e6b6-be8e62f5c3ee

Select the close icon **X** in the top right corner to return to the Exports page without saving any changes. Search for the export template name in the search field or choose your export template category from the list on the left. UUID-1815730e-84ef-13a4-b55e-dbad16faa370

UUID-1815730e-84ef-13a4-b55e-dbad16faa370

Select **See all** to unfold a complete list of export templates. If necessary, sort the results by popularity or alphabet. For that, select **See all** on the right and choose a sorting option from the **Sort by** dropdown. UUID-19af844e-d89f-5a20-a851-54f0083a0c73

UUID-19af844e-d89f-5a20-a851-54f0083a0c73

Select a necessary export template name in the list to open its description. UUID-a6b986f5-7fb3-3979-600f-76f987a50ee2

Not all export templates have descriptions yet. The Productsup team is working on adding them. You can select one or several export templates: * To select one (1) export, hover over the necessary export template and select **Add**. UUID-c5e3b5df-17c5-8348-e4fa-52f365ec7b69

UUID-c5e3b5df-17c5-8348-e4fa-52f365ec7b69

* To select several export templates, select the corresponding checkboxes next to their names. Confirm the choice by selecting **Add exports** at the bottom of the page. UUID-ab1b5944-fcac-17fb-b2e8-420793224987

UUID-ab1b5944-fcac-17fb-b2e8-420793224987

If you don't want to proceed with the chosen export templates, uncheck the box for the number of selected exports or select the trash bin icon. The *Export Overview* page opens with your export templates already added. Now, you can set up your exports. Set up your export [#set-up-your-export] When you add one or more exports, the platform automatically returns you to the *Exports* page, where you can view the list of all added export templates and set them up individually. Every export's setup page consists of four (4) tabs: * Overview * Settings * Labels, Tags & Sorting * Pricing In most cases, you only need to set up the destination in the *Overview* tab. Overview tab [#overview-tab] In the export's Overview tab, you can view your export dashboard and add destinations and files. The export dashboard gives you an overview of your export runs: UUID-6f378c6f-8659-f0ee-604a-1c310ad48707

UUID-6f378c6f-8659-f0ee-604a-1c310ad48707

* *Last Export* shows the date and time of the previously run export. * *Next Export* shows the date and time of the next scheduled export if you have set it up . * *Items* shows the quantity of exported items. * *Channel* is the name of the export template used for the current export. To set up your export, you must add a destination in **Destinations**: Select **Add Destination**. UUID-378fd981-7d3e-d6f5-afdb-2c4662709197

UUID-378fd981-7d3e-d6f5-afdb-2c4662709197

Select a destination from the dropdown and then edit its name as needed in **Name**. UUID-0f467505-5948-727e-fbb2-83145085d8a3

Select **Save**. To learn more about destinations, see [Set up an export destination](/docs/help-center/export-data-feeds/set-up-an-export-destination). You change the file name or limit the number of items per file: Select **Setup** in the *Files* section. UUID-335dcd27-016b-dd8e-2b6f-e4498f70db54

UUID-335dcd27-016b-dd8e-2b6f-e4498f70db54

Enter the desired filename and a valid feed format extension in the **Filename** field. Valid feed formats are `.xml`, `.csv`, `.txt`, `and .tsv`. If you want to compress the file, consider using extensions such as `.bz2`, `.zip`, or `.gz`. Enter the number of items you want to export per file in the **Limit (Products per File)** field. Here is some guidance: * To export all items from the file without limits, set the limit to `0`. This means that the export begins with the first item, skipping the table header. * Enter the target value to limit the number of items in your data feed. Limiting can be helpful in case you want to test and try out a new export. You can limit the number of items, for example, to 100, to avoid sending your entire catalog. Select **Save**. To split the data feed into several files: Select **Add File** in the *File* section. Enter the desired filename and a valid feed format extension in the **Filename** field. Valid feed formats are `.xml`, `.csv`, `.txt`, `and .tsv`. If you want to compress the file, regard such extensions as `.bz2`, `.zip`, or `.gz`. Enter the number of items you want to export per file in the **Limit (Products per File)** field. Select **Save**. If you add a second feed, you are not exporting to the channel twice. You only split the export into two (2) feeds in equal parts. Or if you set a limit per file, the platform splits the feeds according to the set limits. For example, if your data feed contains 1,000 items and you set up three (3) files with a 200-item limit, the platform only exports 600 items. The remaining 400 items aren't present in any file. To avoid this situation, set a limit of `0` in your last file to ensure you export all items. If the number of items is less than the sum of all file limits, the platform doesn't update unnecessary files. If you want to receive empty files instead, turn on the *Allow empty files* option in the *Settings* tab. See [Settings tab](#section-idm243459226017834). If you want to export once as a CSV and once as an XML file, you must set up two (2) separate exports for this. You can add a dynamic filename with Twig: Select the **Setup** button in the *Files* section. Enter the filename in the following format: * To use the site and export names as dynamic placeholders in the filename:`{{ Site.id ~ "" ~ Export.name | replace({ "/":"" }) }}.txt` UUID-4a349276-5a91-e5f3-bbe6-eb68f11de845

UUID-4a349276-5a91-e5f3-bbe6-eb68f11de845

* To add the export name and date, enter the following filename:`{{ Export.name | replace({ " ":"" }) ~ "" ~ "now" | date("Ymd") }}.csv` Settings tab [#settings-tab] In the export's Settings tab, you can you can activate the following settings of your export output: UUID-46042343-35b9-cec5-ee7c-a08c750bd1ed

UUID-46042343-35b9-cec5-ee7c-a08c750bd1ed

In **CSV Separator**, select the separator. Leave **CSV Enclosure** selected if you want to enclose data in CSV files containing more than one word or number. Enclosure prevents the platform from incorrectly parsing data when it encounters a delimiter. Select **Enable Pixel Tracking** to activate a tracking pixel, a small piece of code in the form of a pixel that you implement in your website code. When you select **Enable Pixel Tracking**, the **Tracking column** dropdown appears to let you choose the needed attribute. Select **Enable Redirect Tracking** to activate redirect tracking, which collects your site ID, export ID, and product ID. It sets a cookie for the conversion pixel. Select **Shorten Tracking URL** if your channel only accepts a limited number of characters in the tracking URL. When you select **Shorten Tracking URL**, the **Tracking column** dropdown appears to let you choose the needed attribute. We don't support using plugins any longer but if your output file requires a specific format, such as JSON or XLSX. Take the following steps: On the export setup page, go to the *Settings* tab, leave the **Export-Plugin** empty and select **Save**. Open the tab *Labels, Tags & Sorting*, find the section *Export Tags*, and enter the following under **Add new tag**: 1. In **Key**, enter `custom_csv_writer_class`. 2. In **Value**, enter `ProductsUp_Csv_File_Writer_Json`. Select **Add tag** to save it. UUID-c1fdf18f-5be9-498d-e432-6a003e787b6c

UUID-c1fdf18f-5be9-498d-e432-6a003e787b6c

For an Excel XLSX plugin, enter the following value in the **Export-Plugin** field on the export's *Settings* page: * `\Export\Xlsx` UUID-f382bd7e-d278-b5c8-3ac2-66368d76d293

UUID-f382bd7e-d278-b5c8-3ac2-66368d76d293

Contact [support@productsup.com](mailto:support@productsup.com) if you need help with a non-JSON or Excel XLSX plugin. Select **Allow empty files (0 products)** to let Productsup export empty files. It can be helpful if you create internal reports. For example, you can export a file that reports image URLs that lead to a 404 page. In this case, having an empty file with headers is suitable. In **Product Uniqueness**, choose the attribute in the dropdown that you consider unique for your export and select **Add**. The platform prevents duplicate values and exports unique items. You can see **id** selected by default, but you can remove it and select one or more attributes of your choice. Select **Hide unmapped attributes on the Intermediate** to hide unmapped attributes on the intermediate stage. Select **Save**. In some specific exports, such as blank exports, you may find the following settings: Select **Export as XML** to send your file as XML. Remember to change the filename extension to *.xml*. Select **XSL Template for XML Export** to use an XSL template as a style sheet for your XML export. Use **Add Header before Main Header in CSV (optional)** and **Add Header after Main Header in CSV (optional)** if your channel requests additional headers before or after the CSV attribute's header name. You can use these settings in *Blank Export (empty)* and *Blank Export (with ID)*. UUID-fd451ef6-3901-49ce-55b5-4aa340c063b1

UUID-fd451ef6-3901-49ce-55b5-4aa340c063b1

Request the on-demand setting **Replace Main Header in CSV (optional)** if you need to replace the header row of your CSV export file with a header that suits your needs. **Replace Main Header in CSV (optional)** is available in one export only: *Blank Export (with ID)*.To have the **Replace Main Header in CSV (optional)** filed in any other export, contact [support@productsup.com](mailto:support@productsup.com) or your Customer Success Manager. This service is free of charge. To replace the header row in your CSV export file: Go to **Exports** from your site's main menu and select the needed export. Select the **Settings** tab. In **Replace Main Header in CSV (optional**), enter your new header row and separate the names of the attributes with a comma (`,`). The platform omits the commas in the output file.For example, enter the string *product\_ID,product\_title,price* for the CSV export file to contain the header row `product_IDproduct_titleprice`.If you enter the string *product\_ID, product\_title, price,* the platform outputs an export file with the header row `product_ID product_title price`. You can use empty and dynamic attribute names in **Replace Main Header in CSV (optional)**: 1. Empty attribute names.You can enter a space character instead of the attribute's name in between commas if you need an attribute without a name. For example, enter *product\_ID, ,price* for the CSV export file to contain the header **product\_ID price**. 2. Dynamic attribute names.If you need an attribute to contain dynamic data, such as today's date, you can enter a Twig expression instead of the attribute's name in between commas. For example, enter *product\_ID, \{\{ "now"|date("m/d/Y") }}, price* for the CSV export file to contain the header **product\_ID 06/22/2022 price**. Select **Save**. Labels, Tags & Sorting tab [#labels-tags--sorting-tab] In the export's Labels, Tags & Sorting tab, you can set up labels, tags, and sorting for your export. . Labels.If you have many different exports, labels help you categorize them. You can later use these labels as filters in Exports. To add a label: Go to **Exports** from your site's main menu and select the export you want to modify. Select the **Labels, Tags & Sorting** tab. Add one or more labels separated by a comma (`,`) in **Labels**. UUID-df1f962d-eea6-d7b7-11e5-5df788735f33

UUID-df1f962d-eea6-d7b7-11e5-5df788735f33

Select **Save**.Once you've created a label(s), the *Labels* dropdown appears in the *Exports* page, and you can search for your exports with particular labels: Go to **Exports** from your site’s main menu. If any export has a label, you can see it below the export's names. Select **Labels** and choose the desired label(s) from the dropdown. Select **Apply**. UUID-32756f2f-cd0c-b6b1-5ebd-29a4c3efb30b

UUID-32756f2f-cd0c-b6b1-5ebd-29a4c3efb30b

. Export Tags.*Export Tags* let you distinguish attribute titles for each exported item. Go to **Exports** from your site's main menu and select the export you want to modify. Select the **Labels, Tags & Sorting** tab. In the *Export Tags* section, enter **Key** and **Value**. UUID-d783bbb5-4ebf-ed2d-00bc-94ddb1543f78

UUID-d783bbb5-4ebf-ed2d-00bc-94ddb1543f78

Select **Add Tag**. You can also use **Predefined Tags** from an external system by connecting to it via the chosen authentication from the dropdown. See [Add OAuth authentication to external systems](/docs/help-center/import-data-feeds/import-your-data-into-productsup/add-oauth-authentication-to-external-systems) to set up authentication with an external system. Here are two examples of the key and value entries to get the desired outcome:Desired outcome #1: BMEcat without CDATA ( `` ) - * Key: *custom\_xml\_writer\_class* * Value: *ProductsUp\_Xml\_File\_Writer\_BMEcatWithoutCDATA* * Output result: `Here is the value from the attribute` Desired outcome #2: Show CSV output with enclosures ( `‘’ or ““ or ||` ) - * Key: *custom\_csv\_writer\_class* * Value: *ProductsUp\_Csv\_File\_Writer\_AllEnclosured* * Output result: `‘row1’;’row2’;’size’;’price’;’product_id’` . Sorting.*Sorting* lets you define the order of items in the export based on a specific attribute, mode, and direction. UUID-204cc1b3-58f1-0de4-5923-845444236ce3

UUID-204cc1b3-58f1-0de4-5923-845444236ce3

Choose an attribute in **Select Column**. Choose a sorting mode in **Select Mode**, which can be *Alphabetical*, *Numerical*, or *Natural*. Choose a sorting order in **Select Direction**, which can be either *Ascending* or *Descending*. Select **Add Sorting Rule**. Pricing tab [#pricing-tab] Add a pricing model for your export to calculate costs in the *Reporting* page. UUID-fd2ddb52-6dab-7ef3-a9cd-980366ca0eb7

UUID-fd2ddb52-6dab-7ef3-a9cd-980366ca0eb7

Build your export from scratch [#build-your-export-from-scratch] In some cases, the existing export templates may not cover your needs. Then, you can build an export from scratch using blank exports. There are four (4) types of blank exports: Blank Export (empty), Blank Export (with ID), Delta Blank Export, and Export2Datasource Blank. See [Build your exports from scratch](/docs/help-center/export-data-feeds/add-export/build-your-exports-from-scratch) for more information. To add a new blank export: Go to **Exports** from your site’s main menu and select **Add export**. Select the necessary blank export template in the gray banner under the search field. UUID-66c1a6b9-78f2-b3fb-d559-aee7bf9db90a

UUID-66c1a6b9-78f2-b3fb-d559-aee7bf9db90a

After adding a blank export template, you need to set it up. Each blank export has its setup peculiarities. See [Build your exports from scratch](/docs/help-center/export-data-feeds/add-export/build-your-exports-from-scratch) for more information. Edit an export name [#edit-an-export-name] You can modify the export's name. This is helpful when you use the same export template for different exports. For example, you can differentiate *Google Merchant Center*, *Google Merchant Center (clothes only)*, etc. UUID-96d4ab47-47ff-1038-98ae-d4442ad3282e

UUID-96d4ab47-47ff-1038-98ae-d4442ad3282e

To modify an export's name: Go to **Exports** from your site's main menu and select the cogwheel icon (**⚙**) next to the export you want to modify. Select the **Edit** icon next to the export's name. UUID-9093bb66-58bd-773f-3af4-3e2e04c67d2c

UUID-9093bb66-58bd-773f-3af4-3e2e04c67d2c

Modify the export's name and add a short description. Select the checkmark icon to save your modifications. View the export run status and reorder the export attributes [#view-the-export-run-status-and-reorder-the-export-attributes] When you are in any export setup page, you can see a specific main menu on the left from where you can go to the **Status** or **Order Attributes** pages, or return to the **Setup** page. Status page [#status-page] The Status page becomes available in the main menu when you are in any export setup page. UUID-7326c280-65e6-c2ac-f6d5-4b9829d53157

UUID-7326c280-65e6-c2ac-f6d5-4b9829d53157

The Status page lets you see the following information about all past export runs: * *Export Started* shows the data and time when the export run started. * *Export Finished* shows the data and time when the export run completed. * *Number of exported Products* shows the number of items exported during the export run. UUID-068957b2-68f6-04a5-d78a-9ac060cf1f0e

UUID-068957b2-68f6-04a5-d78a-9ac060cf1f0e

Order Attributes page [#order-attributes-page] The *Order Attributes* page becomes available in the main menu when you are in any export setup page. You can change the order of attributes in your final output feed by selecting and dragging them up and down as needed. The colors of the attributes have specific meanings: * When the attributes are in their initial order, they are green. UUID-4de4fe08-59b6-d2d8-102f-83650320ed9e

UUID-4de4fe08-59b6-d2d8-102f-83650320ed9e

* When you change the order, the attributes turn black. To reset the order to its original state, select **Reset column order to initial state**. When you change the order of the attributes, you can see the result in the export stage of Dataflow. To see it: Go to **Dataflow** and select the needed export from the dropdown on the left. Select **View** in the upper ribbon and select **Sort by**. UUID-1d4f8240-c663-1045-dc64-baa6be7ea824

UUID-1d4f8240-c663-1045-dc64-baa6be7ea824

Select **Export Order** in the dropdown. Check the export stage in the Dataflow. # Add Facebook Dynamic Ads (Delta Upload) export import { Callout } from "fumadocs-ui/components/callout"; import { Step, Steps } from "fumadocs-ui/components/steps"; Introduction [#introduction] The *Facebook Dynamic Ads (Delta Upload)* export sends changed products to [Facebook Commerce Manager](https://business.facebook.com/commerce/), one of Meta Business Manager tools, via the Facebook Marketing API. This export uses delta files, which means it sends only new, updated, and deleted products to Facebook instead of the entire catalog. The export doesn't send unchanged products to Commerce Manager, which helps reduce site-running times. With your product catalog available in Commerce Manager, you can advertise your products to wide audiences across the entire Meta ecosystem based on users' interests and previous behavior. The Meta ecosystem includes Facebook, Instagram, Messenger, and the Audience Network. See [Add Facebook Dynamic Ads export](/docs/help-center/export-data-feeds/add-export/add-facebook-dynamic-ads-export) for the difference between this export and other Facebook exports available in Productsup. Prerequisites [#prerequisites] To send your product catalog to Facebook Commerce Manager using the export *Facebook Dynamic Ads (Delta Upload)*, you need: . A Facebook business account with at least one product catalog created in it. . The ID of the catalog where you want to send your products. . A Facebook authentication in your Productsup organization.To add a Facebook authentication: Go to **Authentication** from the organization's, project's, or site's menu and select **Add Authentication**. In **Type**, select *Facebook*, give it a desired name, and select **Next**. Select **Connect** for Productsup to redirect you to a Facebook page where you can give Productsup access to your Facebook business account. Once ready, Facebook redirects you back to Productsup. Close the confirmation window to proceed. Set up the Facebook Dynamic Ads (Delta Upload) export [#set-up-the-facebook-dynamic-ads-delta-upload-export] Go to **Exports** from your site's main menu, and select **Add export**. Search for *Facebook Dynamic Ads (Delta Upload)*, hover over it, and select **Add**. UUID-c56b04a9-5f82-4d0e-4a21-8be05b0071a9

UUID-c56b04a9-5f82-4d0e-4a21-8be05b0071a9

Go to **Dataflow** from the site's main menu and choose the added export from the dropdown in the toolbar. Map all relevant attributes from import to export. See [Use Dataflow to map your attributes from import to export](/docs/help-center/map-and-optimize-your-data/dataflow/use-dataflow-to-map-your-attributes-from-import-to-export) for more information.There are only 9 mandatory attributes for Facebook: UUID-28b253cc-8611-07a8-a5a0-e5c995ef9d37

UUID-28b253cc-8611-07a8-a5a0-e5c995ef9d37

Go to **Exports** and select *Facebook Dynamic Ads (Delta Upload)*. Select **Add Destination**. Select *Facebook Marketing API: Data Feed Delta* from the **Destination** drop-down menu, and choose **Save**. UUID-638b1994-8a42-7224-7257-901b22ed5433

UUID-638b1994-8a42-7224-7257-901b22ed5433

In **Product сatalog id**, enter the ID of the product catalog in Commerce Manager where you want to send your products. If you have already created an authentication for Facebook in your current site, project, or organization, you can choose it in the **Facebook authentication** drop-down menu. If not, see [Prerequisites](#N1736181018845). Leave the **Feedback import** toggle *On* to let the platform receive feedback files from the Facebook Marketing API in case of export errors. This helps to troubleshoot the setup. Ignore the toggle **Replace instead of Patch**. It is a legacy setting that no longer affects how the destination works. Toggle **Active** to *On* to activate the destination. Select **Save**. Go to **Data View**. In the top ribbon, select *Readiness* from the **Overview** drop-down menu to see what data transformations are necessary to meet Facebook's product data requirements. See [Analyze your data in Data View](/docs/help-center/map-and-optimize-your-data/data-view/analyze-your-data-in-data-view) for more information on using the Analyzer feature. If your data is ready, select **Run** or **Export** in the top-right corner of the page. If the run finishes with issues, you can go to **Error Log** to troubleshoot. Go to your Facebook business account to check that Facebook has successfully uploaded all your product data changes to the needed catalog. In case of issues, get back to Productsup and go to **Data Sources** to access Facebook's feedback about your export in the additional data source *Feedback data from destination Facebook Marketing API: Data Feed Delta*. This additional data source is only available if you have turned on the setting **Feedback import**. # Add TikTok Product Catalog API export import { Step, Steps } from "fumadocs-ui/components/steps"; Use the TikTok Product Catalog API export template to upload products to your product catalog. The export uses delta logic, which means that it exports only updated data instead of the entire product feed data. See [TikTok for Business Developers](https://ads.tiktok.com/marketing_api/docs?id=1701890909484033) for more information about TikTok API for Business. Add and set up the export [#add-and-set-up-the-export] To add the TikTok API export in Productsup: Go to **Exports** from your site’s main menu and select **ADD EXPORT**. Search for *TikTok Product Catalog API* , hover over it, and select **Add**. UUID-a462fb59-b19c-10f9-fa57-17673b8ab5e4

UUID-a462fb59-b19c-10f9-fa57-17673b8ab5e4

On the **Exports** page, select the name of the added export template to set it up. Select **Add Destination** and choose *TikTok Business Center API* from the dropdown. Give it a name as desired, and select **Save**. UUID-1a9fd0ef-2624-9419-1ce3-0f2e227d644e

UUID-1a9fd0ef-2624-9419-1ce3-0f2e227d644e

Enter your TikTok Ads Manager organization ID in **TikTok Business Center ID**. In **Catalog ID**, enter your TikTok catalog ID. The destination searches for catalogs without an ID if this field is left empty. Enter a name to locate your catalog in **Catalog Name**. The platform attempts to find a catalog with a matching name, country, and currency. Specify your locale in **Target Country**. Select the currency of your locale in **Currency**. If a catalog doesn't exist, the platform automatically creates one when you select **Create Catalog**. In **Authentication to use**, select an existing authentication from the dropdown or create a new TikTok authentication by selecting **Add New Authentication**. * To add a new authentication, the platform then redirects you to TikTok once you select **Type** and enter the **Name** of your authentication. Then, select **Next** and **Connect** and enter your TikTok credentials to proceed. UUID-a276c6b8-9f61-088a-0554-372255d477a3

UUID-a276c6b8-9f61-088a-0554-372255d477a3

If you want an error file returned to the platform once your data export finishes, switch **Feedback import** to **On**. If not, skip this step and go to step [15](#N1630676389653). Select the attribute where you want to receive a feedback import file in **Main feed connection column**. Enter the attribute that connects to your feedback import in **Feedback file connection column**. Switch **Active** to *On* to activate the destination. Select **Save**. UUID-15eb863d-df90-b0fe-1e7e-5567aa9252ef

UUID-15eb863d-df90-b0fe-1e7e-5567aa9252ef

# Migrate your Google Content API export to Merchant API (single account) import { Callout } from "fumadocs-ui/components/callout"; import { Step, Steps } from "fumadocs-ui/components/steps"; Google is shutting down the Content API for Shopping on August 18, 2026, in favor of the new Merchant API (generally available since July 2025). If you use a Content API-based destination to export your product data to Google Merchant Center, you need to migrate to the Merchant API destination before that date to keep your exports running. This migration is mandatory, but full feature parity is maintained and your export templates require no changes. You only need to add the new destination, configure it, and disable the old one. Throughout this guide, **data source** refers to a data source (feed) as configured in Google Merchant Center — not a Productsup data source — unless explicitly labeled **Productsup data source** or **feedback data source** (both of which are Productsup entities used in the feedback-file workflow described in [Enable the feedback file](#enable-the-feedback-file)). Scope [#scope] This migration covers Content API to Merchant API destinations only. If you deliver your Google feed via SFTP or FTP, this guide does not apply to you. Moving from SFTP to API is a separate change that uses different export templates and isn't required as part of this migration. Choose your data source strategy (optional) [#choose-your-data-source-strategy-optional] We recommend keeping the same data source (feed) you already use: map **Feed Label**, **Content Language**, and **Default Currency Code** to the correct target as described in this guide. This approach requires no manual intervention in Google Merchant Center. This matches Google's "Keep existing Content API data sources" option: data sources created with the Content API for Shopping remain fully compatible with the Merchant API. See [Choose your data source strategy](https://developers.google.com/merchant/api/guides/compatibility/data-sources#choose-data-strategy) in Google's documentation for more information. Destination name mapping [#destination-name-mapping] The following table maps the old destination to its Merchant API replacement. | Old destination (Content API) | New destination (Merchant API) | | :------------------------------ | :----------------------------------- | | Google Content API for Shopping | Google Merchant API — single account | What changes in the destination settings [#what-changes-in-the-destination-settings] The destination configuration has changed. The **Target Country** and **Target Language** dropdowns are replaced by three free-text fields. Before, with the Content API destination: | Field | Example value | | :----------------------------- | :--------------------- | | **Target Country** (dropdown) | *United Arab Emirates* | | **Target Language** (dropdown) | *English* | After, with the Merchant API destination: | Field | Description | Example value | | :------------------------ | :--------------------------------------------------------------------------------------------------------------------------------------- | :------------ | | **Feed Label** | Replaces Target Country. Uppercase ISO country code. Maximum 20 characters (A–Z, 0–9, hyphen, underscore). Immutable after feed creation | `AE` | | **Content Language** | Replaces Target Language. ISO 639-1 two-letter code in lowercase. Google validates this server-side and flags mismatches | `en` | | **Default Currency Code** | New field. ISO 4217 three-letter uppercase currency code. See the field mapping table for valid values per country | `AED` | Use the ISO 3166-1 alpha-2 country code in uppercase as your **Feed Label** (for example, `AE`, `ES`, `GB`) to keep it consistent with how Merchant Center identifies data sources and to ensure you continue pushing to the same primary data source. This value is immutable once the data source is created, so confirm it before saving. Example: United Arab Emirates / English [#example-united-arab-emirates--english] | Old setting | Old value | New field | New value | | :-------------- | :--------------------- | :-------------------- | :-------- | | Target Country | *United Arab Emirates* | Feed Label | `AE` | | Target Language | *English* | Content Language | `en` | | — | — | Default Currency Code | `AED` | Full field mapping reference [#full-field-mapping-reference] Use this table to find the correct values when you configure the new destination. **Feed Label** uses the uppercase ISO country code, **Content Language** uses the lowercase ISO 639-1 code, and **Default Currency Code** uses the uppercase ISO 4217 code. | Old: Target Country | Feed Label | Content Language(s) | Default Currency Code | | :------------------- | :--------- | :------------------ | :-------------------- | | Argentina | `AR` | `es` | `ARS` | | Australia | `AU` | `en` | `AUD` | | Austria | `AT` | `de` | `EUR` | | Bahrain | `BH` | `ar` | `BHD` | | Belarus | `BY` | `ru` | `BYN` | | Belgium | `BE` | `fr` / `nl` / `de` | `EUR` | | Brazil | `BR` | `pt` | `BRL` | | Canada | `CA` | `en` / `fr` | `CAD` | | Chile | `CL` | `es` | `CLP` | | Colombia | `CO` | `es` | `COP` | | Czechia | `CZ` | `cs` | `CZK` | | Denmark | `DK` | `da` | `DKK` | | Ecuador | `EC` | `es` | `USD` | | Egypt | `EG` | `ar` | `EGP` | | Ethiopia | `ET` | `en` | `ETB` | | Finland | `FI` | `fi` / `sv` | `EUR` | | France | `FR` | `fr` | `EUR` | | Georgia | `GE` | `ka` | `GEL` | | Germany | `DE` | `de` | `EUR` | | Ghana | `GH` | `en` | `GHS` | | Greece | `GR` | `el` | `EUR` | | Hong Kong | `HK` | `zh` / `en` | `HKD` | | Hungary | `HU` | `hu` | `HUF` | | India | `IN` | `en` / `hi` | `INR` | | Indonesia | `ID` | `id` | `IDR` | | Ireland | `IE` | `en` / `ga` | `EUR` | | Israel | `IL` | `he` | `ILS` | | Italy | `IT` | `it` | `EUR` | | Japan | `JP` | `ja` | `JPY` | | Jordan | `JO` | `ar` | `JOD` | | Kazakhstan | `KZ` | `ru` | `KZT` | | Kenya | `KE` | `en` | `KES` | | Kuwait | `KW` | `ar` | `KWD` | | Lebanon | `LB` | `ar` | `LBP` | | Malaysia | `MY` | `ms` / `en` | `MYR` | | Mauritius | `MU` | `en` / `fr` | `MUR` | | Mexico | `MX` | `es` | `MXN` | | Netherlands | `NL` | `nl` | `EUR` | | New Zealand | `NZ` | `en` | `NZD` | | Nigeria | `NG` | `en` | `NGN` | | Norway | `NO` | `no` | `NOK` | | Oman | `OM` | `ar` | `OMR` | | Paraguay | `PY` | `es` | `PYG` | | Peru | `PE` | `es` | `PEN` | | Philippines | `PH` | `en` / `tl` | `PHP` | | Poland | `PL` | `pl` | `PLN` | | Portugal | `PT` | `pt` | `EUR` | | Romania | `RO` | `ro` | `RON` | | Russia | `RU` | `ru` | `RUB` | | Saudi Arabia | `SA` | `ar` | `SAR` | | Singapore | `SG` | `en` / `zh` | `SGD` | | Slovakia | `SK` | `sk` | `EUR` | | South Africa | `ZA` | `en` | `ZAR` | | South Korea | `KR` | `ko` | `KRW` | | Spain | `ES` | `es` | `EUR` | | Sweden | `SE` | `sv` | `SEK` | | Switzerland | `CH` | `de` / `fr` / `it` | `CHF` | | Taiwan | `TW` | `zh` | `TWD` | | Tanzania | `TZ` | `sw` / `en` | `TZS` | | Thailand | `TH` | `th` | `THB` | | Turkey | `TR` | `tr` | `TRY` | | Uganda | `UG` | `en` | `UGX` | | Ukraine | `UA` | `uk` | `UAH` | | United Arab Emirates | `AE` | `ar` / `en` | `AED` | | United Kingdom | `GB` | `en` | `GBP` | | United States | `US` | `en` / `es` | `USD` | | Uruguay | `UY` | `es` | `UYU` | | Uzbekistan | `UZ` | `uz` | `UZS` | | Vietnam | `VN` | `vi` | `VND` | | Zambia | `ZM` | `en` | `ZMW` | | Zimbabwe | `ZW` | `en` | `USD` | Migrate to the Merchant API destination [#migrate-to-the-merchant-api-destination] Take a few screenshots of your current product output before you start. The new destination has been validated internally, but a before-and-after reference lets you confirm it produces identical results, and gives you something to compare against if anything looks unexpected. Go to **Destinations** and add *Google Merchant API — single account*. Configure the destination: enter **Feed Label**, **Content Language**, and **Default Currency Code** using the field mapping table, and complete all other required credentials. Switch **Active** to **On** and select **Save**. Disable the previous destination *Google Content API for Shopping* and select **Save**. Run the site to push your data through the new destination and confirm the output looks correct. No further action is needed. Export templates require no changes. Important settings to check before and during the switch [#important-settings-to-check-before-and-during-the-switch] Enable the feedback file [#enable-the-feedback-file] Switch on the feedback file to keep visibility into actionable insights if products get rejected due to data quality issues. If something goes wrong, the feedback file is available as an additional downloadable Productsup data source, showing what's failing and why. Some clients don't use the feedback file, so sites can fail silently. This isn't caused by the migration — it's caused by unrelated data quality issues that only the feedback file would surface. If you enable the feedback file and start seeing more errors than before, two separate things are usually happening: . **Real product-level errors from Google become visible.** Many accounts never had the feedback file enabled under the Content API, so Google's product-level rejections went unnoticed. In most cases, these errors are pre-existing catalogue or data-quality issues that existed before the migration. . **Unmapped-items notifications appear as separate UI noise.** The feedback file arrives as an additional feedback data source in Productsup and isn't automatically mapped to your main Productsup data source. This can trigger extra notifications that look like errors but aren't actual export problems. To reduce this noise, map ID to ID from the feedback data source to your main Productsup data source, or snooze the notification on the feedback data source. Use Force Full Upload and Cleanup with care [#use-force-full-upload-and-cleanup-with-care] Only switch on **Force Full Upload** or **Cleanup** when there's a clear, identified need — for example, when Productsup and Google Merchant Center are de-synced and products still exist in GMC that Productsup has no record of, and only when Productsup is the single source of truth for that data source (feed). Leaving these options on unnecessarily increases the risk of hitting your daily quota limits. Disable them again as soon as the sync is back to normal. Set the Full Upload Interval correctly [#set-the-full-upload-interval-correctly] Google removes products from Merchant Center if they haven't been refreshed within 28 days. **Full Upload Interval** controls how often Productsup sends your entire catalogue to Google as a full upload, rather than only new or changed products. This refreshes every product's timestamp, including unchanged ones, and prevents Google from dropping them after 28 days. Do not set **Full Upload Interval** to `0`, especially on a schedule that runs daily. A value of `0` forces a full upload on every run, which removes the delta export benefit and significantly increases the risk of hitting your daily quota. The more often you export, the larger this value should be, closer to 28. The less often you export, the smaller it should be, for example `7`–`14`, so unchanged products still get refreshed before Google's 28-day cutoff. Do not use Dry Run for this migration [#do-not-use-dry-run-for-this-migration] **Dry Run** is intended for new clients who are still testing their data setup before going live. If your site is already running in production, using Dry Run interferes with your normal delta and export flow. Add and activate the new destination as described in [Migrate to the Merchant API destination](#migrate-to-the-merchant-api-destination) instead. After the switch [#after-the-switch] Once you've switched, the data source may still be labeled *Content API* inside Google Merchant Center. This is expected and won't affect your exports. The label in Merchant Center hasn't been renamed yet, but the underlying integration is already Merchant API and continues to work after August 18, 2026. To confirm the switch was successful, check that: * Products in the data source (feed) have an update timestamp after the switch. * There has been a successful run since the switch. * The feedback file shows no issues. Fallback procedure [#fallback-procedure] If something goes wrong after switching, restore your previous setup: Disable the new *Google Merchant API — single account* destination. Re-enable the old *Google Content API for Shopping* destination. Restart the delta on the site and run it again to restore normal data flow. Contact your Customer Success Manager or [support@productsup.com](mailto:support@productsup.com) immediately to report the issue. Act quickly. The faster you switch back, the shorter the gap in data delivery. FAQ [#faq] Do I need to update my export templates? [#do-i-need-to-update-my-export-templates] No. Export templates for *Google Content API for Shopping* remain unchanged. Only the destination changes. What actually changes in the destination configuration? [#what-actually-changes-in-the-destination-configuration] The **Target Country** and **Target Language** dropdowns are replaced by three free-text fields: **Feed Label** (for example, `AE`), **Content Language** (for example, `en`), and **Default Currency Code** (for example, `AED`). See [What changes in the destination settings](#what-changes-in-the-destination-settings) for the full breakdown and the field mapping table for all 71 countries. Will my data source in Merchant Center change? [#will-my-data-source-in-merchant-center-change] No. If you follow this guide and use the recommended Feed Label, an uppercase ISO country code, Productsup pushes to the same primary data source (feed) as before. No manual action is needed in Merchant Center. See [Choose your data source strategy](#choose-your-data-source-strategy-optional). After the switch, my data source in Merchant Center is still labeled Content API. Did the migration fail? [#after-the-switch-my-data-source-in-merchant-center-is-still-labeled-content-api-did-the-migration-fail] No, this is expected. Even though the data source may still show as *Content API* in the Merchant Center UI, you're already exporting via the new Merchant API destination under the hood, and it continues working past August 18, 2026, as long as you've switched to *Google Merchant API — single account* in Productsup. See [After the switch](#after-the-switch). Why are we still using Google Content API export templates? [#why-are-we-still-using-google-content-api-export-templates] This is intentional. The Merchant API destination was built to work with your existing Content API export templates, so you don't need to change them now or in the future. Do I still need to choose between the single-account and multi-threading destinations? [#do-i-still-need-to-choose-between-the-single-account-and-multi-threading-destinations] No. The new *Google Merchant API — single account* destination handles this automatically. It's a unified solution that replaces both the *Google Content API (single account)* and *Google Content API (single account + multi-thread)* destinations, so you no longer need to choose between them. What happens if I don't migrate by August 18, 2026? [#what-happens-if-i-dont-migrate-by-august-18-2026] The Content API stops accepting requests and your exports fail until you switch to a Merchant API destination. What if I only use one feed? [#what-if-i-only-use-one-feed] No additional action is needed. Data is pushed to your main catalogue automatically. What is the correct Feed Label value? [#what-is-the-correct-feed-label-value] Use the ISO 3166-1 alpha-2 country code in uppercase, for example `GB`, `ES`, `AE`. It must match the feed label configured in Merchant Center. This value cannot be changed after the data source (feed) is created. How do I confirm the switch was successful? [#how-do-i-confirm-the-switch-was-successful] Check that products in the data source (feed) have an update timestamp after the switch, that there's been a successful run since, and that the feedback file shows no issues, or only pre-existing issues unrelated to the migration. See [After the switch](#after-the-switch). What if something goes wrong after switching? [#what-if-something-goes-wrong-after-switching] Follow the [Fallback procedure](#fallback-procedure): disable the new Merchant API destination, re-enable the old Content API destination, restart the delta, run again, and contact us immediately. Act quickly, since the faster the fallback, the shorter the gap in data delivery. Should I turn on Force Full Upload or Cleanup during the switch? [#should-i-turn-on-force-full-upload-or-cleanup-during-the-switch] Only if there's a clear, identified need, for example if Productsup and Google Merchant Center are de-synced and Productsup is the single source of truth for that data source (feed). Otherwise, leave them off. See [Use Force Full Upload and Cleanup with care](#use-force-full-upload-and-cleanup-with-care). What should Full Upload Interval be set to, and why does it matter? [#what-should-full-upload-interval-be-set-to-and-why-does-it-matter] Never `0`. Google removes products that haven't been refreshed in 28 days, and Full Upload Interval refreshes unchanged products so they aren't dropped. As a rule of thumb, the more frequently your site runs, the higher this number should be, closer to 28. The less frequently it runs, the lower it should be, for example `7`–`14`. See [Set the Full Upload Interval correctly](#set-the-full-upload-interval-correctly). I'm seeing frequent internal_error responses in the feedback file. What's going on? [#im-seeing-frequent-internal_error-responses-in-the-feedback-file-whats-going-on] The Merchant API is still going through some instability on Google's side. `internal_error` and similar transient failures are typically temporary issues on Google's side rather than something caused by your setup or by Productsup. See Google's [Merchant API known issues](https://developers.google.com/merchant/api/known-issues) for current known issues. # Add TikTok Shop exports import { Callout } from "fumadocs-ui/components/callout"; import { Step, Steps } from "fumadocs-ui/components/steps"; TikTok Shop provides a new, native checkout experience for TikTok users and lets them shop, order, and pay without leaving the TikTok app. This leads to a smoother shopping experience, higher conversion rates, and more transparent ad performance, which yields a higher return on ad spend. TikTok Shop is currently available in the United States, the United Kingdom, Spain, France, Germany, and Italy. Currently, Productsup can support you in selling your products on TikTok Shop only in the UK, Germany, and the US. To let you sell your products on TikTok Shop, Productsup has built an ecosystem that sends product and order data to TikTok Shop and imports order data from TikTok Shop into Productsup: . \*TikTok Shop - Product Catalog API (US)\*This export creates, updates, and deletes products on TikTok Shop via API for the US market and contains the attributes relevant to products of all product categories. When setting up this export, you also use multiple category-specific attributes that let you send products of relevant product categories to TikTok Shop. This export sends only delta updates to TikTok Shop instead of exporting the entire product catalog during every site run. . \*TikTok Shop - Product Catalog API (UK)\*This export creates, updates, and deletes products on TikTok Shop via API for the UK market and contains the attributes relevant to products of all categories. When setting up this export, you also use multiple category-specific attributes that let you send products of relevant product categories to TikTok Shop. This export sends only delta updates to TikTok Shop instead of exporting the entire product catalog during every site run. . TikTok Shop - Product Catalog API (DE)This export creates, updates, and deletes products on TikTok Shop via API for the German market. When setting up this export, you also use multiple category-specific attributes that let you send products of relevant product categories to TikTok Shop. Currently, it supports only a limited number of categories under *Health & Beauty*. Contact your Customer Success Manager or [support@productsup.com](mailto:support@productsup.com) to request the necessary categories. This export sends only delta updates to TikTok Shop instead of exporting the entire product catalog during every site run. . *TikTok Shop - Shipment Notifications API*This export sends shipping updates to TikTok Shop via API to let you send tracking information to TikTok and inform customers on TikTok that you shipped their orders. This export sends only new shipment data to TikTok Shop instead of sending the entire product catalog during every site run. . *TikTok Shop Order Import*This API-based data source imports orders from TikTok Shop into Productsup to let you send the order data to your order management system. Prerequisites [#prerequisites] To set up the TikTok Shop ecosystem in Productsup, you need: . Product variants in your product data.Your data should support product variants, which means multiple rows in your data source can represent one main product that varies in size, color, model, etc.All products in your data feed must have **product\_id** and **parent\_id**. The **product\_id** attribute uniquely identifies product variants, and the **parent\_id** attribute links all product variants to their main product.If a product doesn't have variants, it still must have the **parent\_id** attribute. It can just have the same value as the **product\_id** attribute.See [Mind product variants and their attributes](#section-idm243374369527850) for more information. If your data doesn't support product variants and doesn't have the needed main product and variant IDs, you need to optimize your data in Productsup to ensure that it meets the TikTok Shop requirements. . A project in your Productsup organization where you are going to create three (3) sites, pushing and pulling data from TikTok Shop. In this separate project, you need to create a separate site for each TikTok Shop export and data source. This is a recommended option. If a separate TikTok Shop project doesn't fit your overall organization structure, you can ignore this advice. . A TikTok seller account and a shop set up on TikTok Shop. See [Set Up TikTok Shop Using TikTok Seller Center](https://ads.tiktok.com/help/article/set-up-tiktok-shop-using-tiktok-seller-center?lang=en) for more information. . A list of all TikTok categories you want to sell products in. This integration has [category-specific attributes exports](/docs/help-center/glossary#N68b809d75a5fd). Productsup supports only some categories by default. But we can add missing categories upon request. It may take around two weeks to add support for your request. To request the necessary categories or countries for this integration, contact your Customer Success Manager or [support@productsup.com](mailto:support@productsup.com) and provide the following information: * List of categories. See [Product Categorisation](https://seller-sg.tiktok.com/university/essay?knowledge_id=7643185937581825\&from_article=1\&identity=1) for more information on choosing the right TikTok Shop product categories. * List of countries. Now, we only support the UK, Germany, and the US. . An approval from TikTok to sell products of specific categories and brands. Some brands and categories on TikTok Shop are invite-only, so you need to reach out to TikTok to get their approval to work with the categories and brands that aren't publicly available. . A TikTok Shop authentication created on the project or organization level to use across all TikTok Shop sites. See [Add OAuth authentication to external systems](/docs/help-center/import-data-feeds/import-your-data-into-productsup/add-oauth-authentication-to-external-systems) for more information.Add this authentication as follows: 1. Go to **Authentication** from your organization's or project's menu and select **ADD AUTHENTICATION**. 2. In **Type**, select the needed authentication type based on your country of interest, give it a custom name as desired, and select **Next**: * Select *TikTok Shop US Authentication* if you want to sell products on the US market. * Select *TikTok Shop Non-US Authentication* if you want to sell products on the UK or German markets. 3. Select **Connect** for Productsup to redirect you to a TikTok account page where you can give Productsup access to your account. Follow the instructions on TikTok to connect the systems. | UUID-9f9a9b4a-b6a1-f315-d5a1-e9230bb53304

UUID-9f9a9b4a-b6a1-f315-d5a1-e9230bb53304

UUID-11d0fbf5-028b-744b-1fef-f91d28ba583a

| | --------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------- | 4. Once ready, TikTok redirects you back to Productsup to finish the authentication process. Close the confirmation window in Productsup to proceed. Send products to TikTok Shop [#send-products-to-tiktok-shop] To send your products to TikTok Shop in the US, Germany, or the UK, you first need to add and set up the export *TikTok Shop - Product Catalog API (US)*, *TikTok Shop - Product Catalog API (DE)*, or *TikTok Shop - Product Catalog API (UK)* and create a *Partner Taxonomy Mapping* list for your category attribute. Your next steps depend on what attributes you want to send to TikTok Shop. If you plan to send any of the following attribute types, you need to take additional steps to set them up: * The brand attribute * Attributes that require predefined values * Multi-value attributes * Product variant attributes See the following sections for information on setting up the export itself and working with each attribute type listed above. To see what data in your feed doesn't meet the export channel requirements, you can use the Analyzer feature. See \[component:65264] for more information on identifying the data that needs optimization. See [TikTok Shop Partner Center API Documents](https://partner.tiktokshop.com/doc/page/262784?external_id=262784) for reference on TikTok Shop's requirements for each attribute. Add and set up your TikTok Shop export [#add-and-set-up-your-tiktok-shop-export] In the site dedicated to the TikTok Shop export, add and set up the needed export as follows: Go to **Exports** from your site's main menu and select **ADD EXPORT**. Search for the needed export based on your country of interest, hover over it, and select **Add**: * Search for and add *TikTok Shop - Product Catalog API (US)* if you want to sell products on the US market. UUID-5f534def-dd5e-2b5f-8d74-b92fb1401bee

UUID-5f534def-dd5e-2b5f-8d74-b92fb1401bee

* Search for and add *TikTok Shop - Product Catalog API (UK)* if you want to sell products on the UK market. UUID-39fba53d-f4fe-ae77-65ae-ab120f44e168

* Search for and add *TikTok Shop - Product Catalog API (DE)* if you want to sell products on the German market. UUID-29ac6e3c-bee0-41c2-ecaf-520441ba72f3

On the Exports page, select the name of the added export. Select **Add Destination**, choose *TikTok Shop Export Products* from the dropdown, give it a name as desired, and then select **Save**. UUID-1113ce73-1500-6c2d-6213-8b7489bd8a7b

UUID-1113ce73-1500-6c2d-6213-8b7489bd8a7b

In **Authentication**, select the TikTok Shop authentication you have added to your Productsup organization or project. To let the platform create a file and log all calls to the TikTok Shop API, toggle the **Log API calls** button to *On*. You can also toggle **Log headers of API calls** to *On* to let the logs feature request and response headers. You can use these settings to troubleshoot your export setup on demand, but you shouldn't use them permanently because they slow down the export process. Toggle the **Enable Feedback File** button to *Off* if you don't want the platform to receive feedback files from TikTok.This feature is active by default to let Productsup receive a feedback file from the TikTok Shop API in case of export errors. This helps to troubleshoot the setup. Toggle the **Active** button to *On* to activate the destination. Select **Save**. Go to **Lists** from your site's main menu and select **ADD LIST**. Choose **Partner Taxonomy Mapping** and select **Continue**. Give the list a desired name, select the needed taxonomy in **Taxonomy**, and choose **Import** in **Stage**: * Search for and add the taxonomy *Tiktok US categories with ids* if you want to sell products on the US market. UUID-8201a930-6b62-3907-271e-64f523c96f5e

UUID-8201a930-6b62-3907-271e-64f523c96f5e

* Search for and add the taxonomy *Tiktok UK categories with ids* if you want to sell products on the UK market. * Search for and add the taxonomy *Tiktok DE categories with ids* if you want to sell products on the German market. Select the **Attribute** field to choose the attribute in your import stage that contains your products' category data. Then, select **Add** at the bottom of the page to add the list. Go through all the values of your category attribute in the column on the left and select the corresponding TikTok Shop categories in the **Replace term** column. UUID-c2f3e530-53c5-c709-5844-a3ee7a04273b

You must create and set up a new Partner Taxonomy Mapping list every time you modify the chosen category attribute in your data source and import its new values into your site. Otherwise, the already existing list can't upload your new values, and you can't map them to the corresponding TikTok Shop categories. Once you create a new Classification Mapping list, you need to choose it in the related rule box. Go to **Dataflow** and select the added export from the dropdown on the left. Map all the needed attributes from import to export. The attributes you see in the export stage are relevant for products of all your TikTok categories. Map your import-stage category attribute to both **category\_id** and **category\_path** in the intermediate stage to add the needed rule boxes and apply the Partner Taxonomy Mapping list. Select **category\_id** in the intermediate stage and open the **Select an Option** dropdown on the right to find and add the rule boxes: 1. Search for and select **Taxonomy Mapping**. Choose your category list in **List**. 2. Search for and select **Split String**. Enter `|` in **Splitter**, `0` in **From**, and `1` in **Items**. Select **Save**.This way, the **category\_id** attribute contains only the ID of the needed category. Select **category\_path** in the intermediate stage and open the **Select an Option** dropdown on the right to find and add the rule boxes: 1. Search for and select **Taxonomy Mapping**. Choose your category list in **List**. 2. Search for and select **Split String**. Enter `|` in **Splitter**, `1` in **From**, and `1` in **Items**. Select **Save**.This way, the **category\_path** attribute contains only the path of the needed category. To let the site display your category-specific attributes in Dataflow, select **Run** in the top-right corner of your view. This run will fail because you haven't yet mapped all the mandatory attributes, so no data export occurs at this stage. The aim of the run is to import the needed categories and attributes in Dataflow. Once the site run finishes, the **Classifications** dropdown appears in the top ribbon in Dataflow. Select each category in this dropdown to let Dataflow display the relevant category-specific attributes in the export stage. Map all the needed attributes from import to export. UUID-851628c1-299a-3792-c36e-44bb28a60f66

If you can't see the **Classifications** dropdown when the site run finishes, try refreshing your page. Set up the brand attribute [#set-up-the-brand-attribute] When receiving brand information about a product, TikTok Shop requires the ID of that brand. To satisfy this requirement, you need to create a Partner Taxonomy Mapping list in your site and map your current brand attribute with the brand IDs expected by TikTok: Go to **Lists** from your site's main menu and select **ADD LIST**. Choose **Partner Taxonomy Mapping** and select **Continue**. Give the list a desired name, select **Tiktok brands with ids** in **Taxonomy**, and choose **Import** in **Stage**. UUID-c954ca55-f751-a3c1-251f-6a1cc454ccdf

UUID-c954ca55-f751-a3c1-251f-6a1cc454ccdf

Select the **Attribute** field to choose the attribute in your import stage that contains your products' brand data. Then, select **Add** at the bottom of the page to add the list. Go through all the values of your brand attribute in the column on the left and select the corresponding TikTok-recognized brands and brand IDs in the **Replace term** column. UUID-b225c038-7b2c-d310-40f6-165b88861fee

UUID-b225c038-7b2c-d310-40f6-165b88861fee

You must create and set up a new Partner Taxonomy Mapping list every time you modify the chosen brand attribute in your data source and import its new values into your site. Otherwise, the already existing list can't upload your new values, and you can't map them to the corresponding brands and brand IDs recognized by TikTok Shop. Go to **Dataflow** and select **TikTok Shop Product Export API Main** from the dropdown on the left. To apply the brand-mapping list to your attributes and extract the needed data from it, select **brand\_id** in the export stage and open the **Select an Option** dropdown on the right to find and add the rule boxes: 1. Search for and select **Taxonomy Mapping**. Choose your brand-mapping list in **List**. 2. Search for and select **Split String**. Enter `|` in **Splitter**, `0` in **From**, and `1` in **Items**. Select **Save**.This way, the **brand\_id** attribute contains only the IDs of the needed brands, as required by TikTok Shop. Set up attributes that require predefined values [#set-up-attributes-that-require-predefined-values] For some attributes, TikTok Shop accepts predefined values only and requires receiving the IDs of those values together with the values themselves. For example, TikTok Shop accepts only the values *Foldable* and *Non-Foldable* for the attribute `product_attribute. Foldable Furniture#100887` and also expects to receive those values' IDs *1002263* and *1002263* in this attribute. You thus need to send the values as follows: `Foldable:::::1002263` and `Non-Foldable:::::1004668`. To check which attributes in your feed require predefined values with value IDs: Go to **Dataflow** and select your export from the dropdown on the left. For category-specific values, open the **Classification** dropdown and select the needed category. In the **Overview** dropdown, select **Readiness**. The platform highlights problematic attributes in orange or red. Select the readiness percentage under the name of each problematic attribute. If the attribute supports only predefined values, you will see a similar pie chart in the *Analyzer tests* section and a list of the supported values for this attribute. UUID-19b7bf14-9b37-5ec5-244d-456e599985a6

UUID-19b7bf14-9b37-5ec5-244d-456e599985a6

See \[component:65264] for more information on the Analyzer and export readiness scores. To provide the right values and the relevant value IDs in the attributes that support only predefined values, do the following for each of these attributes: Go to **Lists** from your site's main menu and select **ADD LIST**. Choose **Partner Taxonomy Mapping** and select **Continue**. Give the list a desired name, select **Tiktok non-customized with ids** in **Taxonomy**, and choose **Import** in **Stage**. UUID-a5357328-3087-2b9a-3698-7c9b7ab3c484

UUID-a5357328-3087-2b9a-3698-7c9b7ab3c484

Select the **Attribute** field to choose the attribute in your import stage that should contain predefined values. Then, select **Add** at the bottom of the page to add the list. Go through all the values of your chosen attribute in the column on the left and select the corresponding values supported by TikTok Shop in the **Replace term** column. UUID-354b1c5b-d6fe-f346-18a2-05ebfdaf6429

UUID-354b1c5b-d6fe-f346-18a2-05ebfdaf6429

You must create and set up a new Partner Taxonomy Mapping list every time you modify the chosen attribute in your data source and import its new values into your site. Otherwise, the already existing list can't upload your new values, and you can't map them to the corresponding predefined TikTok Shop values with IDs. Go to **Dataflow** and select your export from the dropdown on the left. To apply the list to the chosen attribute and extract the needed data from it, select the relevant attribute in the export stage and open the **Select an Option** dropdown on the right to find and add the rule boxes: 1. Search for and select **Taxonomy Mapping**. Choose your list in **List**. 2. Search for and select **Split String**. Enter `|` in **Splitter**, `1` in **From**, and `1` in **Items**. Select **Save**. Set up multi-value attributes [#set-up-multi-value-attributes] TikTok Shop allows some attributes to contain multiple values. Here are some of these attributes: * Images * Material * Delivery service IDs To see if an attribute can send multiple values to TikTok Shop, you can use the Analyzer feature. If an attribute doesn't have analyzer tests at the export stage in the Analyzer, the attribute is likely to support multiple values. See \[component:65264] for more information on the Analyzer feature. You can also see which attributes support multiple values in your TikTok account. Most multi-value attributes are category-specific. For all the attributes that should send multiple values to your TikTok Shop account, do the following: Go to **Dataflow** and select your export from the dropdown on the left. Map an attribute from the import stage to the corresponding multi-value attribute in the intermediate stage. Select the attribute in the intermediate stage and open the **Select an Option** dropdown on the right to find and add the rule boxes. Search for and select **Append/Prepend Column**. UUID-1aae6a86-4060-591c-49c7-93eb2d03019b

UUID-1aae6a86-4060-591c-49c7-93eb2d03019b

In **Column**, choose another attribute that should add its value to the multi-value attribute. Then, select **append** in **Mode**. In the **text** field, enter `#` to separate the value of the added attribute from the current value. Open the **Select an Option** dropdown to search for and select **Text Replace**. UUID-61646542-d63a-082c-8572-c3943200a815

UUID-61646542-d63a-082c-8572-c3943200a815

Enter `#` in **Search for** and `#` in **Replace by**. With the suggested settings, the Append/Prepend Column rule box adds the value of your chosen attribute to the current value in your edited multi-value attribute by using the number sign (`#`) and a space before it as a delimiter.Don't forget to enter the space before `#` in **Search for** to let the Text Replace rule box remove the space. Select **Save**. If you want to add more than one (1) attribute to a multi-value attribute in the intermediate stage, you need to add as many Append/Prepend Column rule boxes as necessary to append all the desired values.Mind that the order of the rule boxes matters. The higher a rule box is in the list of added rule boxes, the earlier a site processes and applies it to the data. So the order of the Append/Prepend Column rule boxes from top to bottom should be the same as your desired order of values in the attribute.You should add the Text Replace rule box only once, and it should be at the bottom of the rule box list. Mind product variants and their attributes [#mind-product-variants-and-their-attributes] The TikTok Shop product data scheme uses main products and product variants. All products in your feed must have **product\_id** and **parent\_id**. The **product\_id** attribute uniquely identifies product variants, and the **parent\_id** attribute links all product variants to their main product. The platform considers the first product variant with a new **parent\_id** as both a product variant and the main product. All product variants have the same values as their main products in such attributes as **parent\_id**, **product\_name**, **images**, **category\_id**, **description**, etc. However, some attributes can contain values individual to each product variant. The names of these varying attributes start with **sku.**, except for **product\_id**. When modifying the data in your feed, you shouldn't let product variants with the same **parent\_id** have different values in the shared attributes. But the values in **product\_id** and the **sku.** attributes can differ per product variant. Import orders from TikTok Shop [#import-orders-from-tiktok-shop] To let Productsup import your orders from TikTok Shop, do the following in the site dedicated to the TikTok Shop data source: TikTok users can cancel orders within one (1) hour after placing an order. You can import orders created within the last hour, but you shouldn't ship them right away. Go to **Data Sources** from your site's main menu and select **ADD DATA SOURCE**. Search for *TikTok Shop Order Import*, select **Add**, give it a name as desired, and then choose **Continue**. UUID-bde35242-8441-95aa-37eb-4608785bce50

UUID-bde35242-8441-95aa-37eb-4608785bce50

In the **Order Status Filter** area, select the statuses that orders should have for Productsup to import them. If you don't select any order statuses, the platform imports orders of all statuses. Hold the *Ctrl* or *Cmd* key to select multiple order statuses. *Shift* helps to select a range of statuses. See [Fulfillment Process Integration Design](https://partner.tiktokshop.com/doc/page/273742) for more information on the TikTok Shop order status flow. If you want to import orders created within a specific timeframe only, enter the needed number of days in **Earliest Order Creation Time** or **Earliest Order Update Time**. The expected input format is a digit in both fields.For example, if you enter `7` in **Earliest Order Creation Time**, the platform imports only the orders created within the last seven (7) days. To import orders updated within the past three (3) days, enter `3` in **Earliest Order Update Time**. In **Authentication selection**, select the TikTok Shop authentication you have added to your Productsup organization or project. Specify the desired name of the data source in **Description (optional)**. Select **Save**. Go to **Exports** from your site's main menu and select **ADD EXPORT**. Find your order management system, add it as an export, set it up, and map the needed attributes in Dataflow. Choose **Run** in the top-right corner of the page to let the site import your order data and send it to your order management system. Send shipment updates to TikTok Shop [#send-shipment-updates-to-tiktok-shop] There are two (2) types of shipping methods available on TikTok Shop: . Self-shipping, which you manage yourself. . Shipping managed by TikTok. * Currently, Productsup supports only self-shipping and doesn't allow splitting and batching packages. * TikTok users can cancel orders within one (1) hour after placing an order. You shouldn't ship orders created within the last hour because there is a cancellation risk. To send shipment updates to TikTok Shop and notify your customers of the shipment process, do the following in the site dedicated to the TikTok Shop shipment export: Go to **Exports** from your site's main menu and select **ADD EXPORT**. Search for *TikTok Shop - Shipment Notifications API*, hover over it, and select **Add**. UUID-a58cfc18-f49f-21bc-9621-26aa2b65bf13

UUID-a58cfc18-f49f-21bc-9621-26aa2b65bf13

On the Exports page, select the name of the added export to set it up. Select **Add Destination**, choose *TikTok Shop Shipment Notification Export* from the dropdown, give it a name as desired, and then select **Save**. UUID-e6de1113-e44e-1379-192e-523487b8759b

UUID-e6de1113-e44e-1379-192e-523487b8759b

In **Authentication selection**, select the TikTok Shop authentication you have added to your Productsup organization or project. Toggle the **Feedback Import** button to *Off* if you don't want the platform to receive feedback files from TikTok.This feature is active by default to let Productsup receive a feedback file from the TikTok Shop API in case of export errors. This helps to troubleshoot the setup. Toggle the **Active** button to *On* to activate the destination. Select **Save**. Go to **Dataflow** and select your TikTok Shop - Shipment Notifications API export from the dropdown on the left. Map all the needed attributes from import to export. Once all the settings are ready, you can send your shipment updates to TikTok Shop. Select **Run** in the top-right corner of your view to send the data. # Add CrossEngage (JSON) export import { Step, Steps } from "fumadocs-ui/components/steps"; Introduction [#introduction] The CrossEngage (JSON) export lets you send product data to your CrossEngage instance directly from the platform. Using the Crossengage (JSON) export, you must access a plug-in in the platform to convert your data as a JSON file. Add and set up export [#add-and-set-up-export] To add and set up the *Crossengage (JSON)* export in Productsup: Go to **Exports** from your site’s main menu. Select **ADD EXPORT** and search for *Crossengage (JSON)*. Select **Add** and confirm adding it again as an export. UUID-f21567af-a518-19b5-f1cd-2efc537a07ee

UUID-f21567af-a518-19b5-f1cd-2efc537a07ee

Now, select **Add Destination** and choose your desired destination from the drop-down list. (Optional) In **Name**, you can customize the destination name. Select **Save**. UUID-7727dbb6-313e-c2e1-8625-1246b3db18c0

UUID-7727dbb6-313e-c2e1-8625-1246b3db18c0

Enter the credentials or settings for your destination, as necessary. Before converting your feed file to JSON, rename it to *xxx.json*. For example, `myexamplecrossengfile.json`. Go to the **Settings** tab in the Crossengage (JSON) export channel and confirm that `,COMMA` appears in **CSV Separator**. To confirm that the export plug-in functions correctly, switch the **CSV Enclosure** button to **On**. In **Export-Plugin**, enter the following path for the plug-in: `\Export\JsonCrossengage`. UUID-51e12ae5-e4bb-a017-0714-fa2807a3f059

UUID-51e12ae5-e4bb-a017-0714-fa2807a3f059

Select **Save**. # Add TikTok Product Catalog export import { Step, Steps } from "fumadocs-ui/components/steps"; The TikTok Dynamic Product Ads feature automatically retargets users with relevant product ads based on their activities inside advertiser apps and websites. Use the TikTok Product Catalog to push your product catalog with enhanced product information for your Dynamic Product Ads. This export creates a CSV catalog feed file for uploading your products to the catalog. To export product data using delta logic, use the *TikTok Product Catalog API* export instead. See [Add TikTok Product Catalog API export](/docs/help-center/export-data-feeds/add-export/add-tiktok-product-catalog-api-export). See [TikTok for Business Developers](https://ads.tiktok.com/marketing_api/docs?id=1701890909484033) for more information on connecting to your TikTok for Business. Add and set up the export [#add-and-set-up-the-export] To add the TikTok Product Catalog export in Productsup: Go to **Exports** from your site’s main menu and select **ADD EXPORT**. Search for *TikTok Product Catalog* , hover over it, and select **Add**. UUID-9f902e35-f9b9-1810-4af6-a5eae57fceab

UUID-9f902e35-f9b9-1810-4af6-a5eae57fceab

On the **Exports** page, select the name of the added export template to set it up. Select **Add Destination** and choose your desired destination from the dropdown, for example *Productsup Server*. Give it a name as desired, and select **Save**. See [Find the most suitable export destination](/docs/help-center/best-practices/find-the-most-suitable-export-destination) to learn what destination fits you. UUID-a0e8b147-2a47-bda9-bd94-3c787546993b

UUID-a0e8b147-2a47-bda9-bd94-3c787546993b

Select **Save**. # Add Bing Shopping export import { Step, Steps } from "fumadocs-ui/components/steps"; Introduction [#introduction] Bing Shopping is a key Microsoft Advertising platform that lets customers search for products from various sellers. Prerequisites [#prerequisites] To set up the Bing Shopping export, you need: . Your Microsoft Advertising account. Set up Bing Shopping export [#set-up-bing-shopping-export] Go to **Exports** from your site's main menu and select **ADD EXPORT**. Search for *Bing Shopping*, hover over it, and select **Add**. UUID-2a044af9-dad9-557b-1b7f-448164680a83

UUID-2a044af9-dad9-557b-1b7f-448164680a83

Go to **Exports** and select your *export name*. Select **Add Destination**, choose the needed destination from the Destination drop-down menu, and select **Save**. You can choose any standard flat-file destination option, such as *Productsup Server* or *SFTP/FTP/FTPS Server*. UUID-976e9e55-8fd3-9610-ac50-b7fcab759f6f

UUID-976e9e55-8fd3-9610-ac50-b7fcab759f6f

Select **Save**. Go to **Dataflow** from the site's main menu and choose the added export from the drop-down menu in the top ribbon on the left. Map the attributes from import to export. See [Use Dataflow to map your attributes from import to export](/docs/help-center/map-and-optimize-your-data/dataflow/use-dataflow-to-map-your-attributes-from-import-to-export) for more information. When your data is ready, select **Run** or **Export this export** in the upper right corner of the page. Productsup creates a link to the TXT output file. To find it, scroll to the *Filename* section at the bottom of the export setup page. Copy the link and paste it into the file in your Microsoft Advertising account to upload your products. # Set up the Amazon Product Export import { Callout } from "fumadocs-ui/components/callout"; import { Step, Steps } from "fumadocs-ui/components/steps"; The Amazon Product Export lets you create new product listings on Amazon and update existing ones directly from Productsup. It works for both Seller Central (third-party sellers) and Vendor Central (first-party vendors) accounts, and connects via Amazon's Selling Partner API (SP-API). Prerequisites [#prerequisites] Before setting up the Amazon Product Export, confirm the following: * You have an active Amazon Seller Central or Vendor Central account. * You have your **Seller ID** (Seller Central) or **Vendor Code** (Vendor Central). You can find these in the left-hand navigation or the product listing view in your Amazon account. * The marketplace you want to export to is available in the export list. See [Add the export](#add-the-export). * Your Amazon account is in good health: valid payment method, correct VAT or tax details, and no outstanding compliance issues. If authentication fails during setup, the most common cause is an issue with your Amazon account — for example, an expired payment method or missing VAT details — and not a Productsup error. Check your Amazon account health before raising a support request. Add the export [#add-the-export] Go to **Exports** from your site's main menu and select **ADD EXPORT**. Search for the marketplace you want to export to. Exports follow the naming format: * **Amazon Seller Central – Product Creation (XX)** for Seller Central accounts * **Amazon Vendor Central – Product Creation (XX)** for Vendor Central accounts Replace **XX** with the country code of your target marketplace, for example *US*, *DE*, or *AU*. Amazon export list showing Seller Central entries for US, AU, CA, MX, DE, and ES

Amazon export list showing Seller Central entries for US, AU, CA, MX, DE, and ES

If the marketplace you need is not in the list, that region is not yet supported. Contact your Customer Success Manager or [support@productsup.com](mailto:support@productsup.com) to request it. Hover over the export and select **Add**. Configure the destination [#configure-the-destination] On the **Exports** page, select the name of the export you added. Select **Add Destination**. From the dropdown, choose the destination that matches your account type: * *Amazon Seller Central Products* for Seller Central accounts * *Amazon Vendor Central Products* for Vendor Central accounts Give the destination a name and select **Save**. In **Authentication**, select an existing authentication or select **Add New Authentication** to connect your Amazon account via OAuth. Selecting **Add New Authentication** redirects you to Amazon to complete the authorisation. Once authorised, Amazon redirects you back to Productsup automatically. In **Marketplace ID**, select the country or region you are exporting to. This must match the export you selected in [Add the export](#add-the-export). If you are using a Seller Central account, enter your Amazon Seller ID in **Seller ID**. If you are using a Vendor Central account, enter your Amazon Vendor Code in **Vendor Code**. Destination settings panel showing authentication, Marketplace ID set to Germany, Vendor Code field, Feedback Import toggled on, and Category Specific Attributes toggled on

Destination settings panel showing authentication, Marketplace ID set to Germany, Vendor Code field, Feedback Import toggled on, and Category Specific Attributes toggled on

Switch **Feedback Import** to *On*. This is required to receive error feedback from Amazon after each export run. Keep **Category Specific Attributes** set to *On*. Switch **Active** to *On* and select **Save**. Set up category mapping [#set-up-category-mapping] You must map your attributes to the Amazon categories using a *Classification Mapping* list to let Productsup know which category-specific attributes should be available to you. Go to **Lists** from your site's main menu and select **ADD LIST**. Select **Classification Mapping** and select **Next**. ADD LIST screen with Classification Mapping selected

ADD LIST screen with Classification Mapping selected

In **Name**, give the list a descriptive name, for example *Amazon classification mapping*. In **Classification**, select the Amazon export you added in [Add the export](#add-the-export), for example *Amazon Seller Central – Product Creation (DE)*. In **Stage**, select whether your category data comes from the **Import** or **Intermediate** stage. In **Attribute**, select the attribute in your data that contains your product categories. Configure Classification Mapping list showing Name, Classification, Stage, and Attribute fields

Configure Classification Mapping list showing Name, Classification, Stage, and Attribute fields

Select **Add**. Map the category values pre-populated in the list to the corresponding Amazon categories. Map attributes in Dataflow [#map-attributes-in-dataflow] Go to **Dataflow** from your site's main menu and select your Amazon export in the dropdown on the left. Map your category attribute to `__category_path` in the intermediate stage, and apply the *Classification Mapping* rule box using the list you created in [Set up category mapping](#set-up-category-mapping). Select **Run** in the top-right corner of your view. This run will fail — this is expected. The platform uses this run to retrieve the category-specific attribute (CSA) templates from Amazon for the product types in your data. After the run completes, the **Classifications** dropdown appears in the Dataflow toolbar. Use the **Classifications** dropdown to switch between CSA sub-channels and map the attributes for each product type. Some attributes only appear for specific sub-channels — these are the category-specific ones. Dataflow view showing __category_path mapped and the Classifications dropdown open with Amazon Vendor – DE – BRAKE_ROTOR visible

Dataflow view showing __category_path mapped and the Classifications dropdown open with Amazon Vendor – DE – BRAKE_ROTOR visible

Once all attributes are mapped across all sub-channels, check your export readiness before going live. See [Check your export readiness](#check-your-export-readiness). Check your export readiness [#check-your-export-readiness] Use the Readiness analysis tool in Data View to verify your data meets Amazon's requirements before going live. Go to **Data View** from your site's main menu and select your Amazon export from the dropdown on the top left. Select the **Overview** dropdown and choose **Readiness**. Review the readiness score and use rule boxes to correct any flagged issues. Aim for 100% readiness before running a live export. Monitor results after submission [#monitor-results-after-submission] Amazon validates your products in stages — first when you submit them, then through asynchronous compliance checks — before they ever reach a buyer. Productsup does not just send your product data to Amazon; it also brings back the issues Amazon raises during and after submission. That means you can spot errors early, act on them in time, and keep your products live. Channel Feedback for Amazon [#channel-feedback-for-amazon] Channel Feedback is your one-stop dashboard for monitoring product feed issues on Amazon. Instead of hunting through raw error logs, you get a structured, prioritised view of everything Amazon has accepted, rejected, or flagged — all in one place. Channel Feedback for the Amazon export requires activation per site. Contact your Customer Success Manager or [support@productsup.com](mailto:support@productsup.com) with your site ID to request it. See everything at a glance [#see-everything-at-a-glance] The Channel Feedback History page records every feed submission from the past 30 days. Open any export to see what happened, compare results over time, and track your progress as you resolve issues. Feedback from both product submission and compliance checks appears here.

Channel Feedback History page showing a list of exports with feedback status, products exported, total issues, errors, and download options

Comparing exports over time in Channel Feedback History

The following statuses may appear in the history list: | Status | What it means | | -------------------- | ------------------------------------------------------ | | *Received* | Feedback successfully synced — ready to review | | *Partially Received* | Some feedback synced, but the report may be incomplete | | *Not Received* | Sync failed — raise a support ticket for investigation | | *Awaiting* | Sync in progress — check back in a few minutes | | *0 issues found* | No errors or warnings reported for this run | You can download the raw feedback as a CSV file from the history list. Get to the bottom of every issue [#get-to-the-bottom-of-every-issue] Select any export in the history list to open the Channel Feedback Detail page, which shows exactly what Amazon reported back. For each issue, you can see: * How serious it is — whether it is a critical error blocking your products or a suggestion for improvement. * Which field has the problem — price, description, image, and so on, identified immediately. * How many products are affected — so you can gauge the impact at a glance. * What to do about it — clear error messages that make sense. You can switch between two views to investigate issues the way that suits you: * **View by issue** — feedback grouped by error message, with the affected attribute, severity, and the number of products affected by each issue. * **View by product** — feedback grouped by product ID, so you can see every issue tied to a single item. Channel Feedback Detail page — View by issue, showing severity, affected attribute, and number of products per issue

Channel Feedback Detail page — View by issue, showing severity, affected attribute, and number of products per issue

Channel Feedback Detail page — View by product, showing every issue affecting a single item

Jump straight to the problem products [#jump-straight-to-the-problem-products] When you spot an issue, select **Affected Products** to open a filtered Data View showing only the products with that specific problem — with the affected field already highlighted. You can see exactly which products need attention and act on them immediately, without searching through your entire catalog manually. Channel Feedback reflects Amazon's synchronous validation only. A product accepted at this stage is not guaranteed to be live on Amazon. See [Check for downstream issues](#check-for-downstream-issues) to catch issues that arise after acceptance. Check for downstream issues [#check-for-downstream-issues] Amazon runs a second round of validation hours after the initial acceptance. Issues at this stage do not appear in Channel Feedback. To check for downstream issues, set up an Amazon Product Import datasource using the **Listings API** source. The platform pulls your products back from Amazon with any errors or warnings flagged after acceptance — equivalent to the product issues view in Seller Central or Vendor Central. The Listings API supports up to 1,000 products per call. Use SKU or severity filters to narrow results when working with large catalogs. If the Listings API and the Amazon UI show conflicting results, treat the **Amazon UI as the source of truth**. Discrepancies between the two are an Amazon-side issue. As an alternative, log in to your Seller Central or Vendor Central account directly and review product issues there. Common issues [#common-issues] | Issue | Likely cause | What to do | | -------------------------------------------------------- | ----------------------------------------- | -------------------------------------------------------------------------------------------------------------- | | Authentication fails | Amazon account health issue | Check your Amazon account for expired payment details, missing VAT, or compliance flags | | Products rejected in Channel Feedback | Incorrect or missing attribute values | Review the error messages, correct the data, and run the export again | | Product accepted but not visible on Amazon | Amazon downstream async validation failed | Check via the Product Import (Listings API) datasource or Seller/Vendor Central | | Product not in Channel Feedback and not on Amazon | Submission may have failed silently | Contact [support@productsup.com](mailto:support@productsup.com) with the affected SKU(s) | | Marketplace or product type missing from the export list | Not yet supported | Contact your Customer Success Manager or [support@productsup.com](mailto:support@productsup.com) to request it | # Add Idealo Partner API v2.0 export import { Step, Steps } from "fumadocs-ui/components/steps"; Introduction [#introduction] This section describes how you can modify and upload your feed to the Idealo Partner API v2.0 in the Productsup platform. See Idealo's [Partner Web Service (PWS 2.0) API documentation](https://import.idealo.com/docs/#_put). In the platform, choose from three (3) Idealo Partner API v2.0 export templates to upload your feed: * Idealo Partner API v2.0 - Price Comparison Offers export template for products available for price comparison. * Idealo Partner API v2.0 - Offers Export template for products available for direct checkout and price comparisons on Idealo. * Idealo Partner API v2.0 - Partial Offer Updates for updates to existing products only. Requirements [#requirements] You need to map two attribute groups in *Dataflow* to set up an Idealo Partner API v2.0 successfully: `paymentCosts` attributes - You must provide a value for at least one (1) payment cost field and for any payment method you accept. UUID-ee0dfaeb-801f-8eed-df79-abb74365c7bb

UUID-ee0dfaeb-801f-8eed-df79-abb74365c7bb

* If you do not want to associate a cost, enter `0.00`. `energyLabels`, referred to as EEK (Energy Efficient Class) attributes - You must have values for applicable products, for example, electronics, lighting, and tires, for these fields, as required under EU law: UUID-ae3cda5e-ab8a-4344-3d67-5486c5014e93

UUID-ae3cda5e-ab8a-4344-3d67-5486c5014e93

See: * [Elektronische Geräte](https://idealo.us8.list-manage.com/track/click?u=55d1194af6621aef71dfb168f\&id=621b39b7b7\&e=3cb2722f36) * [Reifen](https://idealo.us8.list-manage.com/track/click?u=55d1194af6621aef71dfb168f\&id=ab17deae6c\&e=3cb2722f36) * [Lichtquellen](https://idealo.us8.list-manage.com/track/click?u=55d1194af6621aef71dfb168f\&id=a3d2e5828e\&e=3cb2722f36) You can also learn more in Idealo's API documentation regarding labels. See [Partner Web Service (PWS 2.0) API Documentation](https://import.idealo.com/docs/#_put). Delete products from Idealo Partner API v2.0 [#delete-products-from-idealo-partner-api-v20] Productsup applies delta logic to capture products removed from import data and automatically delete them from Idealo. Delta logic means that when you remove offers from the import data, the platform compares products to the previous run and identifies changed and deleted products. The platform changes or deletes those products from the export during the next run. Unchanged products stay without changes. Idealo Partner API v2.0 - Price Comparison Offers [#idealo-partner-api-v20---price-comparison-offers] Use the Idealo Partner API v2.0 - Price Comparison Offers export template for products available for price comparison. Go to **Exports** from your site’s main menu. Select **ADD EXPORT** and search for *Idealo Partner API v2.0 - Price Comparison Offers*. UUID-44f38f43-de0f-cdec-e2e6-20f74ec52261

UUID-44f38f43-de0f-cdec-e2e6-20f74ec52261

Select **Add**, give it a custom name if you desire, and select **Add** again. Under **Destinations**, select **Add Destination** and choose *Idealo Offer Export API* from the drop-down list. Optionally, you can customize the destination's description in **Name**. UUID-6d5b5b0f-8a74-819b-c6d6-745d3474c4f9

UUID-6d5b5b0f-8a74-819b-c6d6-745d3474c4f9

In **Client ID** and **Client Secret**, enter your Idealo client credentials. Enter the Idealo **Shop ID** for shop orders. (Optional) To continue with the feedback import option, switch **Feedback import** to **On**. Use this option if you want an error file returned to the platform once your data export finishes. The platform returns the feedback error file to your site as an additional data source with the following: * `SKU`: Your product ID. This field contains the default name or the name you defined during setup in step [3](#N1641219469571). * `**___idealo_id**`: The Idealo product ID. * `**___idealo_status**`: Product upload status. For example, `OK`, `failed`, and `ignored`. * `**___idealo_status_message**`: The reason why the upload failed for this product. For example, `Mandatory field 'title' is missing or empty!` Turn on the destination by switching **Active** to **On**. Select **Save**. UUID-11dc8687-15af-fd6e-62e9-3a546344f2e5

UUID-11dc8687-15af-fd6e-62e9-3a546344f2e5

Idealo Partner API v2.0 - Offers Export [#idealo-partner-api-v20---offers-export] Use the Idealo Partner API v2.0 - Offers Export template for products available for direct checkout and price comparisons on Idealo. Go to **Exports** from your site’s main menu. Select **ADD EXPORT** and search for *Idealo Partner API v2.0 - Offers Export*. UUID-1fcce15d-ea84-cf8d-9bb0-22a5e6a677b6

UUID-1fcce15d-ea84-cf8d-9bb0-22a5e6a677b6

In **Client ID** and **Client Secret**, enter your Idealo client credentials. Enter the Idealo **Shop ID** for shop orders. (Optional) To continue with the feedback import option, switch **Feedback import** to **On**. Use this option if you want an error file returned to the platform once your data export finishes. The platform returns the feedback error file to your site as an additional data source with the following: * `SKU`: Your product ID. This field contains the default name or the name you defined during setup in step [3](#N1641220327143). * `**___idealo_id**`: The Idealo product ID. * `**___idealo_status**`: Product upload status. For example, `OK`, `failed`, and `ignored`. * `**___idealo_status_message**`: The reason why the upload failed for this product. For example, `Mandatory field 'title' is missing or empty!` Turn on the destination by switching **Active** to **On**. Select **Save**. UUID-11dc8687-15af-fd6e-62e9-3a546344f2e5

Idealo Partner API v2.0 - Partial Offer Updates [#idealo-partner-api-v20---partial-offer-updates] Use the Idealo Partner API v2.0 - Partial Offer Updates for updates to existing products only. This method is efficient since there are fewer attributes required to send. Go to **Exports** from your site’s main menu. Select **ADD EXPORT** and search for *Idealo Partner API v2.0 - Partial Offer Updates*. UUID-efabb3fb-f13b-f016-82dc-d48358622f88

UUID-efabb3fb-f13b-f016-82dc-d48358622f88

Select **Add**, give it a custom name if you desire, and select **Add** again. Under **Destinations**, select **Add Destination** and choose *Idealo Offer Updates API* from the drop-down list. Optionally, you can customize the destination's description in **Name**. UUID-c662b7f5-19d1-b33a-e546-82ffa37a50ef

UUID-c662b7f5-19d1-b33a-e546-82ffa37a50ef

In **Client ID** and **Client Secret**, enter your Idealo client credentials. Enter the Idealo **Shop ID** for shop orders. (Optional) To continue with the feedback import option, switch **Feedback import** to **On**. Use this option if you want an error file returned to the platform once your data export finishes. The platform returns the feedback error file to your site as an additional data source with the following: * `SKU`: Your product ID. This field contains the default name or the name you defined during setup in step [3](#N1641220304541). * `**___idealo_id**`: The Idealo product ID. * `**___idealo_status**`: Product upload status. For example, `OK`, `failed`, and `ignored`. * `**___idealo_status_message**`: The reason why the upload failed for this product. For example, `Mandatory field 'title' is missing or empty!` Turn on the destination by switching **Active** to **On**. Select **Save**. UUID-2f1f2e3c-803c-4291-0aa2-7f4fc297fbdb

UUID-2f1f2e3c-803c-4291-0aa2-7f4fc297fbdb

# Set up the Walmart Marketplace Price & Inventory export import { Callout } from "fumadocs-ui/components/callout"; import { Step, Steps } from "fumadocs-ui/components/steps"; Walmart Marketplace treats pricing and inventory as two separate updates. Productsup provides a dedicated export and destination for each: * **Walmart Marketplace Pricing update**, sent to the *Walmart Marketplace Price export* destination. * **Walmart Marketplace Inventory update**, sent to the *Walmart Marketplace Inventory export* destination. Both update products you've already listed on Walmart Marketplace. Prerequisites [#prerequisites] * You have an approved Walmart Marketplace seller account (US) with access to Seller Center. * You have set up the [Walmart Marketplace Product Creation export](/docs/help-center/export-data-feeds/add-export/add-walmart-marketplace-product-creation-export), or your products are otherwise already listed on Walmart Marketplace. Set up the pricing export [#set-up-the-pricing-export] Go to **Exports** from your site's main menu and select **ADD EXPORT**. Search for **Walmart Marketplace Pricing update** and select **Add**. Select the export's name link. Select **Add Destination** and choose *Walmart Marketplace Price export* from the dropdown. Give it a name as desired and select **Save**. In **Authentication**, choose the Walmart authentication you previously set up, or select **Add New Authentication** to connect your account. Toggle **Active** to **On** and select **Save**. Go to **Dataflow** and select **Walmart Marketplace Pricing update** in the dropdown on the left. Map your price attributes from the intermediate to the export stage. The export uses **SKU** as the delta key to match rows to your existing listings. Select **Run** in the top-right corner to send your pricing updates to Walmart. Set up the inventory export [#set-up-the-inventory-export] Go to **Exports** from your site's main menu and select **ADD EXPORT**. Search for **Walmart Marketplace Inventory update** and select **Add**. Select the export's name link. Select **Add Destination** and choose *Walmart Marketplace Inventory export* from the dropdown. Give it a name as desired and select **Save**. In **Authentication**, choose the Walmart authentication you previously set up, or select **Add New Authentication** to connect your account. Toggle **Active** to **On** and select **Save**. Go to **Dataflow** and select **Walmart Marketplace Inventory update** in the dropdown on the left. Map your inventory attributes from the intermediate to the export stage. The export uses **SKU** as the delta key to match rows to your existing listings. Select **Run** in the top-right corner to send your inventory updates to Walmart. Walmart limits pricing and inventory updates to 6 runs per day. If you need to update more often, request a higher limit directly from Walmart Marketplace. # Add Magento 2.x Stock and Price Export import { Step, Steps } from "fumadocs-ui/components/steps"; Introduction [#introduction] The Magento 2.x Stock and Price Export lets you export products from the Productsup platform to a Magento 2.x instance. Use the Magento Stock and Price Export to enhance your data and provide more product information. Add and set up export [#add-and-set-up-export] To add the Magento 2.x Stock and Price Export in Productsup: Go to **Exports** from your site’s main menu. Select **ADD EXPORT** and search for *Magento 2.x Stock and Price Export.* UUID-fc7d0a61-ec7b-7d83-3070-492def2f630f

UUID-fc7d0a61-ec7b-7d83-3070-492def2f630f

Select **Add** and confirm adding it again as an export. In the export setup, select **Add Destination** and choose *Magento 2 API Stock and Price Export* from the drop-down list. Now enter a destination **Name**. UUID-4eaa8786-c9c9-03d1-be2f-75706015131e

UUID-4eaa8786-c9c9-03d1-be2f-75706015131e

In **Authentication**, choose **Select authentication**. Then choose an available authentication from the drop-down list or select **Add New Authentication**. You can also choose to use pre-existing export tags from another platform in **Authentication**. See [Add OAuth authentication to external systems](/docs/help-center/import-data-feeds/import-your-data-into-productsup/add-oauth-authentication-to-external-systems) to set up authentication with another platform. Add your Magento store URL in **Base URL**. Switch **Feedback import** to **On** if you want an error file returned to the platform once your data export finishes. Go to step [10](#listitem-idm11616685403177) if **Feedback import** is set to **Off**. Choose a column that you want to receive a feedback import file on in **Main feed connection column**. Enter the column that connects to your feedback import in **Feedback file connection column**. Select a **Magento Version** from the drop-down list. Turn on the destination by switching **Active** to **On**. Select **Save**. UUID-16b4e020-6eb1-e8ba-0230-b111c953d6c4

UUID-16b4e020-6eb1-e8ba-0230-b111c953d6c4

# Add Google Responsive Search Ads export import { Callout } from "fumadocs-ui/components/callout"; import { Step, Steps } from "fumadocs-ui/components/steps"; Introduction [#introduction] This document explains the necessary steps for exporting your product ads using the Google Responsive Search Ads export. And how to use your exports during campaign creation in Google Ads. The Google Responsive Search Ads export replaced the Google Ads API export. Productsup sunset the Google Ads (API) in anticipation of Google discontinuing support for expanded text ads on 30 June 2022. You can create Google Ads campaigns, even if you don't list your products in Google Merchant Center, such as real estate listings. To export ads to the Google Ads API, follow these required steps: Add Google Ads authentication. Set up the Google Responsive Search Ads export. Set up the Google Responsive Search Ads destination. Add your Google Ads authentication [#add-your-google-ads-authentication] To add and set up Google Ads authentication: Go to **Authentication** from the site's main menu. Then select **ADD AUTHENTICATION**. UUID-16d3cd75-a9a0-9109-fb9c-f753f3da04a6

UUID-16d3cd75-a9a0-9109-fb9c-f753f3da04a6

Next, select *Google Ads* from the drop-down menu and enter a custom name as desired in **Name**. Then select **Next**. UUID-4e96a2b5-b945-637c-22ae-56f30056a148

UUID-4e96a2b5-b945-637c-22ae-56f30056a148

After selecting **Connect**, you can now proceed to Google to authenticate and authorize your Google and Productsup connection. UUID-6a28ead6-aecc-1989-3fbe-75dfac7748f1

UUID-6a28ead6-aecc-1989-3fbe-75dfac7748f1

Set up the Google Responsive Search Ads export [#set-up-the-google-responsive-search-ads-export] Go to **Exports** and select **ADD EXPORT**. Next, choose the *Google Responsive Search Ads* export and select **Add**. Confirm the export again by selecting **Add**. UUID-f8f651fd-9a74-42c4-87c0-8888e8d13132

UUID-f8f651fd-9a74-42c4-87c0-8888e8d13132

To set up the export destination, select **Add Destination**, and choose *Google Responsive Search Ads* from the drop-down menu. Now enter a custom name if you desire in **Name**. UUID-0361000f-e196-f921-18c0-6f16cb945209

UUID-0361000f-e196-f921-18c0-6f16cb945209

In **Authentication to use**, select **Add New Authentication** or choose **Select authentication**. Choose the authentication you previously set up in step [1](#N1618330122474). You can also use pre-existing export tags from another platform in **Authentication**. See [Add OAuth authentication to external systems](/docs/help-center/import-data-feeds/import-your-data-into-productsup/add-oauth-authentication-to-external-systems) to set up authentication with another platform. Now, enter the **Manager customer ID** and **Campaign owner customer ID**, and **Campaign ID** found in your Google Ads account. Enter a value in **Final URLs column values separator** to separate URLs. The default separator is a comma (`,`). Turn on the destination by switching **Active** to **On**, then select **Save**. UUID-72d2f0c8-7f08-8329-e4b7-39b9c980e452

UUID-72d2f0c8-7f08-8329-e4b7-39b9c980e452

Create your campaign ads in Productsup and then perform an export to send them to Google Ads. Creating Adgroups [#creating-adgroups] You can find the different Adgroups that structure your text ads within your Google Ads account. Aside from assigning existing Adgroups to your text ads, you can dynamically create them. By populating the `group_name column`, the export to API creates the Adgroups if they are not yet present in Google Ads. Populate export columns in Dataflow [#populate-export-columns-in-dataflow] Add export column fields to populate ad content, as seen in the following expanded text ad examples: UUID-d454a489-8831-de37-0e45-10b444592405

UUID-d454a489-8831-de37-0e45-10b444592405

The following content was necessary to create the expanded text ad, as previously shown: | Export Column | Content | | --------------- | ---------------------------------------------------- | | `headlinePart1` | Cruise to Mars #12QjNuTP | | `headlinePart2` | Best Space Cruise Line | | `description` | Buy your tickets now! | | `finalUrls` | [http://www.example.com/0](http://www.example.com/0) | | `path1` | all-inclusive | | `path2` | deals | Run log and warnings [#run-log-and-warnings] You can open the Run log while the site is processing to get live responses from the Google Responsive Search Ads export. Select the **Run log** icon in the top-right corner. UUID-1d843065-afeb-583b-144c-9591ffdc7933

UUID-1d843065-afeb-583b-144c-9591ffdc7933

The Run log can warn you about trademark violations, unapproved word usage, and syntax errors. # Add Google Things To Do export import { Step, Steps } from "fumadocs-ui/components/steps"; *Things to do* is an area within Google Travel where users can discover and book tours, activities, and attractions. You can list your tours, activities, and attractions, providing descriptions, prices, and availability information. When users select a listing, they get to the operator's website and can book directly without any Google's commission. You can use the *Google Things To Do* export in Productsup to upload your product feed to Google in the specified JSON format. Prerequisites [#prerequisites] To set up the *Google Things To Do* export, you need: . Create a Things to do centre account and Secure File Transfer Protocol (SFTP) endpoints in Google. During the setup, you need to provide the following SSH key to Google: | `ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABgQDNnqgT4GoIWhMaY7kp1XvLJXjWLy7Q49ltWaLGbFFN80GzWWWRYOjpGZSPi8KgvkbACkbGu5kYDGYDy+jBlhiiI/XDTO02h5ZNjkaEHJ8s/FMqhaY6eOwwiRfQDdwBAoPY5yxZI/yfsdP3lJaZgZykyMPCiYviUK662j1H6gvLBFcIhROCD1BIby5x2JgRck7apgkEWAmdArWjCDJCMtouEb1X90gQZwgkzsZDDiE8gKxFvqyMoLtCM2Vo6caC/IyIX9mrj9cOhsOOYxK1LCHZTOL1UiYkDGGJpaItyQwjkVuQ4ACuWv1eVGGWCZCw7dShntBOuY4ryu5YzcAbBGm8r/lzdZ+bVnmBeCC8Cf1Al+46jV+KmpVkqcXeLuWCA1rk9xLPv0fa92DFQcRW5x9GLV+Kq25Q4F34RxmQ3LLX6gTky+MhVa8NFBijRcTiaPrTyjzlRKS2acYuX8rnBFfI9l8MqDPzZq0XEjO2HJNzmAzknwFR6ZogDzxUybu+GbU= google-things-to-do@productsup.com` | | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | See [Things to do centre: Starter guide](https://support.google.com/google-ads/answer/13387362?hl=en-AU#:~:text=Initial%20setup,in%20Things%20to%20do%20centre.) for more information. | Set up Google Things To Do export [#set-up-google-things-to-do-export] Go to **Exports** from your site's main menu and select **Add export**. Search for *Google Things To Do*, hover over it, and select **Add**. UUID-91e46608-43b8-145f-e559-721dfc2a8573

UUID-91e46608-43b8-145f-e559-721dfc2a8573

In Exports, select the added export *Google Things To Do*. Select **Add Destination**. Select *Google Things To Do* from the **Destination** drop-down menu, and choose **Save**. In **SFTP Host**, enter your SFTP server address without prefixes, such as `sftp://`. In **Port**, enter the port number that the platform should use to establish a connection with your SFTP server. By default, the platform uses port `22`. In **SFTP Username**, enter your server username. If you want to send your data to a specific folder on your SFTP server, provide the path to the desired folder in **SFTP Directory**. By default, the platform sends your data to the root folder. Leave the **Feedback Import** toggle *On* to let the platform receive feedback files from the Google API in case of export errors. This helps to troubleshoot the setup. Toggle **Active** to *On* to activate the destination. Select **Save**. UUID-b6c05286-438c-c46d-b0f2-6fd7624e568f

UUID-b6c05286-438c-c46d-b0f2-6fd7624e568f

Go to **Dataflow** from the site's main menu and choose the added export from the drop-down menu in the top ribbon on the left. Map the attributes from import to export. See [Use Dataflow to map your attributes from import to export](/docs/help-center/map-and-optimize-your-data/dataflow/use-dataflow-to-map-your-attributes-from-import-to-export) for more information. Use the following recommendations: 1. The platform creates the attributes for the data in English. If you need to add attributes containing the data in other languages, you can add user-generated attributes in Dataflow. Provide them with the names according to the following naming convention: `product.title.[language abbreviation]` such as **product.title.en** for English, **product.title.de** for German, and so on. 2. For sections with multiple values, such as product features, product media, and product options, for the sake of brevity, we support only one value by default. If you need more values, you can add them by creating separate user-generated attributes. Name them the same way as shown in the example: * For **product.media\[0].url**, add **product.media\[1].url**, **product.media\[2].url**, and so on. * For **option\[0].id**, add **option\[1].id**, **option\[2].id**, and so on. * For **option\[0].price\_option\[0].id**, add **option\[0].price\_option\[1].id**, **option\[0].price\_option\[2].id**, and so on. 3. To provide coordinates in the coordinates attribute, use the comma (`,`) separator, such as `-25.3510319200353,131.03269662583725`. 4. As the products for Things to do can serve different user experiences, the mandatory attributes may vary, which we can't highlight on the platform as usual. You can find the list of mandatory attributes that you must map in [Required and recommended fields](https://developers.google.com/actions-center/verticals/things-to-do/guides/partner-integration/required-fields#:~:text=Note:%20By%20providing%20the%20required,other%20fields%20are%20considered%20optional.\&text=%5B1%5D%20Experience%20module%20may%20choose,tickets%20and%201st%20party%20experiences.). If your data is ready, select **Run** or **Export** in the upper right corner of the page. If you don't want to run the entire site, including all active exports set up in it, you can go to **Exports**, select the added *Google Things To Do* export, and then choose **Export this export**. # Add DoorDash exports import { Callout } from "fumadocs-ui/components/callout"; import { Step, Steps } from "fumadocs-ui/components/steps"; Introduction [#introduction] DoorDash is a US-based on-demand delivery platform where grocery and convenience retailers list their products for local delivery. Productsup has built the DoorDash exports to let you keep your DoorDash listings up to date automatically — your product catalog, your store-level pricing and availability, and your store opening hours. DoorDash keeps three kinds of data separate — your product catalog, your store-level inventory, and your store details. Productsup provides four channels across them. You can add one, some, or all of them, depending on what you need: | Channel | What it sends | When to use it | | ----------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------- | | **DoorDash Items - API** | Your product catalog — names, descriptions, images, and categories. | You need your products listed on DoorDash. | | **DoorDash Inventory - API** | Store-level pricing and availability as a delta — only what has changed since the last run is sent directly to DoorDash. | You need ongoing, incremental price and stock updates per store. | | **DoorDash Inventory Pull - API** | Store-level pricing and availability as a full catalogue — every run prepares a complete per-store file that DoorDash collects itself. | You have large or batch-style stock updates, or DoorDash prefers to pull a full file. | | **DoorDash Store Management - API** | Each store's opening hours and holiday hours. | You need your store hours synced to DoorDash. | Inventory has two flows: choose **DoorDash Inventory - API** for incremental delta updates pushed to DoorDash, or **DoorDash Inventory Pull - API** for full-catalogue files that DoorDash pulls. Use one or the other, not both, for a given store. Each channel is added and set up separately, following the same steps. The DoorDash exports cannot delete items or create stores. DoorDash has no delete operation, so to remove a product you mark it as unavailable instead. The **DoorDash Store Management - API** channel only updates stores that already exist on DoorDash — it cannot create new ones. Prerequisites [#prerequisites] To add a DoorDash export, you need: . A DoorDash merchant account with API access enabled. . Your DoorDash API credentials: **Developer ID**, **Key ID**, and **Signing Secret**. You enter these in the destination settings in Productsup. . For the **DoorDash Store Management - API** channel, the stores you want to update must already be live on DoorDash. Add and set up the export [#add-and-set-up-the-export] Repeat these steps for each DoorDash channel you want to use. Go to **Exports** from your site's main menu and select **ADD EXPORT**. Search for the DoorDash channel you need — *DoorDash Items - API*, *DoorDash Inventory - API*, *DoorDash Inventory Pull - API*, or *DoorDash Store Management - API* — hover over it, and select **Add**. On the *Exports* page, select the name of the added export to set it up. Select **Add Destination**, choose the matching DoorDash destination from the drop-down list, give it a name as desired, and then select **Save**. Enter your DoorDash API credentials in **Developer ID**, **Key ID**, and **Signing Secret**. These let the Productsup platform authenticate with your DoorDash account. Switch **Active** to **On** to activate the destination. Select **Save**. Go to **Dataflow** from your site's main menu and select the added export from the drop-down menu in the upper ribbon. Map the attributes from import to export, then run the export. See [Use Dataflow to map your attributes from import to export](/docs/help-center/map-and-optimize-your-data/dataflow/use-dataflow-to-map-your-attributes-from-import-to-export) for more information. Map repeating fields [#map-repeating-fields] The channel template already includes the columns you map your data into. Some fields can repeat — for example, a store's opening hours or a product's images — and these come as numbered columns ending in `_1`, `_2`, `_3`, and so on. The template ships with a set number of these columns. If a store or product needs more, add the next-numbered column following the same name. | What repeats | Already in the template | Add more as | | -------------------------------------------------- | -------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------- | | Store opening hours (Store Management) | `open_hours_day_index_1` to `_8`, each with its matching `open_hours_start_time_N` and `open_hours_end_time_N` | `open_hours_day_index_9`, `_10`, and so on, with matching start and end times | | Store holiday and special hours (Store Management) | `special_hours_date_1` to `_5`, each with its start time, end time, and closed value | `special_hours_date_6`, `_7`, and so on | | Product images (Items) | `image_url_1` | `image_url_2`, `image_url_3`, and so on | For a day that has a break — for example, a store that closes for lunch — map that day a second time in the next available block. A seven-day store with one lunch break maps into blocks `_1` to `_8`. Keep the numbering in order from 1, with no gaps. A missing number stops the platform from picking up every column after it. Map product attributes [#map-product-attributes] The **DoorDash Items - API** channel can send DoorDash product attributes — extra descriptive properties such as *limited edition*, *alcohol vintage*, or *battery required*. You do not need these built into the template in advance; you add them yourself using custom numbered columns. Each attribute uses two columns that share the same number: a name column and a value column. . Add a name column, `product_attribute_1_name`, and set its value to the attribute's name exactly as DoorDash expects it — for example, `limited_edition`. . Add one value column for that same attribute, chosen by the attribute's type: | Value column | Attribute type | Accepted values | | ----------------------------------------- | -------------- | ------------------------------------------ | | `product_attribute_1_multi_select_string` | Text | One value, or several separated by commas | | `product_attribute_1_multi_select_double` | Number | One number, or several separated by commas | | `product_attribute_1_single_select_bool` | True or false | `true` or `false` | To send a second attribute, add `product_attribute_2_name` with its own value column, then `_3`, and so on. The name column and its value column must always share the same number. For example, `product_attribute_2_name` pairs only with `product_attribute_2_multi_select_string` — not with `product_attribute_1_multi_select_string`. Delta export and category updates [#delta-export-and-category-updates] The **DoorDash Items - API** channel is a delta export. Productsup's delta engine decides, per item, whether to send it as a POST (a new item, never sent before) or a PATCH (a modified item that has already been sent). Once an item has been sent once, every later export of that item goes out as a PATCH. DoorDash's API only accepts category data (`item_categorizations`) on a POST. DoorDash rejects a PATCH that carries category data, and the whole item fails with the error "Item categorizations update using PATCH is not supported." This has a practical consequence: for an item already sent once, a normal re-export cannot update its category. The delta always sends that item as a PATCH, which can never carry category data. To force every item back through POST and send category data again, reset the site data in the site's **Advanced Settings**. This resets the delta completely, so the next export run treats every item as new and sends full category data for all of them. Resetting the site data resets the delta for the entire site, not just category data. The next export run resends every item as a POST. Check the feedback file [#check-the-feedback-file] After each export, the platform retries any failed records automatically. Anything that still fails is written to a feedback file that names the product or store that failed and the reason DoorDash gave. The feedback file is the first place to look when something does not appear on DoorDash as expected. The following table covers the most common issues: | What you see | Likely cause | What to do | | ----------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- | | Some items show errors on the first run | The items already exist on DoorDash, and the export had no way to know | This is expected. Later runs correct themselves. | | Every record fails | Missing, incorrect, or expired credentials in the destination settings, or a DoorDash outage | Check your credentials in the destination settings, then check DoorDash's status. | | A store's hours are rejected | The hours were not in the format DoorDash expects | Check the feedback file for that store and review the hours formatting in your feed. | | A store update fails with "not found" | That store is not set up on DoorDash yet | Use a store that is already live on DoorDash. | | A product attribute does not appear on DoorDash | The name column and value column do not share the same number, the value column type is wrong, or the value is empty | Check that the `product_attribute_N_name` column and its value column use the same number, and that the value is not blank. | | An item fails with "Item categorizations update using PATCH is not supported" | The item was already sent once, so the delta exported it as a PATCH, which cannot carry category data | See [Delta export and category updates](#delta-export-and-category-updates). Reset the site data if you need category data resent. | | An error never appears in the feedback file | DoorDash reported the problem after accepting the request | Check your DoorDash developer portal. | # Add Google Merchant Center export import { Callout } from "fumadocs-ui/components/callout"; import { Step, Steps } from "fumadocs-ui/components/steps"; [Google Shopping](https://shopping.google.com/) shows your products as search results in the *Shopping* tab of Google Search. Google Shopping ads are product advertisements visible across the entire Google ecosystem. Although possible locations of your Google Shopping ads depend on your chosen type of Google Shopping campaign, your product ads can generally appear in Google Shopping, Google Search, Google Images, Google Maps, etc. In Productsup, you can use multiple exports to send your data to Google Merchant Center (GMC), which lets you post your products in Google Shopping and advertise them with Google Shopping ads. You can send different types of data to Google Merchant Center from Productsup using different exports: | Type of data | Exports in Productsup that send this data to GMC | | --------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | General product data (titles, images, prices, descriptions, brands, stock levels, etc.) | *Google Merchant Center*, *Google Content API for Shopping*, or *Google Content API for Shopping (multi)*.See the following sections in this document for the setup of these exports. | | Promotion data and promo text for ads | *Google Merchant Promotions* or *Google Merchant Center - Promotions (API)*.See [Add Google Merchant Promotions export](/docs/help-center/export-data-feeds/special-export-setups/add-google-merchant-promotions-export).See [Add Google Merchant Center - Promotions (API) export](/docs/help-center/export-data-feeds/special-export-setups/add-google-merchant-center-promotions-api-export). | | Star-based product ratings, overall number of product reviews, and other reviews data | *Google Product Ratings* or *Google Products Reviews* | Choose how you want to send data to GMC [#choose-how-you-want-to-send-data-to-gmc] The Productsup platform lets you export your product feed to Google Merchant Center. The specific way of setting up the export in the platform depends on how you want GMC to ingest your product data: . Via URL generated by Productsup. . Via SFTP server provided by Google Merchant Center. Google stopped supporting FTP in Merchant Center. See [End of support for FTP in Merchant Center](https://support.google.com/merchants/answer/13033917) for more information. . Via API integration between Productsup and GMC that lets you automate and schedule data uploads. You can choose any option based on the number of products you have and the rate of their data changeability: * If your feed contains few products and the data doesn't change often, consider using the URL or the SFTP server. * If your feed contains many products and the data constantly updates, select API. With API, you can only send product data updates to GMC instead of entire feeds, which speeds up the export. Prerequisites [#prerequisites] To export your product data to Google Merchant Center via URL, you need: . A Google Merchant Center account. . Product data containing the needed product attributes. See [Product data specification](https://support.google.com/merchants/answer/7052112) for information on all mandatory and optional attributes for GMC. To export your product data to Google Merchant Center via SFTP, you need: . A Google Merchant Center account. . Relevant SFTP server credentials, such as a username and a password. . Product data containing the needed product attributes. See [Product data specification](https://support.google.com/merchants/answer/7052112) for information on all mandatory and optional attributes for GMC. To export your product data to Google Merchant Center via API, you need: . A Google Merchant Center account. . GMC authentication in your Productsup organization. See [Add OAuth authentication to external systems](/docs/help-center/import-data-feeds/import-your-data-into-productsup/add-oauth-authentication-to-external-systems) for more information.To add GMC authentication to your Productsup organization: Go to **Authentication** from the organization's, project's, or site's menu and select **ADD AUTHENTICATION**. In **Type**, select *Google Merchant Center*, give it a custom name as desired, and select **Next**. Select **Connect** for Productsup to redirect you to a Google account page where you can give Productsup access to your Google Merchant Center account. Once ready, Google redirects you back to Productsup. Close the confirmation window to proceed. . Your Merchant ID that Google assigned to your payment profile. See [Find your Merchant ID](https://support.google.com/paymentscenter/answer/7163092?hl=en) for more information. . Product data containing the needed product attributes. See [Product data specification](https://support.google.com/merchants/answer/7052112) for information on all mandatory and optional attributes for GMC. . A clear strategy for migrating to the API export method: You can skip this requirement if you have never uploaded any products to your GMC account. * If you have already uploaded product data to your Google Merchant Center account, use the same product IDs you used with your previous data upload mechanisms to avoid data conflicts and loss. * You must stop uploading product data using other mechanisms and let the API method in Productsup be the only way you send product data to your GMC account. Upload data to Google Merchant Center via URL [#upload-data-to-google-merchant-center-via-url] To upload your product data to Google Merchant Center via URL, add the Google Merchant Center export template to your site and use the Productsup Server destination: Go to **Exports** from your site's main menu and select **Add export**. Search for *Google Merchant Center*, select **Add**, give it a name as desired, and again select **Add**. UUID-bd325c3b-1fec-13ba-4e83-4a9b977179e6

UUID-bd325c3b-1fec-13ba-4e83-4a9b977179e6

Select **Add Destination**, choose *Productsup Server* from the dropdown, give it a name as desired, and then select **Save**. UUID-3e24346b-c5a9-5e6e-30d7-786da3260a9f

UUID-3e24346b-c5a9-5e6e-30d7-786da3260a9f

Go to **Dataflow** to locate all the attributes mandatory for Google Merchant Center and map them from import to export. Go to **Data View** to optimize your data as needed. See [Rule box category Google Merchant Center](/docs/help-center/add-a-rule-box/find-the-needed-rule-box-category/rule-box-category-google-merchant-center) for more information. Upload data to Google Merchant Center via the SFTP server [#upload-data-to-google-merchant-center-via-the-sftp-server] To upload your product data to GMC via the SFTP server, add the Google Merchant Center export template to your site and use the Google Merchant Center SFTP destination: Go to **Exports** from your site's main menu and select **Add export**. Search for *Google Merchant Center*, select **Add**, give it a name as desired, and again select **Add**. UUID-bd325c3b-1fec-13ba-4e83-4a9b977179e6

Select **Add Destination**, choose *Google Merchant Center SFTP* from the dropdown, give it a name as desired, and select **Save**. Set up Google Merchant Center SFTP destination: 1. In **User**, enter your SFTP server username. 2. In **Password**, enter the password for your SFTP server account. 3. Select **On** in **Active** to activate the destination. 4. Select **Save**. Go to **Dataflow** to locate all the attributes mandatory for Google Merchant Center and map them from import to export. Go to **Data View** to optimize your data as needed. See [Rule box category Google Merchant Center](/docs/help-center/add-a-rule-box/find-the-needed-rule-box-category/rule-box-category-google-merchant-center) for more information. Upload data to Google Merchant Center via API [#upload-data-to-google-merchant-center-via-api] When you use the API option to upload your product feed to Google Merchant Center, Productsup continuously processes all changes you perform in your data and syncs only the changed parts of the data with GMC. The API uploads delta files only. Besides automating data synchronization and helping you work with more products, uploading data to GMC via API lets Productsup receive error responses from GMC as feedback files in *Data Sources*. You can troubleshoot your product data optimizations using these files. To upload your product data to GMC via API, you should use one of the following export templates: . *Google Content API for Shopping*. Use this option to export one product feed to one Google Merchant Center account. If you have multiple parent GMC accounts to which you want to send your feed, add and set up multiple templates of the Google Content API for Shopping export to your site. . *Google Content API for Shopping (multi)*. Use this option to export one product feed to multiple sub-accounts within your parent GMC account. With the Google Content API for Shopping (multi) export, you can use multithreading to push products to GMC in parallel and speed up your exports. Add Google Content API for Shopping export [#add-google-content-api-for-shopping-export] Google recommends limiting the size of the product batches you export from Productsup into GMC. The default batch size is 1,000 products. You can expect that Productsup typically sends batch sizes ranging from 100 to 1,000 products. Go to **Exports** from your site's main menu and select **Add export**. Search for *Google Content API for Shopping*. Select **Add**, give it a name as desired, and again select **Add**. UUID-e92b5256-4e04-c48d-5ee5-d2697d9f85b4

UUID-e92b5256-4e04-c48d-5ee5-d2697d9f85b4

Select **Add Destination** and choose *Google Content API (single account)* from the dropdown. You can optionally customize the destination's description in **Name**. Select **Save**. UUID-5ae96901-65fc-2e90-9ed3-94b1773d09c3

UUID-5ae96901-65fc-2e90-9ed3-94b1773d09c3

In **Merchant Center ID**, enter your [Merchant ID](#listitem-idm243381106444736). If you have a multi-client GMC, enter the Merchant ID of your sub-account. Select the appropriate target country and language for the feed in **Target Country** and **Target Language**. Define how often you want the platform to perform a complete product upload in **Full Upload Interval (in days)**. To avoid product expiration, the platform exports new, deleted, changed, and unchanged products during a complete upload performed once every defined time interval. Google Merchant Center deactivates unchanged products after 30 days or sooner if a specified number of days have passed. In **Merchant Center Cleanup**, choose **Yes** to delete products within GMC that do not originate from Productsup. By default, this option is disabled.*This setting should only be used once*. You can enable it if you are migrating from other service providers to Productsup. Once the migration is over, you should disable this setting. Keeping this setting enabled can cause unexpected product deletions. For example, during a full catalog export, the destination matches the items it exports from your site with the products already available in your GMC. If a product in your GMC isn't present in the export, the destination removes it from GMC. Choose your GMC authentication in **Authentication to use**. If you haven't created the authentication in the platform yet, select **Add New Authentication** and create it, as previously seen in [Prerequisites](#listitem-idm241690553222369). Select **On** in **Enable Error Log File** to let Productsup upload feedback files that contain export-related errors as a new data source. You can also download the zipped errors file from the Run log. UUID-1d268d00-6460-64d6-db15-24fe27409261

UUID-1d268d00-6460-64d6-db15-24fe27409261

The ZIP folder may contain error logs spread across different files. You can search for something specific in the logs using a keyword, for example, `product ID`. Some text editors let you search for a keyword across all files in a ZIP file. In **Log API calls**, select **On** for the platform to log calls to the GMC API. You can find the logs in the Run log. In **Log headers of API calls**, select **On** to add response headers to the logs. In **API call logging end time**, enter a date using the `YYYYMMDD` or `YYYY-MM-DD` format, stating when the platform should stop logging API calls. Do not let this feature run indefinitely, as it generates excessive files and slows exports. Turn on the destination by selecting **On** in **Active**. Select **Save**. Go to **Dataflow** to locate all the attributes mandatory for Google Merchant Center and map them from import to export. Go to **Data View** to optimize your data as needed. See [Rule box category Google Merchant Center](/docs/help-center/add-a-rule-box/find-the-needed-rule-box-category/rule-box-category-google-merchant-center) for more information. The API is more restrictive than the SFTP or URL upload. If you upload an incorrect category or your feed is missing mandatory attributes, the product upload fails. Add Google Content API for Shopping (multi) export [#add-google-content-api-for-shopping-multi-export] Google recommends limiting the size of the product batches you export from Productsup into GMC. The default batch size is 1,000 products. You can expect that Productsup typically sends batch sizes ranging from 100 to 1,000 products. Go to **Exports** from your site's main menu and select **Add export**. Search for *Google Content API for Shopping (multi)*. Select **Add**, give it a name as desired, and again select **Add**. UUID-df874b19-7aad-4fac-48c1-84d608ccdb8e

UUID-df874b19-7aad-4fac-48c1-84d608ccdb8e

Select **Add Destination** and choose *Google Content API (multi account)* from the dropdown. You can optionally customize the destination's description in **Name**. Select **Save**. UUID-426e296d-98b3-435f-e8d0-d3d7825cd62c

UUID-426e296d-98b3-435f-e8d0-d3d7825cd62c

In **Parent Merchant Center**, enter the [Merchant ID](#listitem-idm243381106444736) of your GMC sub-account. In **Merchant Reference Column**, choose the attribute within your feed that contains your merchant center name, merchant center ID, or seller ID. Select the appropriate target country and language for the feed in **Target Country** and **Target Language**. Define how often you want the platform to perform a complete product upload in **Full Upload Interval (in days)**. To avoid product expiration, the platform exports new, deleted, changed, and unchanged products during a complete upload performed once every defined time interval. Google Merchant Center deactivates unchanged products after 30 days or sooner if a specified number of days have passed. Choose your GMC authentication in **Authentication to use**. If you haven't created the authentication in the platform yet, select **Add New Authentication** and create it, as previously seen in [Prerequisites](#listitem-idm241690553222369). Select **On** in **Create Merchant Centers** to let the platform create new merchant centers in your GMC account. This option only works when you use the merchant center name or seller ID as your merchant reference in **Merchant Reference Column**. By default, this option is on. Select **On** in **Enable Error Log File** to let Productsup upload feedback files that contain export-related errors as a new data source. You can also download the zipped errors file from the Run log. UUID-1d268d00-6460-64d6-db15-24fe27409261

The ZIP folder may contain error logs spread across different files. You can search for something specific in the logs using a keyword, for example, `product ID`. Some text editors let you search for a keyword across all files in a ZIP file. In **Merchant Center Cleanup**, choose **Yes** to delete products within GMC that do not originate from Productsup. By default, this option is disabled.*This setting should only be used once*. You can enable it if you are migrating from other service providers to Productsup. Once the migration is over, you should disable this setting. Keeping this setting enabled can cause unexpected product deletions. For example, during a full catalog export, the destination matches the items it exports from your site with the products already available in your GMC. If a product in your GMC isn't present in the export, the destination removes it from GMC. In **Reference Validation (regex)**, leave the default value `#.+#` for Productsup to check whether your products follow the data structure required by GMC. Once the platform validates your products, it can send them to Google Merchant Center. From the **Merchant Reference Type** drop-down list, choose one of the following options depending on what the attribute you chose in **Merchant Reference Column** contains: * **Merchant Reference Column contains the Merchant Center Name** * **Merchant Reference Column contains the Merchant Center ID** * **Merchant Reference Column contains the Seller ID** Enter the name of each newly created merchant center account in **New Merchant Account Name**. This setting applies only if you use the seller ID as a merchant reference. Select **On** in **Remove Empty Subaccounts** to remove empty sub-accounts from your Google Merchant Center before running a new export. With this option On, the API deletes empty sub-accounts every time the site runs. In **Log API calls**, select **On** for the platform to log calls to the GMC API. You can find the logs in the Run log. In **Log headers of API calls**, select **On** to add response headers to the logs. In **API call logging end time**, enter a date using the `YYYYMMDD` or `YYYY-MM-DD` format, stating when the platform should stop logging API calls. Do not let this feature run indefinitely, as it generates excessive files and slows exports. Turn on the destination by selecting **On** in **Active**. Select **Save**. Go to **Dataflow** to locate all the attributes mandatory for Google Merchant Center and map them from import to export. Go to **Data View** to optimize your data as needed. See [Rule box category Google Merchant Center](/docs/help-center/add-a-rule-box/find-the-needed-rule-box-category/rule-box-category-google-merchant-center) for more information. The API is more restrictive than the SFTP or URL upload. If you upload an incorrect category or your feed is missing mandatory attributes, the product upload fails. Export your feed to GMC via API [#export-your-feed-to-gmc-via-api] When you export to GMC via API, you can't download your export file from the Files panel in the Overview tab of your export setup. Export your product feed by selecting **Export** or **Run** in the top-right corner of your site's view. Make sure to export unavailable products with the status `out of stock`. Otherwise, they appear available in GMC. Once the run completes, you can see the result in the Run log. To open it, select the **Run log** icon in the top-right corner of your site's view. UUID-c49d07b2-0eaa-f8b5-552c-4619a1132b0a

UUID-c49d07b2-0eaa-f8b5-552c-4619a1132b0a

If the export fails, you can check error messages in the Run log provided that you have turned on the **Enable Error Log File** option as previously seen in [see the relevant section](#step-idm241657788961800) or [see the relevant section](#step-idm243316491590336). Otherwise, correct your feed and try again.You can also go to **Error Log** and open your site's last run to see what went wrong with it. UUID-c477cdef-f5c6-f4f7-582c-51dd086544f1

UUID-c477cdef-f5c6-f4f7-582c-51dd086544f1

After the first upload in GMC, your products could take longer than expected to display in your organization. If you have already exported your feed to GMC via API, the process should take less time. # Add Google Analytics 4 exports import { Callout } from "fumadocs-ui/components/callout"; import { Step, Steps } from "fumadocs-ui/components/steps"; Introduction [#introduction] Google has announced the sunsetting of Universal Analytics by July 2023 and a move to the platform's new version called Google Analytics 4. Productsup has added five (5) Google Analytics 4 export channels that let you send data to your GA4 instances: . *Google Analytics 4 - Cost Data Export* – This export template lets you import cost data, such as campaign costs, into GA4 and get a better overview and analysis of campaign performance and ROI. . *Google Analytics 4 - Item Data Export* – This export template lets you import item data into GA4 and measure user behavior, traffic, conversions, and other metrics at the product level. . *Google Analytics 4 - Offline Data Export* – This export template lets you import offline data from sources that don't have an internet connection into GA4 to enrich the data collected online. . *Google Analytics 4 - User Data Export (client-ID)* – This export template lets you import user data, such as last purchase date or loyalty rating, into GA4 to improve user segmentation and remarketing audiences. Use this export template if you identify users by Client ID assigned to each unique user of your website. . *Google Analytics 4 - User Data Export (user-ID)* – This export template lets you import user data, such as last purchase date or loyalty rating, into GA4 to improve user segmentation and remarketing audiences. Use this export template if you identify users by User ID assigned only to logged-in users. You can still use *Google Analytics Product Export* while using Universal Analytics. But we encourage you to move to the new Google Analytics 4 exports as soon as you move to GA4. All these exports use the flat-file approach, where Productsup generates a CSV file with the needed data to let you upload it to your Google Analytics property manually. See [About Product Data](https://support.google.com/analytics/answer/6066852) for more information on uploading product data to Google Analytics 4. Prerequisites [#prerequisites] To upload the product data from Productsup to GA4, you need to: * Have an active GA4 account. Set up Google Analytics 4 exports [#set-up-google-analytics-4-exports] To set up the necessary GA4 exports: Go to **Exports** from your site's main menu and select **ADD EXPORT**. Search for the needed Google Analytics 4 export, hover over it, and select **Add**. UUID-3cc0bd6b-7fd4-8180-3bea-a6dbdaae0d9a

UUID-3cc0bd6b-7fd4-8180-3bea-a6dbdaae0d9a

Go to **Dataflow** from the site's main menu and choose the added export from the dropdown in the toolbar. Map the attributes from import to export. Use the **Automap connections** drop-down menu in the top ribbon to let the platform automatically connect the attributes. UUID-6fdde14a-a605-ad25-11cb-ae35d3e6ee47

UUID-6fdde14a-a605-ad25-11cb-ae35d3e6ee47

Go to **Exports** and select the name of the needed export. Select **Add Destination**. Select *Productsup Server* from the **Destination** drop-down menu and select **Save**. If you want to send your CSV file to an FTP, SFTP, or FTPS server, select *SFTP/FTP/FTPS Server* as a destination. If you don't have a server account yet, you can create one using the **FTP Accounts** feature in Productsup. See [Export your data to an FTP, SFTP, or FTPS server](/docs/help-center/export-data-feeds/set-up-an-export-destination/add-an-ftp-sftp-or-ftps-destination) for more details. If your data is ready, select **Run** or **Export this export** in the upper right corner of the page. To download the output CSV file, select the link to the file that appears in the *Filename* section at the bottom of the export setup page. UUID-1cc3fcb1-b5a8-f4a4-e6ee-2b4fcc2eafe9

UUID-1cc3fcb1-b5a8-f4a4-e6ee-2b4fcc2eafe9

Import the downloaded file to your GA4 account. # Add Bazaarvoice export import { Callout } from "fumadocs-ui/components/callout"; import { Step, Steps } from "fumadocs-ui/components/steps"; Bazaarvoice is a platform brands can use to integrate user-generated content such as product reviews, ratings, Q\&As, and visual and social content. Our Bazaarvoice integration enables you to syndicate your product catalog to Bazaarvoice to map the UGC to the correct products. The export generates an XML file and sends it to Bazaarvoice's SFTP. If your product catalog is above 750,000 products, Bazaarvoice sometimes recommends splitting it into multiple XML files. You should confirm with your Bazaarvoice contact whether you should do this in your case. Productsup provides the **Split feed** feature in the Bazaarvoice destination setup page, which lets you split the feed into multiple files. Prerequisites [#prerequisites] To add the Bazaarvoice export, you need to: . Create a Bazaarvoice account, if you don't have one. . Get the SFTP credentials for Bazaarvoice. Set up Bazaarvoice export [#set-up-bazaarvoice-export] Go to **Exports** from your site's main menu and select **ADD EXPORT**. Search for *Bazaarvoice*, hover over it, and select **Add**. UUID-290da605-bde6-1109-dd83-fd3e7b288cd6

UUID-290da605-bde6-1109-dd83-fd3e7b288cd6

UUID-9281947d-c6cf-5007-53d3-db0023db5d1f

Choose **Classification Mapping** and select **Continue**. UUID-97ed9356-5ba0-634a-3edb-e34711f23e0b

In **Name**, give your list a custom name to help you identify it among others. You can later edit it. In **Classification**, select **Bol Products Delta API (NL, BE)**. UUID-77315e81-6e68-c32e-81a9-44c0f27a3c69

UUID-77315e81-6e68-c32e-81a9-44c0f27a3c69

In **Stage**, choose the **Import** stage to replace values with the classification categories. In **Attribute**, enter and select attributes from the list of pre-defined values from your selected import attribute's column. The platform later populates the list with the values of this attribute to let you choose and map the needed category values. Optionally, toggle on the **Share list** button and choose one of the following: 1. **Account level** shares this list with all sites across all projects under this organization. 2. **Project level** shares this list with all sites under this project. If you share the list at the organization or project level, the platform updates the list during an import from the original site where you created the list. Select **Add**. Map your categories to the Bol categories. Go through all the values of your category attribute in the column on the left and select the corresponding Bol categories in the **Replace term** column. You must create and set up a new Classification Mapping list every time you modify the chosen category attribute in your data source and import its new values into your site. Otherwise, the already existing list can't upload your new values, and you can't map them to the corresponding Bol categories. Once you create a new Classification Mapping list, you need to choose it in the related rule box. After setting up the export as explained in the next section, you can map the attributes and apply the Classification Mapping list with the rule boxes. Send your products to Bol [#send-your-products-to-bol] In the site dedicated to sending your products to Bol, add and set up the export *Bol Products Delta API (NL, BE)*: Go to **Exports** from your site's main menu and select **ADD EXPORT**. Search for *Bol Products Delta API (NL, BE)*, hover over it, and select **Add**. UUID-3bdecd3d-2f44-8d3f-a7da-9fe665b49ee8

UUID-3bdecd3d-2f44-8d3f-a7da-9fe665b49ee8

On the **Exports** page, select the name of the added export to set it up. Select **Add Destination**, choose *Bol.com Product Delta Export (NL/BE)* from the drop-down list, give it a name as desired, and select **Save**. In **Authentication selection**, select an existing one or select the **Add New Authentication** button. The platform redirects you to the Bol retailer account. UUID-e99d988b-bdc6-7cf7-bdb9-df4773d44e98

UUID-e99d988b-bdc6-7cf7-bdb9-df4773d44e98

Leave the **Feedback Import** button *On* to let Productsup receive a feedback file from the Bol API in case of export errors. This helps troubleshoot the setup. Leave the **Category Specific Attributes** button *On* to map category-specific attributes in Dataflow. Toggle the **Active** button to *On* to activate the destination. Select **Save**. Go to **Dataflow** and select *Bol Products Delta API (NL, BE)* from the drop-down menu on the left. Set up the main channel: Map the `category` attribute in the import level to `__gpc_code` and `gpc_code_name` in the intermediate stage. UUID-1f8e5a2e-59c5-9fd9-6524-05b02efec0c6

UUID-1f8e5a2e-59c5-9fd9-6524-05b02efec0c6

For both **\_\_gpc\_code** and **gpc\_code\_name**, on the intermediate level, add the **Classification Mapping** rule box and choose the list created in [Set up a Classification Mapping list for Bol](#section-idm353416186897364). UUID-0068d6cd-a9c4-2664-8837-aba62df01503

UUID-0068d6cd-a9c4-2664-8837-aba62df01503

For **\_\_gpc\_code**, on the intermediate stage, add the **Split String** rule box below the *Classification Mapping* rule box and enter the following values: * **Splitter**: a single space without the quotation marks * **From**: `0` * **Items**: `1` UUID-d37eebc0-1327-f496-c5bd-6d812bb97035

UUID-d37eebc0-1327-f496-c5bd-6d812bb97035

For **gpc\_code\_name**, on the intermediate stage, add the **Split String** rule box below the *Classification Mapping* rule box and enter the following values: * **Splitter**: a single space without quotation marks * **From**: `1` * **Items**: `1` UUID-cbab6834-3e41-c7b5-3260-7bda51df1991

UUID-cbab6834-3e41-c7b5-3260-7bda51df1991

Ensure you saved all changes. Map these and other necessary attributes from the import to the export stage. To let the site display your category-specific attributes in Dataflow, select **Run** or **Import** in the top-right corner of your view. This run will fail because you haven't yet mapped all the mandatory attributes, so no data export occurs at this stage. The aim of the run is to import the needed categories and attributes into Dataflow. Once the site run finishes, the **Classifications** drop-down menu appears in the upper ribbon in Dataflow. Select each category in this drop-down menu to let Dataflow display the relevant category-specific attributes in the export stage. Map all the needed attributes from import to export. UUID-851628c1-299a-3792-c36e-44bb28a60f66

If you can't see the **Classifications** drop-down menu when the site run is complete, refresh your page. If some attributes are missing on the intermediate stage, add them manually. Go to **Data View** from the same site's main menu and choose *Bol Products Delta API (NL, BE)* from the drop-down menu on the top left-hand side. For each attribute, select **Analyze** to ensure your data is compliant with the Bol expectations. Alternatively, select the **Overview** drop-down and choose **Readiness**. Once your data is ready, select **Run** in the top-right corner of your view to send your products to Bol. Import your offers to Productsup [#import-your-offers-to-productsup] After you have exported your products, you can import your offers to Productsup as an additional data source and map them by EAN (European Article Number) to the products. This allows Productsup to identify which EANs the platform has already placed as offers on Bol and which it should send as new offers. To import your offers: Go to **Data Sources** from the main menu of the site dedicated to the Bol offers. Select **ADD DATA SOURCE**. Add your products as the main data source. For example, you can use the *Google Sheets* data source. It should be the same product feed that you used in the site dedicated to product creation. Go back to the **Data Sources** page, search for *Bol Offers* in the **Search** bar, and select **Add**. Give your data source a custom name as desired, then select **Continue**. UUID-642773f8-ae74-b865-aa3f-6e852fe6b4aa

UUID-642773f8-ae74-b865-aa3f-6e852fe6b4aa

Set up your data source: In **Authentication selection**, select an existing one or select the **Add New Authentication** button. The platform redirects you to the Bol retailer account. Optionally, add a description. Select **Save**. After the platform redirects you to **Data Sources**, select the cogwheel icon (**⚙**) next to your newly added data source. Scroll down to the **Content Mode** panel and select **Additional Data Source**. In the **Additional Data Source Types** section, leave **Additional Data Source Values Always (Default)** selected by default. This option lets you replace the main data source values with the additional data source values, even if the additional data source values are empty. UUID-a2e43bee-de53-8052-d819-8e7c235b87d0

UUID-a2e43bee-de53-8052-d819-8e7c235b87d0

In **ID Column In This Feed**, enter the column's name within your additional data source that contains the products EANs. This field is case-sensitive. In the **ID Column From Your Main Feed** drop-down menu, select a column in your main data source that Productsup should map to the products EANs. * The platform updates the offers for the products with the same EANs in the main and additional data sources, instead of creating new offers. * The platform creates new offers for the products with EANs that don't match between the main and additional data sources. * The platform deletes the offers related to EANs that aren’t in the feed anymore. Select **Save**. Select **Import** to import your offers to Productsup. If your **fulfilment.method** attribute contains FBR, you must provide the number of delivery days in the **deliveryCode** attribute. If your **fulfilment.method** attribute contains FBB, you must set `null` in the **deliveryCode** attribute. See [Update an offer](https://api.bol.com/retailer/public/Retailer-API/v9/functional/retailer-api/offers.html#_update_an_offer) for more information about specific attribute settings. Send your offers to Bol [#send-your-offers-to-bol] After you have imported the offers, you can add and set up *Bol Offers Management Delta* in the site dedicated to offers: Go to **Exports** from your site's main menu and select **ADD EXPORT**. Search for *Bol Offers Management Delta*, hover over it, and select **Add**. UUID-e01cbc53-d79c-0bdd-f127-a38725b0e0ab

UUID-e01cbc53-d79c-0bdd-f127-a38725b0e0ab

On the **Exports** page, select the name of the added export to set it up. Select **Add Destination**, choose *Bol Offers Management Delta* from the drop-down list, give it a name as desired, and then select **Save**. In **Authentication selection**, select an existing one or select the **Add New Authentication** button. The platform redirects you to the Bol retailer account. Leave the **Feedback Import** button *On* to let Productsup receive a feedback file from the Bol API in case of export errors. This helps troubleshoot the setup. Toggle the **Active** button to *On* to activate the destination. Select **Save**. Go to **Dataflow** and map the attributes from import to export. The **economic\_operator\_id** attribute is mandatory now for creating a valid offer. To get the ID: Add the economic operator manually in the Bol. seller’s account. Import the ID via API using Postman or similar tool. See [Economic Operator API - V1 (1.0.4)](https://api.bol.com/registry/redoc/economic-operators/economic-operators-v1.html) for more information. Add the ID of the created operator to the **economic\_operator\_id** attribute. Ensure you map **economic\_operator\_id** attribute from import to export in Dataflow. Contact your Customer Success Manager or [support@productsup.com](mailto:support@productsup.com) if you need help with adding your economic operator ID. Once your data is ready, select **Run** in the top-right corner of your view to send your offers to Bol. Running the offers export in less than 15 minutes after the previous run results in retrieving the same export file. You need to wait at least 15 minutes after the previous export run to send the new, updated, or deleted offers. Import orders from Bol [#import-orders-from-bol] To let Productsup import your orders from Bol, do the following in the site dedicated to the Bol orders: Go to **Data Sources** from your site's main menu and select **ADD DATA SOURCE**. Search for *Bol Orders*, select **Add**, give it a name as desired, and choose **Continue**. UUID-cc43d40c-15c7-76bf-ebb9-e3e98e07304c

UUID-cc43d40c-15c7-76bf-ebb9-e3e98e07304c

Set up your data source: In **Fulfilment method**, select the fulfillment option that Productsup should import: * **FBR** imports only orders fulfilled by the retailer. * **FBB** imports only orders fulfilled by Bol. * **ALL** imports both FBR and FBB. In **Status**, select the order status that Productsup should import: * **OPEN** imports only open orders excluding shipped and canceled orders. * **SHIPPED** imports only shipped orders. * **ALL** imports both open and shipped orders. Set either **Change interval minute** or **Latest change date** that are mutually exclusive: * In **Change interval minute**, you can set how many minutes passed since the latest change on an ordered product. You can enter the values from `1` to `60`. * In **Latest change date**, you can select the date when the latest change happened on an ordered product. You can select the date in the period of up to three (3) months. Bol recommends using *Change interval minute*. See [Bol's Best practices - order process](https://api.bol.com/retailer/public/Retailer-API/v9/functional/retailer-api/orders-shipments.html#_filtering_order_items_by_fulfilment_method). In **Authentication selection**, select an existing one or select the **Add New Authentication** button. The platform redirects you to the Bol retailer account. Optionally, add a description. Select **Save**. Select **Import** to import your orders. During the time between retrieving an open order and shipping it, a customer can still request cancellation. If there is a long time between retrieving an open order and shipping, we recommend retrieving all the open orders again before shipping to check for possible cancellation requests from the customers. Send order cancellation updates to Bol [#send-order-cancellation-updates-to-bol] To change the status of your orders on Bol and inform your customers about order status changes, after importing the orders from Bol to Productsup, you can add and set up *Bol Order Cancellation Delta* in the site dedicated to orders: Go to **Exports** from your site's main menu and select **ADD EXPORT**. Search for *Bol Order Cancellation Delta*, hover over it, and select **Add**. UUID-4db7c524-404a-c1bf-4676-c5ca898dae1d

UUID-4db7c524-404a-c1bf-4676-c5ca898dae1d

On the Exports page, select the name of the added export to set it up. Select **Add Destination**, choose *Bol Order Cancellation Delta* from the drop-down list, give it a name as desired, and select **Save**. In **Authentication selection**, select an existing one or select the **Add New Authentication** button. The platform redirects you to the Bol retailer account. Leave the **Feedback Import** button *On* to let Productsup receive a feedback file from the Bol API in case of export errors. This helps troubleshoot the setup. Toggle the **Active** button to *On* to activate the destination. Select **Save**. Once your data is ready, select **Run** in the top-right corner of your view to send your data about cancellations to Bol. If a customer only cancels a single item within an order, you only need to cancel this one item and ship the other ordered items. To confirm the cancellation of a single ordered item within an order, assign the value *REQUESTED\_BY\_CUSTOMER* to the **reasonCode** attribute. Don't use the reason *REQUESTED\_BY\_CUSTOMER* without a customer cancellation. For example, when the item is out of stock, as it negatively impacts your performance scores. Send shipment notification updates to Bol [#send-shipment-notification-updates-to-bol] To change the status of your shipment at Bol and inform your customers about it, you can add and set up *Bol Order Shipment Delta* in the site dedicated to orders after importing the orders from Bol to Productsup. Bol supports shipment in three (3) different ways: 1. *LVB/FBB* means that Bol handles the order from start to end. Therefore, the shipment export doesn't include FBB orders. 2. *FBR with own shipping labels* means that you process these orders by yourself and must provide the information about them with tracking numbers and transporter codes to Bol. See [Transporters](https://api.bol.com/retailer/public/Retailer-API/v9/functional/retailer-api/orders-shipments.html#_transporters). 3. *FBR with shipping labels purchased via Bol* isn't supported by Productsup. If you haven't handled the order within three (3) days of the expected delivery date, Bol automatically cancels such FBR orders and this negatively impacts your performance score. An order can consist of one or more items. All mutations in the API depend on an item. This means you ship or cancel every item separately using its **orderItemId**. Even if you ship them in one box, the API needs separate confirmations or cancellations per item. The order remains open until you shipped all items. It stays open also for the already shipped items from the same order. Correspondingly, there are two ways of setting up the shipment or cancellation export: . [Set up shipping or cancellation per orderItem](#section-idm234553733872264). . [Set up shipping or cancellation of the entire order in one package per orderId](#section-idm234553762431943) Set up shipping or cancellation per orderItem [#set-up-shipping-or-cancellation-per-orderitem] Bol prefers this approach. This setup gives you full control over each item in an order. For example, it lets you ship one (1) order in multiple parcels if needed or to confirm the customer's cancellation of a specific item from the order. You must import `trackingNumber` and `careerCode` per **orderItemId** to Productsup. Go to **Data Sources** from your site's main menu and select **ADD DATA SOURCE**. Add your order management system as the main data source and set it up. Go to **Exports** from your site's main menu and select **ADD EXPORT**. Search for *Bol Order Shipment Delta*, hover over it, and select **Add**. UUID-8e528643-6833-01cd-25c1-6db17306e4b0

UUID-8e528643-6833-01cd-25c1-6db17306e4b0

You may also choose to add the *Bol Order Cancellation Delta* export instead. On the Exports page, select the name of the added export to set it up. Select **Add Destination**, choose *Bol Order Shipment Delta* from the drop-down menu, give it a name as desired, and select **Save**. In **Authentication selection**, select an existing authentication or select the **Add New Authentication** button. The platform redirects you to the Bol retailer account. Leave the **Feedback Import** button *On* to let Productsup receive a feedback file from the Bol API in case of export errors. This helps you troubleshoot the setup. Toggle the **Active** button to *On* to activate the destination. Select **Save**. Go to **Dataflow** and map the attributes from import to export. Once your data is ready, select **Run** in the top-right corner of your view to send your shipment notifications to Bol. # Add the Amazon Offer Creation export import { Callout } from "fumadocs-ui/components/callout"; import { Step, Steps } from "fumadocs-ui/components/steps"; The Amazon Offer Creation export lets you list a new offer (price, condition, and availability) on an Amazon ASIN that already exists in Amazon's catalog. This is different from the Amazon Product Export: it does not create a new product or touch the ASIN's content data, and it does not require category-specific attribute (CSA) mapping. Use it when you want to co-list against an existing catalog entry rather than create a listing from scratch. Once an offer exists, use the [Amazon Inventory and Price Update SP-API export](/docs/help-center/export-data-feeds/add-export/add-amazon-inventory-and-price-update-sp-api-export) to keep its price and stock current. The Offer Creation export only creates new offers — it does not update existing ones. Prerequisites [#prerequisites] Before setting up the Amazon Offer Creation export, confirm the following: * You have an active Amazon Seller Central account. This export is not available for Vendor Central accounts. * You know the ASIN you want to attach each offer to. If you only have a barcode (UPC, EAN, GTIN, ISBN, or JAN), see [Find Amazon ASINs by barcode](/docs/help-center/import-data-feeds/import-data-from-third-party-external-systems/find-amazon-asins-by-barcode) first. * The marketplace you want to export to is available in the export list. See [Add the export](#add-the-export). * Your Amazon account is in good health: valid payment method, correct VAT or tax details, and no outstanding compliance issues. Amazon restricts who can list an offer against certain ASINs — for example, brand-registered or gated products. If Amazon rejects your offer for this reason, you or your client need approval from Amazon or the brand owner before the offer can go live. This is an Amazon policy, not a Productsup limitation. Add the export [#add-the-export] Go to **Exports** from your site's main menu and select **ADD EXPORT**. Search for the marketplace you want to export to. Exports follow the naming format **Amazon Seller Central – Offer Creation (XX)**, where **XX** is the country code of your target marketplace, for example *US*, *DE*, or *FR*. If the marketplace you need is not in the list, that region is not yet supported. Contact your Customer Success Manager or [support@productsup.com](mailto:support@productsup.com) to request it. Hover over the export and select **Add**. Configure the destination [#configure-the-destination] On the **Exports** page, select the name of the export you added. Select **Add Destination**, choose *Amazon Seller Offer Creation Delta Export* from the dropdown, give it a name, and select **Save**. In **Authentication**, select an existing authentication or select **Add New Authentication** to connect your Amazon account via OAuth. Selecting **Add New Authentication** redirects you to Amazon to complete the authorization. Once authorized, Amazon redirects you back to Productsup automatically. In **Marketplace ID**, select the country you are exporting to. This must match the export you selected in [Add the export](#add-the-export). In **Seller ID**, enter your Amazon Seller ID. Leave this blank to use the Seller ID of the account you authenticated with in step 3. Switch **Active** to *On* and select **Save**. Map your data [#map-your-data] Unlike the full Amazon Product Export, this export does not use category-specific attribute templates. Amazon resolves the product category for you, based on the ASIN, so you only map the offer fields below. | Field | Required | Notes | | :------------------------------------------------- | :------- | :------------------------------------------------- | | SKU | Yes | Your own identifier for this offer | | ASIN | Yes | The existing Amazon ASIN you're co-listing against | | Condition | Yes | For example *new\_new* or *used\_good* | | Price | Yes | Your offer price, with currency | | Fulfillment channel | Yes | Whether you or Amazon (FBA) fulfill this offer | | Quantity | Yes | Available stock for this offer | | Handling time, sale price, and other offer details | No | Optional fields available in Dataflow | Go to **Dataflow** from your site's main menu and select your Amazon Offer Creation export in the dropdown on the left. Map your attributes to the fields listed above in the intermediate stage. Select **Run** in the top-right corner of your view to submit your first offers. Monitor results after submission [#monitor-results-after-submission] An unknown, missing, or invalid ASIN is skipped rather than escalated to full product creation. Check your export's feedback to find and fix these rows. A rejection specific to one offer, such as an invalid attribute value, is skipped so the rest of your export continues. Review the feedback for the affected SKU, correct the issue, and the offer is resubmitted on the next run. Submission is asynchronous — a successfully submitted offer may take a few minutes to appear against the ASIN in Seller Central. To check on a specific offer immediately, set up an Amazon Product Import datasource using the **Listings API** source. Common issues [#common-issues] | Issue | Likely cause | What to do | | :--------------------------------------------------- | :------------------------------------------------------------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Offer skipped with feedback | ASIN is missing, invalid, or has no product type in this marketplace | Confirm the ASIN exists in this marketplace, or find it with [Find Amazon ASINs by barcode](/docs/help-center/import-data-feeds/import-data-from-third-party-external-systems/find-amazon-asins-by-barcode) | | Offer rejected due to brand or category restrictions | The ASIN is brand-gated or otherwise restricted | Get approval from Amazon or the brand owner before listing against this ASIN | | Offer accepted but not visible on Amazon | Amazon's asynchronous validation is still processing | Wait a few minutes, then check via the Amazon Product Import (Listings API) datasource or Seller Central | | Authentication fails | Amazon account health issue | Check your Amazon account for expired payment details, missing VAT, or compliance flags | | Marketplace missing from the export list | Not yet supported | Contact your Customer Success Manager or [support@productsup.com](mailto:support@productsup.com) to request it | # Build your exports from scratch import { Callout } from "fumadocs-ui/components/callout"; import { Step, Steps } from "fumadocs-ui/components/steps"; Build exports from scratch using a blank export if existing export templates don't suit your needs. Blank export is a blank canvas that you can customize as you need. There are four types of blank export templates in Productsup: . *Blank Export (empty)*. This blank export template lets you manually create a custom set of attributes in the export stage of Dataflow to meet the requirements of the desired channel. See [Set up Blank Export (empty) and Blank Export (with ID)](#section-idm455072265296483337401677465) for more information.Use *Blank Export (empty)* in the following cases: * To create custom exports, test your exports, or use them in reports. * To create an item setup sheet. See [Use an item setup sheet](/docs/help-center/export-data-feeds/special-export-setups/use-an-item-setup-sheet#section-idm463502822158883297643722671) for more information. * To download a feed with more than 10,000 items. See [First steps with Data View](/docs/help-center/map-and-optimize-your-data/data-view/first-steps-with-data-view#section-idm232217635442184) for more information. . *Blank Export (with ID)*. This blank export template is similar to *Blank Export (empty)* but has the **id** attribute pre-defined as a mandatory attribute in the export stage in Dataflow. See [Set up Blank Export (empty) and Blank Export (with ID)](#section-idm455072265296483337401677465) for more information. . *Delta Blank Export*. This blank export template lets you work with delta updates. The most popular use case for Delta Blank Export involves exporting only new, changed, and removed items to your channels without exporting items with unchanged data. Delta updates reduce transport time and data volume for big feeds requiring few updates. See [Set up Delta Blank Export](#section-idm4557758669414433380650892281) for more information. . *Export2Datasource Blank*. This blank export template lets you compile data from different sites within one organization into a single bucket and use this bucket as a data source in another data-accumulating site. See [Set up Export2Datasource Blank](#section-idm4663886527628833382440260539) for more information. There are no analyzer tests for blank exports. Add a blank export [#add-a-blank-export] To add a blank export to your site, take the following steps: > > In Exports, you can see the added export. See the next sections for further setup steps based on the chosen blank export template. > Go to **Exports** from your site's main menu. Select **Add export**. Select the necessary blank export in the gray banner under the search field. UUID-66c1a6b9-78f2-b3fb-d559-aee7bf9db90a

Set up Blank Export (empty) and Blank Export (with ID) [#set-up-blank-export-empty-and-blank-export-with-id] *Blank Export (empty)* and *Blank Export (with ID)* let you create custom exports if none of the ready-made export templates fit your needs. These export templates are blank canvases where you can manually add and map the desired attributes in Dataflow. The process of setting up the exports *Blank Export (empty)* and *Blank Export (with ID)* is similar: Take the steps from [Add a blank export](#section-idm353337036706384) to add *Blank Export (empty)* or *Blank Export (with ID)*. Go to **Dataflow** from the site's main menu and select your blank export from the dropdown on the left of the top toolbar. Map the needed attributes from intermediate to export by dragging a connection from an attribute in the intermediate stage to **Drop or Click to add new field** in the export stage. UUID-63ea3aaf-7279-067b-8416-31832c27e29f

UUID-63ea3aaf-7279-067b-8416-31832c27e29f

For *Blank Export (with ID)*, the **id** attribute is the only mandatory attribute. You must connect it with a corresponding attribute in the intermediate stage. Go to **Exports**, find your blank export in the list of exports, and toggle its status in the *Status* column to **Active**. Select the name of your blank export in the *Export name* column. On the export setup page, select **Add Destination**. Select the needed destination option from the **Destination** dropdown, and choose **Save**. See [Find the most suitable export destination](/docs/help-center/best-practices/find-the-most-suitable-export-destination) to choose a destination. Set up your destination, and toggle **Active** to *On* to activate it. Select **Save** when done. Select **Export this export** in the top-right corner of the page to send your data to the destination. Alternatively, the platform exports the data during the next scheduled run. Set up Delta Blank Export [#set-up-delta-blank-export] When you work with extensive data feeds, data processing in the platform may take a long time. With the help of *Delta Blank Export*, which uses delta updates, you can send only updated data to the needed channel. Delta updates are a way of storing or transmitting data in the form of differences, called deltas, rather than complete data sets. With delta updates, the platform doesn't export unchanged items, which allows it to reduce transport time and data volume for large feeds. The platform uses a unique item identifier, such as an ID, GTIN, or variant ID, to identify each item and compare its current data to its data from the previous run. The platform generates up to four (4) types of files for delta updates, depending on the data changes: * **New**: items new to the feed. * **Changed**: items that have been in the feed before, but the data has changed. * **Deleted**: items that aren't in the feed anymore because of skip rules or deletions. * **Unchanged**: items that have been in the feed before and haven't changed. Use *Delta Blank Export* in the following cases: * If you don't expect your entire data feed to change frequently. * If your target channel requires you to export your data feed as delta updates due to technical requirements on their side. Apart from *Delta Blank Export*, several partner-specific export templates have similar delta update features. For example, *Salesforce Commerce Cloud B2C: Inventory (Delta)* or *Facebook Dynamic Ads (Delta Upload)*. If you need support exploring your optimal solution, reach out to your Customer Success Manager or contact [support@productsup.com](mailto:support@productsup.com). To set up your *Delta Blank Export*, take the following steps: Take the steps from [Add a blank export](#section-idm353337036706384) to add *Delta Blank Export*. Go to **Dataflow** from the site's main menu and select your blank export from the dropdown on the left of the top toolbar. Map the needed attributes from intermediate to export by dragging a connection from an attribute in the intermediate stage to **Drop or Click to add new field** in the export stage. UUID-a91ef686-345e-5ee7-a62a-6adf6131ef72

UUID-a91ef686-345e-5ee7-a62a-6adf6131ef72

The export stage already has the **id** attribute. You must connect it with a corresponding attribute in the intermediate stage. Go to **Exports**, find your blank export in the list of exports, and toggle its status in the *Status* column to **Active**. Select the name of your blank export in the *Export name* column. On the export setup page, select **Add Destination**. Select the needed destination option from the **Destination** dropdown, and choose **Save**. See [Find the most suitable export destination](/docs/help-center/best-practices/find-the-most-suitable-export-destination) to choose a destination. Set up your destination, and toggle **Active** to *On* to activate it. Select **Save** when done. 1. Some export destinations, for example, *Productsup Server*, may automatically create a file in the *Files* section on the export setup page. You don't need this file for *Delta Blank Export*. If you see an automatically created file, select **Setup** next to the file, then select **Delete**, and then confirm the action. On the export setup page, select **Update Files** in the *Delta Files* section. A pop-up displays four files for delta updates: unchanged, new, modified, and deleted. Modify the file names as needed. UUID-62d59f9f-7ba1-a46a-01e8-c74eb126f046

UUID-62d59f9f-7ba1-a46a-01e8-c74eb126f046

If the pre-configured extension of the files doesn't match requirements, contact [support@productsup.com](mailto:support@productsup.com). In the *Delta Files* pop-up, toggle **Add Site ID to Delta Filenames** to *On* if your destination receives files with delta updates from multiple sites or systems. Enabling this option appends the site ID to the file names, allowing you to distinguish between files from different sites. Select **Save** to close the *Delta Files* pop-up. Select **Export this export** in the top-right corner of the page to send your data to the destination. Alternatively, the platform exports the data during the next scheduled run. After each export run, you can download any file with delta updates in the *Filename* section at the bottom of the export setup page. Generate empty delta files [#generate-empty-delta-files] You may want the platform to generate files with delta updates for deleted or new items, even if such files are empty. It is necessary if your destination or target channel always expects to have four files (new, changed, deleted, and unchanged) with every export run. Otherwise, your destination or channel might ingest files from previous runs, which can cause ID conflict issues and item duplicates. To enable the generation of empty files, follow the steps: Your target channel or destination settings must also allow empty files. They may discard these empty files if they interpret them as obsolete or unchanged. Go to **Exports** and select your *Delta Blank Export*. Go to the *Settings* tab. Check the box **Allow empty files (0 products)**, and select **Save** at the bottom of the page. UUID-237b5045-0aa8-7648-0519-d81646f52075

UUID-237b5045-0aa8-7648-0519-d81646f52075

Export data in JSON and avoid creating empty delta files in Delta Blank Export [#export-data-in-json-and-avoid-creating-empty-delta-files-in-delta-blank-export] If you use the `\Export\Json` plugin to export data in JSON files, the platform ignores whether you have checked the box **Allow empty files (0 products)** and always creates empty delta files for each export run. If you want to both export your data in the JSON format and avoid creating empty delta files, you should take these steps: On the export setup page, go to the *Settings* tab, remove `\Export\Json` in **Export-Plugin**, and select **Save**. Open the tab *Labels, Tags & Sorting*, find the section *Export Tags*, and enter the following under **Add new tag**: 1. In **Key**, enter `custom_csv_writer_class`. 2. In **Value**, enter `ProductsUp_Csv_File_Writer_Json`. Select **Add tag** to save it. UUID-c1fdf18f-5be9-498d-e432-6a003e787b6c

Check your Delta Blank Export history [#check-your-delta-blank-export-history] Go to **Exports** from your site's main menu. Go to the *Export history* tab. Activate the option **Show delta file changes** to view the export history with a breakdown of all types of delta updates. Set up Export2Datasource Blank [#set-up-export2datasource-blank] *Export2Datasource Blank* lets you compile data from different sites within an organization into one bucket and use this bucket as a data source in another data-accumulating site. UUID-f3f9daf8-f131-4423-4e7c-bfba22f53a27

UUID-f3f9daf8-f131-4423-4e7c-bfba22f53a27

For example, you run a marketplace and, in the Productsup platform, you have hundreds of sites exporting your separate product feeds to the designated Google Merchant Center accounts. In this case, you may want a site that combines these different feeds into one main feed and exports it to price comparison channels, Facebook, or other systems. If you did it manually, you would have to create exports in each site, send data for each export to the Productsup Server, and then add each separate Productsup Server link as a data source in one data-accumulating site. Instead, you can use the *Export2Datasource Blank* export and export all your separate feeds into a bucket. Later, you can use this bucket as a single data source. Contact [support@productsup.com](mailto:support@productsup.com) if you want to use this feature. Since it's an advanced tool, you may need assistance with the initial setup. Prerequisites [#prerequisites] To be able to export to and import from buckets, your Productsup organization should meet the following requirements: * All sites from which you want to send data to the same bucket should have the export *Export2Datasource Blank* with the same bucket name. You can create a copy of the export if you plan to use it multiple times without starting from scratch. See [Add export](/docs/help-center/export-data-feeds/add-export#section-idm353339436030962) for more information. * If you have several buckets in your organization, each should have a unique name. Otherwise, the platform can't distinguish which bucket it should send data to. * All sites that send data to the same bucket should have feeds with the same structure. Export2Datasource Blank setup steps [#export2datasource-blank-setup-steps] Take the steps from [Add a blank export](#section-idm353337036706384) to add *Export2Datasource Blank*. Go to **Dataflow** from the site's main menu and select your blank export from the dropdown on the left of the top toolbar. Map the needed attributes from intermediate to export by dragging a connection from an attribute in the intermediate stage to **Drop or Click to add new field** in the export stage. UUID-3cc20fc3-7694-9b61-dd44-eeb6d727d807

UUID-3cc20fc3-7694-9b61-dd44-eeb6d727d807

Go to **Exports**, find your blank export in the list of exports, and toggle its status in the *Status* column to **Active**. Select the name of your blank export in the *Export name* column. On the export setup page, select **Add Destination**. Select *Export to Data Source* from the **Destination** dropdown and select **Save**. UUID-e6881d3d-5869-de42-3911-a286dcc2ec52

UUID-e6881d3d-5869-de42-3911-a286dcc2ec52

On the destination setup page, add a unique bucket name in **Bucket**. By default, the destination doesn't export skipped items. To include skipped items in the export, toggle **Allow skipped rows** to *On*. By default, the destination includes platform-generated attributes, for example, created by a data service, into the export and sends them to the bucket. This allows you to use these attributes in other sites without needing to apply the same data services or other features again. If you don't want to export these attributes to the bucket, toggle **Remove Passthru Columns** to *On*. By default, the destination sends empty attributes to the bucket. To avoid sending empty attributes to the bucket, toggle **Remove Empty Columns** to *On*. By default, the destination sends the export output file to the bucket regardless of whether it contains any data. To avoid exporting files without data, toggle **Prevent Empty Upload** to *On*. Toggle **Active** to *On* to activate the destination. Select **Save**. UUID-c21f2810-7d87-7f46-616c-fc4194ecd3ee

UUID-c21f2810-7d87-7f46-616c-fc4194ecd3ee

Select **Export this export** in the top-right corner of the page to send your data to the destination. Alternatively, the platform exports the data during the next scheduled run. *Export to Data Source* is a destination and not a file format. As a result, you can't edit file settings, such as file name, item limit, sorting actions, or item count. Import data from a bucket via the data source Export to Data Source [#import-data-from-a-bucket-via-the-data-source-export-to-data-source] To import data from a bucket into a data-accumulating site, take the following steps to set up the data source *Export to Data Source*: # Add Kaufland exports and import order data from Kaufland import { Callout } from "fumadocs-ui/components/callout"; import { Step, Steps } from "fumadocs-ui/components/steps"; Introduction [#introduction]