Glossary
What Is Certificate Journey?
In Verifycate, the certificate journey is the tracked path of one certificate from how its recipient arrived, through release and delivery, to whether anyone ever opened, downloaded or verified it.
Also called: certificate funnel, issuance analytics, engagement
What it's for
Issuing three hundred certificates is the easy part. Knowing what happened to them is where most programs go dark: 300 sent, some opened, a few shared, and nobody can say which. The usual spreadsheet has one column — "sent: yes" — and no way to answer the only question that matters, which is whether anyone ever did anything with the certificate.
The certificate journey is that story, tracked end to end per certificate: how each recipient arrived, what stood between them and their certificate, whether it was delivered, and what they did with it afterwards.
How it works
The journey has four stages, and each one is measured:
- Arrival. Where the recipient came from: file import, API, manual entry, or their own initiative through a request form. A cohort that fills itself through requests reads very differently from one you imported by hand — and the split is visible.
- Release. How the certificate reached their hands: directly on issue, or gated behind an unlock form. Gate conversion — how many people complete the form to get the certificate — is the number most issuers have never seen.
- Delivery. Whether the email landed: sent, delivered, bounced, or blocked — with provider-level outcomes per recipient, so a "we sent them their certificate" claim can be checked against reality.
- Engagement. What happened next: email opened, certificate opened, downloaded, added to LinkedIn, shared, verification details viewed. Each recipient's depth is one progression — not engaged, to opened, to viewed, to downloaded, to shared.
Beyond the issuer's own numbers, the certificate's public page has a reach of its own: who visited, from where — delivery email, QR code scans, LinkedIn, WhatsApp, search — and how many came back.
Journey analytics are per certificate and per workspace: one certificate's funnel on its own page, the aggregate on the dashboard. The point isn't dashboards for their own sake — it's that every stage maps to a lever. Low gate completion means the form is too long. Delivery failures mean a list problem, not a design problem. Zero verification views on a batch means the QR never got seen — a template change fixes that; another email blast doesn't.
Everything on this page runs in Verifycate. The first 300 certificates are free, no card. Start for free
Common questions
- Is this just email open tracking?
- No — email opens are one stage of four. The journey runs from how the recipient arrived through delivery to what they did with the certificate itself, including whether anyone viewed its verification details.
- Can I see the journey for a single recipient?
- Yes. Each recipient carries their own progression — opened, viewed, downloaded, shared — alongside their status, so a specific person's story is one search away, not a support investigation.
- What are traffic sources on a certificate's public page?
- Where verifiers and visitors came from: the delivery email, QR code scans, social platforms like LinkedIn and WhatsApp, copied links, or organic search. It tells you whether the certificate travels after delivery or sits in an inbox.
- Does tracking the journey cost credits?
- No. Analytics are part of the workspace; the credit meter only reads at issue time.
Related terms
- Certificate RecipientIn Verifycate, a certificate recipient is one person on a certificate's list — the record carrying their name, contact details, attribute values and status from import through issue to verification.
- Certificate Unlock FormIn Verifycate, a certificate unlock form is a form a recipient must complete before their certificate is released — a survey, feedback or a testimonial — sent to each recipient as a private link.
- Certificate VerificationCertificate verification is confirming that a certificate was really issued by the organisation it names, to the person it names, and hasn't been altered since.
- QR Code VerificationQR code verification puts a scannable code on the certificate itself, so anyone holding a copy — printed or digital — can reach the issuer's own record of it in one scan.
See what actually happens after you hit issue.
Arrival, release, delivery and engagement, tracked per certificate. Issue your first 300 free, no card.
“We issued 2,000+ certificates for InCTF — winners, participants, the lot.” — Aravind BL, Amrita InCTF
Start for free