WordPress Integration
WordPress courses can issue TRUE certificates when a student finishes
WordPress on its own does not run courses; the LMS plugin on top of it does. That is the good news, because those plugins are where the completion event lives, and several of them can already call an external system when a student finishes. We connect TRUE to whichever one you run, and the certificate issues on your own domain.
TL;DR
The first question is always which LMS plugin you use, because that decides the route. Several of the widely used ones can already send a completion to an external system, either through their own webhook support or through their REST endpoints. Where a plugin cannot, TRUE reads completions through the WordPress REST API instead. Either way the certificate is issued against your design, sits on your own domain, and is written to blockchain at the moment of issue.
- The plugin is the source, not WordPress. Which LMS plugin you run decides how the connection is made.
- Several plugins already do this. The common ones can call an external system on completion without anything custom.
- A fallback that always works. Where a plugin cannot call out, TRUE reads completions through the WordPress REST API.
How does the WordPress certificate integration work?
Your LMS plugin knows when a student has finished. The connection takes that moment and hands it to TRUE, which issues the certificate against your design and delivers it. What differs between WordPress sites is only how the plugin lets that moment out.
1
Tell us which LMS plugin you run
This is the whole question. Several of the widely used plugins can call an external system on course completion, and knowing which one you have decides the rest in one step.
2
Connect the completion event
Either the plugin's own outgoing call, pointed at TRUE, or TRUE reading completions through the WordPress REST API where the plugin has no outgoing call of its own.
3
Certificates issue themselves
Once it is running, a completion produces a branded, blockchain secured certificate with a permanent verification link.
What does the certificate carry?
The student name, the course, your organisation and the date it was issued, written to blockchain at the moment of issue so it cannot be edited or backdated afterwards.
- Student name and course. Read from your LMS plugin's own completion record, so it matches the course as your site shows it.
- Your organisation. The certificate is branded as yours and lives on your own domain.
- Date of issue, fixed. Written to blockchain at issuance, which is what makes backdating impossible.
- A permanent verification link. An employer confirms it by opening the link or scanning the QR code, without contacting you.
What has to be in place before it can be switched on?
An LMS plugin that runs your courses, access to the site, and a certificate design. If you are not sure which plugin you use, that is the first thing we work out together.
- The LMS plugin you run, because that decides the route.
- Access to the WordPress site, or to whoever maintains it for you.
- A certificate design, built by us to your profile or adapted by you from an existing template.
What does a student receive?
A branded, animated certificate delivered by email, on your own domain rather than ours. It carries a QR code and a permanent verification URL, so anyone can confirm it without contacting you, and it goes onto a LinkedIn profile in one click.
- Beautifully designed. Animated, branded and interactive rather than a static PDF.
- A shareable link. One URL that works in an email signature, a portfolio or a CV.
- QR code verification. An employer, a client or a regulator confirms the credential instantly.
- LinkedIn ready. Added to a profile in one click, which puts your name in front of their network.
- Blockchain secured. It cannot be edited, forged or backdated after issue.
How is student data handled?
The connection passes the student name, email address and the course details, which is what a certificate needs to exist. Because it is your site, the access we are given is scoped by you and can be withdrawn by you.
TRUE is hosted in the EU, and we sign a data processing agreement with you before anything is switched on.
How much has TRUE issued for organisations like yours?
More than 500,000 documents for over 200 organisations in 15 or more countries, and credentials shared by their recipients have produced over 100 million marketing impressions. These are TRUE platform figures, not third party research.
500K+ Documents issued
200+ Organisations
15+ Countries
100M+ Marketing impressions
Is the plugin's own certificate enough?
Most LMS plugins can produce a certificate, and as something for the student to keep, it is fine. What it cannot do is let a stranger check it without asking you.
| Capability | The plugin's own certificate | The plugin with TRUE connected |
|---|---|---|
| Proof outside your organisation | The reader has to take it on trust | A permanent verification link anyone can open |
| Tamper proof | No | Yes, written to blockchain at issue |
| Lives on your domain | No | Yes, branded on your own domain |
| LinkedIn shareable | A file to attach | One click add to LinkedIn |
| Effort per learner | Manual handling for anything formal | None once the connection is running |
| If you change plugin | The certificates go with the plugin | Already issued credentials stay live and verifiable |
| Analytics | None | Views, shares and verifications tracked |
What do WordPress site owners ask about this?
Mostly which plugins are supported, whether it slows the site down and what happens if they change plugin. The common ones, no, and the certificates stay.
Which LMS plugins does this work with?
The route depends on the plugin, and the widely used ones can already call an external system on completion. Tell us which one you run and we will tell you exactly how the connection is made.
What if our plugin cannot call out?
Then TRUE reads completions through the WordPress REST API instead. It is the fallback that works regardless of the plugin.
Does it slow the site down?
No. The certificate is issued on our side, so nothing extra is rendered on your pages and nothing is added to the page load.
What happens if we change LMS plugin later?
The certificates already issued stay live and verifiable, because they live on your own domain rather than inside the plugin. The connection is remade against the new plugin.
Do participants need a TRUE account?
No. The certificate arrives by email with a unique link. No login, no account and no app.
Can the certificate carry our own design?
Yes. We build the design to your graphic profile, or you adapt one from an existing template. The certificate is branded as yours and lives on your own domain.
Can we issue certificates for courses that already finished?
Yes. Earlier completions can be issued as a batch, so a backlog does not have to be handled by hand.
What does a recipient do with the certificate?
Share it. It is a link rather than a file, so it goes on a LinkedIn profile in one click and into an email signature or CV, and every share points back to a verification page carrying your name.
Ready to connect your site?
Tell us which LMS plugin you run and we will tell you the route, what it takes and how quickly the first certificate can go out.