Plugin Directory

Test out the new Plugin Directory and let us know what you think.

Credly Custom Badge Assertion Shortcode

Easily create an official Credly Badge Assertion page on your site.

For Credly Pro members: Easily creates a page on your site for displaying official Credly Badge Assertions. Just add the shortcode to any page or post.

The page will then dynamically embed the official badge information for any of your issued Credly badges, when a visitor is redirected to your site from a recipient's shared badge.

This shortcode provides WordPress support for the Credly "Custom Assertion Location" feature, available to Pro members in their Credly "Account Settings."

What is Custom Assertion?

The Custom Assertion Location feature allows Credly Pro and Premium members to redirect accepted badges they issue to their own website. This means that badges shown on a user’s Credly profile or that they share on social networks will redirect when clicked to the website URL the issuer provides, instead of to Credly. In this manner, issuers can enjoy several benefits, such as:

  • Extra Validity: The validity and authenticity of the credit is reinforced, as the badge assertion is displayed on your domain.
  • Enhanced Branding: White label the badge assertion page by placing it on your site.
  • Additional Context: Customize where and how you display credit on your site, offering additional information about your programs and offerings, enrollment opportunities, or other information for observers when they click through to learn about earned badges.
  • Your Analytics: With badges redirected to your site, you can leverage your own web site analytics to track traffic directly to your site from badges you issue.

What does a Custom Assertion Location look like in action?

First let’s look at the default behavior when an accepted badge is clicked. Without a Custom Assertion Location activated, badges link to the standard Credly assertion page. Here is an example: https://credly.com/credit/10318

When a Custom Assertion Location is in place, click-throughs from accepted badges that you have issued are redirected to the website you specify in your Account Settings. Credly appends the ID number of the badge to the URL you provide in your Account Settings. Here is an example of a Custom Assertion Location, whereby a badge is redirected to a non-Credly website: http://aaslhcommunity.org/cert/?ID=26312

How does it work?

It's very easy. Essentially, all you do is place a shortcode on any page on your WordPress site. Here are the details:

  1. Put the shortcode on any page or post on your site: [credly_assertion_page]

  2. Copy the permalink of the page you used and append "/?CID={id}" to the end of it. For example, if the link to your page is http://www.yoursiteurl.com/certificate, your link format would be: http://www.yoursiteurl.com/certificate?CID={id}

  3. Paste the full link into the "Custom Assertion Location" field in the Account Settings area of your Credly Pro account. Save your Account Settings.

That's it! All of your Credly badges will be re-routed to your designated WordPress page and will display the official badge information automatically. You don't need to do anything else.


This shortcode is already available in the BadgeOS plugin. So if you already have BadgeOS activated, you do not need this standalone plugin.

Note: Custom Assertion Location requires a Pro or higher level membership to Credly.

Resources / Helpful Links

Learn more about how Custom Assertion Location works: Background on Custom Assertion Location

This plugin is made available by Credly, LLC. Here are some ways to stay connected and to see what else we are up to:

License Info

Credly, LLC licenses this plugin to you under the terms of the GNU Affero General Public License, version 3, as published by the Free Software Foundation.

There is NO WARRANTY for this software, express or implied, including the implied warranties of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Affero General Public License, version 3, at http://www.gnu.org/licenses/agpl-3.0.html for more details.

Requires: 3.5 or higher
Compatible up to: 3.7.0
Last Updated: 8 months ago
Active Installs: 30+


1 out of 5 stars


Got something to say? Need help?


Not enough data

0 people say it works.
0 people say it's broken.