Recipient share rate: define the event before interpreting the result

Recipient share rate can help a credentialing team understand use of a particular sharing action. It does not, by itself, establish that a credential reached an employer, improved a recipient’s prospects or generated revenue for the issuer.

Before comparing programs, define what your system can actually observe. A click on a sharing control, a completed platform action and a visit from an external destination are different events. Do not give them the same label simply because each is related to sharing.

Define the numerator and denominator

Write the metric as a specific question. For example: “What proportion of eligible credentials had at least one recorded use of the selected sharing action during our review window?”

If that is your definition, calculate:

Credential share-action rate = distinct eligible credentials with a recorded qualifying action / distinct eligible credentials in the cohort × 100.

Count each credential once in this calculation, even if it has several qualifying actions. Keep total action count as a separate measure. If you instead want a recipient-level rate, deduplicate recipients and use eligible recipients as the denominator. A recipient with several credentials should not silently become several people in that report.

The formula is a suggested measurement definition, not a claim that every platform supplies these fields. Confirm the available event meaning and identifiers in your own reporting setup before calculating it.

Choose a cohort and observation window

Specify which issued credentials belong in the cohort, its issue-date range and the amount of follow-up each credential receives. State how tests, withdrawn credentials, replacements and repeated notifications are handled.

Compare cohorts with equivalent follow-up. A recent cohort may have had less opportunity to use its credentials than an older one. There is no universal day at which all recipient behavior stops changing.

Keep unknown tracking coverage visible. If a destination or sharing method is not observed, do not count the missing event as proof that no sharing occurred. Likewise, a recorded share action does not prove that another person viewed the credential.

Use a worked example without turning it into a benchmark

In a hypothetical cohort, 100 eligible credentials have complete coverage for the action being measured. Twenty distinct credentials record that action at least once. Under the definition above, the rate is 20 ÷ 100 × 100 = 20%.

If those credentials produce 35 total recorded actions, the distinct-credential rate remains 20%. The action count is 35. Neither number tells you how many employers saw the credential or how many recipients obtained a job.

This is arithmetic using fictional data. It is not a Sertifier customer result, a recommended target or an industry comparison.

Investigate a change before explaining it

A lower recorded rate can prompt questions, but it cannot identify the cause on its own. Review whether the event definition, instrumentation, cohort eligibility or observation window changed before drawing a behavioral conclusion.

Then inspect the recipient journey. Could recipients open the intended credential? Did the achievement and issuer make sense? Were optional sharing instructions accurate? Did a control or destination fail during a controlled test?

Use the credential email delivery checklist for notification issues and the certificate support guide for recipient reports. Keep a delivery problem separate from a recipient’s choice not to publish an achievement publicly.

Test a specific improvement

Choose one change that addresses an observed problem. You might clarify the access instruction, correct misleading achievement wording or repair a documented broken destination. State the expected effect as a hypothesis before making the change.

For notification copy, use the certificate email templates. Do not promise that a rewritten subject line or redesigned badge will raise sharing. Compare the result under the same measurement definition and note other changes that could affect the comparison.

Use observed data to decide whether to retain, revise or stop the change. A flat result is still useful. A small sample or incomplete tracking may leave the question unresolved.

Report what the metric can support

A useful report names the cohort, action definition, unit of analysis, numerator, denominator, follow-up window, exclusions and tracking limitations. Include the source and observation date so another reviewer can reproduce the calculation.

Report recipient access, recorded share actions, verifier visits and business outcomes separately. Attribute pipeline or revenue only when the relevant records can be connected reliably. Sharing activity alone is not a return-on-investment calculation.

Frequently asked questions

What is a good recipient share rate?

There is no supported universal target in this guide. Use your own consistently measured cohorts and program purpose. Do not diagnose a design failure or low recipient interest from an arbitrary percentage.

Does no recorded share mean the credential was unused?

No. The recipient may use it privately, through an untracked route or at a later date. State the observation as “no qualifying action recorded in this window,” rather than making a claim about motivation or value.

Is a download a share?

A download is a download unless your chosen definition explicitly groups it with other actions. Keep that choice visible. Downloading a file does not establish that it was distributed to someone else.

Start with a clear recipient workflow

Create a Sertifier account to prepare your credential workflow. Review the supported reporting events for your setup and test a controlled sample before treating a dashboard number as evidence of recipient outcomes.