How to fill the “Prefix field”?

Hi David

The prefix is only necessary if you use the Google Feed plugin marketed by woocommerce.com

Most (if not all) other feed plugins don’t use a prefix.

I checked one product on your shop: https://tokyoto-luggage.es/product/maleta-de-mano-white-soldier/

It does contain the script that is generated by our plugin: https://take.ms/dMBfP

It transmits the product ID “19031” for this product to Google. Does it match your product ID in your Google Merchant Center? If yes, that part of the setup is fine.

The other part of the setup of a successful dynamic remarketing campaign is entirely in Google Ads. There are several guides by Google that explain how to do it. We might also create one in the near future.

But unfortunately doesn’t preform well, the products displayed on the Ads Are not dynamic at all. Thy are always the same.

If the first part of the setup works fine, the problem is in your Google Ads setup.

Does this help?

Thank you, I fixed the Product ID discrepancy between Merchant and my site.

However there is an error message: “100% of ecomm_prodid values received don’t match your feed”and the Google Tag assistant says that the “ecomm_pagetype” is pointing to “home” and not to the “Product”.

So, what am I missing here? Google asked me that only this code could fix it:

<script>
gtag(‘event’,’view_item’, {
‘value’: 998.55,
‘items’: [
{
‘id’: 1234,
‘google_business_vertical’: ‘retail’
}]
});
</script>

Awaiting for some light on this,

Kind regards
David.

TOKYOTO LUGGAGE

The code Google provided to you is the new code they specified recently.

The one that is in the current plugin works with the old specification which still works fine. There is a period during which the old and the new code will work in parallel in order to phase out the old one. This is normal in software development.

The report for matching products usually doesn’t report the most recent date, but lags one or two days behind. So you have to wait.

We already are testing the new Google code with some accounts and it looks to be working fine (meaning the retail audiences update fine). But there is a problem with the reporting. Neither Google Tag Assistant nor the Google Ads internal reports reflect that the new specified code works 100% correctly. That could be because the code is buggy, or it could be that the Google Tag Assistant and the Google Ads reports have not been updated to the new specification and therefore are not reporting the correct state. Knowing that Google has always been slow in updating their Google Tag Assistant and reports in Google Ads, I think the problem is the latter.

Because of that reporting problem I am currently hesitant to publish the new tag code to the public, because there is a risk that many advertisers will run into the reporting issues I mentioned and therefore will think that the tag doesn’t work (but in fact is working fine).

I can provide you our beta version of the plugin which implements the new tag specification if you want to test it. In that case please send us an email to [email protected]

• This reply was modified 4 years, 7 months ago by alekv.

Thank you your quick response Alekv,

The G-Ads Audience Tag source, still shows this legend: “94% of ecomm_prodid values received don’t match your feed”.

I understand from your words I must still wait, correct?

Good news is that the Google Tag Assistant already shows Ecomm_pagetype pointing to “Product”, so one less problem.

I understand from your words I must still wait, correct?

Yes

Good news is that the Google Tag Assistant already shows Ecomm_pagetype pointing to “Product”, so one less problem.

Thats great

Sorry to bother you again Mr. Alekv,

I am totally stucked.

Suddenly the Google Tag assistant shows Ecomm_pagetype pointing to “Home”. Any idea why it might happen?

I am insisting to Google, they say the tag “AW-xxxxxxxxx” is not in the head. But I cannot put it on the HEAD because it depends on your plugin ??

Thanks for your time.

Kind regards
David.

Hi David

It doesn’t matter if the code is in the header or the footer. It is only recommended to be installed in the header, but it will work nonetheless.

Unfortunately the Google Tag Assistant has stopped showing proper results when verifying the products. That’s probably since more than a year. So we can’t rely on that and makes debugging more difficult.

We have many accounts that work just fine with the setup you have, so I am not sure where the problem is.

There are a number of paths we can take. Best would be the following two:

1. You install our new plugin version which has implemented the new tag specification. It is still in beta, but should work fine.

2. You give us access to your accounts and we try to debug further.

For both paths it is best you contact us under [email protected]