• Resolved GrayHunter

    (@grayhunter)


    Hello,
    I am interested in your plugin but have some doubts. My questions may look naive but I want to make the right choice and understand why it’s the right one. Please advise:

    1. It states that your plugin supports product variables, but does it support these cases:
      1.1 My parent products do not have SKUs, only variations themselves. Will your plugin use the variation SKUs (for MPN) or there will be an issue? E.g. the official WooCommerce plugin (“Google Listings and Ads”) does not deal with this, it supports parent/general SKU only.
      1.2 Also, the official plugin does not take the “Brand” global attribute for variations. What about your plugin?
      1.3. Finally, the official plugin shows the same title for every variation (creating separate products for them in Google). This creates a lot of products with different pricing & attributes but with the same titles – not good. I believe some of the attributes (e.g. colour) should be added to the product title in Google (not on the website itself), but can your plugin do this? Or does it offer a better solution?
    2. Regarding the plugin feature which fixes the Woocommerce structured data bug – is this still actual with the new version of WooCommerce? Can your solution effect other plugins which work with the data and/or the design of the website?
    3. Is your plugin fully compatible with the Divi theme and LiteSpeed Cache plugin?
      4.2 Will I be able to display the EAN or MPN data (from the fields created by your plugin) by Divi on a product page? At the moment I display the product SKU on a product page (with products MPNs in the SKU field).
    4. Your plugin will add several product input fields: Brand, GTIN, UPC, MPN, EAN, etc. But what if I already have the “Brand” attribute (created as a global one) – What will happen then, and how should I act in order to avoid any issues with already created products?
      Will I need to copy the value from the “Brand” attribute created by me to the “Brand” field created by your pluging for all my products?
      I currently display the “Brand” attribute data in the product details tab (on a product page) – will I be able to proceed doing this?

    4.2 If there is no way but using the field created by your plugin, what will happen if I deactivate the plugin one day in future?

    1. Does your plugin sync products with Google Merchant Center automatically (like the official plugin does) or I’ll need to manually create & upload to Google a file after any price update?
    2. Anything else I should know before switching from the “Google Listings and Ads” plugin to your plugin? E.g. should I just deactive the official plugin and activate yours or I need to do anything extra? Maybe some clean up (in my admin panel or Google Centre)?
    3. Why I should decide to go with your plugin? Afterall, there are many other options, why yours one is better?
    4. Finally, your plugin add’s pixels and conversion API (CAPI) and Google Dynamic Remarketing pixel to websites. How is that compatible with Google Analytics code I have added to the < header > of my website? Should I delete the Google Analytics code or they can work together?
Viewing 5 replies - 1 through 5 (of 5 total)
  • Hi,

    Thanks for reaching out and showing interest in our plugin. Let me try answering your questions:

    1.1 Yes, our plugin will use the variation SKU’s

    1.2 That depends. I assume that the brand for product variations is the same for all variations and thus you added an attribute holding the brand at the parent variable product?

    1.3 Yes, our plugin dynamically creates unique product titles for the product variations. It adds the attribute values to the parent variable product name. So, for example you’ll get product variation title’s like this: Productname – blue – small, Productname – red – medium, and so on.

    2. This is a feature of our paid Elite plugin version. Unfortunately, per the WordPress forum guidelines, we’re not allowed to discuss our paid Elite plugin here so for any questions about our paid plugins, please contact our support team directly.

    3. Our plugin is getting its data from your WooCommerce attributes. It doesn’t matter what theme’s are being used. Yes, our plugin is compatible with most caching plugins. Bear in mind though that you need to exclude the feed URL’s from being cached in your caching plugin. The extra fields (MPN, EAN, and so on) offered by our plugin are part of our paid Elite plugin and as such we are not allowed to answer that question here.

    4. This is a feature of our paid Elite plugin version. Unfortunately, per the WordPress forum guidelines, we’re not allowed to discuss our paid Elite plugin here so for any questions about our paid plugins, please contact our support team directly.

    5. Our plugin does not have a content API connection with your merchant center. We have done so on purpose as, for many users, this is too technical and causing lots of issues. Our plugin is creating product feeds. This blog post explains how you can connect those to your merchant center: https://adtribes.io/setting-up-your-first-google-shopping-product-feed/

    6. Yes you cannot have our plugin run parallel with the Google Listings and Ads” plugin as that will result in two sources uploading products into your merchant center. It will cause duplicates and disapprovals. So when you will start using our plugin you need to disable the Google Listings and Ads” plugin. We have no experience ourselves with the Google Listings and Ads” plugin so we can’t tell if any clean-up needs to be done in your wp-admin area or merchant center.

    7. I think it goes without saying when you check our reviews. Our plugin has most reviews and the best score’s.

    8. You can leave your GA implementation. The pixels are added next to it.

    Hope this answers your questions? Do not hesitate to reach out to us again when you have more questions.

    Thread Starter GrayHunter

    (@grayhunter)

    Many thanks for the details!

    1.2 Yes, I added an attribute holding the brand at the parent variable product (and it is a global attribute). Please advise.

    2, 3 ,4. I’ll discuss with you directly, thanks.

    5. What issues could I potentially have with a content API connection (comparing to the plugins which have this feature) and what is the difference between a content API connection and creating product feeds?

    1.2 Yes, that can be used for product variations. It basically means that all of your product variations will get the same brand filled in for your parent variable product.

    5. I think the reviews of the Google Listings and Ads perfectly represent the type of issues users are experiencing. In theory a content API connection has one big advantage over feeds. When a product is being added in your WooCommerce store or a change is being made to an existing product those are being pushed to your Google Merchant Center directly whereas with feed implementation (such as ours) Google will only fetch your updated feed only once a day (you can do a manual fetch and processing though).

    Hopefully this answers your questions?

    Thread Starter GrayHunter

    (@grayhunter)

    Yes, thank you for the great support!

    I’ve emailed you my 2, 3 ,4 questions and hope to get answers not slower than on the forum, please 🙂

    Please mark the topic as resolved.

    Assuming the issue at hand has been resolved and our support is no longer required I will close this topic for housekeeping reasons now.

    Do not hesitate to reach out to us again in-case you need our help again.

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘Pre-sale questions’ is closed to new replies.