Title: Duplicate Check Method and cookie
Last modified: June 22, 2018

---

# Duplicate Check Method and cookie

 *  Resolved [newance](https://wordpress.org/support/users/newance/)
 * (@newance)
 * [7 years, 12 months ago](https://wordpress.org/support/topic/duplicate-check-method-and-cookie/)
 * I had the **Duplicate Check Method** set at 24 hours after checking the Cookie
   box then experimentally cleaned the browser cookie and I was able to rate the
   same item multiple times. So is there a way to set it up in a way to prevent 
   this from happening? Thank you.

Viewing 1 replies (of 1 total)

 *  Plugin Author [dpowney](https://wordpress.org/support/users/dpowney/)
 * (@dpowney)
 * [7 years, 11 months ago](https://wordpress.org/support/topic/duplicate-check-method-and-cookie/#post-10450056)
 * Hi newance,
 * In order to be able to identify someone, they need to be authenticated (e.g. 
   logging in). The Pro version ensures logged in users can only rate once.
 * A cookie validation check is used to help prevent duplicate ratings. You’re right
   in that a user can clear their cache and submit multiple ratings. In the past
   the plugin had an IP address validation check (prior to GPDR), but an IP address
   is not reliable either.
 * Thanks,
    Daniel

Viewing 1 replies (of 1 total)

The topic ‘Duplicate Check Method and cookie’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/multi-rating_d6dfe6.svg)
 * [Multi Rating](https://wordpress.org/plugins/multi-rating/)
 * [Support Threads](https://wordpress.org/support/plugin/multi-rating/)
 * [Active Topics](https://wordpress.org/support/plugin/multi-rating/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/multi-rating/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/multi-rating/reviews/)

 * 1 reply
 * 2 participants
 * Last reply from: [dpowney](https://wordpress.org/support/users/dpowney/)
 * Last activity: [7 years, 11 months ago](https://wordpress.org/support/topic/duplicate-check-method-and-cookie/#post-10450056)
 * Status: resolved