Integrity Analytics analyzes completed quiz attempts for statistically unusual patterns and flags the ones worth a second look. Two rules define the feature and never bend: flags never change a score (they only direct attention to attempts a person should review), and no IP addresses are ever collected, anywhere, for any reason.
The Four Detectors
Timing Anomaly
Flags attempts where a large share of questions were answered correctly in a small fraction of the expected time. The expected time comes from the question’s own expected-seconds value when set, or from how long other students typically spend on that question once enough attempts exist to form a baseline.
Answer Similarity
Compares pairs of completed attempts on the same quiz, looking for agreement on uncommon wrong answers. Two students choosing the same rarely-selected wrong option, repeatedly, is a much stronger signal than matching correct answers, which count only minimally. The signal is boosted when the two attempts overlapped in time or shared a device. This comparison is the most computationally expensive detector, so it runs in the background in batches rather than at submission.
Shared Device
Flags attempts when the same device appears across two or more different user accounts on the same quiz within a 30-day window. The flag details list the related attempts.
Concurrent Session
Flags a user with overlapping quiz attempts running at the same time, or an attempt where the device changed between start and submission.
Flags Are Leads, Not Verdicts
Every detector has innocent explanations, and the review screens say so alongside the evidence. A class that was taught the same misconception will pick the same wrong answer without any collusion, which is exactly why the similarity detector weighs uncommon wrong answers rather than popular ones. A legitimate device change, or an attempt paused on one device and resumed on another, can look like a concurrent-session signal. Flags exist to tell you where to look; the judgment is always yours.
Enabling Integrity Analytics
Integrity Analytics is off by default. To enable it:
- Navigate to PressPrimer Quiz > Settings > Proctoring.
- In the Integrity Analytics section, turn on Enable Integrity Analysis.
- Optionally adjust the Retention Period (default 365 days).
Individual quizzes can override the site setting. In the quiz editor’s Premium Settings tab, the Integrity Analysis option can follow the site default, or force analysis on or off for that quiz, with the same semantics as the per-quiz proctoring overrides.
What Is Captured and Analyzed
On quizzes where integrity analysis is active, the plugin records a random device token and basic browser information at attempt start and submission. The token is a first-party identifier minted by the plugin itself; it is not an IP address, and no network identity of any kind is collected. If a browser blocks storage and no token is available, the attempt simply records without one; it is never an error.
Detectors analyze attempts completed after the feature is enabled. Answer similarity is the exception: it also reviews a quiz’s existing completed attempts in the background, so long-running quizzes get coverage of their history.
The Integrity Review Page
Open flags across your quizzes are reviewed from PressPrimer Quiz > Reports > Integrity Review. The queue can be filtered by quiz, detector, and severity. Each flag carries a severity (Info, Review, or High), a plain-language evidence summary, and the false-positive context described above.
From the queue, or from the Integrity panel on an attempt’s detail view, reviewers can:
- Acknowledge a flag, marking it reviewed and worth remembering, with an optional note
- Dismiss a flag as explained or not concerning, with an optional note
- Dismiss All, which dismisses every open flag matching the current filters (this cannot be undone in bulk)
- Recompute similarity for a quiz on demand, rather than waiting for the background schedule
Acknowledge and dismiss actions are recorded in the audit log, including the note. Access follows the same rules as other reports: teachers, and LearnDash Group Leaders in LearnDash Groups Mode, see only the attempts from their own groups, while administrators see everything.
Data Handling
- Retention: The daily cleanup removes device records and resolved flags older than the retention period. Open flags are never deleted automatically; they wait for review.
- Guest erasure: When guest data is erased through the WordPress privacy tools, the integrity records for those attempts are erased with it.
- Progress resets: Resets from the free plugin’s Data Tools remove the integrity records for the deleted attempts, and the reset preview shows the counts.
- Turning it off: Disabling the feature stops capture immediately. Existing records continue to age out under the retention setting.
For live monitoring during an attempt (tab switching and fullscreen enforcement), see Quiz Proctoring. The two features complement each other: proctoring watches attempts as they happen, while Integrity Analytics studies the patterns afterward.