Pulling Product Attribute and mapping to g:id

  • Resolved kandap

    (@kandap)


    7 years, 1 month ago

    Update- I figured out it’s the underscore in feed_sku that is the problem. When I name the product attribute as feedsku, it works fine. Will you be adding special characters to the acceptable input (or if not then make sure the instructions say not to use them when naming product attributes to go into the feed)?

    Hi Joris-

    I like the new implementation on the category and product mapping! I haven’t finished up yet but so far so good.

    I am having a different issue. We previously mapped the attribute g:id to our store product SKU. We have a need in some cases to use a custom SKU so we created a product attribute for each product and named it feed_sku . We also use product attributes for brand and upc which map successfully to g:brand, g:gtin and g:mpn. The attribute mapping of g:id to feed_sku (Product attribute) is not working. It leaves it blank. If I go back to SKU, it populates fine. Like I mentioned, the product attributes for brand and mpn work fine. And the feed_sku is available in the pulldown menu of choices for attribute mapping. Is there something special about what g:id can and cannot map to?

    Thanks,
    Karen

    • This topic was modified 7 years, 1 month ago by kandap.
Viewing 6 replies - 1 through 6 (of 6 total)
  • Thread Starter kandap

    (@kandap)

    Ok, we have changed feed_sku to feedsku and the feed now properly populates g:id with feedsku. We also have g:item_group_id mapped to Product Id. The filter to exclude products is no longer working correctly since we changed from when we had g:id populated with SKU. No matter what field I choose under the IF column to identify which product to exclude, it is leaving this placeholder in the feed:
    <item>
    <g:google_product_category/>
    </item>
    How can I remove those?

    Hi Karen,

    It is kind of hard to follow how exactly your feed is configured now with all of the above changes you made. Can you generate the debug.log again for me so I can have a look?

    Thx,
    Joris

    Thread Starter kandap

    (@kandap)

    Good point! I meant to do that and forgot.:-) I have sent the link to the support email along with some screenshots of configs.

    Thanks!
    Karen

    Hi Karen,

    I had a look and think I know what is going on. You have mapped your pa_feedsku attribute to Google’s g:id. In the filter section you than try to filter on a product ID attribute. The problem is, as you did not map any field to your product ID you also cannot filter on it.

    What I would suggest doing (always) is map the g:id field to your product ID and than the filters should work. The pa_feedsku attribute should than be mapped to one of Google’s unique identifiers (such as the MPN field).

    Something like this should work:
    https://www.dropbox.com/s/del49uubqqv2die/attribute-mapping-karen.png?dl=0

    Let me know if this worked out for you.

    Have a great evening,
    Joris

    Thread Starter kandap

    (@kandap)

    Hi-

    Google suggests mapping g:id to SKU where possible. https://support.google.com/merchants/answer/7052112
    Our PPC team likes to use SKU rather than mapping g:id to the product ID because SKU is descriptive and keyword rich.

    Sometimes in our industry, Google will disapprove a product and our Google support tells us that in certain cases the only way to get around it is to create a new sku. That’s why we need feedsku. It’s easier than changing the actual sku of the product in the backend of store.

    I can change g:mpn to map to Product ID instead of UPC. Then I can filter on Product ID to remove products.

    Net, if I use g:id mapped to feedsku and g:mpn to product ID, will it work?

    Thanks,
    Karen

    Assuming the issue at hand has been solved. If not please reach out.

    Have a wonderful Easter-weekend.

    All the best,
    Joris

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Pulling Product Attribute and mapping to g:id’ is closed to new replies.