See where certificate page visitors come from
Public certificate pages now report views, unique and returning visitors, and the sources that brought people to the page.
A certificate page is a public surface. It is opened by the recipient, shared to LinkedIn, scanned from a printed certificate, and forwarded to an employer. Until now, the team could see that a certificate was viewed but not where the viewer came from.
Public reach analytics changes that.
What it shows
Page views, unique visitors, returning visitors, and the sources that referred them. The certificate page's own verification loop is part of the picture: a viewer who arrives from a LinkedIn post, a WhatsApp link, or a QR scan is a different kind of proof than a recipient opening their own portal.
Open the certificate's Analytics tab and choose the public reach view. The workspace dashboard rolls it up across certificates.
Where it is useful
A sponsor wants to know that the certificate page was seen, not just that the logo was printed. A training provider wants to know whether graduates share their certificates. An event team wants to see whether the QR code on a printed award is actually used.
The boundary
These are page-level signals, not identity claims. Verifycate does not know who the visitor is unless they take an action that identifies them. Treat the numbers as a measure of reach, not a list of people.
Related