Support Center

Frequently asked questions and support documentation for RatingWidget.

  • >
  • Features & Functionality

Results

  • How is RatingWidget for Shopify different from Yotpo?

    Bottom line – we help to bring new potential customers to the store while Yotpo helps to close the deal by showing previous clients reviews (if positive). How we do that? We help the store to use the wisdom of the crowd, and collect an instant feedback using straight forward 5 star rating. Then, by leveraging the Rich-Snippets Premium feature, the ratings intelligently embedded into Google’s SERP to increase the CTR by up to 30%. More traffic = more sales!

  • I’ve followed all the Rich-Snippets instructions but I don’t see any ratings on Google search results – what’s wrong?

    The first thing you should do is to make sure that you’ve configured the ratings’ rich-snippets correctly. Go back to the this topic and follow the instructions. Once the configuration is right, usually it takes about two weeks until Google will add the Rich-Snippets ratings. It’s really varies according your store’s content quality, crawling frequency, pagerank and many other parameters. Even though we have many clients that the ratings appeared on their SERP, we can’t assure that Google will eventually add the ratings’ rich-snippets. Unfortunately we don’t have an access to their algorithms.

  • When someone voted a rating, can he ever vote it again?

    By default, every visitor can rate each rating ONCE. This voting frequency is configurable and could be changed to:

    UNLIMITED: Visitor can contribute as many votes as he likes.

    DAILY: Visitor can rate once in every 24 hours.

    WEEKLY: Visitor can rate only once in every 7 days.

    MONTHLY: Visitor can rate once in every 30 days.

    YEARLY: Visitor can rate once in every 365 days.

    You can read more about the frequency configuration in our documentation.

  • How do you identify the visitor / voter?

    In order to prevent from multiple votes from the same visitor (check out the topic about voting frequency here), our default identification technique is cookies. We leverage both regular HTTP cookie and LSO (Local shared object a.k.a  Flash Cookie) to uniquely mark the visitor’s device. As you probably figured out, it’s very simple to clean your cookies or use incognito mode, to actually make more than one vote from the same device. Thus, if fraud votes is a critical issue for you, our premium product support additional identification methods:

    1. By IP: These visitor identification method means that by default only one vote can be contributed from the IP. The advantage of this method is that it’s much harder to change IPs than cookies (requires some hacking skills but possible using proxies, etc.). The disadvantage is that different visitors who are using the same NAT (E.g. same router device), won’t be able to vote more than once.
    2. By Login: We provide a very useful JavaScript callback called beforeRate, you can use it to force a login to your site before being able to rate. Note: These method is also not 100% safe and could be hacked.
    3. By Social Login: Before a visitor can rate, he is required to connect his social identify with RatingWidget (currently we’ve implemented Facebook Connect). We believe this is the most safe identification method for many reasons. The main one is that in order to make fraud/fake vote – it requires a new social identity (creating of social identity takes time, requires unique email, etc.). The disadvantage of this method is that it significantly reduces the number of votes (some people don’t like to connect their social identity with external services).
  • Do you have a refresh code for Ajax loaded content?

    In order to refresh / re-render the ratings on the page all you need to do is execute the following JavaScript line.

    RW.render(null, true);

    You can add the following code snippet right before your closing </body> tag (requires jQuery support) and it will automatically do the job.

    <script type="text/javascript">
        (function($){
            $(document).ajaxSuccess(function() {
                setTimeout(function(){
                    if ("undefined" !== typeof(RW))
                        RW.render(null, true);
                }, 500);
            });
        })(jQuery);
    </script>

    If you care about efficiency, call this method only after you add new ratings’ HTML containers (not on every Ajax call).

    Using the WordPress Plugin?

    To add the snippet right in your WordPress’ footer, add the following code to your theme’s functions.php file:

        /* Append ratings render-er after ajax call.
        ------------------------------------------*/
        function rw_render_ratings_after_ajax()
        {
    ?>
    <script type="text/javascript">
        (function($){
            $(document).ajaxSuccess(function() {
                setTimeout(function(){
                    if ("undefined" !== typeof(RW))
                        RW.render(null, true);
                }, 500);
            });
        })(jQuery);
    </script>
    <?php        
        }
    
        add_action('wp_footer', 'rw_render_ratings_after_ajax');