Vote certification is a M/IC feature used to manage and approve important votes that require an audit trail. Certification provides granular visibility of voting behaviour and patterns in order to provide greater control and compliance around sensitive audience voting.
Certification supports incoming votes from M/IC Apps (e.g. via a Vote Element), from Facebook Live Questions & Twitter Hashtags and from other sources such as Twilio, WhatsApp or Facebook Messenger.
Threat detection algorithm highlights suspicious voting patterns
Approve or Rejection workflow
Exclude suspicious voting groups
See how many votes per option came from specific IPs
Export CSV Reports of all votes
To enable certification, go to Project Settings and select the Certification tab. Edit the settings and enable the check box. The Certification tab will then appear in the main menu
Certification on an element level can only be enabled if it's enabled on the project level.
Certification for a specific element can be enabled via element settings as per screenshot below. This must be done before publishing as this setting can not be changed after element is published.
There is also extra configuration for the certification control in the Elements spec.
If certification is disabled on the project level before element is published then element is published with certification switched off.
If certification is disabled on the project level while element with certification enabled is active then certification data collection continues until the end of the element. By re-enabling certification on the project level one can still get access to this element's certification data within Studio
Threat level must be taken as a guide only as different projects might require different interpretation of certain voting patterns.
There are two factors we currently use when calculating threat level:
Quantity - the formula is less sensitive at the lower numbers of votes.
Deviation - this factor assesses whether someone is trying to rig the vote in favour of a particular answer option. It's derived from the difference of number of votes received for the top option and the runner up option.
Below is an example of how the threat estimation works out for specific scenarios. First three columns set a number of votes per each answer option:
Please note that if a user is allowed to cast more than one vote per option or vote for more than one option then the number of answers is used instead of the number of votes. For example when user answers in a poll and casts 2 votes for one option and 1 vote for another option we consider this as a single vote for the "Quantity" factor.