Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 3 Next »

Baby & Children Products algorithm is developed to automatically identify particular characteristics of a new potential customer interested in baby and children products with particular parameters, and specify product recommendations based on this data.

Algorithm determines child's age, gender, clothing and shoe size, predisposition to certain cosmetic and hygiene products, as well as particular food products preferences.

Following steps are covered

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:

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:

Mandatory?ValueDescription
YesmMale
YesfFemale


Consider the following example of use:

XML example
...
<offer ...>
	...
	<child>
		<gender>f</gender>
	</child>
</offer>
...

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:

Mandatory?ValueDescription
NotoyToys
NoeducationEdicational games, constructor sets
NonappyDiaper
NofurnitureFurniture
NoschoolSchool supplies
NotransportTransportation devices (strollers, baby car seats, scooters, bicycles, etc.)


Consider the following example of use:

XML example
 ...
<offer ...>
    ...
	<child>
	    <gender>f</gender>
	    <type>toy</type>
	</child>
</offer>
...

Age

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:

Mandatory?AgeValue
No1-3 months0.25
No4-6 months0.5
No7-9 months0.75
No10-12 months1
No13-15 months1.25
No16-18 months1.5
No19-21 months1.75
No22-24 months2
No3 years3
No4 years4
No...etc.


Consider the following example of use:

XML example
 ...
<offer ...>
    ...
	<child>
	    <gender>f</gender>
		<age>
			<min>0.5</min>
			<max>1</max>
		</age>
	</child>
</offer>
...


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:

...
<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:

...
<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.

...
<offer ...>
	...
	<child>
		<gender>f</gender>
		<age>
			<min>1.5</min>
			<max>2</max>
		</age>
	</child>
	<fmcg>
		<periodic>1</periodic>
		<type>food</type>
	</fmcg>
</offer>
...
  • No labels