Google Shopping and Variant links

[Hofer]

Hi

On google shopping the requirements state that if listing a variant product the link must go to the page with the variant preselected on the page. Is there a way to do this with Miva? Right now the link is only to the main product and the customer has to figure out that they need to select all the options and find the product again. creating a separate product for every variation is not an option.

Any suggestions?

Thank you

[tguefen]

Hello,

We will be solving this problem when we build a native google shopping integration in 9.0006

We have some code that will allow you to pass through the variant ID in the master product's url, to have the correct choices selected.
https://gist.github.com/tessguefen/a...c8e3#file-prod

Toolbelt will be needed for this.

You can add this at the top of the PROD page.

The links will look like:
www.mystore.com/my-product.html?v=123
If you have the correct variant ID, this will pre-load all the necessary selected attributes/ options for that variant.

To get a list of these, you can create a page template and add this code:
https://gist.github.com/tessguefen/dd3a615ce1562429e8b4

You will also need to assign the product list item, as it will loop through and create a CSV of all the links after it is done going through all products.

[elcucococo]

I am glad Miva is working on a in-house solution to this problem.

If the above fix is not your cup of tea, Kent Multer helped me with this same issue last summer. He developed a module for our store that met the Google Shopping specifications for products with variants. The module has worked flawlessly since then by loading the correct variant via the URL supplied to Google Shopping: http://www.miva.com/forums/forum/onl...ry-variant-url

[Hofer]

Hello,

We will be solving this problem when we build a native google shopping integration in 9.0006

We have some code that will allow you to pass through the variant ID in the master product's url, to have the correct choices selected.
https://gist.github.com/tessguefen/a...c8e3#file-prod

Toolbelt will be needed for this.

You can add this at the top of the PROD page.

The links will look like:
www.mystore.com/my-product.html?v=123
If you have the correct variant ID, this will pre-load all the necessary selected attributes/ options for that variant.

To get a list of these, you can create a page template and add this code:
https://gist.github.com/tessguefen/dd3a615ce1562429e8b4

You will also need to assign the product list item, as it will loop through and create a CSV of all the links after it is done going through all products.

Thank you for this solution. When the page loads will it also load the swatch images and the correct inventory for that variant? I currently use the template data feed, will I then need to manually add the correct link to the export file?

[Hofer]

I am glad Miva is working on a in-house solution to this problem.

If the above fix is not your cup of tea, Kent Multer helped me with this same issue last summer. He developed a module for our store that met the Google Shopping specifications for products with variants. The module has worked flawlessly since then by loading the correct variant via the URL supplied to Google Shopping: http://www.miva.com/forums/forum/onl...ry-variant-url

Hi, I did come across your post yesterday and contacted Kent about it.

Thank you.

[Kent Multer]

Hi folks, sorry to be late to the party; my forum account is still broken.

Yes, I have a module that solves this problem. It works by recognizing a URL parameter on incoming links to product pages, a single number such as ?VS=12345. The module figures out the correct attribute selections from this number, and sets the attributes to match it when the page is displayed. If you have a page design that updates the displayed price, swatch images, etc. to match the attribute selection, the page will display the correct selections.

To get the special links into the search engines, the module stores the URL parameter in a custom field for each product. Your data-feed templates can include this custom field as part of the product URL; and the search engines will provide these links to their users.

If your store uses inventory counts and variants, the store may not allow customers to select attributes for an out-of-stock variant. If a customer arrives at your store with a link that selects an out-of-stock item, the module will display an advisory message. The text of this message is part of the product page template, so you can easily change the wording, font, etc. to your liking.

Anyone who'd like this module for their store is welcome to email me for more details.

Thanks --

[monkeyevil]

Hello,

We will be solving this problem when we build a native google shopping integration in 9.0006

We have some code that will allow you to pass through the variant ID in the master product's url, to have the correct choices selected.
https://gist.github.com/tessguefen/a...c8e3#file-prod

Toolbelt will be needed for this.

You can add this at the top of the PROD page.

The links will look like:
www.mystore.com/my-product.html?v=123
If you have the correct variant ID, this will pre-load all the necessary selected attributes/ options for that variant.

To get a list of these, you can create a page template and add this code:
https://gist.github.com/tessguefen/dd3a615ce1562429e8b4

You will also need to assign the product list item, as it will loop through and create a CSV of all the links after it is done going through all products.

Back from the dead. Any example code for how to pull the variant id in a feed? I can get a list of URLs for each master product, but I'm not sure how to associate each ID with a specific inventory variant product code?

[tguefen]

Hi!

If you are loading in the variant's via Marketing > Feeds, you can utilize this to detect what the variant_id is. This will use `?variant_id=XXXX` instead of ?v=xxx (?variant_id is native)


======

<mvt:do file="g.Module_Library_DB" name="l.settings:record:variant:part_list_count" value="ProductVariantList_Load_Part( l.settings:record:variant:id, l.settings:record:variant:parts_list )" />

<mvt:comment>
|
| Get the last variant_id in `record:variant:parts_list`
|
</mvt:comment>

<mvt:if expr="l.settings:record:variant:part_list_count GT 0">
<mvt:foreach iterator="variant" array="record:variant:parts_list">
<mvt:if expr="l.settings:variant:product_id EQ l.settings:record:id">
<mvt:assign name="l.settings:record:variant:variant_id" value="l.settings:variant:variant_id" />

<mvt:foreachstop />
</mvt:if>
</mvt:foreach>

<mvt:if expr="l.settings:record:variant:variant_id GT 0">
<mvt:assign name="l.settings:record:canonical_uri" value="l.settings:record:canonical_uri $ '?variant_id=' $ l.settings:record:variant:variant_id" />
<mvt:assign name="l.settings:record:google_code" value="l.settings:record:variant:code" />
</mvt:if>
</mvt:if>

[Bruce - PhosphorMedia]

Before using this welcome hack, are their updated NATIVE template code to solve this?

What was the point of 'adding' variants if they weren't added in a way the average cave...i mean store owner could use?

[afiumano]

I am having this problem with Google Merchant Center now as well - Google wants the variant pre-selected - what is best fix for this now?

[Kent Multer]

My module is still available. You can email me to discuss getting a copy for your client.