...
Algorithm determines child's age, gender, clothing and shoe size, predisposition to certain cosmetic and hygiene products, as well as particular food products preferences.
| Panel | ||
|---|---|---|
| ||
|
Add Additional Parameters to Your XML-file
For the algorithm to work properly every product in your XML Product Feed should have additional properties:
- gender this product is targeted at
- age bracket, if, for instance, this product is intended for babies of 2 andlessyears old;
- additional category-specific data, written in these separate sections:
- apparel (<fashion> section)
- cosmetics (<cosmetic> section)
- fast-moving consumer goods (<fmcg> section)
This data should be included into the XML-file in the form of specific product parameters and send to PersonaClick.
Section <child>
A distinctive adult product feature is presence of the <child> subsection inside the <offer> section.
Add the following parameters to each product in your XML-File.
Gender
Mandatory parameter <gender>. Placed inside the <offer> section, within the <child> subsection.
Consider the following table of possible values:
...
Consider the following example of use:
...
| language | xml |
|---|---|
| title | XML example |
...
...
| Info |
|---|
No need to specify the gender this particular product is targeted at, if you do not have this data. In this case, this particular product will simply be marked as 'unisex' and will have a lower displaying priority in relation to other products with the specified gender parameter. |
Product Type
Optional parameter <type>. Placed inside the <offer> section, within the <child> subsection.
Consider the following table of possible values:
...
...
...
...
...
...
Consider the following example of use:
...
...
...
...
Optional parameter <age>. Placed inside the <offer> section, within the <child> subsection.
Bracket age (for less than 2 years old babies) supported through subparameters <min> (minimum age) and <max> (maximum age).
Consider the following table of possible values:
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
Example of use of interconnected <child> and <fashion> sections
In case this particular baby and children product is a piece of clothing, hence, all the additional product data should be passed in the <fashion> section:
| Code Block | ||
|---|---|---|
| ||
...
<offer ...>
...
<child>
<gender>f</gender>
<age>
<min>1.5</min>
<max>2</max>
</age>
</child>
<fashion>
<type>jacket</type>
<sizes>
<size>h80-82</size>
<size>h83-85</size>
<size>h86-88</size>
</sizes>
</fashion>
</offer>
... |
Example of use of interconnected <child> and <cosmetic> sections
In case this particular product belongs to both cosmetic and hygiene products categories, hence, all the additional data should be passed in the <cosmetic> section:
| Code Block | ||
|---|---|---|
| ||
...
<offer ...>
...
<child>
<gender>f</gender>
<age>
<min>1.5</min>
<max>2</max>
</age>
</child>
<cosmetic>
<hypoallergenic>1</hypoallergenic>
<skin>
<part>face</part>
<part>body</part>
<type>normal</type>
<type>oily</type>
<condition>sensitive</condition>
<condition>problem</condition>
</skin>
<volumes>
<volume>
<value>200</value>
<price>1000</price>
</volume>
<volume>
<value>400</value>
<price>2000</price>
</volume>
</volumes>
</cosmetic>
</offer>
... |
Example of use of interconnected <child> and <fmcg> sections
In case this particular baby and children product belongs to the FMCG (fast-moving consumer goods) category, hence, all the additional data should be passed in the <fmcg> section.
...
| language | xml |
|---|
...