We extract some information from your Google Product Feed and put it into the resulting content in Sailthru as tags and vars. We can get tags and vars in a variety of ways, listed below.

How Product Feed attributes are mapped to tags and vars

We do some pre-processing on the information we extract from the Google Product Feed to map some of the attributes to tags and/or vars within Sailthru automatically.

For every product, a var is created on the Sailthru content called  variants, which stores some of the attribute information from the product feed.  This data type is an array to support duplicate URLs/variants in the product feed and ensure duplicated content isn’t loaded into Sailthru (see Duplicate URLs). You can obtain the first item in the variants array in Zephyr as follows {variant = first(content.vars.variants)}.

{variant = first(content.vars.variants)}
{variant.custom_product_category}

By default, we’ll extract the following fields if they’re present and map these to tags and/or vars on the Sailthru Content.

Google Product Feed Field	Value in Google Product Feed	Resulting Sailthru content tags	Resulting Sailthru content vars
google_product_category	Clothing & Accessories > Clothing > Dresses	clothing-and-accessories-clothing-dresses, clothing-and-accessories, clothing, dresses	google_product_category: "Clothing & Accessories > Clothing > Dresses"google_product_categories: ["Clothing & Accessories", "Clothing", "Dresses"]
product_type	Dresses > Maxi Dresses	dresses, maxi-dresses	product_type: "Dresses > Maxi Dresses" product_types: ["dresses", "maxi_dresses"]
condition	New	new	variant.condition: "New"
color	Red	red	variant.color: "Red"
size	Large	large	variant.size: "Large"
pattern	Stripes	stripes	variant.pattern: "Stripes"
gender	Unisex	unisex	variant.gender: "Unisex"
age_group	kids	kids	Variant.age_group: "kids"
brand	Sailthru	sailthru	variant.brand: "Sailthru"
availability	in stock	N/A	variant.availability: "in stock"
price	15.00 USD	N/A	variant.price: "15.00 USD"
sale_price	10.00 USD	N/A	variant.sale_price: "10.00 USD"
sale_price_effective_date	2016-02-24T11:07:31​+0100 / 2016-02-29T23:07:31​+0100	N/A	variant.sale_price_effective_from: "2016-02-24T11:07:31​+0100" variant.sale_price_effective_to: "2016-02-29T23:07:31​+0100"
sailthru_tags	this,that,the-other	this, that, the-other	N/A

Group all products in a feed with Feed-level Tags

On the New Source page in Product Sync, there’s a field called Tags for this source, highlighted in the following image:

Tags in the Tags for this source field will be applied to each item imported from this source. In the instance above, all products imported from the Google Product Feed will have the tags this, that and the-other in all of the resulting content items.

This can be very useful when you want to distinguish between content imported Product Sync and content from other sources, or if you want to know which source a content item came from.

For example, let’s say you have different Google Product Feeds for US products and New Zealand products. You could give the US feed a us tag and the New Zealand feed an nz tag – this would make it easier to only recommend NZ Products to New Zealanders, and only recommend US Products to Americans.

Pull additional tags from your webpages with Web Tags

When Web Tagging is enabled for a Google Product Feed, we’ll collect additional content tags from each product’s page on your website.

There must be a <meta> tag with a name either sailthru.tags or keywords, with comma-separated tags in a content field for us to collect tags from the product’s page, as described here. Note that when Web Tags is enabled, we will only collect tags, and no other metadata.

For example:

• <meta name="sailthru.tags" content="red,triangular,soft"> will result in a content item with tags including red, triangular and soft
• <meta name="keywords" content="blue,square,hard"> will result in a content item with tags including blue, square and hard

By default, when we’re collecting web tags, we’ll query your website at a maximum rate of 2 requests per second. If this seems like too much or too little for your use case, please don’t hesitate to get in touch with our support team, and we’ll do our best to help out.